My simple process to help your tech make sense
I don’t just write. I dig, test, and collaborate until your product’s value is clear to your audience. Here’s how it works:
1. Ask annoying questions
I’ll ask your team (especially your engineers) a lot of questions. The goal: to find out what makes your product unique and what your users actually need.
2. Go down rabbit holes
I’ll use your product, break things, and find the real use-cases that matter. This is where the best documentation ideas come from.
3. Create a roadmap
You’ll get a clear outline of what we’re building, why it matters, and how it’ll help your users. No writing starts until you’re happy with the plan.
4. Collaborate, not disappear
We’ll work together to review, refine, and improve the content. You’ll always know what’s happening and why.
What you get
- Documentation that actually helps users (and reduces support tickets)
- Technical content that drives signups, not just traffic
- A partner who cares about your product’s success