The agreed build goes live on time.
Scoped in writing, tested against the standard above, approved by you, live within seven days of the start date. If I miss it, you do not pay.
The method
The same twelve steps, every single time.
You are not buying my availability. You are buying a process that runs the same way for every business, hands you a document at every phase, and has to pass a written standard before anything touches a real customer.
0
steps from first contact to handover, the same every time
0
phases inside the build, each one ending in a document
0
documents that stay yours, whatever happens next
0
builds that have gone live without passing the standard below
First contact to handover. Nobody skips a step, including me.
I read your form before we speak, so the call is a conversation and not a questionnaire. From there the same path carries a good fit all the way through payment, launch, ownership, follow-up, and proof you have approved.
Steps 1 to 4
You leave with something either way.
The free diagnosis is real work, not a form gate. If what you need is smaller than what I sell, step four is me saying so.
01Useful diagnosis
02Fit form
0315-minute call
04Recommendation
Steps 5 to 7
Nothing starts on a verbal yes.
A scope you sign, terms in writing, then payment. Onboarding collects your working rules before a single thing gets built on a guess.
05Proposal and agreement
06Payment
07Onboarding
Steps 8 to 12
Built, tested, approved, then live.
You approve the path before it meets a customer. After launch there is training, a follow-up schedule, and proof only if you approve the wording.
08Build and test
09Approval
10Launch and training
11Follow-up
12Proof, referral, or care
Inside step eight, seven phases and a document at each one.
This is the part most providers keep vague. Here it is with the output named, so you know what lands in your hands and when.
Day1
Map
Every handoff drawn, every task that waits on you named and timed. You correct it before anything gets built on top of it.
You keep the Operations MapDay2
Build
One piece at a time, demonstrated as it stands up. No single reveal at the end that turns out to have missed how you work.
Shown to you as it goesDay5
Test
Normal path, exception path, failure path, checked line by line against the standard below.
You keep the Test RecordDay6
Approve
You walk the path yourself and approve it in writing. Nothing goes live on a verbal yes.
Your written approvalDay7
Launch
Switched on one channel at a time, supervised, with the first live item watched end to end.
You keep the Launch LogDay7
Train
One hour, hands on. You change your own hours and your own prices while I watch.
You keep the Operating ManualDone✓
Hand over
Logins, the list of what lives where, and a written statement that it stays yours.
You keep the Ownership PackWhat actually lands in your hands.
Three of the seven. Not slides about the work, the work itself, in a form you keep.
Operations MapOwner-dependency registerTest Record
Written approvalsLaunch LogOperating Manual
Ownership PackWeekly updates
Phase 1 · the map
Every task that still waits on you, counted.
Each handoff drawn, each owner-dependent task named, how often it happens, and how many minutes it takes. Then the same minutes added up per month at a number you set yourself.
You correct this before anything gets built on top of it.
Phase 3 · the test record
The proof it was tested, not the promise.
Normal path, exception path, failure path, follow-up, data and ownership. Every line checked on day five, before you ever see it, and signed off one at a time.
If a line cannot be ticked, it does not launch and the date moves.
Phase 7 · the ownership pack
The keys, and a written note that they are yours.
Every account in your name, the list of what lives where, and plain-language instructions for changing any of it yourself. A care plan is optional. The build stays either way.
Nothing in it depends on an account I control.
What you keep
Seven documents, and they stay yours whatever happens next.
The Operations Map, the Test Record, your written approvals, the Launch Log, the Operating Manual, the Ownership Pack, and the weekly updates from the whole build. If we never work together again, another provider could pick this up from the paperwork alone.
Why it works this way
A documented system is worth more than a working one.
A working system nobody wrote down is a system that depends on whoever built it. That is fine until you want to change something, hire someone, or stop working with me. Documented, it is an asset your business owns.
The standard every build has to pass, printed in full.
Most providers will tell you they test. Here is the actual list, so you can hold me to it, or hand it to whoever you hire instead.
The normal pathAn inquiry arrives on every connected channel, gets answered in your voice, qualified, offered two real times, and confirmed on your calendar.Required
The exception pathA question outside scope reaches you and you are told where. Anything sensitive never gets an automatic answer. "Call me" gets you.Required
The failure pathCalendar unreachable, channel disconnected, duplicate inquiry, someone replying to an old thread. Each has a defined behaviour and you find out first.Required
The follow-up pathA dated next action that keeps going, and stops properly when it books, when you take over, or at a clear end.Required
The dataEvery inquiry appears once, with a stage and a next action. Where Soma is included, one entry reaches every destination it should.Required
The ownershipEverything lives in accounts you own, you can log in and see it, and no part of the build sits behind an account I control.Required
Checked on day five, before you ever see it, and again on launch day.
If a line on this list cannot be ticked, it does not launch. The date moves and you hear it from me the same day.
What stays human
Judgment, exceptions, approvals, and anything sensitive.
The repeating path moves without waiting on you. Decisions that need you still reach you, in the place you already look. That boundary is set by you during onboarding, not assumed by me during the build.
What you bring
The real process, and answers when I ask for them.
Access to your own accounts, your working rules, and a decision when the build is waiting on one. Delay from my side is on me. Delay from yours pauses the clock, and I tell you in writing the day it happens.
Live in 7 days, or you don't pay.
That is a promise about the build, and it is the only promise I make.
A number of bookings.
How many people book you depends on how many were asking in the first place. Anyone promising you a booking number does not know your inquiry volume, and neither do they know your market.
The risk is your time, not your money.
Two calls and some access. If the build is late, it costs you nothing. That is the deal, and it is the same deal for every build.
The method
Read the standard first. Then decide.
The fit form asks how work actually reaches you and where it falls through. I read it before we speak, and if what you need is smaller than what I sell, I will tell you on the call.