Process - How projects run
The process is designed to keep the important decisions visible, not buried inside a long project plan.
Each stage ends with something concrete to review, so the next step is based on real decisions rather than assumption.
Discovery
We start by working out what the site needs to change, who it needs to persuade, and where the current version is getting in the way.
The output is a working plan: page priorities, user paths, and the decisions that need settling before design begins.
Included in this phase
- Project goals and constraints
- Audience and intent notes
- Page priorities and scope
- Decision log and actions
Design
We turn the plan into page flows, wireframes, and the main templates the site will rely on.
Design choices are made to support reading, navigation, and decision making. The pages should feel easier to use, not simply more polished.
Included in this phase
- Wireframes and user flows
- Key page templates
- Design system basics
- Typography and colour direction
Content
If the copy or imagery still needs work, we shape it together. If the material already exists, we edit and reorganise it so the pages read better and answer questions sooner.
The point is to put the right information in front of people sooner, instead of burying it under secondary detail.
Included in this phase
- Copywriting and editing (optional)
- Content hierarchy and messaging
- Calls to action and FAQs
- Search-ready structure
Development
We build the site with performance, accessibility, and maintainability treated as part of the job.
You get regular updates, and we test the important paths across current devices and browsers before launch.
Included in this phase
- Front-end and back-end build
- Performance optimisation
- Accessibility checks
- Cross-device testing
I always knew what was happening next. The updates were clear, the decisions were easy to make, and the launch felt calm.
Launch and optimisation
We run final checks, connect measurement where needed, and take the site live without guesswork.
After that, we either hand over cleanly or stay involved for the next round of fixes and improvements.
Included in this phase
- Launch checklist and QA
- Deployment and handover
- Launch support
- Post-launch optimisation
Timelines and investment - Typical timing and budget
Every job is different, but most follow a steady rhythm with clear review points and a similar approval pattern.
- Typical timeline. Most projects run 6 to 12 weeks, depending on scope, review cycles, and how ready the content is.
- Project rhythm. Weekly updates, short review loops, and decision points at the end of each stage.
- Investment bands. Most full website projects sit between GBP 2k and 30k. Audits and focused fixes can land below that. Larger platforms and more complex catalogues can exceed it.
Stakeholder roles - Who needs to be involved
Website projects move better when decision ownership is clear from the start. These are the roles we usually see around the table.
- Founder or sponsor. Sets the commercial direction and signs off the larger calls.
- Marketing lead. Keeps messaging, audience fit, and campaign priorities aligned across the key pages.
- Operations or delivery lead. Helps keep timings realistic, content ownership sensible, and post-launch upkeep clear.
Across the job - What is covered as standard
Most jobs span more than one discipline. These are the areas handled as part of doing the work properly.
- Design. Page structure, hierarchy, and visual direction that keep the main message readable.
- Technical quality. Fast loading, stable layouts, and dependable behaviour across current devices.
- Search basics. Search-ready structure with sensible metadata and page organisation.
- Content clarity. Editing and page structure that make the content easier to scan and easier to believe.
- Campaign support. Support for campaign pages and landing pages when they are needed.
- Ongoing upkeep. Updates and follow-on improvements to keep the site in decent shape.
Post-launch - After launch
Most teams need a light but reliable routine once the site is live, especially when content keeps changing after launch.
- Monthly governance. A review cycle for key pages, enquiry routes, and technical quality.
- Audit-led resets. When the site starts drifting, an audit gives you a ranked fix list.
- Care plans. Ongoing support to keep the site accurate and stable as the business changes.
Read more in website care plans and audits.
Need the site to do a better job?
Send a short outline and we will come back within two working days with a sensible next step.
If you are still gathering input internally, start with the project pack.