Process

A clear process from brief to launch.

Each phase has a purpose, a review point and a clear next step, so responsibilities and approvals stay visible.

Start with your brief
01

Discover

We learn how the business works, who the website serves and where the current friction lives.

02

Define

We agree the strategy, content structure, technical shape and standard for success.

03

Design

We explore the visual direction, prototype important journeys and build a responsive system.

04

Deliver

We develop, test, refine and prepare the website for a controlled launch.

05

Improve

We use real feedback and performance evidence to guide the next useful change.

Evidence and exit points.

Each stage ends with something reviewable. That reduces hidden work, vague approval and late surprises.

01

Discover

Evidence: Business context, audiences, current evidence and constraints.

Exit: A shared problem statement and open questions.

02

Define

Evidence: Page architecture, content responsibility, platform direction and acceptance criteria.

Exit: An approved scope and delivery plan.

03

Design

Evidence: Realistic content, responsive flows, interface states and reusable components.

Exit: An approved system ready for implementation.

04

Deliver

Evidence: Production code, content integration, forms, metadata, accessibility and QA.

Exit: A deployable release with checked critical journeys.

05

Improve

Evidence: Enquiries, feedback, field performance, search data and maintenance needs.

Exit: A prioritised evidence-based improvement backlog.

What we need from you.

Access to the right people, honest feedback, real content and timely decisions. We make the work easy to follow, but the strongest result is always collaborative.

The release is controlled.

A launch plan identifies the public domain, redirects, forms, search controls, privacy configuration, analytics choice, owners, monitoring and the recovery route. Production proof is separate from a local build passing.

Use the launch checklist