The Complete SaaS Launch Checklist
73 actionable steps from validation to planning to building to marketing to launch and growth. Choose a mode that fits where you are. With worked examples for two SaaS ideas and path-specific advice. Your progress saves automatically.
Choose your mode
Tailor to your path
Phase 11-3 weeks
0/12
Idea Validation
Most SaaS products fail because they solve a problem nobody has. Before writing a single line of code, prove that real people will pay for what you're building.
Define your target audience with painful specificity
"Small businesses" is too vague. "Freelance designers who waste 5+ hours/week on invoicing" is a market. The narrower you go, the easier everything else becomes.
If B2B: For B2B, define by company size, industry, and the buyer's role. 'Marketing managers at 50-200 person SaaS companies' is specific enough to build for.
If B2C: For B2C, define by lifestyle and pain frequency. 'Freelancers who invoice 10+ clients/month' tells you the pain is recurring and worth solving.
Write it as: "[Role] who [specific frustration] and currently [workaround they use]". If you can't fill in all three, you don't know your audience yet.
DevAPIAI-powered API docs tool"Backend engineers at 20-100 person startups who waste 4+ hours/week writing and updating API docs by hand, and currently use a mix of Swagger and Notion."
BookLocalSalon appointment booking"Independent salon owners who lose 3-5 appointments/week to no-shows and phone tag, and currently manage bookings with a paper diary or WhatsApp messages."
Join 3-5 communities where your target users hang out
Reddit subreddits, Discord servers, Slack groups, Facebook groups, LinkedIn groups. Lurk first. Understand how they talk about their problems.
If B2B: LinkedIn groups, niche Slack communities (e.g., RevGenius for sales, Superpath for content), and industry-specific subreddits are where B2B buyers talk openly.
If B2C: Reddit, Facebook groups, and Discord servers. B2C users are more vocal about frustrations in casual spaces - search for rant threads.
Don't pitch anything for at least 2 weeks. Just listen, note recurring complaints, and save threads where people describe their pain. Use F5Bot to get email alerts whenever your keywords are mentioned on Reddit or Hacker News - it's free and catches conversations you'd miss. Set up Google Alerts for your niche terms too, and create a Feedly board pulling RSS feeds from relevant subreddits and HN searches so you have a single feed of conversations to monitor daily.
DevAPIAI-powered API docs toolr/webdev, r/node, DevOps Slack groups, and the Postman Community forum. Search for complaints like "API docs are always outdated" and "Swagger is painful to maintain."
BookLocalSalon appointment bookingr/hairstylist, Facebook groups like "Salon Owners Hub," local business owner meetups. Listen for phrases like "clients keep texting at midnight" and "I hate phone bookings."
Set up a feedback capture and language mining system
Pick 1-2 primary discovery channels (Reddit + cold email, or LinkedIn + niche Slack groups). Set weekly outreach targets: 5 cold DMs, 3 Reddit comments, 1 post per week. Track every response in a spreadsheet with columns: exact words they used, where you found them, what made them reply. Review weekly - the language patterns that pull real replies become your marketing copy.
Don't just 'be active online.' Define a cadence: Monday = post in 2 communities, Wednesday = reply to 5 relevant threads, Friday = send 5 cold DMs. Track which messages get responses and double down on that angle. Use keyword alerts to catch niche conversations you'd miss by manual browsing.
Mine competitor reviews for unmet needs
Read 1-star and 2-star reviews on G2, Capterra, and Product Hunt. These are people who paid money, tried the product, and were disappointed - that's your opportunity. Pay attention to the exact language patterns - not just what they complain about, but how they describe the pain. Track whether they say "confusing," "too complex," "missing X," or "overpriced." These recurring phrases map directly to your positioning and copy.
Create a spreadsheet with columns: complaint, frequency, severity. Focus on high-frequency, high-severity issues that competitors keep ignoring.
Validate search demand with keyword research
Use Ahrefs, Semrush, or Google Keyword Planner to confirm people are actively searching for solutions. No search demand usually means no organic acquisition channel.
Look for keywords like "[competitor] alternative", "best [category] for [audience]", and "how to [task your product solves]". These reveal commercial intent.
Conduct 10-15 customer discovery interviews
Talk to potential users. Don't pitch - ask about their problems, current workarounds, and what they've tried. Document the exact words and phrases they use - this becomes your marketing copy and SEO keywords.
If B2B: Reach out via LinkedIn or warm intros. B2B buyers are used to vendor calls - frame it as research, not sales. Offer to share your findings as a hook.
If B2C: Post in communities offering a $10-20 gift card for a 20-minute call. B2C users need more incentive but give more candid feedback.
Never ask "would you use this?" (everyone says yes to be nice). Instead ask: "How do you currently handle this?" and "What have you tried?" Past behavior predicts future behavior.
DevAPIAI-powered API docs toolDM backend engineers on Twitter/X or Dev.to. Ask: "Walk me through what happens when your API changes - how do docs get updated?" You'll hear about manual Swagger edits, docs drifting out of sync, and onboarding confusion.
BookLocalSalon appointment bookingVisit 10 salons in person. Ask: "How do clients book with you today?" You'll hear about missed calls, double bookings from the paper diary, and clients who just walk in hoping for a slot.
Confirm this is a painkiller, not a vitamin
Painkillers solve urgent, burning problems people actively seek solutions for. Vitamins are nice-to-have. Build painkillers - things people will pay to fix right now.
Ask yourself: will someone switch from their current solution to yours? If they're "fine" with what they have, you have a vitamin.
Map 5+ competitors and identify your gap
Direct competitors, adjacent tools, and even manual workarounds. Know what you're replacing, then pinpoint what they all miss - simplicity, a specific integration, better UX, or pricing for smaller teams.
No competition usually means no demand. Some competition with clear gaps is the sweet spot for a new entrant.
Create a landing page to capture interest
Build a simple page (Carrd, Framer, or a single Next.js page) describing the solution with an email signup form. This is your first real demand test.
Technical: Spin up a Next.js or Astro page on Vercel in under an hour. Use Resend or Loops for the email capture.
Non-technical: Use Carrd ($19/yr), Framer, or Typedream. All are drag-and-drop, deploy in minutes, and look professional enough to test demand.
You don't need the product built. Describe the outcome: "Send invoices in 30 seconds, not 30 minutes." If people sign up, they want the outcome.
DevAPIAI-powered API docs toolHeadline - "API docs that update themselves." Subhead - "Point it at your codebase. Get always-accurate, beautifully formatted docs. No more Swagger wrestling." CTA - "Get early access."
BookLocalSalon appointment bookingHeadline - "Stop losing clients to missed calls." Subhead - "Online booking for salons - clients book 24/7, you get fewer no-shows." CTA - "Join the waitlist."
Drive targeted traffic to your landing page
Share in communities you joined, post on social media, do direct outreach to people who expressed the pain. Even $50-100 in paid ads can give you signal.
Use Hypefury or Buffer to schedule social posts across platforms. For Reddit, engage genuinely in threads first - link-dropping gets you banned. Pulse can help you find and engage with relevant Reddit threads at scale.
Hit 100+ email signups or 5+ pre-sales
These are your minimum validation thresholds. Email signups show interest. Pre-sales (even $1) prove willingness to pay - which is 10x more valuable.
Offer early-bird lifetime pricing at a deep discount. People who pay before the product exists are your most committed future users.
DevAPIAI-powered API docs toolOffer a $49 lifetime deal (normally $29/mo) to the first 20 people on your waitlist. Dev tools with clear ROI can pre-sell - engineers buy tools that save them time.
BookLocalSalon appointment bookingPre-selling is harder for SMBs - aim for 150+ email signups instead. Offer "first 3 months free" to the first 50 salon owners who sign up. They're skeptical of new tools, so low risk = higher conversion.
Survey signups on willingness to pay and feature priorities
Send a short survey: What would you pay monthly? Which features matter most? This shapes your pricing tiers and MVP scope before you write any code.
Use the Van Westendorp model: ask about too cheap, cheap, expensive, and too expensive price points. The overlap reveals the optimal price range.
Phase 21-2 weeks
0/10
Planning & Foundation
You've proven demand. Now define what you're building, how you'll charge, and the legal and brand foundation you need. Cut scope ruthlessly - your MVP should take weeks, not months.
Before you start: 5+ people told you they'd pay for this. You can describe the target user in one sentence. You've identified a clear gap competitors miss.
Write a one-sentence value proposition
"We help [WHO] do [WHAT] without [PAIN]." If you can't express it in one sentence, you don't understand the product yet.
Test it on a stranger. If they say "oh, that's useful" instead of "what does that mean?" - you nailed it.
Define the single core job-to-be-done
Your MVP does ONE thing exceptionally well. Not five things adequately. What's the one workflow that, if it works perfectly, makes users stay?
Frame it as: "When [situation], I want to [motivation], so I can [outcome]." This is the Job Story format - it keeps you focused on user intent.
DevAPIAI-powered API docs tool"When my API changes, I want docs to update automatically, so I can stop manually editing Swagger files and keep my team unblocked." The core job = auto-sync docs from code.
BookLocalSalon appointment booking"When a client wants to book, I want them to see my open slots and confirm instantly, so I can stop playing phone tag." The core job = self-serve booking.
List minimum features, then cut that list in half
Write down everything you think the MVP needs. Then ruthlessly remove anything non-essential for the core job. Then cut again. Ship the smallest thing that works.
If a feature doesn't directly help users complete the core workflow, it's not MVP. Settings pages, admin panels, dashboards - all can wait.
Define your "aha moment"
The exact point where a user realizes value. For Dropbox it's syncing a file. For Slack it's getting a reply. What's the moment users go from curious to committed?
Your entire onboarding should be laser-focused on getting users to this moment as fast as possible. Every extra step before it increases drop-off.
Choose your pricing model and set 2-3 tiers
Flat-rate, tiered, usage-based, freemium, or per-seat. Each tier should serve a different use case or scale, not just stack more features. Users should self-select into the right tier immediately.
If B2B: Per-seat or tiered pricing works best. B2B buyers expect annual discounts (20-30% off) and need invoicing/PO support. Plan for a sales-assisted tier above $500/mo.
If B2C: Keep it simple - 2 tiers max. B2C users comparison-shop fast and abandon complex pricing pages. Monthly-first with an annual toggle works well.
Freemium works for products with viral loops (Notion, Slack). If yours doesn't spread through usage, a free trial with card upfront converts better. Make the middle tier visually prominent.
DevAPIAI-powered API docs toolUsage-based by API endpoints documented. Free tier: 3 endpoints. Pro ($29/mo): unlimited endpoints + versioning. Team ($79/mo): SSO + multi-repo. Developers expect free tiers - use it as your funnel.
BookLocalSalon appointment bookingFlat monthly fee. Starter ($19/mo): 1 staff, online booking page. Pro ($39/mo): 5 staff, SMS reminders, Google Calendar sync. Keep it dead simple - salon owners won't parse usage-based pricing.
Decide on free trial structure
14 days is standard. Credit card upfront converts fewer trialists but higher-quality ones. No card upfront gets more signups but lower conversion.
If B2B: B2B trials should be 14-30 days - enterprise evaluation cycles are longer. Offer a guided demo or onboarding call for high-value accounts.
If B2C: 7-14 days is plenty. B2C users decide fast - if they don't activate in 3 days, they probably won't. Consider a freemium tier instead of a trial.
If your product's value is obvious within one session, require a card upfront. If it takes days to see value (like analytics tools), don't.
Calculate target unit economics
Know your target ARPU, acceptable CAC, and expected LTV. Aim for a 3:1 LTV-to-CAC ratio minimum. This frames every marketing and pricing decision you'll make.
Quick formula: if monthly churn is 5%, average customer lifetime = 20 months. LTV = ARPU x 20. Your CAC should be ≤ LTV / 3.
Register your domain name
Get a .com if possible. Check that the name doesn't have trademark conflicts and that social handles are available. Act fast - good names disappear quickly.
Draft legal documents (ToS, Privacy Policy, cookie consent)
Use Termly, iubenda, or a legal template. Cover data handling, user responsibilities, liability, and cookie consent. If you're targeting EU users, ensure GDPR compliance.
Don't skip this. App stores, payment processors, and enterprise customers all check for legal docs. Takes 30 minutes with a template generator.
Define brand identity: name, colors, typography
Doesn't need to be perfect, but be consistent from day one. Pick 2 brand colors, one font, and a simple logo. Consistency builds trust faster than perfection.
Use Realtime Colors or Coolors to generate a palette. For fonts, Inter or DM Sans are safe defaults that always look professional.
Phase 34-6 weeks
0/13
Build the MVP
Ship something real in 4-6 weeks. Not a prototype, not a mock-up - a working product that solves the core problem. Perfect is the enemy of launched.
Before you start: You have a one-sentence value proposition that strangers understand. Your MVP feature list fits on a sticky note. You've chosen a pricing model and set initial tiers.
Choose your tech stack (framework, database, hosting)
Use what you already know - Next.js, Rails, Laravel, Django all work. Pick a database (PostgreSQL is the safe default) and a hosting platform (Vercel, Railway, Fly.io). Optimize for speed to market, not perfection.
Technical: Next.js + Supabase + Stripe is a proven, well-documented stack. If you know Rails or Laravel, those are equally fast. Prioritize what you can ship in, not what's trendy.
Non-technical: Use Bubble.io, Softr, or a no-code SaaS boilerplate. You can build a real, paying product without writing code. Rewrite later if you hit scale limits.
If you're a solo founder, use a SaaS starter kit (Shipfast, Supastarter, LaraFast). They handle auth, billing, and emails out of the box and save weeks of boilerplate.
DevAPIAI-powered API docs toolNext.js + Supabase + Stripe. You need fast API parsing, so pick a stack you can extend with custom backend logic. Use Vercel for hosting - Edge Functions handle the doc generation pipeline.
BookLocalSalon appointment bookingUse a SaaS boilerplate like Shipfast or go no-code with Bubble. The booking logic is standard CRUD - don't over-engineer. Spend your time on the SMS reminder integration, not the framework choice.
Choose auth and payment solutions
For auth: Clerk, Supabase Auth, or NextAuth. Don't roll your own. For payments: Stripe is standard, or use Paddle/Lemon Squeezy if you want global sales tax handled for you (Merchant of Record).
If B2B: Enterprise buyers expect SSO (SAML/OIDC). Plan for it architecturally even if you don't build it yet. Use Clerk or WorkOS - they make adding SSO later trivial.
If B2C: Social login is non-negotiable. Add Google and Apple sign-in at minimum. Every extra field in your signup form costs you 10-15% of signups.
Non-technical: Bubble has built-in auth. For payments, connect Stripe via a Bubble plugin - it takes about 30 minutes. Softr handles Stripe natively.
Clerk and Supabase Auth are the fastest to integrate. For international sales, a Merchant of Record handles VAT, GST, and sales tax in 50+ jurisdictions so you don't have to.
DevAPIAI-powered API docs toolClerk + Stripe. Developers expect GitHub OAuth - add it on day one. Use Stripe's metered billing for usage-based pricing on API endpoint count.
BookLocalSalon appointment bookingSupabase Auth + Lemon Squeezy. Salon owners won't have GitHub accounts - use Google and email/password. Lemon Squeezy handles tax compliance so you can sell to salons globally without worrying about VAT.
Set up your repository with CI/CD
GitHub + GitHub Actions (or Vercel auto-deploy). Every push to main should deploy automatically. If deployment is painful, you'll ship less often.
Non-technical: If using no-code, your platform handles deployment. Skip this step - Bubble, Softr, and Webflow publish with one click.
Implement authentication
Signup, signin, password reset, email verification. Add Google or GitHub social login - it reduces signup friction significantly.
Social login can increase signups by 20-50%. At minimum, add Google OAuth. Takes about 30 minutes with most auth providers.
Build the ONE core workflow that delivers value
This is the feature that makes your product worth paying for. Everything else is support scaffolding for this single workflow. Build it first, build it well.
Define the workflow as a 3-5 step user journey. If it takes more than 5 steps to reach value, simplify until it doesn't.
DevAPIAI-powered API docs toolThe core workflow is: connect repo → auto-parse API routes → generate formatted docs → publish to a hosted URL. Four steps. Everything else (versioning, custom themes, team permissions) comes later.
BookLocalSalon appointment bookingThe core workflow is: owner sets available hours → client picks a slot → both get a confirmation. Three steps. SMS reminders, calendar sync, and payment collection are all Phase 2.
Design empty states that guide users forward
A blank dashboard is a dead end. Every empty state should explain what belongs there and include a clear CTA to get started.
Great empty states: "No invoices yet. Create your first one in 30 seconds →". Bad empty states: a sad illustration with "Nothing here yet."
Build responsive - test on actual mobile devices
At least 40% of SaaS signups happen on mobile. If your landing page or onboarding breaks on phones, you're silently losing nearly half your potential users.
Set up billing end-to-end
Integrate payments in production mode, create subscription plans, handle the full lifecycle (trials, upgrades, downgrades, cancellations, failed payments), and build a self-service page where users manage their plan without emailing you.
Test these specific flows: upgrade mid-cycle, cancel during trial, payment fails and retries, customer re-subscribes after cancellation. Stripe's Customer Portal is the quickest path for self-service.
Implement security essentials
HTTPS everywhere, CSRF protection, Content Security Policy headers, rate limiting on auth endpoints (5-10 req/min per IP), and all secrets in environment variables - never in source code.
If B2B: B2B buyers will ask about SOC 2, GDPR, and data residency. You don't need SOC 2 certification yet, but document your security practices on a /security page - it unblocks sales conversations.
Use securityheaders.com to scan your site. Add .env to .gitignore before your first commit. An A+ security rating takes about 15 minutes to configure.
DevAPIAI-powered API docs toolYou're handling source code access - security is a deal-breaker. Add scoped API tokens (read-only by default), audit logs for repo connections, and a clear data retention policy. Enterprise prospects will ask for these before trialing.
BookLocalSalon appointment bookingBasic security is enough early on. HTTPS, rate limiting, and GDPR-compliant data handling. Salon owners won't ask for SOC 2, but their clients' phone numbers and emails need to be stored securely.
Set up error and uptime monitoring
Sentry for errors, BetterStack or UptimeRobot for uptime. You need to know when things break before your users tell you. Install before launch, not after your first fire drill.
Configure Sentry with source maps and user context so you can actually reproduce bugs. A stack trace without context is nearly useless.
Configure automated database backups
Daily backups with a tested restore process. Most managed databases handle this automatically - verify it's enabled and test a restore at least once.
Backups you've never tested restoring are not real backups. Restore to a staging environment once and verify data integrity.
Optimize for Core Web Vitals
Page load under 3 seconds, LCP under 2.5s, CLS under 0.1. Slow products feel broken. Run Lighthouse and fix red flags before anyone sees it.
Biggest wins: optimize images (use next/image or equivalent), lazy load below-the-fold content, minimize blocking third-party scripts.
Test the full user journey end-to-end
Signup → onboarding → core workflow → upgrade → payment → settings. On desktop AND mobile. Fix every single point of friction you find.
Record yourself doing the full flow on Loom. Watch it back at 2x speed. You'll spot UX issues you completely missed while building.
Phase 42-4 weeks
0/13
Pre-Launch Marketing
Start marketing weeks before launch. Build anticipation, collect a waitlist, and line up distribution channels. Launch day traffic doesn't happen by accident.
Before you start: Your core workflow works end-to-end without crashing. At least 3 people have completed the core workflow successfully. Billing is functional - users can actually pay you.
Build a landing page that converts
Clear value proposition above the fold, feature/benefit sections, pricing, social proof, and multiple CTAs. Answer "what is this, who is it for, and why should I care" in 5 seconds.
Use the PAS framework: Problem (name the pain), Agitate (make it worse), Solution (your product). This structure outperforms feature-first pages every time.
DevAPIAI-powered API docs toolLead with the developer pain - "Your API docs are lying to your users." Show a side-by-side: manually maintained Swagger (outdated, ugly) vs. DevAPI-generated docs (auto-synced, clean). Include a live demo link - developers want to try before they trust.
BookLocalSalon appointment bookingLead with the outcome - "Your clients book while you sleep." Show a mock booking page with the salon's branding. Include a calculator: "If you lose 3 appointments/week at $50 each, that's $7,800/year." SMBs respond to dollar amounts, not features.
Record a product demo or walkthrough video
A 60-90 second screen recording showing the core workflow. People who watch a demo video convert 1.5-2x higher than those who don't.
Don't narrate every click. Show the outcome: "Watch me go from blank to finished invoice in 30 seconds." Focus on speed and simplicity.
Add social proof - even from beta users
Testimonials, company logos, user count, or metrics like "saved 120 hours for our beta users." Social proof is the number one conversion element after your headline.
If B2B: Company logos are the strongest B2B social proof. Even if you only have 3 beta customers, display their logos. Add a 'trusted by' row above the fold.
If B2C: Star ratings and user count matter most. 'Join 500+ freelancers' or '4.8/5 from 50 reviews' builds instant trust for consumer products.
No testimonials yet? Use quotes from discovery interviews: "Before [product], I spent 3 hours a week on this" - attributed to "Design freelancer, beta user."
DevAPIAI-powered API docs toolShow GitHub stars, logos of companies using it in beta, and a quote like "Cut our doc maintenance time from 4 hours/week to zero." Developers trust metrics and peer validation over marketing claims.
BookLocalSalon appointment bookingShow the number of bookings processed: "2,400+ appointments booked through BookLocal." Add a testimonial like "I used to lose 5 clients a week to no-shows. Now it's maybe 1." - Sarah, salon owner. Real names and photos matter for local businesses.
Write meta titles, descriptions, and OG images for every page
Every public page needs SEO metadata and social sharing cards. When someone shares your link on Twitter or LinkedIn, the preview card should look compelling.
Submit sitemap to Google Search Console
Generate a sitemap.xml, submit through GSC, and verify your site is being indexed. Also configure robots.txt to control crawler access.
Google can take weeks to index new domains. Submit early so you start appearing in search results around launch day.
Publish 3-5 blog posts targeting bottom-of-funnel keywords
"[Competitor] alternative", "best [tool] for [audience]", "how to [task your product solves]". These attract people already looking for a solution - your highest-converting traffic.
Bottom-of-funnel content converts 5-10x higher than educational top-of-funnel posts. Prioritize comparison and alternative pages early.
Set up all email sequences
Transactional emails (welcome, password reset, receipts) plus a waitlist nurture sequence: Day 0 welcome, Day 2 your story, Day 5 behind-the-scenes preview, Day 7-10 launch announcement with early-bird offer.
Your welcome email has the highest open rate you'll ever see. Don't waste it on "Welcome!" - guide users to their aha moment. Personal, founder-voice emails outperform polished marketing.
Install analytics and define your conversion funnel
Plausible, PostHog, or GA4 for web analytics. Set up event tracking for signup, activation, and payment. Define the funnel before launch so you can measure from hour one.
Track these events at minimum: page_view, signup_started, signup_completed, onboarding_completed, feature_used, trial_started, payment_completed.
Build in public and grow your network
Share your journey on Twitter/X, LinkedIn, and Indie Hackers. Reply to others' posts, share their content, offer real help. When launch day arrives, you'll have allies who amplify your reach.
If B2B: LinkedIn is your primary channel. Post about the problem you're solving 3x/week. Comment on posts by people in your target industry. Join niche Slack groups like RevGenius, Superpath, or Exit Five.
If B2C: Twitter/X, Reddit, and TikTok are your channels. Short-form content showing the product in action outperforms text posts. Reddit threads mentioning your problem space are golden - use Pulse to find and engage with them.
The 90/10 rule: 90% of posts provide value (insights, tips, behind-the-scenes). 10% mention your product. Use Hypefury to schedule threads and auto-retweet your best posts. Nobody follows an account that only promotes itself.
DevAPIAI-powered API docs toolTwitter/X is your primary channel. Post threads like "5 API doc mistakes that confuse your users" and share your build journey. Engage in dev-focused communities - contribute to discussions about documentation tools, API design, and DX.
BookLocalSalon appointment bookingLinkedIn and local Facebook groups. Post stories like "I visited 30 salons and learned how they all manage bookings. Here's what I found." Local business owners share content that reflects their struggles - be the person who understands them.
Run a beta program and collect testimonials
Recruit 20-50 testers from your waitlist and communities. Run it for 2-4 weeks with active weekly check-ins. Resolve all critical bugs, then ask happy users for 2-3 sentence testimonials.
Your best beta testers are people who complained about competitors in communities. They have the problem and they're vocal about it.
Prepare launch content for all platforms
Product Hunt (tagline, maker comment, screenshots, demo GIF), Hacker News (Show HN), Reddit, Indie Hackers, and your email list. Tailor each post to the platform's culture.
Reddit and HN punish blatant self-promotion. Lead with the story and the problem. "I spent 6 months building X because Y" works. "Check out my new SaaS!" doesn't.
Define your early-adopter offer
First 100 users get 30% lifetime discount, founding member pricing, or a one-time lifetime deal. Give early users a compelling reason to commit now instead of later.
Set up customer support infrastructure
Live chat (Intercom, Crisp) or a dedicated support email. Write help docs for common workflows. Prepare canned responses for the 10 questions you know are coming.
On launch day, fast response time is your unfair advantage. Reply within minutes, not hours. Early users who get quick help become your biggest advocates.
Phase 51 day
0/5
Launch Day
All your preparation comes down to execution. Launch early, monitor everything, respond to everyone, and document the wins - big and small.
Before you start: Your landing page is live with social proof and a clear CTA. You have launch content prepared for at least 3 platforms. Your email list has 100+ subscribers to notify.
Test the full flow one final time
Signup → onboarding → core feature → payment. On desktop and mobile. This is your last chance to catch breaking issues before real users hit it.
Launch on Product Hunt, Hacker News, Reddit, and Indie Hackers
Post on Product Hunt at 12:01 AM PST for max visibility. Use "Show HN" format for Hacker News. Follow each subreddit's self-promotion rules. Share your honest story on Indie Hackers.
Your Product Hunt maker comment should tell the story: why you built it, who it's for, what makes it different. On HN, keep the title factual and be ready for technical questions.
DevAPIAI-powered API docs toolLead with a Show HN - the developer audience there is your exact target. Title: "Show HN: DevAPI - auto-generated API docs that stay in sync with your code." Prepare for questions about how parsing works, which frameworks you support, and self-hosting options.
BookLocalSalon appointment bookingProduct Hunt is your primary launch platform - HN won't care about salon booking. Title: "BookLocal - the simplest way for salons to take online bookings." Pair it with a launch offer: first 3 months free for Product Hunt hunters.
Send launch announcements to waitlist and social media
Email your waitlist with the early-adopter offer and a deadline for special pricing. Post a Twitter/X thread about the journey, a LinkedIn post about the problem. Tag supporters and ask them to reshare.
If B2B: Send personalized emails to your beta users' managers and decision-makers. In B2B, the person who tested it often isn't the person who buys it - help them make the internal case.
If B2C: Emphasize urgency and exclusivity. 'First 100 users get lifetime pricing' or 'Early bird ends Friday' drives immediate action from consumer audiences.
DevAPIAI-powered API docs toolSend a launch email with a live link to docs generated from a popular open-source project. "See what DevAPI does with the Stripe API" - let the output sell itself. Post a Twitter/X thread walking through the before/after of manually maintained docs.
BookLocalSalon appointment bookingSend an email with a personalized booking page mockup: "Here's what your salon's booking page could look like." Include the founding-member discount and a hard deadline. Post in local business Facebook groups with the story of why you built it.
Monitor performance, errors, and conversions in real time
Check dashboards every 30 minutes. Watch for errors, slow responses, and funnel drop-offs. Have your deploy pipeline ready for emergency hotfixes.
Set up Slack or Discord alerts from your monitoring tools so you're notified instantly instead of staring at dashboards all day.
Reply to every comment, email, and social mention
Within 1 hour. Launch day engagement builds momentum. Every reply is a chance to convert a curious visitor into a paying user.
Block your entire calendar for launch day. No meetings, no distractions. Just ship fixes and respond to people. This is your highest-leverage day. Set up F5Bot alerts for your product name on Reddit and HN so you don't miss any mentions.
Phase 62 weeks
0/9
Post-Launch: First 2 Weeks
The real work starts now. Launch day buzz fades fast. Retain the users you acquired, learn from them rapidly, and fix the biggest problems before they churn.
Before you start: You launched on at least one platform. Real users have signed up (not just friends and family).
Ship daily fixes based on real user feedback
Prioritize the bugs and UX issues that the most people report - not the most technically interesting ones. Speed of iteration in the first two weeks builds trust and loyalty.
Create a public changelog (changelog.yoursaas.com or a Notion page). Users love seeing rapid progress, and it proves you're actively listening.
Analyze your funnel and identify retention behaviors
Where are users dropping off - after signup, during onboarding, before the aha moment? Then look at what active users do differently from churned ones. If users who complete 3+ projects stick, push onboarding toward that behavior.
If less than 40% of signups complete onboarding, the onboarding is the bottleneck - not your product. This is your activation metric. Find your product's equivalent of Slack's 2,000 messages.
DevAPIAI-powered API docs toolTrack: connected repo → generated first docs → shared docs link → invited team member. If users who share their docs link retain 3x better, add a "Share your docs" prompt right after first generation. The sharing step is your activation event.
BookLocalSalon appointment bookingTrack: created profile → set availability → got first booking → got first repeat booking. If salons that get 5+ bookings in week one stick, focus on driving that first booking - send a "share your booking link" email immediately after setup.
Build a structured feedback and churn-language tracker
Go beyond NPS. Track the exact words churned users use, where active users first heard about you, and which support tickets reveal systemic confusion. Categorize feedback by: feature request, UX confusion, missing integration, pricing objection. Review weekly with your usage data - the overlap between 'what users say' and 'what users do' reveals your real priorities.
Create a 'voice of customer' doc that your whole team (even if it's just you) can reference. Pull quotes from support conversations, cancellation surveys, Reddit mentions, and review sites. Update it weekly. The patterns that repeat across 3+ sources are your next high-priority fix.
Interview 5-10 early users on video calls
White-glove treatment. Watch them use the product, ask what confused them, what delighted them, and what almost made them leave. This feedback is irreplaceable.
Offer a $20 gift card or a free month for 30 minutes of their time. The insights from one session are worth 100x the cost.
Send an NPS survey at day 14
"How likely are you to recommend [product]?" Follow up on detractors (0-6) immediately - they'll tell you exactly what's broken. Promoters (9-10) are your testimonial goldmine.
Ask activated users for testimonials and reviews
Happy users after 2 weeks are your best advocates. Ask them to leave a review on Product Hunt, G2, or provide a quote for your landing page.
Set up a SaaS metrics dashboard
Track MRR, signups, activation rate, churn rate, and trial-to-paid conversion. Use ChartMogul, Baremetrics, or even a spreadsheet. Review weekly without fail.
Early-stage benchmarks to aim for: under 8% monthly churn, 25-40% trial-to-paid (with card upfront), 40%+ activation rate.
Set up behavior-triggered onboarding emails
Day 1: Welcome + quick start. Day 3: Highlight an unused key feature. Day 7: Check-in. Day 14: Value summary + upgrade CTA. Triggered by behavior, not just time.
"You created a project but haven't invited a team member" beats "Day 3 email." Behavior-triggered emails consistently outperform time-based sequences.
Reach out to every churned user
When someone cancels, ask why. A simple "What could we have done differently?" email yields the most honest, actionable feedback you'll ever receive.
Most early churn comes from three causes: confusing onboarding, a missing critical feature, or the product being slower than expected. Fix these first. Structure your churn interviews: ask what they hoped the product would do, what actually happened, and what they switched to. Categorize responses (onboarding, missing feature, price, competitor) and track the distribution monthly - when one category dominates, that's your next sprint.
Phase 7Weeks 3-12
0/11
Growth Foundation
You survived the first two weeks. Now build the engine that compounds - content, distribution, retention, and revenue expansion. Growth is a system, not a hack.
Before you start: You have at least 10 paying customers. Your monthly churn is under 15%. Users are completing the core workflow without hand-holding.
Double down on your best acquisition channel
Analyze where your first paying customers actually came from. SEO? Twitter? Product Hunt? Reddit? Invest 80% of effort into the one channel that's working.
If B2B: For B2B, content marketing (SEO) and cold outreach typically have the best CAC. Build a cold email sequence targeting companies that match your best customers - personalize the first line using their tech stack or recent hires.
If B2C: For B2C, social media and community-driven growth dominate. Reddit, Twitter, and TikTok short-form content showing your product in action drives organic signups at near-zero CAC.
Most early-stage SaaS products get 60-80% of growth from 1-2 channels. Spreading thin across five means being mediocre at all of them.
DevAPIAI-powered API docs toolIf most signups came from your Show HN post and Twitter threads, double down on developer content marketing. Write about API design best practices, publish benchmarks comparing doc generation tools, and contribute to open-source projects that integrate with yours. Cold outreach to engineering managers at companies using outdated doc tools.
BookLocalSalon appointment bookingIf most signups came from Facebook groups, invest there. Create a "salon business tips" content series, partner with beauty supply distributors for referrals, and walk into salons with a tablet showing their own booking page mockup. Local, in-person outreach has the highest conversion rate for SMB tools.
Publish content targeting high-intent keywords
Publish 2-4 posts per month. Prioritize comparison pages ("[Your product] vs [competitor]"), alternative pages, and how-to guides. These rank for high-intent keywords and convert extremely well.
One "[Competitor] vs [Your Product]" comparison page can generate more signups than ten educational posts. Prioritize commercial intent keywords.
Build a referral or word-of-mouth loop
In-app sharing, "powered by" badges, referral discounts, or features that naturally involve inviting others. The best growth comes from users bringing in users.
If B2B: In B2B, 'invite your team' is the natural viral loop. Per-seat pricing incentivizes expansion within companies. Add a 'powered by [your product]' badge on shared outputs.
If B2C: Referral credits work well - 'Give $10, get $10' or 'Both get a free month.' Make sharing dead simple with pre-written social posts and one-click invite links.
Dropbox's referral program grew them from 100K to 4M users in 15 months. Even a simple "invite your team" prompt helps significantly.
DevAPIAI-powered API docs toolAdd a "Powered by DevAPI" badge to every hosted docs page (with a link back). Every time a developer reads API docs powered by you, they see the brand. Offer a free month for every team member invited. The viral loop is: dev reads docs → clicks badge → signs up for their own project.
BookLocalSalon appointment bookingAdd "Book with BookLocal" branding on the booking page. Every client who books sees it. Offer a free month to salon owners who refer another salon. The referral loop is salon-to-salon: "My friend uses this booking tool and her no-shows dropped to zero."
Implement progressive onboarding
Tooltips, checklists, guided tours - help users discover features gradually instead of dumping everything on them at once during signup.
An in-app checklist ("3 of 5 steps complete") can boost activation by 20-30%. Keep it to 5 steps maximum.
A/B test your pricing page
Test different price points, tier structures, and page layouts. Even small changes to pricing presentation can swing conversion rates 10-30%.
Test adding an annual plan toggle with a visible discount ("Save 20%"). Annual plans reduce churn and dramatically improve your cash flow.
Launch expansion revenue opportunities
Add-ons, higher tiers, seat-based upgrades, or annual plans. Existing customers are 5-7x cheaper to monetize than acquiring new ones.
Track Net Revenue Retention (NRR). If NRR exceeds 100%, your existing customers are growing faster than they churn. This is the holy grail of SaaS metrics.
Get listed on directories and review sites
G2, Capterra, Product Hunt, SaaSHub, AlternativeTo, and niche directories. These generate steady, high-intent organic traffic with minimal ongoing effort.
If B2B: G2 and Capterra are must-haves for B2B. Enterprise buyers use these to build shortlists. Ask every happy customer to leave a review - even 5-10 reviews makes you visible.
If B2C: Product Hunt, AlternativeTo, and niche communities matter more. B2C users discover tools through recommendations and 'best of' lists.
Build automated win-back emails for churned users
Send a "we've improved" email 30 days after cancellation, highlighting new features and fixes. A percentage of churned users will come back.
Include a special offer: "Come back and get 50% off for 2 months." Winning back a churned user costs far less than acquiring a new one.
Implement usage-based engagement triggers
Email users who haven't logged in for 7 days. Celebrate milestones ("You created 100 invoices!"). Nudge toward underused features. Keep users engaged before they drift away.
Create a public roadmap
Use Canny, Productboard, or a simple Notion page. Let users vote on features. This reduces "why doesn't it do X?" tickets and shows you're user-driven.
A public roadmap doubles as a retention tool. Users stick around when they see their requested feature is "planned" or "in progress."
Schedule quarterly security and performance reviews
Dependency scanning, basic penetration testing, performance audits, database query optimization. Technical debt compounds like interest - pay it down regularly.
Run npm audit (or equivalent) monthly. Update dependencies quarterly. One unpatched vulnerability can undo months of trust-building.