Scope & priorities
Define what is included, what depends on external services and what can wait for a later version.
A project is a series of good decisions
Know what we’re working on, what we need from you and what the next decision is. Explore the seven stages of a project.
Start with your business, your customers and the work that gets in the way. A practical example tells us more than a long wish list.

A shared problem statement and clear priorities.
Your current process, customer questions and existing tools.
A shared problem statement and clear priorities.
The complete workflow
Every project is different. These are the conversations and outputs that give the work structure.
Start with your business, your customers and the work that gets in the way. A practical example tells us more than a long wish list.
What to prepare: Your current process, customer questions and existing tools.
Working output: A shared problem statement and clear priorities.
Turn the conversation into a useful scope. Separate essential journeys from later ideas, and identify content, data and integration dependencies.
What to prepare: Priorities, existing systems and constraints.
Working output: A proposed scope, page or feature map and delivery approach.
Explore the structure, key screens and visual direction. Review how a customer moves from a question to an action, on desktop and mobile.
What to prepare: Brand materials, content and feedback on the proposed direction.
Working output: Page layouts and key interaction designs.
Build the interface and the systems behind it in manageable pieces. Review working functionality as the project takes shape.
What to prepare: Agreed designs, sample data and access to required services.
Working output: A working implementation for review.
Try ordinary tasks and awkward cases: an incomplete form, a slow connection, a narrow screen or a failed request. Review content and accessibility alongside functionality.
What to prepare: Realistic scenarios and feedback from the people who will use it.
Working output: Reviewed journeys and a record of fixes.
Prepare hosting, domains, production settings and release checks. Review what needs to be managed and how the project will be handed over.
What to prepare: Approved content, deployment access and release decisions.
Working output: A deployed version and agreed handover materials.
Keep a clear route for feedback and future improvements. Agree support needs, maintenance responsibilities and any next phase around the project.
What to prepare: Feedback, changing needs and operational priorities.
Working output: An agreed list of fixes or next improvements.
Before work begins
Define what is included, what depends on external services and what can wait for a later version.
Agree how designs and working features will be reviewed, who makes decisions and how changes affect scope.
Choose a practical way to share updates, questions and feedback. The approach should fit the project and the people involved.
Discuss hosting, accounts, documentation and maintenance responsibilities. Support arrangements are agreed for each project.
Schedules and support arrangements depend on the agreed scope, content readiness and integration requirements.
From a business problem to a working solution
A clear brief or an idea that needs shaping. Let’s find the useful next step together.
Tell us about your idea