How we work

No black boxes. No surprises.

How a project with us actually runs, from the first message to launch and beyond. Read it before you talk to us, so the first call is about your product, not our process.

  • 01Fixed scope before we start
  • 02Working demo every week
  • 03You own every line of code
Ways to work with us

Three engagement models, one standard.

01Most common

Fixed-scope project

Best for

A defined product or feature with a clear goal.

How it works

Scope, price and timeline agreed up front. Change requests are priced before they’re built.

02

Dedicated team

Best for

Ongoing product work with a changing roadmap.

How it works

A small team works as an extension of yours, planning in weekly cycles against your priorities.

03

Support & iteration

Best for

Products already live that need care and improvement.

How it works

Monitoring, fixes and a steady flow of improvements, planned month by month.

The process

Five phases, start to finish.

01

Discover

We dig into the problem, the users and the constraints, and decide what v1 genuinely needs.

You get

  • Written scope and priorities
  • Fixed cost and timeline
  • Risks flagged up front

Your part

A call and access to the people who know the problem.

02

Design

Flows, interfaces and architecture are designed together, then tested as a clickable prototype.

You get

  • User flows and wireframes
  • High-fidelity UI
  • Clickable prototype

Your part

Feedback in short review rounds.

03

Build

We build in the real production codebase, with tests and CI from day one, and demo it every week.

You get

  • Weekly working demos
  • Code reviews on every change
  • Automated tests and CI

Your part

Thirty minutes a week to review the demo.

04

Launch

Deployed to production with monitoring in place, then handed over in full.

You get

  • Production deployment
  • Monitoring and alerts
  • Full handover pack

Your part

Go-live sign-off.

05

Grow

Real usage shows what to improve next. We stay on if you want us, and step back cleanly if you don’t.

You get

  • Improvement roadmap
  • Ongoing fixes and features
  • Optional support plan

Your part

Only what you choose.

Getting started

What happens after you get in touch.

  1. First

    You get in touch

    A short form or a booked call. Tell us what you’re building, in your own words.

  2. Next

    Discovery call

    We ask a lot of questions and tell you honestly if we’re not the right fit.

  3. Then

    Written proposal

    Scope, price, timeline and team, in plain language, before you commit to anything.

  4. Kickoff

    Work starts

    Shared channel set up, first priorities agreed, first demo date in the calendar.

At handover

Everything is yours. Literally everything.

No lock-in and no hostage code. At launch you get the whole project, organised so your own team, or another agency, can pick it up without us.

your-product/
  • ├─source-code/Full repository, in your GitHub or GitLab
  • ├─infrastructure/Cloud accounts and config, owned by you
  • ├─design/Figma files and the design system
  • ├─docs/Architecture, setup and runbooks
  • ├─credentials.mdEvery account and key, transferred to you
  • └─roadmap.mdWhat we’d build next, and why
Communication

You’ll always know where things stand.

01

A shared channel

Slack, WhatsApp or Teams, whichever you already use. You talk to the builders directly.

02

Weekly demo

Working software on screen, not a slide deck. Feedback goes straight into the next week.

03

Visible board

Every task and its status in one place you can check any time.

04

Honest updates

If something slips or costs more, you hear it immediately, along with the options.

Questions

About the process.

It usually does, a little. We price each change before building it, so you decide whether it’s worth it. Nothing gets added to the invoice by surprise.