The scoping decision that determines everything
An MVP has one job: get a real user through one valuable journey and learn from it. Every feature that is not on that journey is a delay to learning, and delayed learning is the only genuine risk at this stage.
The practical test I use is simple. Write down the single sentence describing what a user does and what they get. Anything that does not directly enable that sentence goes on a list for later. Admin panels, settings, team management, onboarding wizards, notification preferences — all of it can wait, and most of it turns out to be unnecessary once real usage arrives.
This is unpopular in the room, because every deferred item has an advocate and each one individually seems small. The compounding is what kills projects: four small additions is a doubled timeline, and a doubled timeline is where MVPs die.
How AI tooling actually changes MVP delivery
The build itself is roughly three to five times faster. Tools like Lovable, Cursor and Claude Code turn a well-specified screen into working code in minutes rather than hours, and the boilerplate that used to consume the first two weeks of a project largely disappears.
What has not changed is everything around the code: deciding what to build, judging whether the output is right, understanding the user, and getting someone to pay. Those remain human, and they remain the bottleneck. The result is that product judgement is now a larger share of the total effort than it was five years ago, not a smaller one.
There is also a specific trap. AI tools make it cheap to build, which makes it cheap to build the wrong thing at speed. A team without scope discipline will produce four half-working features in the time it takes a disciplined one to ship a single journey that works, and only the second of those can be launched.
What ships with every build
- —A live URL from week two, deployed continuously, never a local-only demo.
- —The core user journey working end to end for a real, non-technical user.
- —Analytics with an activation funnel defined before launch, not after.
- —Evaluation sets for any AI feature, so quality is measurable across releases.
- —A landing page with real pricing and a working payment or waitlist path.
- —Full ownership: your repository, your infrastructure, your accounts, no lock-in.
- —A written next-six-weeks roadmap based on what the usage data actually shows.