MVP, MLP, MMP and SLC Launch Planner

Pick an MVP, MLP, MMP or SLC strategy, score features by priority, impact and effort, add validation methods and risks, and export a launch plan.

The interactive tool loads here when JavaScript runs.

About this tool

What is the MVP, MLP, MMP and SLC Launch Planner?

This planner helps you decide what goes into your first release. Five tabs walk through it: Framework (choose MVP, MLP, MMP or SLC), Product (name, description, target users, core value, timeline, budget), Features (each with a MoSCoW-style priority, impact and effort), Validation (methods, success metrics, risks) and Report.

Auto-Prioritize sorts the feature list with a simple score, and a recommendation box warns when the must-have list is too long for the framework you picked. The Report tab totals must-have features, validation methods, success metrics and risks, writes a short executive summary and downloads it as Text, Image or PDF.

Each framework has a Load Sample button with a complete example plan, from a meditation app (MLP) to a code review platform (SLC). The plan autosaves in your browser under the key ilp-planner; nothing is uploaded.

  • Four launch frameworks with focus, best-for and priority notes
  • Feature list with priority, impact and effort plus Auto-Prioritize
  • Scope warnings based on the number of must-have features
  • Validation methods, success metrics and risk lists
  • Report with Text, Image and PDF export; browser autosave
Read the guide: MVP vs MLP vs MMP vs SLC: Choosing What to Launch First

Updated

How to use the MVP, MLP, MMP and SLC Launch Planner

  1. On Framework, select MVP, MLP, MMP or SLC; read the Best for and Focus lines, or click Load Sample to see a full example.
  2. On Product, enter the name, description, target users, core value, timeline and budget.
  3. On Features, click Add Feature for each one and set Priority, Impact and Effort; click Auto-Prioritize to sort the list.
  4. On Validation, tick the methods you will use and add success metrics and risks with the Add buttons.
  5. Open Report to check the totals and summary, then download it with Text, Image or PDF.

Worked example

How Auto-Prioritize scores three features

Input

Simple Task Creation: must-have, high impact, low effort
Priority Indicators: must-have, medium impact, low effort
Calendar Sync: should-have, high impact, high effort

Output

21, 19, 16 (sorted in that order)

Score = priority x 3 + impact x 2 + ease. Must-have is 4, should-have 3, could-have 2; impact high 3, medium 2, low 1; ease is 3 for low effort, 2 for medium, 1 for high. So 4x3 + 3x2 + 3 = 21, 4x3 + 2x2 + 3 = 19 and 3x3 + 3x2 + 1 = 16. Priority carries the most weight.

Background and insight

The four labels describe different bets. MVP, a term coined by Frank Robinson in 2001 and popularised by Eric Ries's The Lean Startup, is the smallest thing that lets you learn whether your core hypothesis is true. It can be rough, because its job is learning. MMP, from the minimum marketable feature idea in Denne and Cleland-Huang's Software by Numbers, is the smallest release that customers will actually pay for. MLP, a phrase associated with Brian de Haaff of Aha!, argues that a first product must be loved, not just tolerated. SLC, from Jason Cohen's 2015 essay, asks for something Simple, Lovable and Complete: small in scope, but finished for the job it does.

The timeframe badges in the tool (1-3 months for an MVP up to 4-8 months for SLC) and the sample plans are rough defaults. Cohen's point about SLC is that it should be small, like a skateboard rather than a car without wheels, so do not read the longer badge as permission to build a large product. The right framework depends on what you need from launch: learning (MVP), revenue (MMP), word of mouth (MLP) or a narrow job done completely (SLC).

Feature scoring uses MoSCoW priorities (must, should, could), a method developed by Dai Clegg and later adopted by DSDM, combined with impact and effort. It is a sorting aid. Two must-have features with the same score still need a human decision.

Common use cases

  • Cutting scope before a build

    List every feature anyone has asked for, mark priorities honestly, and let the must-have warning force the conversation.

  • Choosing a launch strategy

    Compare frameworks with the Best for lines and the samples before committing to an MVP by default.

  • Planning validation alongside the build

    Decide which experiments and metrics will judge the launch before the first line of code.

  • Briefing a contractor or agency

    Export the report as a short scope document with the must-have list, timeline and budget.

Tips and limitations

  • If more than eight features are marked must-have, the planner warns you. Most first releases need three to five.
  • Choosing a framework other than MVP with fewer than three must-haves triggers a hint to consider an MVP instead; that is advice, not an error.
  • Success metrics should have a number and a time window, for example 100 weekly active teams within 60 days.
  • Load Sample replaces your current plan. Download a report first if you want to keep your own.
  • Auto-Prioritize only reorders features; it never changes their priority, so re-check the bottom of the list by hand.

Sources and further reading

  1. What is a Minimum Viable Product (MVP)?, SyncDev. Frank Robinson's firm, which coined the term in 2001
  2. The Lean Startup: Methodology, The Lean Startup. Eric Ries on the MVP as a tool for validated learning
  3. The Minimum Lovable Product (Forget the MVP), Aha!. Brian de Haaff's 2013 case for the MLP
  4. Your customers hate MVPs. Make a SLC instead., A Smart Bear. Jason Cohen's essay that proposed Simple, Lovable, Complete
  5. MoSCoW Prioritization Template and Poster, Agile Business Consortium. The DSDM body that maintains the MoSCoW method

Frequently asked questions

What is the difference between an MVP and an MLP?

An MVP is the smallest product that tests your core hypothesis and can be rough; an MLP is the smallest product people will love using. Choose an MVP when the main risk is whether the problem is real, and an MLP when the market is crowded and the experience is the reason to switch.

What does SLC stand for in product development?

SLC stands for Simple, Lovable, Complete, a term from Jason Cohen's 2015 essay. It describes a first product that is small, pleasant to use and finished for the one job it does, as an alternative to an MVP that customers experience as broken.

What is a minimum marketable product?

A minimum marketable product is the smallest release that customers will pay for and that can be sold as it is. It sits after the MVP: the hypothesis has been validated, and the goal shifts from learning to revenue.

How does the Auto-Prioritize button rank features?

It sorts by a score of priority x 3 + impact x 2 + ease, where must-have is 4, should-have 3 and could-have 2, impact runs 3 to 1, and ease is 3 for low effort down to 1 for high. The maximum is 21.

How many must-have features should an MVP have?

Usually three to five. The planner warns above eight, because past that point a release is rarely minimal. If everything feels essential, ask which features a customer would miss in the first week and move the rest to should-have.

Where is my launch plan saved?

In your browser's local storage under the key ilp-planner. It survives reloads on the same device and is never uploaded. Use the Report tab's Text, Image or PDF download to share or archive it.

Is there an in-depth guide to the MVP, MLP, MMP and SLC Launch Planner?

Yes. “MVP vs MLP vs MMP vs SLC: Choosing What to Launch First” covers the background, how it works, common pitfalls and worked examples. Read the full guide.