MVP vs full product: what to build first

What an MVP is and isn’t, when to build one and when to build more, how to decide what goes in the first release, and what an MVP costs and takes.

A pencil resting on hand-drawn wireframe sketches
Photo: Vitalii Abakumov on Unsplash

Every founder with a product idea faces the same choice: build the whole vision now, or build something smaller first. The answer depends less on budget than on how much you already know about what your users will actually do.

What an MVP is, and isn’t

A minimum viable product is the smallest useful product that real people can use, built to test the assumptions that matter most. It isn’t a cheap or broken version of your product.

  • It isn’t every feature done badly, a demo that can’t handle real users, or code you will have to rewrite to grow
  • It is the core job done properly, with real sign-up, real data and, where it matters, real payments
  • It is a foundation the next release builds on

When to start with an MVP

  • You haven’t yet seen real people use the product, or pay for it
  • You are unsure which features matter most
  • You want to spend on what users actually need first, and keep the budget for what the evidence supports
  • You need something live to show customers, partners or investors

When to build more from the start

  • You are replacing a system people already use, and they can’t go back to the old one. The first release has to cover the work they do today
  • Rules or regulation require certain features before anyone can use it
  • You have already validated demand, for example with a waitlist or an earlier version, and know what users need

Even then, the work is still released in stages. “Full product” rarely means everything at once. It means a larger first release.

How to decide what goes in

For each feature, ask one question: does a user need it to do the core job on day one? Take a clinic booking app. Booking an appointment, seeing available times and getting a confirmation by SMS are needed on day one. Deposits, patient accounts, doctor ratings, video consultations and loyalty points can wait for evidence.

How an MVP becomes a product

  1. AssumptionsWritten downWhat has to be true for the product to work
  2. MVPUsually 10 to 16 weeksThe smallest product that tests the riskiest ones
  3. Real usersAfter launchBehaviour and feedback, not opinions
  4. Next releasePlanned and priced separatelyBuilt on what the evidence supports

What an MVP can’t do

An MVP doesn’t guarantee product-market fit. It gets you real evidence sooner and cheaper, which is the next best thing.

What it costs and how long it takes

Our SaaS MVPs are typically priced at ₦2.5m to ₦5m, and most we would recommend fit in ten to sixteen weeks. If yours doesn’t, that is usually a sign the scope should be cut, and we will help you cut it. If the idea is still open, product discovery usually takes two to four weeks, and you keep everything it produces, whether or not we build the product. Read how much it costs to build a SaaS product for the full picture.

See digital product development, or tell us about your idea. The first conversation is free.

Have a problem worth solving?

Tell us what you’re trying to build. We reply to every serious enquiry within two working days.

Prefer to talk first? Call +234 803 262 3702 or email info@tekoraservices.com