{"schema":"askedwell-answer-v1","url":"https://askedwell.com/pages/how-long-does/product-launch-take","question":"How long does it take to launch a product?","short_answer":"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).","long_answer":"**The \"launch\" definition trap**\n\n\"Launched\" means three different things and choosing the wrong one wrecks planning:\n\n- **Public-availability launch** (the URL is live) — 1-4 weeks for most products. Lowest bar.\n- **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.\n- **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.\n\nMost 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.\n\n**The canonical timelines (calibrated against YC + Indie Hackers + Pitchbook 2024-2025 data):**\n\n| Product type | MVP → public launch | Public launch → first 10 customers | Total realistic |\n|---|---|---|---|\n| Solo-founder B2B SaaS | 8-16 weeks | 4-12 weeks | 3-7 months |\n| Solo-founder consumer SaaS | 4-10 weeks | 2-8 weeks | 1.5-4.5 months |\n| Funded B2B SaaS (3-5 person team) | 12-26 weeks | 4-12 weeks | 4-10 months |\n| Consumer app with viral loop | 6-14 weeks | hours-7 days (post-launch spike) | 2-4 months |\n| Marketplace (2-sided) | 8-16 weeks platform + 12-26 weeks supply | 3-9 months post-supply | 8-18 months |\n| Open-source dev tool | 4-12 weeks | 4-16 weeks | 2-7 months |\n| Productized service | 1-3 weeks | 1-4 weeks | 2-7 weeks |\n| Hardware (DTC) | 6-18 months (incl. tooling) | 30-90 days | 9-24 months |\n\n**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.\n\n**The 12-week sprint pattern (most common for solo founders):**\n\n- Weeks 1-2: scope + landing page + email capture\n- Weeks 3-6: core feature build (the ONE thing it does)\n- Weeks 7-8: payment + auth + admin\n- Week 9: closed beta with 10-30 hand-recruited users\n- Weeks 10-11: ship fixes from beta\n- Week 12: public launch + first customer push\n\nFor 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.\n\n**Common reasons launches take longer:**\n\n| Reason | Time impact | Fix |\n|---|---|---|\n| Scope creep (5 features → 25) | +200% | Pre-commit to MVP cut list; \"no\" to all additions |\n| Payment integration complexity | +2-4 weeks | Use Stripe Checkout (1-day) not custom Elements (3+ weeks) |\n| Auth flow polish | +2-4 weeks | Use Clerk/Supabase Auth, not roll-your-own |\n| Mobile responsive | +2-3 weeks | Mobile-first design from day 1 (not mobile-after) |\n| Legal/Privacy/ToS pages | +1-2 weeks | Use generator: GetTerms or Termly; lawyer review week of launch |\n| Domain + DNS + SSL | hours-days | Cloudflare + automatic SSL = 1 hour total |\n| Marketing site separate from app | +3-6 weeks | Skip in v0; landing is the marketing site |\n| Founder paralysis on positioning | +4-12 weeks | Ship with sub-optimal positioning; iterate post-launch |\n\n**The 7-day MVP exists (and works) for:**\n\nIndie 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).\n\nThese products typically hit first revenue within 30 days. 30% reach $1k MRR by month 6. 5% scale beyond.\n\nLesson: faster isn't worse. Slower isn't better. Match speed to scope.","duration_iso":"PT12W","ranges":[{"condition":"Solo-founder B2B SaaS MVP","duration":"8-16 weeks build + 4-12 weeks first 10 customers"},{"condition":"Solo-founder consumer SaaS","duration":"4-10 weeks build + 2-8 weeks first customers"},{"condition":"Funded team B2B SaaS","duration":"12-26 weeks build + 4-12 weeks first customers"},{"condition":"2-sided marketplace","duration":"8-18 months total (supply build is bottleneck)"},{"condition":"Productized service","duration":"2-7 weeks (landing + Stripe link + delivery process)"},{"condition":"7-day MVP (no-code)","duration":"7 days build + 30 days first revenue"}],"variables":[{"name":"Scope discipline","effect":"MVP scope locked Day 1: timeline on track. Scope creep (5 features → 25): +200-400% time. The single biggest variable"},{"name":"Auth + payment complexity","effect":"Stripe Checkout + Clerk/Supabase: 1-3 days. Custom Stripe Elements + roll-your-own auth: 3-6 weeks. Use proven services for v0"},{"name":"Founder full-time vs nights/weekends","effect":"Full-time founder: ranges above. Nights/weekends (10-15hr/wk): 2-3× the timeline. Plan accordingly"},{"name":"Pre-existing audience","effect":"Founder with 1000+ engaged followers: first-customer launch can be hours post-public. No audience: add 4-12 weeks to find first 10 customers"}],"sources":[{"label":"Y Combinator \"Startup School\" curriculum","tier":2,"url":"https://www.startupschool.org/","note":"Founder benchmarks across 4000+ YC companies; canonical timing data for funded teams"},{"label":"Eric Ries, \"The Lean Startup\"","tier":2,"note":"Speed-vs-polish empirical data; the \"launch fast + iterate\" framework with retention data backing"},{"label":"Indie Hackers public revenue data","tier":2,"url":"https://www.indiehackers.com/products","note":"Solo-founder shipping timelines across thousands of products; bootstrap-specific patterns"},{"label":"Sean Ellis \"PMF survey\"","tier":2,"note":"The \"very disappointed\" 40%+ threshold methodology for measuring product-market-fit"},{"label":"Pitchbook startup analytics 2024-2025","tier":1,"note":"Funded-startup time-to-first-revenue benchmarks across cohorts and verticals"}],"faq":[{"question":"Is \"launch fast and iterate\" still true in 2025-2026?","answer":"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."},{"question":"Why do funded teams take longer than solo founders?","answer":"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."},{"question":"My MVP keeps growing in scope — what to do?","answer":"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."}],"keywords":["product launch time","how long to build MVP","startup launch timeline","launch time SaaS","MVP timeline","solo founder launch"],"category":"business","date_published":"2026-05-22","date_modified":"2026-05-22","license":"CC-BY-4.0","attribution":"https://askedwell.com"}