Process

Scope first, then visible progress every week

The same four steps run on every engagement. You always know what is being built, what it costs and what is done.

  1. 01

    Scope the risk

    We clarify the user, outcome, constraints and technical risk before estimating. You receive a written scope.

    Output: Scope document and estimate

  2. 02

    Design the product

    Flows, prototype, data model and architecture are decided together before engineering starts.

    Output: Prototype, architecture, delivery plan

  3. 03

    Build in visible increments

    You see working software every week. Scope changes and trade-offs stay explicit.

    Output: Weekly demo of working software

  4. 04

    Launch and measure

    Release, analytics and the first iteration cycle, with code and infrastructure in your accounts.

    Output: Release, analytics, handover

What stays true across every project

  • You work directly with the people building the product.
  • Scope is agreed in writing before build.
  • Every week ends with something you can open and use.
  • Repositories, cloud accounts and infrastructure belong to you.

Tell us what you want to build.

Share the product, stage and constraints. We will reply with the next useful step.

Get scope & estimate