How we work
A clear process. Senior people involved.
What happens before a proposal, what is fixed before work starts, how the build runs, and what we still do after launch. No mystery, no six-week silence.
STEP 01
Understand
WE DO
Listen, look at what exists
YOU SEE
A written summary
YOU APPROVE
Whether to proceed
STEP 02
Scope
WE DO
Structure, scope, price
YOU SEE
A proposal with fixed price
YOU APPROVE
Scope and timeline
STEP 03
Design
WE DO
Wireframes, visual direction
YOU SEE
Clickable prototypes
YOU APPROVE
Page system and key journeys
STEP 04
Build
WE DO
Development alongside design
YOU SEE
Staging links every 1-2 weeks
YOU APPROVE
Each stage before the next
Our process in detail
01
Before a proposal
The first conversation is 15 minutes on what you are trying to achieve, what exists today and where the friction is. We need a rough idea of scope, timing and budget range; you do not need a finished brief. Where the project is large or unclear, we suggest a short paid discovery instead of guessing.
What we need
Goal, current site or system, timing, budget range
What you get
A written proposal with fixed scope and price
02
Scoping
Structure, content direction, functionality, integrations, timeline and price are agreed before the main work starts. Content responsibilities are written down. What can still change: copy, imagery and detail within the agreed structure. What is fixed: the price for the agreed scope.
Fixed
Scope, price, timeline, who does what
Flexible
Copy, imagery, detail inside the scope
03
Design and build
Design and development run together. You see work in progress every week or two in a shared link, not a big reveal at the end. Two rounds of feedback are built into each stage, and technical constraints are raised while the design is being made rather than discovered afterwards.
Reviews
Every one to two weeks, live links
Feedback
Two rounds per stage, written down
04
Payments
Project work is paid in stages tied to delivery: typically a deposit to start, a payment at design sign-off and the balance at launch. Ongoing work such as Growth & Support, CRO or SEO is billed monthly and can stop with notice.
Projects
Staged: start, design sign-off, launch
Ongoing
Monthly, rolling
05
Launch
QA across browsers, devices and the critical journeys. Redirects mapped where URLs change. Analytics and tracking checked. Handover includes training where the team will edit the site, and applicable builds carry a three-month warranty.
Included
QA, redirects, tracking, training, 3-month warranty
Ownership
Code, files and accounts are yours
06
After launch
Launch is where the useful data starts. Growth & Support covers updates, fixes and improvements. CRO, SEO, paid media, development and automation continue where there is a clear commercial reason. Measured against the baseline agreed at the start.
Ongoing
Growth & Support from £300/month
Measured
Against the baseline agreed at scoping
Process questions
Before you ask. The answers are here.
Most projects run six to twelve weeks from kick off to launch, depending on how much content and functionality is involved.
No. A rough idea of the goal, the timing and the budget range is enough to start the conversation.
Where the project is large or the scope is unclear, so the proposal is based on findings rather than guesswork.
Split across the build against agreed milestones, rather than taken up front.
A weekly check in and timely feedback at each milestone. We will always say what we need and by when.
We price the change before anything is built, so nothing appears on an invoice that you have not agreed to.
Let's work together
Book a free
15 minute call
no hard sell.
just a chance to see if working together makes sense.