Our process
You approve the planbefore anything gets built.
Every engagement follows the same sequence: diagnose, scope in writing, build in stages, measure, hand over. Here is the whole thing in order, including what you do at each stage and exactly what you receive.
Why it runs this way
Most project problems are scoping problems that surfaced too late
Missed deadlines, surprise invoices and builds that solve the wrong problem almost always trace back to the same cause: work started before anyone wrote down what it was for.
-
Diagnosis comes before the quote
We do not price a website until we know whether the website is the problem. The audit runs first, and the recommendation follows the evidence, even when the evidence points to a smaller engagement than you came in expecting.
-
The plan is a document, not a conversation
Scope, sequence, cost and the intended effect of each stage are written down and approved. Anything not in that document is a change you decide on, priced separately, rather than an assumption we quietly absorb or quietly bill.
-
Stages are sized to be useful on their own
Each stage is built to produce something you can judge — faster response times, a working form-to-CRM path, a page that converts. You are never waiting until the end to find out whether the approach works.
-
Measurement is set up before launch, not after
Tracking installed after go-live loses the first weeks of data and makes the launch impossible to evaluate. It is part of the build, and it is tested with real submissions before traffic arrives.
Stages one to four
Before anything is built
-
Stage 01
Strategy call
A straight conversation about what you sell, where enquiries come from now, and where the process breaks. We look at the site, the follow-up timing and what your current numbers can and cannot tell you. You bring access to nothing — this stage is discussion. You leave with our honest read on where revenue is leaking, whether or not the conversation goes further.
-
Stage 02
Audit and diagnosis
With read access to what exists — site, analytics, CRM, ad accounts, follow-up tooling — we document the current system as it actually behaves. Response times, tracking gaps, broken handoffs, spend that cannot be attributed, performance and accessibility issues. You receive the written assessment, and you keep it regardless of what you decide next.
-
Stage 03
Growth system plan
The proposal, in writing. What gets built, in what order, what each stage is meant to change, what it costs and how long it takes. Dependencies and anything we need from you are named explicitly. Your job at this stage is to read it critically and challenge it. Nothing starts until you approve it.
-
Stage 04
Approval and setup
Once approved, we confirm the schedule and set up access. Accounts are created or transferred into your name, permissions are scoped to what each process needs, and the content or assets we need from you are listed with dates. Delays here are the most common cause of slipped timelines, so the list is short and specific on purpose.
Stage five
The build runs in stages, and you see each one
Work is delivered in reviewable pieces rather than disappearing for eight weeks and returning as a reveal. Each stage is tested against real data before it handles anything live, and each has a defined purpose you agreed in the plan.
- A short checkpoint at each stage — what was built, what it changes, what is next
- Everything built in accounts registered to you, not staged inside our tooling
- Automations tested with real submissions before they touch live enquiries
- Performance, accessibility and tracking treated as build requirements, not later fixes
- Changes to scope priced and agreed in writing, never absorbed silently into the timeline
- Your part: timely feedback at checkpoints and the content or approvals listed in the plan
Stages six to eight
Launch, measurement and handover
-
Stage 06
Launch
Go-live is a checklist, not an event. Redirects, forms, tracking, automation triggers, error alerting, backups and performance are verified before the switch and again after it. We watch the first live enquiries end to end — from submission to CRM record to the follow-up firing — and fix anything that behaves differently under real traffic.
-
Stage 07
Measurement
Once real volume is running, the numbers replace the assumptions. You get reporting against the intended effect agreed in the plan: whether enquiries are arriving, being answered faster, and being traceable to their source. What underperformed is named as plainly as what worked, along with what we propose to do about it.
-
Stage 08
Optimisation
Improvements are proposed on evidence, in priority order, with the expected effect stated up front. This is optional work, decided each time. If a period has nothing worth doing in it, we say so rather than filling it, and nothing built so far depends on this stage continuing.
-
Stage 09
Handover
Documentation written for a stranger: what each part does, how it is configured, what breaks if it is switched off, and where every account lives. Ownership is already in your name, so handover is a walkthrough rather than a transfer. You can take the system in-house or to another provider at any point without our cooperation.
What you receive
The tangible outputs, stage by stage
Beyond the system itself, an engagement produces a written record. It exists so you can evaluate the work, and so someone other than us can run it.
-
A written system assessment
The diagnosis from the audit — where the current setup leaks, in specific terms. Yours to keep whether or not you proceed.
-
A growth system plan
Scope, sequence, cost, timeline and intended effect per stage, approved before work begins and used as the reference for everything that follows.
-
Accounts and assets in your name
Domain, hosting, site, CRM configuration and automation logic, all registered to you, with our access removable in a few clicks.
-
Documentation and reporting
Plain-language configuration notes plus reporting written against what each stage was meant to change, including the parts that did not perform.
Before you book
Questions about the process
The strategy call and audit typically take days rather than weeks. Most website and automation builds go live in four to eight weeks after approval. The variable is almost always how quickly content, access and approvals come back — not the engineering.
Nothing. You get our read on where the system is leaking whether or not you hire us. If we do not think we are the right fit, we will say so on that call rather than proposing something to keep the conversation alive.
Yes. The assessment and the plan are yours. Some businesses take them in-house or to another provider, and that is a legitimate outcome of the process rather than a failure of it.
It is priced and agreed in writing before it happens. Discovering that something needs to change is normal; discovering it on the final invoice is not.
No. Ongoing optimisation is available and entirely optional. Nothing we build requires a monthly fee to keep running, and the documentation is written so you can maintain it yourself.
Next step
Start with stage one.
Book a strategy call. You will get a straight assessment of where your system is leaking and a clear view of what we would build — before any money changes hands.