Skip to main content
All engagement models

Quick service · 2 weeks

Know exactly what to build, before you fund it.

Two weeks that replace a year of expensive guessing. You leave with a clickable prototype, a scoped plan, and a fixed-price estimate you can take to your board.

Typical starting price

£6,000

Timeline

2 weeks · fixed price

Most projects begin here. Your final quote is scoped to your needs on a 30-minute call, and can land higher for a more ambitious build.

§ 01 / 07· The cost of waiting

What building on a hunch really costs

01

Six-figure rewrites

The wrong architecture chosen early is paid for, twice, at the worst possible time.

02

Months building the unwanted

Without real user input, teams ship features beautifully that nobody asked for.

03

Investors hear a guess

"We think users want this" raises far less than "here is the prototype and the data."

Where you'll be

A decision you can defend.

In fourteen days you go from an idea to a tested prototype, a scoped technical plan and a fixed-price build estimate: proof, not optimism.

§ 02 / 07· Is this you?

Built for a specific moment.

  • You have an idea and a budget, but not yet a plan you trust
  • You need something funders, partners or your team can react to
  • You want a fixed build price before you commit serious money

Straight talk · If you already have validation and a clear spec, skip ahead. Go straight to an MVP Build and keep the two weeks.

§ 03 / 07· What you walk away with

What you walk away with

Real user evidence

Five to eight interviews with the people who would actually use it, not just your stakeholders.

A clickable prototype

Something you can put in front of a customer or an investor and watch them react.

A scoped technical plan

The architecture and stack, chosen for where this scales, not just where it starts.

A fixed-price estimate

One number for the build. No open-ended hourly meter.

§ 04 / 07· How it runs

No mystery. Just the plan.

Days 1–4

Frame

We pin down the problem, the users and the real constraints, and recruit the interview cohort.

Days 5–9

Test

User interviews, a clickable prototype, and the trade-offs surfaced while they are still cheap.

Days 10–14

Scope

Architecture, stack and a fixed-price build estimate, reviewed with you line by line.

§ 05 / 07· Proof
"The sprint told us our flagship feature wasn't the one users wanted. That fortnight saved us a six-month build and the funding round that would have died with it."
NENgozi E.Co-founder · fintech
§ 06 / 07· Your safety net

Permission to walk away, with everything.

If discovery says "don't build this yet," that is a win, and you keep every artefact. Many founders use the prototype to raise before they ever commit to a build.

§ 07 / 07· Before you ask

The questions we always get.

What if discovery says don't build?
Then we've saved you a fortune. You keep the research, the prototype and the plan, and decide on your own terms.
Can the estimate change later?
The fixed-price estimate holds for the scope agreed. New scope is quoted openly before any work starts.
Do I have to build with you afterwards?
No. The sprint is standalone. The artefacts are yours to take to any team.
§ Start here

Find out what's worth building.

Book a 30-minute call with a senior engineer. We'll tell you honestly whether a discovery sprint is the right next step.