Skip to content
How we work

A clear process, from idea to launch.

Five phases, each with a defined outcome. You always know what happens next, what it costs and what you will receive.

Discover1–2 weeksDesign2–4 weeksBuild6–12 weeksLaunch1–2 weeksSupportOngoing5 phases, no surprises
Five phases

What happens, and when.

Typical timings for a first release. We confirm yours at the end of discovery.

  1. 1
    1–2 weeks

    Discover

    We learn your business, users and goals, review what exists and agree what success looks like.

    You receive
    • Scope and priorities
    • Risks and assumptions
    • Fixed quote and timeline
  2. 2
    2–4 weeks

    Design

    We map user journeys, sketch wireframes and design the interface, testing it with real users.

    You receive
    • User flows
    • Clickable prototype
    • Design system
  3. 3
    6–12 weeks

    Build

    We develop in two-week sprints with automated tests, and you review a working build after each one.

    You receive
    • Staging link from week one
    • Sprint demos
    • Release notes
  4. 4
    1–2 weeks

    Launch

    We deploy to production, publish to app stores if needed, and train your team.

    You receive
    • Go-live plan
    • Store submissions
    • Training and handover
  5. 5
    Ongoing

    Support and grow

    We monitor, fix and improve the product as your users and business grow.

    You receive
    • Monitoring
    • Agreed response times
    • Roadmap for next releases
Ways to work with us

Three engagement models. Choose what fits.

We recommend a model after discovery, based on how clear the scope is and how long the product will run.

Fixed scope

Best for: Clear requirements and a set budget

We agree scope, price and timeline after discovery. Changes go through a simple change request.

Dedicated team

Best for: Long-running products

A team of designers and engineers works on your product full time, at a fixed monthly rate.

Team extension

Best for: Adding skills to your team

Our specialists join your team for a specific need, such as mobile, computer vision or QA.

On every project

How we keep projects on track.

Communication

A named project manager, a weekly status update and a shared channel with your team.

Quality

Code review on every change, automated tests and a QA pass before each release.

Security

Access controls, encrypted secrets and security checks built into development.

Documentation

Architecture notes, API documentation and release notes that your team can use.

Ready to start? Discovery is the first step.

Tell us about your project and we’ll suggest a scope, timeline and engagement model.

Start a projectView our work