Skip to main content

Proof of concept / MVP

Answer the hard questions before you fund a full build

We build a focused piece of working software to test the assumption that matters most. You learn whether the technology works, the available data is useful and people can complete the task before making a larger investment.

Task approval phone prototype connected to wireframes and user-test observations — AI-generated illustration

Is this where you are now?

Know what you need to prove before spending more.

An idea can sound convincing while leaving the most important questions unanswered. We agree what needs to be proven and build only enough to test it properly, without pretending it is already a finished product.

For an early product idea or an uncertain technical approach. A proof of concept is not automatically production-ready; security, scale and support needs for a full launch are assessed separately.
See our delivery experience

What you receive

Working evidence for your next investment decision.

We agree the scope around your system and the people who use it. Your project can include:

Deliverable 01

An agreed question to test and clear success criteria

Deliverable 02

Working software limited to the chosen functionality

Deliverable 03

Documented findings from technical tests or user evaluation

Deliverable 04

A recommendation on whether to proceed, revise the idea or stop

How we work

Turn an assumption into something you can test.

  1. 01

    Choose the question

    Choose the assumption that matters most to the investment decision.

  2. 02

    Keep the build focused

    Define the smallest build that can test it meaningfully.

  3. 03

    Test the idea

    Evaluate the software with relevant data, users or system connections.

  4. 04

    Decide what comes next

    Review the findings and what a production version would still need.

Getting started

Bring us what you already know.

Start with the problem, the people affected and any useful notes about your system. We will help you identify what needs attention and set out the work, timescale and responsibilities before the project begins.

Tell us what your software needs to do.

Tell us what is not working, what needs to change or what you need to build. We’ll help you work out the next step.

Discuss a project