A clear process, start to handover.
Five stages on every project, sized to fit. Here is what happens at each one, what you receive and what we need from you.
Discovery
We learn the business before we design anything: goals, customers, competitors, what the current site does and what the new one has to connect to.
You receive
- A written scope with deliverables and a fixed price
- A project schedule
- A list of what we need from you
We need from you
- An hour or two of your time
- Access to the current site and its analytics
- One person who can make decisions
Content and structure
We decide which pages exist, what each one is for and what goes on it. Existing content is reviewed and kept, rewritten or retired.
You receive
- A sitemap
- A page-by-page content plan
- A redirect map for existing addresses
We need from you
- Existing copy, photos and brand files
- Facts only you know: services, areas, pricing rules
- A review of the plan
Design
A visual system first, then page designs for desktop and phone. You see real layouts with real content, not filler text.
You receive
- A type, color and component system
- Designs for the key pages at desktop and mobile sizes
- Revision rounds as defined in the scope
We need from you
- Consolidated feedback from one voice
- Final logo files
- Sign-off before the build starts
Build and integrate
We code the site, build the forms and tools, and connect the systems it depends on. You can watch it take shape on a private link.
You receive
- A working site on a private link
- Forms, lead flows and integrations tested end to end
- Search basics in place: titles, descriptions, structured data
We need from you
- Account access for anything we connect
- Test data or sample inquiries
- A look on your own phone and computer
Launch and support
Testing, migration and go-live, then training so your team can run the site. Ongoing care is available and never assumed.
You receive
- Checks across devices, and keyboard and screen-reader testing
- Migration with redirects, then forms and analytics rechecked
- A training walkthrough with written notes
- Handover of accounts and access
We need from you
- Access to your domain registrar
- A launch date that suits the business
- A decision on who maintains the site
Handover
What is yours at the end.
A project ends with a site you can run, not a dependency on us.
01
Your domain and accounts
Registered and set up in your name, with access you can use.
02
Your content and design
The text, images and design files produced for the project.
03
Written notes
How the site is built, how to edit it and how each custom piece works.
04
A training walkthrough
A session with your team, recorded if that helps.
Staying on track
How we keep it clear.
One point of contact
You talk to the person doing the work, from the first call to handover.
A written scope
Deliverables, responsibilities, schedule and price, agreed before work begins.
A private preview
You can open the site in progress at any time and see where it stands.
Changes in writing
Anything outside the scope is written up with its cost before it is built.
Questions
Questions, answered plainly.
If yours is not here, put it in the planner notes and we will answer it directly.
How do revisions work?
Each stage has a defined review. You give consolidated feedback, we revise, and the number of rounds is written into the scope so nobody is guessing.
What if the scope changes partway through?
It happens. We write up the change, what it adds in time and cost, and you decide before we do the work.
Who writes the content?
It depends on the project. We can write it, edit what you have or work from your copy. The scope says which, page by page.
What happens after launch?
You get training and written notes, and the site is yours to run. If you want us to host it and handle changes, that is a separate care plan.