Skip to content

Service · Product validation

MVP Development

Commission a first release whose job is to answer a question: will this group of people use, pay for or come back to this product? We write down the riskiest assumption with you, cut scope to the one journey that tests it, build that journey properly, and instrument it so the evidence is clear enough to decide what happens next.

Riskiest assumption written down before features are chosen

One complete journey built to production standard

Analytics and feedback capture in place on launch day

Deliverables

What an MVP development engagement delivers.

01Delivered

Assumption and evidence plan

A one-page statement of who the product is for, the problem it solves, what they do today instead, the assumption most likely to be wrong and the signal that would confirm or refute it.

02Delivered

Scoped journey

A map of the single path from first visit to the moment of value, with everything outside it listed as deferred, so the team can say no to good ideas without relitigating them.

03Delivered

Working product

A web or mobile app covering that journey with real sign-up, real data and, where the test depends on it, real payment, built on a codebase that can be extended rather than thrown away.

04Delivered

Measurement setup

Named analytics events for each step of the journey, a funnel view, in-product feedback prompts and an export your team can analyse, all configured before the first user arrives.

05Delivered

Concierge back office

Simple admin screens that let your team do by hand what will later be automated, such as matching, approvals or fulfilment, so the MVP tests demand without building every system first.

Early decisions

Technical decisions we settle early in MVP development.

01Decided

The question the release must answer

An MVP aimed at willingness to pay looks different from one testing retention or supply. We pick one primary question so scope decisions have something to be judged against.

02Decided

What is automated and what is manual

Behind a polished front end, many first releases run on people. We decide which steps must be software for the test to be valid and which a team member can handle from a console.

03Decided

Platform for the first audience

A responsive web app reaches testers without store review; a native app may be essential if the idea relies on the camera, location or push notifications. We choose for the experiment, not for the long-term roadmap.

04Decided

Standards that are not negotiable

Small does not mean careless. Authentication, data protection, backups and basic accessibility are kept at production level, because an MVP still holds real people’s data.

05Decided

Stop, continue or change criteria

Before launch you agree what result would make you pivot, persevere or stop. Writing this down protects the decision from being rationalised after the numbers arrive.

Engagement

How an MVP development engagement runs.

  1. 01Phase 1

    Frame the bet

    A short series of working sessions produces the assumption statement, the target users you can actually reach and the evidence plan, along with a list of features that will not be in this release.

  2. 02Phase 2

    Prototype the moment of value

    We design and test a clickable version of the core journey with a handful of target users, fixing confusion before it becomes code.

  3. 03Phase 3

    Build the slice

    Engineering covers the journey end to end, including the manual console and analytics. You review working builds frequently and make scope calls quickly when trade-offs appear.

  4. 04Phase 4

    Launch to a pilot group and read the signal

    The release goes to a defined group of users. We monitor stability, fix defects, then sit down with you to read the funnel and feedback against the criteria agreed at the start.

Fit

When an MVP is the right choice.

01Good fit

You can reach your first users

You have a waiting list, a community, a sales pipeline or a partner willing to put the product in front of real people soon after launch.

02Good fit

The idea has one central bet

There is a clear assumption that, if wrong, sinks the business, and you would rather learn that from a small release than a full build.

03Good fit

Someone can make scope calls fast

A founder or product owner is available to decide what stays in and what is cut, often within the same day a question comes up.

Minimum means one question, not low quality

An MVP is often misread as a cheap version of the full product. In practice it is a precise instrument for reducing one uncertainty. The minimum is in the number of things it tries to prove, not in how well it is built. A narrow product that works reliably gives clean evidence; a broad product held together with tape gives noise, because users leave for reasons unrelated to the idea.

Choosing the riskiest assumption

Every new product rests on a stack of beliefs: that people have the problem, that they will try a new solution, that they will pay, that supply can be found, that the unit economics work. They are not equally uncertain or equally fatal. We rank them with you and design the release around the one that is both most likely to be wrong and most damaging if it is.

Sometimes the honest conclusion is that code is not the right test yet, and a landing page, a manual service or a prototype study would answer the question more cheaply. We will say so.

Doing things that do not scale on purpose

Many successful products began with people quietly doing work that later became software. An MVP can match supply to demand by hand, approve listings manually or send reports from a spreadsheet, as long as the user experience is genuine. We build a simple console for those tasks, which keeps engineering focused on the parts users touch and lets you learn which manual steps are worth automating.

Measuring without inventing success

Instrumentation is planned before the build, not added afterwards. Each step in the journey emits a named event, so you can see where people drop off, and feedback prompts appear at moments that matter. We do not set benchmarks borrowed from other products; you define what a meaningful result looks like for your market, and the data is read against that.

After the pilot

The release ends with a decision meeting. If the evidence supports continuing, the next step might be broadening the journey, automating the manual console or preparing for paid acquisition. If it does not, you will have spent far less than a full build to find out, and you keep the code, the data and the learning. Either way, the backlog of deferred features is waiting, already written down.

FAQ

Questions to resolve before the build.

01What drives the cost of an MVP?

Mainly the length of the core journey, whether real payments are involved, the number of platforms, integrations the test depends on and how much needs to be automated rather than handled manually from a console. Choosing a sharper question is the most effective way to reduce cost.

02Why will you not quote a standard MVP timeline?

Because duration depends on the journey you choose to test, how quickly decisions are made on your side and external dependencies such as app store review or payment provider approval. We give a plan once the assumption and scope are written down, not before.

03Is the MVP throwaway code?

No. We keep the codebase small but structured so it can be extended if the evidence is positive. What we avoid is building infrastructure for scale or features for users who have not yet appeared.

04Do we own the MVP code and any data it collects?

Yes. Code, design files, analytics accounts and user data belong to you, and are set up in your accounts from the start so nothing needs to be transferred when we finish.

05How do we agree the MVP is ready to put in front of users?

Acceptance covers the core journey working end to end on supported devices, the analytics events firing correctly, the admin console handling the manual steps, and no open defects that would distort the test. You sign off on staging before the pilot audience is invited.

06What does an MVP engagement leave out on purpose?

Features outside the tested journey, scaling work, extensive admin automation, multiple languages and secondary platforms unless the test requires them. User acquisition and marketing are also yours, although we help you plan how pilot users will be recruited.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
    Google Analytics 4: set up events

    How custom events are defined and sent, the basis of funnel measurement in a pilot.

  2. 02
    TestFlight

    Apple’s beta distribution service for putting iOS builds in front of pilot users before store release.

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.