All services

Build & Engineering

Rapid Prototyping & PoC

Four weeks to a decision, not a demo reel.

4 wks
Fixed timebox
1 KPI
Agreed before kickoff
Real data
No synthetic showcase

The problem we solve

A prototype should answer one question: is this worth building properly? We run tightly scoped four-week builds on real data, with the success measure and the kill criterion agreed before we start.

What the work includes

Scoping and success criteria

One question, one metric, one threshold — written down and signed before a line of code.

Production-shaped build

Real data, real permissions and real latency, so the results transfer to a full build.

User testing

Sessions with the people who would actually use it, capturing where trust breaks.

Scale-up costing

An engineering estimate and run-cost model for the production version, based on what the prototype measured.

How the engagement runs

A sequence you can plan a quarter around.

  1. 01

    Week 1

    Scope lock, data access, success criteria and architecture sketch.

  2. 02

    Weeks 2–3

    Build and iterate with mid-point review and user testing.

  3. 03

    Week 4

    Measurement, costing and the go/no-go readout.

Common questions

Before you commit.

What happens to the prototype code?
You keep it. Where it is sound we carry it into the production build; where it is not we say so.
Can it go straight to users?
Only after hardening. A prototype is scoped to answer a question, not to carry production traffic.

Talk through rapid prototyping & poc.

A 45-minute briefing with the people who would run the work — scope, timeline and a straight answer on whether it is the right next step.

Book a briefing