The SaaS Launch Checklist: 47 Steps From Idea to First Customer

Here's what nobody tells you about launching a SaaS: the launch is the easy part.

The hard part is everything before it. Figuring out if anyone actually has the problem you're solving. Cutting your feature list until it hurts. Talking to strangers who might tell you your idea is pointless. That's where most products die — not on launch day, but in the months before when founders skip validation and jump straight to code.

We've watched hundreds of projects come through fromscratch — the ones that get traction almost always share the same pattern. They validated before they built. They launched before they felt ready. And they treated launch day as the start, not the finish line.

This is the checklist we wish we'd had. Forty-seven steps, five phases, zero "it depends" cop-outs. Let's go.

Phase 1: Validate (Steps 1–10)

This phase is the one most founders skip. It's also the one that determines whether everything after it matters.

You're not building yet. You're not designing logos. You're talking to people and figuring out if the problem you want to solve is real, painful, and worth paying to fix.

1. Write down the problem in one sentence

Not your solution. The problem. One sentence.

"Freelancers waste 3 hours per week chasing invoices" is a problem. "An AI-powered invoicing platform with smart reminders and Stripe integration" is a solution looking for a problem. If you can't articulate the pain in one line, you don't understand it well enough yet.

2. Find 10 people who have this problem

Not people who might have it. People who demonstrably, currently have it. Check Reddit, indie hacker communities, Twitter, niche forums. Look for complaints, workarounds, and people asking "is there a tool that does X?"

If you can't find 10 people with this problem, that's data. Either the problem isn't painful enough or you're looking in the wrong places.

3. Talk to them (listen, don't pitch)

This is the step that separates the founders who succeed from the ones who build something nobody wants. Have 10-15 real conversations. The Mom Test by Rob Fitzpatrick is the playbook — don't ask "would you use this?" (everyone says yes). Ask:

• "How do you deal with [problem] right now?"
• "What's the most annoying part of that?"
• "What have you tried? Why did you stop using it?"
• "How much time/money does this cost you?"

If they light up and start ranting about their current workflow, you've found something real.

4. Check if they're already spending money on it

This one matters more than most founders realize. If people are already paying for a solution — even a bad one — that's proof the market exists. If they're using free workarounds and seem fine with it, you'll have a brutal time charging for anything.

Look for: existing SaaS tools in the space, consultants solving this manually, Excel/Google Sheets jury-rigging, or teams hiring someone specifically for this task.

5. Size the market (TAM doesn't matter — your niche does)

Skip the total addressable market slides. What matters is: how many people have this specific problem, in the niche you can actually reach, and how much are they willing to pay?

If 5,000 freelance designers each pay $30/month for a tool like yours, that's $1.8M ARR. That's a life-changing solo founder business. You don't need a billion-dollar TAM.

6. Validate willingness to pay

"Would you pay $30/month for this?" is a useless question. Everyone says yes to hypotheticals. Better approaches:

• Ask people to put their email on a waitlist (mild commitment)
• Ask for a $1 pre-order (real commitment)
• Post a landing page with pricing and a "Buy Now" button that leads to a waitlist

The gap between "I'd totally use that" and "here's my credit card" is enormous. Test for the second one.

7. Build a landing page, not a product

Before you write a line of code, build a page that explains what your product does, who it's for, and what it costs. Use Carrd, Framer, or even a single HTML page. It doesn't matter. What matters is that real humans can see it and react.

8. Run a smoke test

Drive 100-200 people to your landing page. Use a $50-100 ad spend, post in 2-3 relevant communities, or cold-email people from step 2. Measure:

• Email signup rate (aim for 5-10%)
• Click-through on "Buy" or "Get Started" (aim for 2-5%)
• Direct replies and questions (a goldmine of insight)

If 200 people visit and zero sign up, that's a signal. Either the positioning is wrong or the problem isn't painful enough to pay for.

9. Pick your wedge

You can't beat established players on everything. Pick the one thing you'll do radically better and lead with that. Plausible's wedge was privacy. Linear's was speed. Hey's was opinionated email design.

Your wedge should finish this sentence: "It's like [competitor] but [your wedge]."

10. Write your positioning statement

Before you build, nail this: Who is this for, what does it do, why should they care, and why is it different from what exists? Write it in 2-3 sentences. This becomes your homepage copy, your Product Hunt tagline, and your answer when someone asks "so what are you building?"

If you can't write a clear positioning statement, go back to step 3.

Phase 2: Build (Steps 11–22)

You've validated the problem. People want a solution and they're willing to pay. Now build the smallest possible version that delivers on your wedge.

The enemy of this phase is scope. Every founder adds "just one more feature" until the MVP becomes a 6-month project. Fight that impulse.

11. Define your MVP scope — then cut it in half

List every feature your product needs. Now cross off half of them. Seriously. The features you keep should do one thing: solve the core problem well enough that someone would pay for it today.

Stripe launched as a payment form and an API. No dashboard, no analytics, no subscription management. Basecamp shipped a project tracker with no file sharing, no time tracking, and no reports. Both became billion-dollar products.

Your MVP isn't your vision. It's the smallest proof that your vision is worth pursuing.

12. Pick your tech stack and stop changing it

This is the part where solo developers lose months. Pick a stack you know, not the one that's trending on Hacker News this week. If you're productive in Next.js, use Next.js. If you're fast in Rails, use Rails. If you've never used a framework before, pick the one with the most tutorials.

The tech stack does not matter for your first 1,000 customers. Shipping speed matters.

13. Set up error tracking and analytics from day one

Before you build any features, wire up three things:

• Error tracking (Sentry, LogRocket, or similar) — you need to know when things break before your users tell you
• Product analytics (PostHog, Plausible, or similar) — you need to know what users actually do, not what they say they do
• A feedback mechanism — even a simple email link or a Canny board

Don't bolt these on later. You'll miss the most critical early data.

14. Build the core loop first

Every SaaS has one core loop — the action users repeat that delivers value. For a CRM, it's logging interactions. For a scheduling tool, it's booking meetings. For an analytics tool, it's viewing dashboards.

Build that loop first. Make it smooth. Ignore everything else until the core loop feels right.

15. Ship authentication and billing before features

Authentication and billing are the two pieces of infrastructure that touch everything. If you treat them as afterthoughts, you'll spend weeks refactoring later.

Use an auth provider (Clerk, Auth.js, Supabase Auth) and a billing provider (Stripe, Lemon Squeezy) from the start. Don't roll your own auth. Don't defer payments to "when we have paying users." You need billing infrastructure to accept money on day one.

16. Get 3-5 beta users before you feel ready

The single biggest mistake builders make: waiting until the product is "ready." It will never feel ready. Ship it to 3-5 beta users the moment the core loop works, even if the UI is ugly and half the settings page is placeholder text.

Beta users tell you what actually matters. Without them, you're guessing.

17. Build in public (or at least semi-public)

Share what you're building on Twitter/X, Indie Hackers, or a blog. You don't have to share revenue numbers or your roadmap. But showing progress — even a weekly screenshot or a short update — does three things:

1. It builds an audience before launch day
2. It creates accountability (you're less likely to quit)
3. It generates early feedback from people who care about your niche

18. Fix what beta users complain about — ignore what they request

Beta feedback comes in two flavors: complaints and requests. Complaints tell you what's broken. Requests tell you what someone imagines they want.

If three beta users say "I can't figure out how to export my data," that's a real problem. If one beta user says "you should add Gantt charts," that's their vision for your product, not yours. Fix the first. File the second.

19. Set your pricing

If you haven't read how to price your SaaS yet, go do that. The short version:

• Use value-based pricing (what is this worth to them, not what it costs you)
• Three tiers: Good ($29+), Better ($49-99), Best ($149+)
• Annual discount at two months free
• Skip the free plan unless your product has network effects

Start higher than feels comfortable. You can always lower it later. Raising prices after launch is much harder psychologically.

20. Build your landing page for real

Your smoke test page from step 7 was a prototype. Now build the real thing. It needs:

• A headline that states the value (not the feature)
• A subheadline that says who it's for
• Social proof (beta user quotes, early metrics, anything)
• A clear CTA above the fold
• Your pricing
• A demo video or screenshot walkthrough

21. Set up transactional emails

At minimum, you need: welcome email, email verification, password reset, payment confirmation, and trial expiration reminder. These aren't marketing emails — they're the infrastructure of trust. A product with no welcome email feels like abandonware.

22. Test the signup-to-value path end to end

Sign up as a brand-new user. Time how long it takes to experience the core value of your product. If it's more than 5 minutes, you have work to do. Every extra click between signup and "aha moment" is a place where users silently leave.

Phase 3: Pre-launch (Steps 23–33)

Your product works. Beta users are finding value. Now you need to create demand before you flip the switch.

The difference between a launch that fizzles and one that compounds? Preparation. Every successful launch we've seen on fromscratch invested 2-4 weeks in this phase.

23. Pick a launch date and tell people

An unannounced launch date is a wish. A public one is a commitment. Pick a date 2-3 weeks out. Tell your email list, your Twitter followers, your beta users. Post it. The deadline creates urgency — both for you and for your audience.

24. Build an email waitlist

Your waitlist is your launch day army. Every person on it is someone who opted in because they want what you're building. Drive waitlist signups from:

• Your landing page (primary CTA for pre-launch)
• Social posts and build-in-public updates
• Relevant community posts
• Cold outreach to people you interviewed in step 3

A waitlist of 200-500 engaged people is enough to generate real launch day momentum.

25. Write your launch copy

Pre-write everything. Do not wing this on launch day.

• Product Hunt first comment — who you are, what the product does, what's different, a PH-exclusive deal, and two questions. See our Product Hunt launch strategy guide for the exact structure.
• Launch email — short, value-focused, with a single clear CTA
• Twitter/X thread — the story arc of why you built this
• Hacker News Show HN — technical, honest, no marketing speak
• Community posts — adapted for each community's norms

26. Set up attribution and analytics

Before launch day, make sure you can answer: where did each signup come from? Set up UTM parameters for every channel, configure your analytics to track conversion events, and make sure your funnel is measurable from first visit to paid signup.

You'll want this data badly on day two when you're deciding where to double down.

27. Prepare your Product Hunt launch

If you're going to launch on PH (and you probably should — the DR 91 backlink alone is worth it), start preparing now. Create your maker profile, upvote and comment on other products, prepare your assets, and build your supporter list. This is a 2-3 week process, not a one-day event. Read our full Product Hunt launch strategy for the detailed playbook.

28. Submit to beta directories and communities

Product Hunt isn't the only game. Submit to BetaList, Indie Hackers, HackerNews, relevant subreddits, niche Slack/Discord communities, and SaaS-specific directories. Each one is a small bet. Some will send 10 visitors, some will send 500. Stack enough small bets and they add up.

29. Write 2-3 content pieces that target your audience

Start your SEO engine before launch. Write 2-3 blog posts or guides that address problems your target audience is actively searching for. These won't rank overnight, but they start the clock on SEO authority and give you something to share in communities.

If your product is a scheduling tool, write about scheduling workflows, time management for freelancers, or a comparison of existing scheduling tools. Link back to your product naturally.

30. Set up customer support

Keep it simple at launch. A shared inbox (even your personal email with a product alias) and a basic FAQ page or help section is enough. You don't need Intercom. You don't need a knowledge base with 50 articles. You need to be reachable and responsive.

Reply to every support email within an hour during launch week. Speed of response is the single best predictor of early customer satisfaction.

31. Create a demo video or walkthrough

A 60-90 second video showing your product in action converts better than any amount of landing page copy. Use Screen Studio, Loom, or even a screen recording with a voiceover. Show the core loop — the thing that makes users go "oh, that's nice."

Don't script it to perfection. A slightly rough, authentic demo outperforms a polished corporate video for indie products.

32. Do a full dress rehearsal

Sign up with a fresh email. Go through every step: landing page → signup → onboarding → core action → payment. Time it. Note every moment of confusion or friction. Fix anything that takes more than one click too many.

Then do it on mobile. Half your launch traffic will come from phones.

33. Prepare your pricing page

Your pricing page is one of the highest-traffic pages on launch day. Make sure it's crystal clear. Three tiers, feature comparison, FAQ section, and a toggle between monthly and annual. The reader should understand your pricing in under 10 seconds.

Phase 4: Launch (Steps 34–41)

Launch day isn't a single event — it's a coordinated push across every channel you've prepared. The goal: create enough concentrated activity in 24-48 hours that algorithms, communities, and people start amplifying your signal organically.

34. Email your waitlist first

Your waitlist is your warmest audience. Email them before you post anywhere public. Give them early access, a launch-exclusive deal, or just a personal "you were first" note. These are the people most likely to sign up, share, and leave comments on Product Hunt.

Send the email at 6:00-6:30 AM PST for the highest open rates if you're targeting a US audience.

35. Launch on Product Hunt

Go live at 12:01 AM PST when the leaderboard resets. Post your first comment immediately. Activate your supporters in coordinated waves. Reply to every comment within 10 minutes. One quality comment carries the weight of 40-50 upvotes in PH's algorithm. Full playbook: Product Hunt launch strategy.

36. Post a Show HN on Hacker News

Hacker News Show HN has different norms than Product Hunt. Be technical, be honest about limitations, and don't use marketing language. "Show HN: I built a scheduling tool because Calendly's pricing annoyed me" works. "Show HN: The Revolutionary AI-Powered Scheduling Platform" gets downvoted into oblivion.

Include your tech stack, what you learned building it, and ask for specific feedback. HN readers love a builder story.

37. Share on Twitter/X with a story thread

Don't just tweet "we launched!" Write a thread with the story: the problem you noticed, the validation you did, what you built, one or two screenshots, and a link. Story threads outperform announcement tweets by 5-10x on engagement.

38. Post in relevant communities — without spamming

Every community has its own rules. Read the room before posting. On Reddit, add genuine value with your post. On Indie Hackers, share the behind-the-scenes journey. On niche Slacks and Discords, be a member first and a promoter second.

The golden rule: if your post would get upvoted even without the product link, you're doing it right.

39. Send 10 personal emails

Not a mass blast — 10 individual, hand-typed emails to people who would genuinely benefit from your product. Use what you learned in validation. "Hey [name], I remember you mentioned struggling with [problem]. I just shipped something that might help: [one-line description + link]."

Personal outreach converts at 10-30%. No ad campaign comes close.

40. Reply to everything

Every comment on Product Hunt. Every reply on Twitter. Every email. Every DM. Launch day is your one chance to make a first impression at scale. The founders who reply to everything get more engagement, higher PH rankings, and more signups than those who go quiet after the initial push.

Set a timer. Check every channel every 30 minutes for the full 24 hours.

41. Track what's working in real time

By midday, you'll see patterns. One channel is sending high-quality traffic. Another is sending tire-kickers. Double down on what's working. If Twitter is on fire, post more. If Reddit flopped, don't force it. Reallocate your energy every few hours based on data, not assumptions.

Phase 5: Post-launch (Steps 42–47)

Here's the thing about launch day spikes: they always come back down. Half of founders report only a temporary bump in signups after launching. What you do in the next 30 days determines whether that spike becomes a sustained growth curve or a fond memory.

42. Follow up with every signup

Within 24 hours of someone signing up, they should get a personal-feeling welcome email. Not just a transactional "verify your email" — a real email from a real person saying thank you, asking what they're trying to accomplish, and offering to help.

A founder at Unicorn Platform did exactly this. The personal replies built more loyalty than any feature ever could.

43. Set up proper onboarding

Watch your analytics. Where do users drop off after signup? That's where your onboarding is broken. Build a simple guided flow that gets users to their "aha moment" in under 5 minutes. Use empty states wisely — a blank dashboard should show the user exactly what to do next, not stare back at them.

44. Start your content and SEO engine

Launch day traffic is rented. SEO traffic is owned. Start publishing content that targets keywords your audience searches for. This isn't optional — it's how you build sustainable traffic that doesn't depend on the next Product Hunt launch or Twitter thread.

Write comparisons, guides, and how-tos. Internal link them to your product pages. Consistency beats volume — one quality post per week compounds faster than a burst of mediocre ones.

45. Build in public about your numbers

Share your launch results honestly. How many signups? How much revenue? What surprised you? What failed? These retrospectives get massive engagement because most founders keep their numbers secret. Transparency builds trust and attracts the kind of users who root for indie builders.

Tally's launch retrospective got picked up by multiple newsletters and drove more signups than their actual Product Hunt launch.

46. Double down on your best channel

By week 2, you'll know which acquisition channel works best. Maybe it's SEO. Maybe it's Twitter. Maybe it's a single Reddit community. Whatever it is, go all in. Most successful solo SaaS products get 60-80% of their early growth from one channel. Find it and ride it.

47. Get your first paying customer (who isn't your friend)

This is the real milestone. Not the launch. Not the signups. Not the Product Hunt badge. Your first paying customer — someone you didn't know before, who found your product, tried it, and decided to give you their money.

When that happens, you've built something real. Everything before this was validation. Everything after is growth.

The timeline: how long this actually takes

These are rough ranges from real launches. The biggest variable is phase 2 — build time. If you're tempted to spend 6 months building, reread step 11. Cut the scope.

Get the checklist as a template

Want this checklist in a format you can actually check off? We put together a Notion template and a printable PDF with all 47 steps organized by phase. No email required — just grab it and go.

What real launches look like

Theory is great. Here's what actually happened when real indie builders followed (or ignored) this process.

Dub.co — open-source link management — launched on Product Hunt and hit #1 of the Day, Week, and Month with 1,085 upvotes and 663 signups. Their secret wasn't the product alone. They'd spent 3 weeks building a Coming Soon page, had a 25,000-subscriber email list ready to activate, and replied to every single comment. That's phases 3 and 4 done right.

Tally — no-code form builder — launched twice. First attempt: 695 upvotes, #5 Product of the Day, user base doubled from 1,500 to 3,000. Second launch (Tally 2.0): triple #1 plus Golden Kitty award. Weekly signups jumped 91%. Now past $3M ARR with a 5-person team. The difference between launch one and two? Better validation, more preparation, and two years of building in public.

Plausible Analytics — privacy-focused analytics — did almost no pre-launch work. No supporter lists, no advance announcements. Still hit #2 of the Day with 850+ upvotes. But their conversion to paid signups was 1.38% — far below the launches that did phases 1-3 properly. Their founder called Product Hunt "nice to have, not core growth." Which is honest, but also what happens when you skip the pre-launch phase.

The pattern is consistent: founders who invested in validation and pre-launch got 3-5x better conversion from the same amount of launch day traffic. The launch itself is a multiplier. What it multiplies depends on everything you did before.

What to skip (seriously, skip it)

Not everything on every launch advice blog actually matters. Here's what you can safely ignore:

• Logos and branding before you have 10 users. A clean text logo is fine. Nobody churned because of a font choice.
• A mobile app for launch. Build a web app first. React Native or Flutter can come later when you've proven demand.
• Complex analytics dashboards for yourself. A spreadsheet tracking signups, revenue, and churn is enough for the first 6 months.
• Enterprise features like SAML SSO, audit logs, and custom contracts. You don't have enterprise customers yet.
• A blog with 20 articles at launch. Two or three focused pieces outperform a content dump.
• Perfection. Your product will have bugs on launch day. Every product does. Ship anyway.

The mistakes that kill SaaS launches

After watching hundreds of launches on fromscratch, the same patterns keep surfacing.

The most common failure mode we see? A founder builds for months, launches to crickets, blames the market, and moves on to the next idea. The market was fine. The process was broken.

1. step 1

   Validate your idea (Steps 1-10)

   Talk to real people who have the problem. Confirm they're already spending money or time on it. Build a landing page before writing a line of code and run a smoke test to gauge demand.

2. step 2

   Build the MVP (Steps 11-22)

   Define the smallest possible scope, pick a tech stack and commit, ship authentication and billing early, get beta users before you feel ready, and set your pricing higher than your instinct tells you.

3. step 3

   Prepare for launch (Steps 23-33)

   Pick a launch date and announce it publicly. Build a waitlist, set up analytics, write launch copy, prepare your Product Hunt and directory submissions, and test the full signup-to-value flow.

4. step 4

   Execute launch day (Steps 34-41)

   Email your waitlist, launch on Product Hunt and Hacker News, post in communities, send personal emails to 10 potential users, and reply to every single comment within the hour.

5. step 5

   Sustain post-launch momentum (Steps 42-47)

   Follow up with signups, set up onboarding, start a content engine for SEO, share your numbers publicly, double down on your best channel, and convert your first real paying customer.