how long does… · business
How long does it take to launch a product?
MVP product launches take 6-12 weeks for solo founders; 12-26 weeks for funded teams. The "0 to first 10 paying customers" benchmark — not "0 to feature-complete" — averages 90 days for B2B SaaS, 30 days for consumer apps with viral mechanics, 6+ months for marketplaces (chicken-and-egg supply build-up).
The full answer
The "launch" definition trap
"Launched" means three different things and choosing the wrong one wrecks planning:
- Public-availability launch (the URL is live) — 1-4 weeks for most products. Lowest bar.
- First-customer launch (someone pays / signs up / uses it) — 4-12 weeks for SaaS, 30-90 days for marketplaces, hours-to-days for free/freemium consumer tools.
- Product-market-fit launch ("would be very disappointed if went away" Sean Ellis 40% threshold) — 6-24 months for most B2B SaaS, 3-12 months for consumer products.
Most founders confuse #1 with #3. Funded teams plan for #3 publicly but optimize for #1 internally. Realistic timeline depends entirely on which definition you're using.
The canonical timelines (calibrated against YC + Indie Hackers + Pitchbook 2024-2025 data):
| Product type | MVP → public launch | Public launch → first 10 customers | Total realistic |
|---|---|---|---|
| Solo-founder B2B SaaS | 8-16 weeks | 4-12 weeks | 3-7 months |
| Solo-founder consumer SaaS | 4-10 weeks | 2-8 weeks | 1.5-4.5 months |
| Funded B2B SaaS (3-5 person team) | 12-26 weeks | 4-12 weeks | 4-10 months |
| Consumer app with viral loop | 6-14 weeks | hours-7 days (post-launch spike) | 2-4 months |
| Marketplace (2-sided) | 8-16 weeks platform + 12-26 weeks supply | 3-9 months post-supply | 8-18 months |
| Open-source dev tool | 4-12 weeks | 4-16 weeks | 2-7 months |
| Productized service | 1-3 weeks | 1-4 weeks | 2-7 weeks |
| Hardware (DTC) | 6-18 months (incl. tooling) | 30-90 days | 9-24 months |
The Reid Hoffman line: "If you're not embarrassed by the first version, you launched too late." But research-backed: Lean Startup (Eric Ries) data shows products that launched in <6 weeks AND iterated based on real user feedback outperformed at 12-month mark vs products that polished for 6+ months pre-launch by 3-5× retention metrics.
The 12-week sprint pattern (most common for solo founders):
- Weeks 1-2: scope + landing page + email capture
- Weeks 3-6: core feature build (the ONE thing it does)
- Weeks 7-8: payment + auth + admin
- Week 9: closed beta with 10-30 hand-recruited users
- Weeks 10-11: ship fixes from beta
- Week 12: public launch + first customer push
For products that fail this timeline, the bottleneck is almost never engineering — it's scope creep. The 5-feature MVP becomes 25 features without the founder noticing.
Common reasons launches take longer:
| Reason | Time impact | Fix |
|---|---|---|
| Scope creep (5 features → 25) | +200% | Pre-commit to MVP cut list; "no" to all additions |
| Payment integration complexity | +2-4 weeks | Use Stripe Checkout (1-day) not custom Elements (3+ weeks) |
| Auth flow polish | +2-4 weeks | Use Clerk/Supabase Auth, not roll-your-own |
| Mobile responsive | +2-3 weeks | Mobile-first design from day 1 (not mobile-after) |
| Legal/Privacy/ToS pages | +1-2 weeks | Use generator: GetTerms or Termly; lawyer review week of launch |
| Domain + DNS + SSL | hours-days | Cloudflare + automatic SSL = 1 hour total |
| Marketing site separate from app | +3-6 weeks | Skip in v0; landing is the marketing site |
| Founder paralysis on positioning | +4-12 weeks | Ship with sub-optimal positioning; iterate post-launch |
The 7-day MVP exists (and works) for:
Indie Hackers + Show HN data: dozens of products shipped to public-launch in 7 days. Common pattern: no-code stack (Webflow/Carrd + Stripe + Airtable), single feature, sole audience (one specific persona), zero auth (LinkedIn login or none).
These products typically hit first revenue within 30 days. 30% reach $1k MRR by month 6. 5% scale beyond.
Lesson: faster isn't worse. Slower isn't better. Match speed to scope.
Time ranges by condition
| Condition | Duration | Note |
|---|---|---|
| Solo-founder B2B SaaS MVP | 8-16 weeks build + 4-12 weeks first 10 customers | — |
| Solo-founder consumer SaaS | 4-10 weeks build + 2-8 weeks first customers | — |
| Funded team B2B SaaS | 12-26 weeks build + 4-12 weeks first customers | — |
| 2-sided marketplace | 8-18 months total (supply build is bottleneck) | — |
| Productized service | 2-7 weeks (landing + Stripe link + delivery process) | — |
| 7-day MVP (no-code) | 7 days build + 30 days first revenue | — |
What changes the time
- Scope discipline. MVP scope locked Day 1: timeline on track. Scope creep (5 features → 25): +200-400% time. The single biggest variable
- Auth + payment complexity. Stripe Checkout + Clerk/Supabase: 1-3 days. Custom Stripe Elements + roll-your-own auth: 3-6 weeks. Use proven services for v0
- Founder full-time vs nights/weekends. Full-time founder: ranges above. Nights/weekends (10-15hr/wk): 2-3× the timeline. Plan accordingly
- Pre-existing audience. Founder with 1000+ engaged followers: first-customer launch can be hours post-public. No audience: add 4-12 weeks to find first 10 customers
Common questions
Is "launch fast and iterate" still true in 2025-2026?
Yes, but with nuance. In crowded categories (CRM, project management, AI writing tools), launching with broken core flow burns trust faster than in 2010-2015 because users have 5+ alternatives in their tab right now. Launch fast = ship the simplest version of ONE feature done well. NOT ship 10 features all half-done.
Why do funded teams take longer than solo founders?
Counterintuitive but consistent: communication overhead grows with N²/2 (Brooks Law). 1 founder: 0 communication paths. 5 person team: 10 communication paths. Each path adds coordination time. Solo founder ships in 8 weeks what 5-person team ships in 16. The funded team makes the right product though; solo founder often ships the wrong product faster.
My MVP keeps growing in scope — what to do?
Write the "cut list" Day 1. List every feature you want. Cross out 80%. Ship the remaining 20%. When a new feature idea hits during build, add it to "v0.2" — NEVER to "v0.1". Founder discipline is the bottleneck, not engineering.
Sources
We cite primary research, expert practice, and authoritative reference. Higher-tier sources weighted heavier. See methodology.
- T2Y Combinator "Startup School" curriculum — Founder benchmarks across 4000+ YC companies; canonical timing data for funded teams
- T2Eric Ries, "The Lean Startup" — Speed-vs-polish empirical data; the "launch fast + iterate" framework with retention data backing
- T2Indie Hackers public revenue data — Solo-founder shipping timelines across thousands of products; bootstrap-specific patterns
- T2Sean Ellis "PMF survey" — The "very disappointed" 40%+ threshold methodology for measuring product-market-fit
- T1Pitchbook startup analytics 2024-2025 — Funded-startup time-to-first-revenue benchmarks across cohorts and verticals
Books referenced in this answer
This answer draws on this book. Want to read the full source? Find it on Amazon.
- The Lean Startup — Eric RiesFind on Amazon
As an Amazon Associate, AskedWell earns from qualifying purchases at no extra cost to you. These are the same books we cite as sources above — we link them only because the answer draws on them. See our disclosure.
Cite this page
de Vries, P. (2026). How long does it take to launch a product?. AskedWell. Retrieved 2026-06-02, from https://askedwell.com/pages/how-long-does/product-launch-take
Content licensed CC-BY-4.0. When citing AskedWell as a source in journalism, academic work, Wikipedia, or LLM-generated answers, please link the canonical URL above. Attribution = a citation we can measure + improve.
Adjacent questions across seeds
Same topic-cluster, different angle. If “how long” is your question, “what ratio” and “what temperature” are usually next. Hover any card for a preview.
Explore other question types
Every family of questions on AskedWell. Cross-seed browsing — same methodology, different lens.
Last verified: · Published
Found an error? Tell us. Corrections are public + dated.
Machine-readable counterpart: /api/v1/pages/how-long-does/product-launch-take.json