Материалы журнала опубликованы на английском языке. Русская версия сайта

StrategyMVP · SCOPE · EVIDENCE

MVP Development: How to Scope a First Release That Proves Something

How to scope a minimum viable product: choose one risky assumption, build one complete loop, decide the evidence in advance, and plan the timeline and budget of a first release.

The short answer

An MVP is the smallest release that lets real users complete one valuable job and lets you measure what happened. It is not a cheaper version of the full product. Choose one risky assumption, build one complete loop around it, keep the experience credible, and decide in advance which result means continue, change or stop.

Weighing this for your business? Request a project review

Illustration: MVP Development

Our take

Axiom Forge uses MVP to mean minimum viable evidence. We keep the customer-facing journey polished and deliberately limit roles, integrations and automation until real usage shows where the product needs depth.

Gevorg AntonianFounder & CEO, Axiom Forge
In this article6 sections · 4 min

An MVP is an experiment with a product attached

Eric Ries defined the minimum viable product as the version that allows a team to collect the maximum amount of validated learning about customers with the least effort. The word that matters is learning. A first release that teaches you nothing is only a small product.

Public-sector delivery guidance draws the same line. The UK government’s service manual separates discovery, where a team learns about the problem, from alpha, where it tries different solutions, before anything is built to last.

Choose one complete loop

A loop has a trigger, an action, an outcome and an exception path. For a booking product: a customer finds a slot, books it, pays, receives a confirmation, and can cancel. If any link is missing, nobody completes the job and there is nothing to measure.

One loop done properly is more convincing to users and investors than five features that each stop halfway.

What a first release keeps and what it postpones

Reducing scope does not mean lowering quality. It means choosing where depth is needed now.

Scope decisions for a first release
KeepPostpone
One primary user roleSecondary roles and a full permissions matrix
One payment method that works end to endEvery local payment option
Manual back-office steps done by your teamAutomation of rare cases
Analytics for the core loopDashboards for every metric
A polished core journeySettings, themes and edge-case screens

Decide the evidence before the build

Write down what you expect to see and what you will do in each case. How many users should complete the loop? How many should return within a month? What price should they accept? Without thresholds agreed in advance, any result can be read as success.

Instrument the product for these questions from the first day. Analytics added after launch can only describe the weeks that follow.

Timeline and budget

A focused first release with one loop can ship from about four weeks when the scope is fixed in writing and decisions are made quickly. In our planning bands that is $15,000 to $40,000 for a mobile product. A web first release falls in the business-website band of $8,000 to $25,000 when the loop is simple, and in the web-platform band, from $25,000, once it needs accounts, payments and workflows.

When the uncertainty is in the idea itself, start smaller: a clickable prototype tested with real users costs a fraction of a build and can save all of it.

After the MVP: continue, change or stop

The MVP ends with a decision. Continue when the loop works and people come back. Change direction when users want a different job done. Stop when the evidence says the problem is not worth solving.

All three are good outcomes. The bad outcome is a year of building on an assumption nobody tested.

Discuss your project with the founder

Questions leaders ask

How long does it take to build an MVP?

A focused first release with one complete loop can ship from about four weeks when the scope is fixed in writing. Products with several roles, integrations or regulated data take longer.

How much does an MVP cost?

In our planning bands, a mobile MVP is $15,000 to $40,000. A web MVP is $8,000 to $25,000 when the loop is simple and above $25,000 once it needs accounts, payments and workflows. A clickable prototype for testing an idea with users costs less and is often the right first step.

Should an MVP be a mobile app or a web app?

Choose the format in which your users can complete the core job with the least friction. Many first releases are responsive web products, because they need no store review and can change daily.

Sources

  1. The Lean Startup — Principlestheleanstartup.com (opens in a new tab)
  2. GOV.UK Service Manual — How the discovery phase worksgov.uk (opens in a new tab)
  3. GOV.UK Service Manual — How the alpha phase worksgov.uk (opens in a new tab)
  4. Eric Ries — Minimum Viable Product: a guide (2009)startuplessonslearned.com (opens in a new tab)

How Axiom Forge can help

Turn the guidance into an accountable product plan.

Axiom Forge connects product direction, UX, design and engineering for websites, apps and AI systems. Start with the business outcome, the people who must use the product and the operating constraints behind it.

Founder-led review · NDA on request · No obligation

See services and starting prices

Write to us

Email us — we reply in English, Russian or Armenian.

Our time now:

Analytics preferences

We use Google Analytics and Google Ads to understand which pages help visitors and to measure enquiries. Form contents and personal details are never sent to them.