Quantum Beetle

GuidesProduct launches

How to launch a first version: what an MVP is, and what it is not

A first version is the smallest product that teaches you something true. How to choose what goes in, what stays out, and what to measure after launch.

SaaS & technology · 3 min read · 10 October 2026

MVP stands for minimum viable product, and both adjectives are misread. Minimum does not mean poor, and viable does not mean finished. It means the smallest thing a real customer can use to do one real job, so that you learn whether the job is worth doing.

The purpose of a first version is to learn. Everything about its scope follows from that.

01Start from the riskiest belief

Every new product rests on beliefs: that people have this problem, that they will pay to solve it, that they will switch from what they use now. Find the belief that would sink the product if it were false, and build the least that would test it.

02One job, done properly

  • Pick one kind of user and one job they need done.
  • Make that one path complete: start to finish, with nothing missing.
  • Leave out the second kind of user, the settings and the reports.
  • Do by hand, behind the scenes, whatever is expensive to automate and rare.

A narrow product that works beats a wide one that half works. People forgive missing features. They do not forgive a product that fails at the one thing it claims to do.

03What must not be cut

  • Security of accounts and data
  • Working on a phone
  • Speed: a slow product reads as a broken one
  • A way for users to reach you
  • Measurement, so you can see what people do

04What to measure after launch

  1. Did people finish the one job?
  2. Did they come back and do it again?
  3. Where did those who gave up stop?
  4. What did they ask for, in their own words?
  5. Would any of them pay, or pay more?

05Deciding what comes next

After a few weeks of real use you will know more than any amount of planning could tell you. Extend what people used. Fix where they stopped. Drop what nobody touched, however much you liked it. The second version should be shaped by evidence, not by the original wish list.

In short

  • A first version exists to test the belief the product depends on most.
  • One user, one job, complete from start to finish.
  • Security, mobile, speed, support and measurement are never cut.
  • Let what people actually do decide the second version.

Questions

How small is too small?

Too small is when a user cannot complete the job without you standing beside them. If they can finish alone, it is big enough.

Should a first version look polished?

It should look trustworthy. Clean, consistent and quick is enough. Decoration can wait; credibility cannot.

Is the first version thrown away later?

Not if it is built on sound foundations. The scope is small; the engineering should still be something you can build on.

Can Quantum Beetle build a first version?

Yes. We agree the one job it must do, give a clear quote before work starts, and build it so the next version extends it instead of replacing it.

Sounds like your problem?

Tell us about it. We'll say honestly whether the swarm can help, and what it would take.

Talk to ushello@quantumbeetle.ai

Read next