Try it before we build it.

Apps for your customers, websites and online stores, and the tools your team runs on. Designed around the people who'll use them, built by the same team, and looked after once they're live.

The standard it's built to. What every product we ship has to meet, and how you can check it yourself.

  1. 01

    Tried before it's built

    Real people use it before you pay for the build.

    • Clickable prototype
    • Usability tests

    The first version is a prototype, not code, so changing course costs a day, not a release.

    How you can check

    Click through it on your own phone.

  2. 02

    Fast on an ordinary phone

    Pages appear quickly and respond at once, even on mobile data.

    • Core Web Vitals
    • Performance budget

    We set limits for loading, responding and layout shift before the build, and measure every release against them.

    How you can check

    Google's report from real visits rates each page “good”.

  3. 03

    Usable by everyone

    It works by keyboard, with a screen reader and with larger text.

    • WCAG 2.2 AA
    • Keyboard and screen reader tests

    Key pages and flows built to WCAG 2.2 AA, checked by automated tools and then by hand.

    How you can check

    An accessibility report for each key flow.

  4. 04

    Yours from day one

    The code, designs, accounts and data are in your name.

    • Your repository
    • Your accounts

    The code lives in your repository and every service runs on an account you own. You invite us in, not the other way round.

    How you can check

    Log in as the owner of each one, from the first week.

  5. 05

    Easy to change

    Your team updates what it needs to, and each new feature builds on the last.

    • Design system
    • Content editing
    • Automated tests

    Reusable components, a place to edit text and images, and tests that run before every release, so a change in one place doesn't break another.

    How you can check

    Change a page yourself, without calling us.

  6. 06

    Measured

    You know whether it's doing the job it was built for.

    • Goal agreed first
    • Analytics

    Before the build we agree the number that shows it's working, and track the tasks people tried in the prototype.

    How you can check

    A dashboard you can open any time.

The first step

The Prototype Sprint. One question at its centre: can the people it's for do what they came to do?

  1. 01 · Design

    Shape the key flows

    The few tasks that matter most, designed for the customers and team who'll do them.

    You seeThe key flows on screen

  2. 02 · Prototype

    Make it clickable

    Every key screen linked up, so it feels like the real thing on a phone.

    You seeA link you can share

  3. 03 · Test

    Watch five people use it

    People like your customers try the key tasks. We fix where they stumble and test again.

    You seeThe prototype report

  4. 04 · Decide

    Scope the build

    What worked becomes the first release, with its timeline.

    You seeOne price for the build

What you hold at the end

A prototype report.

Each key task, what every person did, and what we changed. This sample shows the format, with tasks from the Mori Coffee case.

Sample format · tasks from the Mori Coffee case

Five people try four key tasks in a prototype. A sample of the report format, not real results.
Key taskPerson 1Person 2Person 3Person 4Person 5
Order your usualCompletedCompletedCompletedCompletedCompleted
Choose a pickup timeChanged, then retriedCompletedCompletedStumbled, then completed after the fixCompletedCompleted
Find your cup on the shelfCompletedCompletedCompletedCompletedCompleted
See your next free drinkCompletedCompletedCompletedCompletedCompleted

After the sprint. The build starts from what worked, once you've said yes.

  • Build

    Your product

    So your customers and team get something they choose to use.

    • The first release scoped in the sprint
    • Front end and back end
    • Connected to your till, accounts and bookings
    • A preview link to check every week
  • Keep improving

    Care Plan

    So it keeps getting better after launch.

    • Hosting, updates and backups
    • Monitoring, so we hear of problems first
    • Improvements every month
  • On its own

    Design handover

    Have your own developers? You get the tested prototype and files ready for them to build from.

What does it cost?

You know the price before any work starts.

  • The first step has a fixed price

    Agreed on the free call, before anything begins.

  • A build is quoted as one number

    With its timeline, once we know what's worth building.

  • We don't bill by the hour

    If something takes us longer, the price doesn't change.

Hosting and the services it runs on are billed straight to your own accounts, so you always see what it costs to run.

Book a free call

What if…

More questions? Ask us on a free call.

  • You see it as it takes shape and click through it before anything is built, so changing course is cheap.

  • Yes. We test what you have first. Often a few reworked flows do more than a rebuild.

  • One person who can make decisions, time to review each week, and help reaching a few people like your customers for the tests.

  • It depends on the first release. You get the timeline with the price, at the end of the sprint.

Tell us what should work better.

Book a free call to talk it through, or send a short brief.