Discover. Diagnose. Build. Handover.
Each step: what you bring · what you leave with · cost.
The four steps
Discover
A conversation about your company as a whole: how the work runs, where it hurts, what you've tried, and where AI could help. No preparation on your side.
Diagnose
Two hours inside your operation. You get a written plan of proposals, like an architect's first sketches: what's worth building, in what order, and what each would take. Yours whether or not we go further.
Build
The Layer, a plugin, a workflow, or a custom system. Installed in your accounts.
Handover
Yours to run. Support options include: Available · Monthly rhythm · Partner.
Prices
credited toward a build
half day, up to 8 people, after a Diagnostic
one leader or one team, $10,000–30,000 across the company
smaller or larger depending on complexity and breadth; the final price comes from the scope of the build
Options include:
Available
reachable when something breaks or you have a question
Monthly rhythm
a monthly check-in; I suggest improvements, you approve before I act
Partner
for a system core to how you run
The order I try things in
- Change the process
- Use what you have
- Buy
- Connect
- Build
For comparison
A part-time fractional CTO runs $8,000–25,000 a month. An embedded engineer from a studio, $15,000–40,000.
Common questions
Is the Diagnostic the only paid step before a build?
Yes, and it's credited if you build within 30 days of the plan.
Who owns what at the end?
You do: your accounts, your repository, your documents.
How fast can we start?
Usually within two weeks of the first conversation.
The first conversation is free.
Start a conversation