A six-month timeline from validation to post-launch. Goals, tactics, exit criteria, tooling, and the launch myths most founders believe.
Methodology. This pillar pulls from public retrospectives by Marc Lou (ShipFast, Indie Page), Sahil Lavingia’s essays on launching Gumroad iteratively, the Y Combinator Startup School library, and the patterns visible across hundreds of Indie Hackers $1K MRR posts. Where we name a tool or company, the reference is to public 2026 information. Personal recommendations come from launching three solo SaaS products. How we research.
The dominant narrative around SaaS launches is built around a single day — usually a Product Hunt post — that supposedly determines whether a product lives or dies. This narrative is not just wrong. It is actively destructive to solo founders, because it focuses attention on the moment that matters least and obscures the six months that actually matter. Sahil Lavingia has written about Gumroad’s launch in The Minimalist Entrepreneur: it was not an event but a series of small, cumulative releases over a year. Marc Lou’s ShipFast did not become a $1M ARR product because of a viral launch day; it grew because of a year of audience-building before launch and a year of iteration after.
This pillar treats launching as a six-month process, not a six-hour event. It is structured as a timeline because that is how launches actually unfold — one month at a time, with each month enabling the next. Read it once linearly to understand the arc, then return to specific months when you arrive at them.
Before diving into each month, here is the full picture. Each phase has goals (what done looks like), tactics (what to actually do), and exit criteria (the threshold for moving on). The biggest mistake solo founders make is moving to the next phase before exit criteria are met — for example, building an MVP before validating demand, or launching before securing design partners.
| Phase | Goal | Output | Exit criterion |
|---|---|---|---|
| Months −3 to 0 | Validate demand | 5 customer interviews + waitlist | 10 hand-raised “I would pay” |
| Month 0–1 | Build the MVP | Working product | One end-to-end flow without bugs |
| Month 1–2 | Onboard design partners | 3–5 paying users | 3 paying customers using weekly |
| Month 2–3 | Set pricing and packaging | Public pricing page | 5 customers at full price |
| Month 3–4 | Launch publicly | Coordinated multi-channel push | 50–200 signups in launch week |
| Month 4–6 | Sustain growth | $1K MRR | 20 paying customers, <10% monthly churn |
Most failed solo SaaS products fail in this phase — specifically, by skipping it. The temptation to start building immediately is enormous, especially with AI tools that make building feel free. Resist. The cost of building something nobody wants is not the development time; it is the six months you spend trying to find customers afterward.
10 hand-raised “I would pay” commitments — ideally with at least 3 of them having actually pre-paid. If you cannot get 10 commitments after talking to 50 prospects, your idea, your positioning, or your audience is wrong. Do not proceed to building. The 48-hour validation guide covers a faster, more aggressive version of this phase if you need one.
The discipline in this phase is ruthless minimalism. The goal is not a polished product. The goal is a single user journey — from sign-up to the “aha” moment to a clean exit — that works without crashing. Everything else is post-launch. What an MVP actually is matters here: it is the smallest thing that produces value, not a feature-complete v1.
One user can sign up, complete the core flow, and pay you, all without your manual intervention. If any of those three steps requires you to be present, you are not yet at MVP. Do not proceed to launching until this works end-to-end on a phone.
Before public launch, you need a small group of customers who use the product, pay for it, and give you feedback. These are design partners — not beta testers, not friends. They have a real version of the problem, they pay (even if at a discount), and their feedback shapes what you build next. Three to five is the right count: enough for signal, few enough that you can give each one personal attention.
3 paying customers using the product at least weekly, with 1+ of them describing the “aha” moment unprompted. If you cannot find three customers willing to pay and use weekly, the product needs more iteration before launch — not more marketing.
By month three you have data: who buys, who churns, who pays full price without negotiation. This is when you turn that data into a public pricing structure. Trying to set pricing earlier is guesswork; trying to set it later is procrastination. Our solo founder pricing playbook covers the model selection in detail; the complete pricing pillar covers the deeper philosophy.
5 customers paying full (non-discounted) price. Discounted customers do not count for this exit criterion — you need proof that someone with no relationship to you, paying full freight, will buy.
Launching is not a Product Hunt post. Launching is two weeks of coordinated activity that converts the audience and momentum you have built up to this point into a measurable customer cohort. Marc Lou’s public launches always combine three or four channels in the same week, with each channel reinforcing the others.
50–200 signups in launch week and 5–15 new paying customers. Specific numbers vary with category and audience size, but a launch with fewer than 50 signups generally indicates the pre-launch audience-building was inadequate. Use the launch checklist to make sure nothing was missed.
The two months after launch are when most solo SaaS products fail — not from lack of users, but from lack of repeatability. The launch produced a one-time spike. What now? This phase is about building a sustainable engine that produces customers when no one is watching. Our zero to $1K MRR playbook is the primary companion to this phase.
$1,000 MRR sustained for two consecutive months, with monthly churn under 10% and at least one acquisition channel producing customers without your daily attention. At this point you are no longer launching. You are running a SaaS business. The next inflection point — whether to quit your day job, when to hire your first contractor, or whether to raise capital vs. bootstrap — is a different conversation.
The launch advice that circulates on solo-founder Twitter is mostly correct in spirit and broken in detail. Here are the five most damaging launch myths solo founders believe in 2026.
Product Hunt is one channel in a coordinated launch week. It is a useful channel — the audience is composed of early adopters and tool-curious folks — but it is not the launch. Launches that rely solely on PH typically produce a 24-hour spike, no SEO benefit, no email list growth, and no compounding distribution. PH is a single contributing chord, not the symphony. The founders who get the most out of PH are the ones who have prepared on Twitter, email, and Hacker News in parallel.
You launch many times. Most successful indie SaaS products have 3–6 distinct “launches” over their first two years — an initial soft launch to design partners, a public Phase 1 launch, a major version launch with new features, an integration partner launch, a category re-positioning launch. Sahil Lavingia’s framing in The Minimalist Entrepreneur is exactly this: launching is a verb you keep doing, not an event that happens once.
You almost certainly do not. TechCrunch coverage of a solo SaaS launch produces, on average, one to two days of traffic and zero long-term value. Press is a downstream effect of distribution, not an input to it. The founders who get press did not need it; the ones who chase press at launch usually waste 40 hours getting nothing. Skip outreach to journalists in your launch week. Your time is better spent on owned channels.
Launch day produces 20–30% of launch-window signups. The other 70% come from the seven days that follow, as your launch content circulates through Twitter, gets reshared in Slack channels, and propagates through email forwards. Founders who optimize obsessively for day-one numbers and ignore the week-long tail leave most of their launch on the table. Plan content for days 1–7, not just day 0.
Helpful, not required. Marc Lou launched ShipFast with a small but engaged audience built over 18 months of consistent posting. Pieter Levels launched Nomad List the same way. The pattern is not “have a network” but “build distribution before you build product” — which any founder can start doing today, regardless of network. If you are reading this and you do not have a network, the right move is to start building one in parallel with Phase 1 of the timeline above.
The solo founders who launch successfully treat the public-launch week as one node in a six-month process. They validate before building. They ship a single end-to-end flow. They get design partners before going public. They set pricing on data, not vibes. They coordinate three to five channels in launch week. And they spend the two months after launch hardening the engine, not declaring victory. This timeline is not the only way. It is the most reliable one.
If you are about to start Phase 1, the most useful companion guides are how to validate a SaaS idea in 48 hours and our customer interview playbook. If you are mid-build, look at the solo founder tech stack, how to build SaaS with Claude, and vibe coding tools to compress the build phase.
Once you have design partners, the pricing playbook and onboarding playbook are next. Use the launch checklist the week of public launch. The zero to $1K MRR playbook is the daily companion for months 4–6. If you want stage-appropriate context on what you are building — concrete micro SaaS examples at this stage — or you are still picking what to build, the broader Pillar Guides hub is the right place to wander.
Finally, on the framework side: product-market fit, SaaS MVP, and design partner are the three glossary entries that will save you the most arguments with yourself during this six-month sprint.
The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.