Survey, plan, build, maintain.
The same four stages on a one-page site and on a two-year application, because the stages are about decisions, not size.
- 01 Survey
- 02 Plan
- 03 Build
- 04 Maintain
STAGE GATE — YOUR SIGN-OFF
STAGE 01
Survey
We find out what is actually there — the existing site, the data, the systems it touches and who maintains it afterwards.
WHAT WE DO
- Read the existing code and hosting
- Map the content and the pages that matter
- Interview whoever uses the systems daily
WHAT YOU GET
- A written summary of what exists
- A list of what is missing or broken
- A recommendation, including “do less”
WHAT WE NEED FROM YOU
- Access to a staging copy, never production
- One decision maker on the call
- Any existing brand material
STAGE 02
Plan
Drawing before building. Scope, sequence and price agreed in writing, with the assumptions visible.
WHAT WE DO
- Draw the screens that carry the work
- Set the token set and type scale
- Break the build into slices you can review
WHAT YOU GET
- A scope document
- A fixed-scope quote in writing
- A sequence with visible checkpoints
WHAT WE NEED FROM YOU
- Agreement on what is out of scope
- Copy or a decision on who writes it
- A deadline you actually care about
STAGE 03
Build
Built in slices you can click in staging. A change is priced in writing before it is absorbed into the build.
WHAT WE DO
- Build against the token set, not by eye
- Deploy staging on every push
- Check accessibility and performance as we go
WHAT YOU GET
- A staging URL you can use
- Weekly progress you can see
- A change log, priced
WHAT WE NEED FROM YOU
- Feedback inside the review window
- One reviewer with the authority to approve
- Decisions answered in writing
STAGE 04
Maintain
Then we keep it standing — or hand it over cleanly to whoever will. Both are legitimate endings.
WHAT WE DO
- Hand over code, domain, DNS and accounts
- Document the deploy and the restore path
- Run updates, monitoring and backups if retained
WHAT YOU GET
- A handover checklist
- A written deploy and recovery path
- A one-year warranty on builds
WHAT WE NEED FROM YOU
- Your own accounts created before handover
- A named contact for support
- An honest answer on who maintains it
HONEST NOTE
Most projects go wrong at the scope, not the code.
- A scope nobody wrote down, so every conversation is a negotiation.
- A handover nobody planned, so the person who built it becomes the only one who can change it.
- A stack nobody agreed to maintain, discovered a year later as a bill.
Questions about the process.
Can we skip the survey if we already have a design?
A design shows layout, not data shapes, integrations or hosting. When client designs are complete, the survey is smaller but it does not disappear.
How does a change request work?
You describe the change, we price it in writing, you approve or decline. Nothing is added to the build by conversation alone.
What if we do not like the concept?
The concept stage exists to absorb that. It is cheaper to redraw a screen than to rebuild one.
Who owns the work in progress?
You do, on payment of the agreed stages. The repository is yours from handover, and the accounts are in your name.
What is not in the warranty?
New features, third-party changes and anything caused by edits made outside the handover path. That is written down, not argued about later.