get answers to your questions about the craft framework
# CRAFT Help Center
FAQ, Knowledge Base, and Support/Ticket Submission
FAQ
Find answers to common questions about CRAFT Framework. Can’t find what you’re looking for?
→ Visit the CRAFT FAQ
Knowledge Base
Find answers in our Knowledge Base with access about CRAFT Framework. Can’t find what you’re looking for?
→ Visit the CRAFT Knowledge Base
Support
Contact us for help and support with anything related to CRAFT.
What Makes CRAFT Different?
Methodology Over Capability
Most AI tools sell capability — what they can do. CRAFT sells discipline — what you can do reliably. The features Anthropic ships in Claude Cowork are remarkable; they’re also primitives. CRAFT is the opinionated convention for composing those primitives so the work compounds instead of evaporating. The moat that survives platform convergence is not a feature list. It’s a way of working.
Production-Systems Thinking
Recipes are versioned. Confidence gates fire on every recommendation. Write-only backups precede destructive operations. Multi-persona validation replaces solo-review blind spots. No feature ships without documentation. Every override on a default gets logged. This is the same discipline that separates playbook-driven incident response from ad-hoc firefighting — applied to AI workflows.
Privacy by Architecture
Most complex AI tools ask you to trust them with your data. CRAFT takes a different approach: your prompts, recipes, and workflows stay in your own files, on your own machine, inside your own Claude Cowork session. We don’t store them. We don’t train on them. We don’t see them. When you control the infrastructure, every prompt is safer by default — and you can use Claude on the work that actually matters: client strategies, proprietary processes, sensitive research.
Built for Production Workflows
CRAFT is built for people whose Claude work is production, not experimentation:
- Operations and revenue analysts whose recurring deliverables — board decks, weekly dashboards, monthly narratives — the rest of the team depends on
- Researchers and document-heavy analysts whose output must hold up under review — competitive analyses, literature reviews, deep research synthesis
- Solo builders shipping serious work who can’t carry methodology in their heads — founders, independent practitioners, consultants on long engagements
If your Claude work needs to be defensible, repeatable, and reviewable — CRAFT is for you.
Have Questions or Need Help?
Let us know how we can help.
