“It happened mid-workflow — they're preparing a strategy document for a quarterly review.. craft handled something they'd been doing manually, and it just worked. That was the moment it stopped being a tool they were evaluating and became one they relied on.”
When I'm preparing a strategy document for a quarterly review, I want to write in an environment that reduces friction and increases focus, so I can structure notes and documents in a way that's useful six months after writing them.
A product manager, writer, consultant, or knowledge worker who uses Craft as their primary document and note environment because it is the only tool that takes both writing and structure seriously at the same time. They're on Apple devices — Mac and iPhone, usually iPad. They've tried Notion (too database-y), Bear (too simple), Obsidian (too much tinkering), and Apple Notes (not embarrassed about this, just limited). Craft is what they settled on. The fact that it looks good is not superficial to them — environment affects their thinking.
To reach the point where write in an environment that reduces friction and increases focus happens through craft as a matter of routine — not heroic effort. Their deeper aim: structure notes and documents in a way that's useful six months after writing them.
craft becomes invisible infrastructure. Write in an environment that reduces friction and increases focus works without intervention. The old problem — web clipper and import features that don't match the polish of the core writing experience — is a memory, not a daily fight. Collaboration that reaches Google Docs-level real-time editing removes the "I'll.
They're preparing a strategy document for a quarterly review. It will be shared with six people, three of whom don't use Craft. They're writing in a Craft document: headers, nested blocks, embedded tables, a callout for the key recommendation. They'll share it as a Craft page link. They know two of the recipients will view it on their phone. They've checked the mobile view. It looks right. They're finishing the third section and they have 45 minutes before the meeting.
Uses Craft on Mac as primary, iPhone for capture and quick review, iPad for longer sessions. Has a Craft workspace with 3–5 top-level spaces: Work, Personal, Reading Notes, Projects. Uses backlinks occasionally — knows they should use them more. Publishes documents externally as Craft share links or PDFs. Has connected Craft to Notion or Readwise for specific workflows. Uses Daily Notes feature. Pays for Craft's premium plan. Has converted two colleagues to Craft. Is mild-to-moderately evangelical about it.
The proof is behavioral: write in an environment that reduces friction and increases focus happens without reminders. They've customized craft beyond the defaults — templates, views, integrations — and their usage is deepening, not plateauing. When new team members join, they hand them their setup as the starting point.
Web clipper and import features that don't match the polish of the core writing experience keeps recurring despite updates and workarounds. They start tracking how much time they spend fighting craft versus using it. The switching cost was the only thing keeping them — and it's starting to look like an investment in the alternative.
Pairs with `notion-primary-user` to map the Craft-for-writing vs. Notion-for-systems document tool philosophy. Contrast with `obsidian-primary-user` for the polished-writing-environment vs. graph-linked-knowledge-base distinction. Use with `substack-primary-user` for writers who draft in Craft and publish elsewhere.