We design and build digital products people want to use.

1. 01

   Discover

   Days, not weeks

   We learn the business before the product: who this is for, what they do today instead, and what has to be true for it to be worth building.

   You receive

   A written summary of the problem, the users and the constraints, in your words and ours.

   Together

   One or two working sessions, plus whatever you already have — decks, spreadsheets, an existing app.

   Decision

   Is this the right problem, and are we the right people for it?

2. 02

   Define

   1–2 weeks

   We turn the problem into a scope: the first release, what it excludes, how it is sequenced, and what it costs.

   You receive

   Feature list split into release one and later, user flows, a technical approach, an estimate and a schedule.

   Together

   You review the scope line by line. Anything you cut here costs nothing; cutting it later costs the build.

   Decision

   Scope, price and timeline signed off before any design starts.

3. 03

   Design

   2–4 weeks

   Wireframes first, so the structure is argued about while it is still cheap. Then interface design, and a system to keep it consistent.

   You receive

   Full screen designs, a design system, and a clickable prototype you can hand to a real user.

   Together

   Shared Figma from day one. Review rounds are scheduled, not open-ended — usually two per flow.

   Decision

   Designs approved. What is drawn is what gets built.

4. 04

   Build

   Set in stage 02

   Design, mobile, web and backend built by the same people, in slices you can open and use rather than a single delivery at the end.

   You receive

   Working builds on a regular cycle — a test app on your phone, a staging URL in your browser.

   Together

   A written update every week: what shipped, what is next, what is blocked. Questions answered same day.

   Decision

   Each slice reviewed as it lands, so the last week holds no surprises.

5. 05

   Launch

   1–2 weeks

   Store submission, hosting, domains, monitoring and analytics — and the rehearsal that makes release day uneventful.

   You receive

   The product live, in your own accounts, with handover documentation and the keys in your name.

   Together

   We handle review feedback and rejections. You pick the date.

   Decision

   Go live, on a day that suits your business rather than our calendar.

6. 06

   Improve

   Ongoing

   Most of a product’s life happens here: fixes, OS and SDK updates, and the next version shaped by what real usage shows.

   You receive

   An agreed response time for issues, and a roadmap revisited with you each cycle.

   Together

   Ongoing, on a retainer or per release — whichever fits how you plan.

   Decision

   What the next version is for, decided on evidence rather than instinct.

Durations describe the shape of a typical project. The dates that bind us are the ones agreed in writing at stage 02, per project.