Approach

How a project runs, phase by phase.

Short cycles, with AI agents on the execution and a person at every gate. Each phase ends with something you can read, click or test, and you approve it before the next one starts.

Phases

The six phases in detail

  1. Discover

    We talk to the people who sell and support the product, then agents help read the analytics, the search data and the current site (content, structure, speed, accessibility, code) so the findings come back quickly. A person decides what they mean.

    Outputs Discovery notes · Audit of the current site · Risks we can see

  2. Define

    The sitemap and URLs, the page templates, the content model and the route to the contact form. Scope and dates are fixed at the end of this phase.

    Outputs Sitemap and templates · Content model · Dated plan

  3. Design

    Type, grid, colour, components and motion, applied to the key templates. You review them as real pages on your own phone as early as we can manage.

    Outputs Design system · Key templates · Motion rules

  4. Engineer

    Accessible, fast code with structured data and analytics events. Agents write and test much of it against the agreed architecture; a person reviews every change before it is merged. Browser tests and audits run on each build so regressions show up before you see them.

    Outputs Staging site · Test suite · Audit reports

  5. Launch

    Old URLs are redirected, search console and analytics are verified, and we go through the launch checklist together. We watch the first week closely.

    Outputs Launch checklist · Redirect map · Handover notes

  6. Improve

    New pages from the existing templates, content and conversion fixes, experiments where there is enough traffic, and regular checks on speed and accessibility.

    Outputs Backlog · Experiment notes · Health checks

Ways to work together

Three ways to hire us

Prices are set per project after a scoping call. There is no rate card.

  • Scoping sprint

    A short, fixed piece of work: an audit, an architecture or a prototype of the risky idea. It ends with a written recommendation you can take to any studio.

  • Project

    A defined scope delivered through the six phases, for a fixed price agreed in the proposal.

  • Ongoing work

    Continued design and engineering on a site or product after launch, on terms agreed in writing.

Quality

What we mean by done

  • Speed

    Core Web Vitals measured on the devices your visitors use, not only on a fast laptop.

  • Accessibility

    WCAG 2.2 AA. Automated audits first, then keyboard and screen-reader passes by hand.

  • Search

    A unique title and description per page, canonical URLs, structured data that matches the page, no orphan pages.

  • Maintenance

    The code and the content model are documented, so your team or another studio can take over.

FAQ

About the process

All questions

How does a project run?

In six phases: discover, define, design, engineer, launch, evolve. Each one ends with something you review and approve. Approach describes them.

What happens after I send a brief?

We read it, ask about anything missing, and if it looks like a fit we suggest a call to scope it. If we’re not the right studio, we say so and, where we can, suggest who might be.

How much of our time will it take?

Most at the start and at each review. Between reviews it’s our job. One person on your side who can make decisions saves more time than anything else.

Fixed price or day rate?

Fixed price when the scope is clear. Time and materials for open-ended work such as prototypes or ongoing iteration. The proposal says which and why.

We have a fixed date. Can you hit it?

Tell us the date in the brief. If the scope fits, we plan backwards from it. If it doesn’t, we’ll say what can realistically go live by then.

Ready to describe the project?

Tell us what you need and by when. We read every enquiry and reply in writing, with questions, a next step, or a plain no if we’re the wrong studio.