Science of Apps - Launchpad · Launch guide

How to launch an MVP:
small, fast, then iterate

An MVP is the simplest thing you can give your first users to see if you can deliver any value at all. Build it in weeks, not months, with extremely limited functionality (some start with a landing page and a spreadsheet), launch it to people who have the problem, get feedback and iterate. YC's Michael Seibel puts it bluntly: launch something bad, quickly.

By , FounderUpdated 4 min read

Share

Quick answer: How do I launch an MVP?

  1. What: the simplest thing that can deliver value to your first users.
  2. How fast: weeks, not months.
  3. How small: extremely limited functionality; a landing page and spreadsheet can count.
  4. Launch to: people with the problem first; then launch sites.
  5. Then: get feedback, iterate; don't fall in love with the MVP.

Key takeaways

  • An MVP tests whether you can deliver value, not whether you can build features.
  • Speed matters more than polish at this stage.
  • Launches aren't special: you can launch again as the product improves.
  • Feedback from real use beats opinions about a demo.
  • Iterate on the problem, not on finding new problems for your solution.

Most MVPs launch too late. The founder keeps adding "just one more feature" because the product feels embarrassing, and months pass without a single real user. Y Combinator's advice is the opposite, and it's blunt: in Michael Seibel's words, "launch something bad, quickly". This guide turns that into a plan: what to build, how fast, where to launch it and what to do next, drawing on YC's Startup School talk and launch-site rules as read on 17 November 2026. Jump to scoping, launching or after launch.

Y Combinator Startup Library page How to plan an MVP by Michael Seibel
YC's MVP talk: launch quickly, get feedback, iterate.Image: Y Combinator · Screenshot shown for commentary, 17 Nov 2026 · source

Scope it small

PrincipleWhat it means
Ridiculously simpleThe first thing that can deliver value to your first users
Weeks, not monthsMost MVPs should be fast to build
Extremely limited functionalityOnly what your initial users need
Any mediumSoftware, or a landing page and a spreadsheet
Don't fall in loveIf it doesn't solve the problem, change it

Table: MVP principles (YC Startup Library, "How to plan an MVP")

Launch it

Diagram of 5 steps for launch it: 1. Talk to users first; 2. Give it to them directly; 3. List it; 4. Show HN; 5. Product Hunt.
Launch it
  1. Talk to users first — know who the MVP is for.
  2. Give it to them directly — personally onboard the first few.
  3. List it — a permanent profile and a launch site that accepts usable early products.
  4. Show HN — if people can try it now.
  5. Product Hunt — once anyone can sign up; it says closed betas usually aren't a fit.

After launch

Checklist: After launch — Talk to every user; Fix the biggest blocker first; Measure one thing; Launch again; Iterate on the problem.
After launch
  • Talk to every user — what did they try, where did they stop?
  • Fix the biggest blocker first
  • Measure one thing — do people come back?
  • Launch again — Seibel's point: launches aren't special
  • Iterate on the problem — not new problems for your solution

Mistakes

Checklist: Mistakes — Months of building before a user sees it; Feature lists instead of one core job; Launching to "everyone"; Treating launch day as the finish line; Falling in love with the solution.
Mistakes
  • Months of building before a user sees it
  • Feature lists instead of one core job
  • Launching to "everyone"
  • Treating launch day as the finish line
  • Falling in love with the solution
Science of Apps Launchpad homepage with the headline Launch your product. Get it found.
The Science of Apps Launchpad: launch an MVP free.Image: Science of Apps · © Science of Apps · source

Ready to launch?

How we know

MVP principles come from Michael Seibel's "How to plan an MVP" in YC's Startup Library; launch-site rules from Product Hunt's help centre and the Show HN guidelines, read on 17 November 2026. The steps are our adaptation.

Key terms, defined

  • MVP: minimum viable product.
  • Iterate: improve in small cycles based on feedback.
  • Pivot: change the problem or customer you target.
  • Core value: the main result the product delivers.
  • Blocker: a problem that stops users reaching value.

Frequently asked questions

What is an MVP?

A minimum viable product: the first, ridiculously simple thing you can give your target users to see if you can deliver any value at all, as YC's Michael Seibel describes it.

How long should an MVP take to build?

Weeks, not months, in most cases. Seibel notes some startups simply start with a landing page and a spreadsheet.

Where should I launch an MVP?

First to people who have the problem, directly. Then on launch sites that accept usable early products: Peerlist, Show HN if it's try-able, Product Hunt once anyone can sign up, and a permanent profile.

What features should an MVP have?

Only the few things your first users need to get the core value. Everything else waits until real use tells you what matters.

What do I do after launching an MVP?

Talk to every user, watch where they get stuck, fix the biggest blocker, and repeat. Launch again when the product is meaningfully better.

Is it bad to launch an unfinished product?

Not at the MVP stage, as long as it delivers some real value and you're honest about what's unfinished. Waiting for polish delays the learning.

Sources

  1. Y Combinator Startup Library — How to plan an MVP (Michael Seibel)
  2. Y Combinator Startup Library — How to talk to users (Gustaf Alströmer)
  3. Product Hunt Help Center — What kind of products get featured (checked 17 Nov 2026)
  4. Hacker News — Show HN guidelines (checked 17 Nov 2026)
  5. Science of Apps — Launchpad: launch your product free
  6. Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

Launch your MVP free on the Launchpad: a permanent profile ranked by relevance, never payment, plus an end-to-end test showing what first users will hit.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition