Skip to content
ADVIQ LABS
All insights

Product3 min read

Scoping an MVP: what to cut, what to keep

Most MVPs run late because they were never minimal. A practical way to find the one loop your product must nail, and a list of things you should not build yourself.

ALBy the Adviqlabs team

Almost every founder we speak to says they want an MVP. Then the feature list arrives: onboarding, a dashboard, notifications, team accounts, a mobile app, an admin panel, integrations with three tools, and "some AI". That is not a minimum viable product. That is version three.

Scope is the single biggest lever you have over cost and launch date. Here is the process we use to get it right before any code is written.

Start with the job, not the features

Write one sentence in this shape:

When [situation], a [type of user] wants to [do something], so they can [outcome].

For example: When a small clinic gets a cancellation, the front desk wants to fill the slot from a waiting list in under a minute, so they don't lose the revenue.

If you can't write this sentence, you're not ready to build. If you can write three different ones, pick one. An MVP that serves two jobs usually serves neither well.

Map the core loop

The core loop is the smallest sequence of steps that delivers the outcome in that sentence. For the clinic example:

  1. A patient joins the waiting list
  2. A slot is cancelled
  3. The front desk sees matching patients
  4. One tap sends an offer
  5. The patient accepts and the slot is filled

That is the product. Everything else either supports this loop or waits.

Sort everything into three lists

Take your full feature list and put every item into one of these:

NowLaterNever (for now)
Required for the core loop to work end to endMakes the loop nicer, faster or more scalableNice ideas with no link to the loop
Waiting list, slot matching, offer message, accept flowAnalytics, bulk import, calendar syncMobile app, loyalty points, chatbot

Be ruthless with the "Now" column. A useful test: if we launched without this, would the first ten users still get the outcome? If yes, it moves to "Later".

Don't build what you can rent

A surprising amount of MVP budget goes into rebuilding solved problems. For a first version, lean on proven services:

  • Authentication: Auth.js, Clerk or Supabase Auth instead of a custom login system
  • Payments: Stripe or Razorpay Checkout instead of a custom billing engine
  • Email and SMS: Resend, Postmark or a local SMS gateway
  • Admin: a database GUI or a simple internal page instead of a full admin product
  • File storage: S3-compatible storage with signed URLs
  • Search: Postgres full-text search before reaching for a dedicated search service

Each of these saves days to weeks. You can replace any of them later, once you know it matters.

Decide what "working" means

Before development starts, agree on how you'll judge the MVP. Keep it to one or two signals, for example:

  • Ten clinics use it for four consecutive weeks
  • At least half of cancelled slots get refilled through the product

This keeps everyone honest when someone suggests "just one more feature" in week five.

Things that are not optional, even in an MVP

Minimal doesn't mean careless. Some foundations are cheap now and very expensive later:

  • A sensible data model, with multi-tenancy designed in if you'll have multiple customers
  • Environment separation (staging and production)
  • Automated backups and a tested restore
  • Basic error tracking so you hear about bugs before users email you
  • Access control that matches who should see what

What a good scope document looks like

At the end of scoping you should have a short document, usually two to four pages, covering:

  1. The job sentence and the target user
  2. The core loop, step by step
  3. The "Now / Later / Never" lists
  4. Services you'll rent rather than build
  5. Success signals for the MVP
  6. Known risks and open questions
  7. An estimate and a milestone plan with a demo each week

If a development partner starts building without something like this, you're paying them to discover your scope as they go. That's the most expensive way to find it.


Planning an MVP? We run scoping as the first step of every engagement. Book a free call and bring your feature list; we'll help you find the loop.

Start a project

Have a product in mind? Let's scope it together.

Book a free call. We'll talk through your idea, suggest the leanest path to launch and follow up with a written proposal.