Schedule a call

Prove It First

Prototype Build

A prototype is not a small product. It is an instrument for answering one question cheaply: will users understand this, or will this integration actually hold. Built deliberately as throwaway, it buys you a decision for a fraction of the cost of discovering the answer halfway through a build.

Prototype an ideaAll services

When this helps

You are probably reading this because of one of these.

  • Two credible people in your business disagree, and no document will settle it
  • The business case depends on an integration nobody has tested end to end
  • You need something a user can hold before committing a build budget
  • A vendor has promised their API does something you would rather verify first

How we help

A delivery sequence, not a discovery phase that never ends.

Every stage produces something you can act on independently, so the engagement can stop at any point without leaving you stranded mid-programme.

  1. Isolate

    Name the single riskiest assumption. Everything else is deliberately left out of scope.

  2. Prototype

    Build only enough to test it - a clickable journey, a spike, or a live call against the real third-party API.

  3. Test

    Put it in front of users or run it under realistic load, and record what actually happened rather than what we hoped would.

  4. Decide

    A build-or-stop recommendation with costed options, and an honest account of what the prototype did not prove.

Delivery sequence for Prototype Build, from first contact through to handover.

Efficiencies driven

The measurable change this engagement is aiming at.

Where teams usually start

  • Confidence based on opinion and slideware
  • Integration risk discovered mid-build
  • Estimates with no evidence behind them

Where the engagement leaves you

  • A decision grounded in something people actually used
  • Integration risk proven or killed in week one
  • Estimates anchored to code that already runs
Typical before and after state for Prototype Build.

1-3 wks

To a defensible decision

1

Assumption tested at a time

Real

APIs, not mocks

What you receive

Artefacts that outlive the engagement.

  • Working prototype or technical spike, with its limits documented
  • Recorded user testing sessions and observed findings
  • Integration proof against the real third-party API, not a mock
  • Costed build options with the assumptions behind each estimate
  • Build-or-stop recommendation you can take to a board

Related

Often combined with

Integration-Heavy Transformation

Do you have multiple integrations in use within your organisation covering a digital transformation, and need expert support to modernise core services and platforms? We can help. Phased delivery is usually the lower-risk route, but where a big bang cutover is the preferred strategic call, we can still manage that transformation for you.

Read more

Technology Consultancy

Strategic advisory that aligns people, process, and platform decisions with measurable outcomes.

Read more

Next step

Prototype an idea.

A short call is usually enough to work out whether this is the right engagement, and what it would cost. If it is not, I will say so.

Schedule a call

Engagement

Prove It First

Idea to working proof

1-3 weeks