how it works
From a first conversation to something you can act on.
Advice
- First conversation. About your business as it is, not as it looks on paper. You get a written scope and price.
- Sessions. We work through the questions that matter, and I write down what we decide.
- Next steps. You leave with a short list of actions that are yours to take, and a way to reach me with questions.
Builds
- Discovery. A call about your actual day: where work gets stuck, who needs to see what, what you'd never give up. You get a written scope and a fixed price.
- Architecture. I map your workflow into a design before building anything, and you approve it.
- Build. Regular check-ins, with something working to look at early.
- Handover. The system lives in your accounts. You get documentation, a short team walkthrough and the access.
- Support. An optional monthly retainer for changes and questions after launch.
What you can hold me to.
- One engagement at a time. I take a single active project so it gets real attention. If I'm full, I'll tell you the start date.
- Written scope and price before work starts.
- Honest limits. I'll tell you what shouldn't be automated, and when I'm not the right person for the question.
- Your tools, your data. The system sits in your Notion or your hosting.
- One dependency, stated plainly. An operations system built on Notion depends on Notion's pricing and features.
The ones I get asked.
Will my team actually use it?
That's why handover includes training, and why WhatsApp stays for client chat. I'd rather fit how your team already works than replace it.
What happens when something breaks later?
A support retainer, or a one-off hourly session.
Who do you work with?
Founders and small teams, in any line of work. Most of my builds so far have been for an interior design studio and an electronics distributor.
Is the advice a substitute for a lawyer, accountant or therapist?
No. I'll say so when a question belongs with one of them.