No lock-in. No minimums.
Stop anytime, no penalty. Work delivered is yours. The guarantee is performance: I build until it’s live and doing the job.
How an engagement runs
From discovery call to a system you own.
No vague proposals. No briefing chains. The sequence below is what happens, in the order it happens, with the plan committed in writing before any build. I build until it’s live and doing the job.
Read it like a contract. That is roughly what it is.
The sequence
Six steps. Same order, every time.
Every engagement runs the same path. Discovery call free; the workflow audit is paid. After commit, you see the plan before any build, and you can stop anytime with no penalty.
- 01 30 min · Free
Discovery call.
30 minutes. Your business, your bottleneck, whether what I build is the right answer. No pitch. If it’s not a fit, you hear it on the call.
- 02 1 hour · Free
Workflow audit.
About an hour, together. Tools, data, manual processes. The audit identifies which workflow becomes the automation, which data feeds the dashboard, where the friction lives. Commit here and scope begins.
- 03 Before any build
Written scope.
Deliverables, scope, assumptions; every Function and Enhancement bundled. No vague statements of work. We meet to agree. You see the plan before any build.
- 04 On real data
Working MVP.
Operational dashboard live on real data: revenue, pipeline, team capacity, client health. Not a mockup. Not a demo. Two iteration rounds, in your environment, behind authentication. Stop anytime, no penalty.
- 05 Scoped to you
The build.
Your custom system, built out on real data, in phases. You use each phase as it ships. Hosting, authentication, database, and the data connections agreed in scoping, all included. I build until it’s live and doing the job. Written into the agreement.
- 06 Yours · forever
Handover. You own everything.
Code, infrastructure, SOPs, knowledge wiki: every artefact yours. No licenses retained. From here, keep going or stop, no penalty either way. Something new to build? Open the next phase, scoped like the last. Want it just kept running? I host it, update it, and refresh the AI as the models improve.
The agreement
What we each commit to.
These aren’t aspirations. Every commitment below is in the service agreement, spelled out in writing.
Once approved, the scope holds.
Enhancements bundled before build. New requests after approval go into the next phase. Every request classified before it changes scope.
Fast feedback. Both sides.
I move fast on scope and MVP. You give fast feedback. If feedback runs longer, the schedule adjusts, in writing, flagged up front.
Code, database, SOPs, wiki.
Source, infrastructure, deployment, knowledge wiki. All transferred on delivery. No licenses retained. If we part ways, the system keeps working.