Start a project
How we work

Clear stages. Visible progress. Steady improvement.

Every project follows the same simple structure, scaled to its size: understand first, agree the plan in writing, design with you, build carefully, then launch and keep improving.
Start a project
See each stage
Planning notes and sticky notes on a desk
Agreed in writingScope, schedule and cost are confirmed before work begins.
At a glance

Five stages, one direction.

01

Discover

Understand the business before proposing anything.
You receiveDiscovery notes and a shortlist of priorities.
02

Define

Turn priorities into an agreed plan.
You receiveA scoped proposal and project plan.
03

Design

Shape the experience with you, not for you.
You receiveApproved designs for the key pages or screens.
04

Build

Engineer it properly, and prove it works.
You receiveA working, tested product on a review (staging) environment.
05

Launch & improve

Go live carefully, then keep getting better.
You receiveThe live product, documentation and recommended next steps.
In detail

What happens at each stage.

01

Discover

Understand the business before proposing anything.
What happens
Conversations about your goals, customers and constraints. We review your current website, tools and any data that’s available.
You receive
Discovery notes and a shortlist of priorities.
We’ll need from you
A little of your time, access to relevant accounts, and honest context about what has and hasn’t worked.
How you’re involved
A kick-off conversation and a review of what we found.
02

Define

Turn priorities into an agreed plan.
What happens
Priorities become a written scope: what will be built, the structure, key features, responsibilities and a realistic schedule.
You receive
A scoped proposal and project plan.
We’ll need from you
Decisions on priorities and one main point of contact.
How you’re involved
Review and approve the scope before design begins.
03

Design

Shape the experience with you, not for you.
What happens
Content structure, user journeys and interfaces are designed, then refined with your feedback in focused rounds.
You receive
Approved designs for the key pages or screens.
We’ll need from you
Timely feedback from the people who will sign off.
How you’re involved
Design reviews and a final approval.
04

Build

Engineer it properly, and prove it works.
What happens
We develop in stages, test across devices and browsers, and check performance, accessibility and security as we go.
You receive
A working, tested product on a review (staging) environment.
We’ll need from you
Content, access to the tools we integrate with, and acceptance testing.
How you’re involved
Staging reviews and testing against the agreed criteria.
05

Launch & improve

Go live carefully, then keep getting better.
What happens
A careful launch with checks, monitoring and a handover, followed by measurement and practical improvements.
You receive
The live product, documentation and recommended next steps.
We’ll need from you
Launch approval and access to analytics.
How you’re involved
Launch sign-off, a training session and periodic reviews.
Collaboration

Working together, at a distance.

Simple habits that keep projects clear and moving, wherever everyone is.

One point of contact

You always know who to ask, and who is responsible for what.

A shared workspace

Plans, files, feedback and decisions kept in one place you can access.

Written decisions

Scope, changes and approvals are recorded, no surprises later.

An agreed rhythm

Check-ins and progress updates at a frequency that suits the project.

Time-zone aware

Meetings scheduled around your working hours.

Clear handover

Documentation, access and training before the project closes.
Built-in standards

Quality isn’t a phase. It’s the default.

Targets we design and test against on every project, adapted to its platform and scope.

Performance

Fast loading and stable layouts, with Core Web Vitals considered from the first wireframe.

Accessibility

WCAG 2.2 AA as the baseline target: keyboard access, contrast, labels and reduced-motion support.

Security

Sensible defaults, least-privilege access, validated input and up-to-date dependencies.

Search foundations

Semantic structure, clean URLs, metadata and structured data where it fits.

Privacy

Collect only what’s needed, explain it clearly, and ask for consent where required.

Maintainability

Readable code, reusable components and documentation for whoever comes next.
FAQ

Questions about the process.

All questions
How involved do we need to be?

Most involvement happens at the start (goals and scope) and at review points (designs, staging, launch). We agree the rhythm of check-ins at kick-off.

Can the scope change during a project?

Yes, priorities often shift as you learn. Changes are discussed, their impact on time and budget is explained, and nothing changes without your written agreement.

Do you work with our in-house team or other suppliers?

Yes. We can collaborate with your developers, marketers or other partners, with responsibilities agreed during the Define stage.

What happens after launch?

We review how the product performs, recommend next steps and can continue with care, optimization or further development if you’d like.

Start a project

Start with a conversation.

Tell us where you are and where you want to be. We’ll suggest a sensible first step.
Start a project
Book a call

Privacy

Cookie preferences

This website currently uses no analytics or marketing cookies. Choose what you would allow if they are added later; your choice is saved in this browser only. Read the cookie policy.