Eight weeks, written down.
The same sequence every time, because the second build should cost half what the first one did. You get a preview link on day one and an update every Friday whether or not there is news — silence is what makes clients anxious, and it costs nothing to fix.
01The build
Diagnostic
We walk your process end to end and map how it works today. You get a written recommendation and a fixed quote. £450, credited against the build.
Setup
Deposit received before anything starts. Every account created in your name — domain, hosting, Stripe, database, email. Scope signed, so we both know exactly what is in and what is out.
Build
Core functionality first, cosmetics last. A preview link from day one so you watch it being built. An update every Friday whether or not there is news, because silence is what makes people anxious.
Content and data
Your content in, your existing customer data migrated. This is the step that slips, because it depends on you — so we start chasing it in week two, not week five.
Testing
We test, then you test on your own phone with your own thumbs. We take a real payment on a real card and refund it. We try to book the last slot twice at once.
Handover
Training session, recorded. Written handover document. Every credential transferred. Final invoice.
Aftercare
Two weeks of snagging included, and a 30-day check-in booked before we go quiet. Then Run starts, or it does not.
02Measurement
Six events. Together they make a funnel you can act on.
Search data tells you how people found you. Product analytics tells you what they did once they arrived. Stripe tells you what they actually spent. Almost every business has one of the three. Almost none has them joined up — and in isolation each is just a screen of numbers.
Joined up, you can say: forty people searched for this, twelve got as far as the booking page, three paid, and here is the exact screen where the other nine gave up. That is something you can fix on Monday. Three separate dashboards is not.
Session start
Someone lands, from wherever they came
Booking initiated
They open the booking flow — interest, not a passing visit
Slot selected
Real intent. They have picked their time
Checkout started
One step from you being paid
Payment completed
The only number that pays your wages
Abandonment
Started and never finished — the expensive one nobody measures
Every build goes live counting at least these six. The site you are reading tags its own links the same way — if we are going to tell you which post brought the booking, we should be able to tell you which one brought you here.
03Handover
The goal is that you don’t need us afterwards.
Training session, recorded, so you are not asking the same question in month four. A written handover: what the system does in plain English, the ten most common tasks with screenshots, where every account lives and who owns it, what it costs to run each month, and what to do if something breaks.
Then two weeks of snagging, and a 30-day check-in booked before we go quiet rather than after. If you want the reporting, that is the Grow retainer. If you don’t, everything still belongs to you and another developer can pick it up tomorrow.
→Start
Tell me what breaks when you get busy.
The first step is a £450 Diagnostic: half a day walking your process end to end, and a written recommendation with a fixed quote attached — whether or not you build anything with us. It is credited in full against a build if you go ahead within thirty days.