← Solutions
ApplicationPopular

MVP build

From validated idea to a production-grade minimum viable product in front of real users, built on foundations you will not have to throw away.

Typical timing
10–14 weeks
Engagement
Fixed scope
Delivery framework
User researchDiscoveryAlphaBetaLive
Discuss this solutionApplication capability →

Objective

Put the smallest product that proves the proposition into the hands of real users, fast, without taking on the technical debt that usually comes with speed. You leave with working software, evidence about what users actually do, and an architecture that can carry version two.

You may need this if

  • You have a funded idea and need evidence before committing a full build budget
  • A prototype exists but was never built to run in production
  • Investors or a board want traction data, not a slide
How it runs

Activities, step by step

The plan follows our delivery framework. Steps that do not apply to this kind of work are left out rather than padded.

  1. 01 · User research1–2 weeks

    Problem and user validation

    • Interviews with target users to confirm the problem is worth solving
    • Competitor and alternative-solution scan
    • Success measures agreed before anything is designed
  2. 02 · Discovery2 weeks

    Scope the thinnest valuable slice

    • Story mapping to cut scope to the core journey
    • Clickable prototype tested with five to eight users
    • Architecture, stack and hosting decisions recorded
  3. 03 · Alpha4–6 weeks

    Build the core journey

    • Fortnightly increments on a live pipeline from week one
    • Automated tests, security scanning and code review on every change
    • Private alpha with a small test cohort
  4. 04 · Beta2–3 weeks

    Harden and widen

    • Accessibility, performance and security testing
    • Analytics and product telemetry wired in
    • Private beta with a wider cohort
  5. 05 · LiveFirst 2 weeks live

    Launch and learn

    • Production release with rollback rehearsed
    • Measure behaviour against the agreed success measures
    • Evidence-backed backlog for version two

Scope flexes, the date does not: anything that does not fit lands on the version-two backlog.

Deliverables

What you keep at the end.

  • Production MVP, deployed to your cloud account
  • Source code, infrastructure as code and CI/CD pipeline you own
  • Tested prototype and research findings
  • Architecture decision records and runbook
  • Launch metrics dashboard
  • Prioritised backlog for the next release

Outcomes

What it is built to change.

  • Evidence of real user demand, in numbers
  • A product that can scale rather than be rebuilt
  • A confident go / pivot / stop decision for the next investment

Often combined with

Every engagement starts with a 45-minute working session with the SME who would own the work. No deck.

Discuss MVP build