Start a project
Menu

Strategy

Scoping an MVP you can launch in twelve weeks

How to cut a first release down to the one journey that proves the idea, decide what to fake, and set a date the whole team believes in.

By Aumair Malik6 min read

Published:

An MVP that takes a year is not minimal. Twelve weeks is long enough to build something real and short enough to keep the team honest about scope.

Find the one journey that matters

Write down the single path a user takes to reach the core value. Everything off that path waits for the second release.

Decide what to fake

Manual steps behind the scenes, a spreadsheet instead of an admin panel, an email instead of a notification center: fake what users never see.

Fix the date, flex the scope

Agree the launch date first and treat scope as the variable. Weekly demos show early what will not make it, while there is still time to choose.

Plan the first month after launch

  • Which numbers decide what comes next
  • Who talks to the first users
  • What the team fixes before building more

Start a project

Got an idea worth building?

Share a few lines about what you have in mind and we'll reply with next steps.