ProcessHow an engagement runs
You know the price before I build. You own everything when I leave.
Six steps. No hourly meter anywhere. Discovery is paid and credited back in full against the build, so looking closely costs you nothing if we go ahead, and only a little if we don’t.
-
Intro call
Thirty minutes on a call. You bring the thing that is slow; I ask what it costs you in hours, missed leads, or rework, and what you have already tried. Most of the time we can tell by the end whether discovery is worth your money. If it is not a fit, I say so and point you somewhere useful.
30 minutes · free -
Paid discovery
A fixed fee to look at how work actually moves: the inbox, the spreadsheet, the phone, the tool nobody opens. I talk to the people who do the work, not just the owner. You get a short written findings document in plain language with a recommended scope. You keep it whether or not we go further. If you go ahead with the build, the discovery fee is credited back in full.
fixed fee · credited back -
Fixed-price proposal
One scope, one price, one finish date, in writing. There is no hourly meter and no surprise invoice. If the scope changes, the price and the date change in writing before work continues, and you decide.
one scope · one price · one date -
Build
Remote, on accounts you own, under logins you control. You get short written updates as the build moves, and nothing goes live without a walkthrough with the people who will use it. Where a migration is involved, there is a cutover plan and a way back.
remote · on accounts you own -
Handoff with a fix-it guide
Training for the people who will run the system, recorded so the next hire gets the same session. Plus a fix-it guide: what to do when a form stops posting, an automation stalls, or someone needs access. Written for whoever is on duty, not for me.
training · documentation -
Optional support
If you want it, a monthly block of time for changes, questions, and the small fixes that keep a system honest. Scoped and priced separately. If you never take it, everything still works, and anyone you hire can change it, because it is all in your accounts and written down.
only if you want it
After handoffWhat you own
Everything. That is the point.
If we never speak again, it keeps working, and anyone you hire can change it.
The accounts
Every tool is set up under your logins, with you as the owner and administrator. I work as an invited user, and you can remove me the day we finish.
The automations
Built in your workspace, named so a stranger can read them, with a one-line note on what each one does and what to check when it stops.
The documents
The discovery findings, the playbook, the fix-it guide, and the training recording. Plain files in your drive, not a portal you lose access to.
The exit
No retainer required to keep things running. Optional support exists for changes and questions, and you can stop it whenever it stops earning its keep.
From youWhat I need
Three things.
-
Access to the accounts you own
Admin on the tools in scope, or someone who can grant it. Nothing gets built on an account I own.
-
One person who can decide
Usually you. Small decisions need an owner or the build stalls waiting for them.
-
Honest answers about what is slow
Including the workarounds nobody is proud of. Those are usually where the real process lives.
Step one is thirty minutes.
No prep, no pitch. We figure out whether discovery is worth your money.