The SaaS Founder's Complete Launch

Kit

How to Use This Kit

Work through each section in order. Every checklist item is binary — done or not
done. No partial credit. If you cannot check a box, that gap is your current highest
priority. Timelines assume a solo founder or small team (1-3 people). Adjust sprint
lengths for larger teams.
Contents
The SaaS Founder's Complete Launch Kit.................................................................... 1
1. MVP VALIDATION CHECKLIST ................................................................................ 6
Phase 0 — Problem Validation (Before Writing Code).............................................. 6
The Problem Is Real ................................................................................................ 6
The Market Is Large Enough ................................................................................... 6
The Solution Hypothesis Is Defined........................................................................ 7
Phase 1 — Solution Validation (Prototype Before Product) ...................................... 7
Fake It Before You Build It....................................................................................... 7
Pre-Sell Before You Build ........................................................................................ 7
Competitive Landscape ........................................................................................... 8
Phase 2 — MVP Definition (What to Build) ................................................................ 8
Scope the MVP Ruthlessly ...................................................................................... 8
Technical Readiness................................................................................................ 8
Phase 3 — MVP Validation (After Shipping) .............................................................. 9
Activation Metrics ..................................................................................................... 9
Revenue Validation .................................................................................................. 9
Pivot or Proceed Decision ....................................................................................... 9
2. LAUNCH CHECKLIST .............................................................................................. 10
T-42 Days — Foundation .......................................................................................... 10
Product ................................................................................................................... 10
Infrastructure .......................................................................................................... 10
Security ................................................................................................................... 10
T-28 Days — Marketing Foundation......................................................................... 11
Brand and Website ................................................................................................ 11
SEO Foundation..................................................................................................... 11
Email Infrastructure ................................................................................................ 11
T-14 Days — Billing and Operations ........................................................................ 12
Stripe....................................................................................................................... 12
Customer Support .................................................................................................. 12
Legal and Compliance ........................................................................................... 12
T-7 Days — Launch Preparation .............................................................................. 13
Product Final Checks............................................................................................. 13
Marketing Preparation ........................................................................................... 13
 Operations .............................................................................................................. 13
T-0 — Launch Day..................................................................................................... 14
Morning (7am–9am)............................................................................................... 14
Launch (9am–12pm).............................................................................................. 14
Ongoing Monitoring................................................................................................ 14
T+7 Days — Post-Launch Review............................................................................ 14
3. BETA PROGRAM CHECKLIST ............................................................................... 16
Program Design ......................................................................................................... 16
Define the Beta Before You Run It........................................................................ 16
Beta User Profile .................................................................................................... 16
Recruitment ................................................................................................................ 17
Finding Beta Users ................................................................................................ 17
Beta Application Process....................................................................................... 17
Onboarding Beta Users ............................................................................................. 17
Beta Kickoff ............................................................................................................ 17
Documentation for Beta ......................................................................................... 18
Running the Beta ....................................................................................................... 18
Week 1 .................................................................................................................... 18
Weekly Cadence (Weeks 2 through End) ............................................................ 18
Feedback Collection Methods ............................................................................... 18
Beta Graduation Criteria............................................................................................ 19
Go/No-Go Assessment .......................................................................................... 19
If Graduation Criteria Not Met ............................................................................... 19
Beta Wrap-Up ............................................................................................................ 19
Closing the Beta ..................................................................................................... 19
Beta Learnings Document ..................................................................................... 20
4. PRICING FRAMEWORK .......................................................................................... 21
Step 1 — Know Your Numbers Before Setting a Price ........................................... 21
Cost Floor (Minimum Viable Price) ....................................................................... 21
Value Ceiling (Maximum Justified Price) .............................................................. 21
Step 2 — Competitive Benchmarking....................................................................... 22
Step 3 — Tiering Framework .................................................................................... 23
The Three-Tier SaaS Pricing Structure ................................................................ 23
Step 4 — Pricing Psychology Checklist ................................................................... 24
Anchoring and Framing ......................................................................................... 24
Trial and Risk Reduction ....................................................................................... 24
The Decoy Effect.................................................................................................... 25
 Step 5 — Pricing Validation Before Launch ............................................................. 25
Pre-Launch Pricing Tests ...................................................................................... 25
Red Flags That Your Pricing Is Wrong ................................................................. 26
Step 6 — Pricing Change Playbook ......................................................................... 26
Raising Prices (Inevitable as You Grow) .............................................................. 26
Lowering Prices (Rare but Sometimes Necessary) ............................................. 26
5. PRODUCT HUNT LAUNCH PLAN .......................................................................... 27
8 Weeks Before Launch ............................................................................................ 27
4 Weeks Before Launch ............................................................................................ 27
Assets Preparation................................................................................................. 27
Copy Templates ..................................................................................................... 28
1 Week Before Launch .............................................................................................. 29
Build Your Launch List ........................................................................................... 29
Schedule and Timing ............................................................................................. 29
Community Prep .................................................................................................... 29
Launch Day Protocol ................................................................................................. 30
12:01 AM — Go Live.............................................................................................. 30
6:00 AM — First Push ............................................................................................ 30
Throughout the Day (Every 2 Hours) .................................................................... 30
6:00 PM — Second Push ...................................................................................... 31
Post-Launch (Day 2 Onwards).................................................................................. 31
What to Expect (Realistic Benchmarks) ............................................................... 31
6. REDDIT LAUNCH PLAN .......................................................................................... 32
Understanding Reddit Before You Post ................................................................... 32
The Cardinal Rules ................................................................................................ 32
4 Weeks Before Launch: Build Karma...................................................................... 32
Key Subreddits by Audience Type ........................................................................ 33
Reddit Post Formats That Work................................................................................ 33
Format 1: "I Built This" (Best for Technical/Developer Audiences)..................... 33
Format 2: "Show r/SaaS" (Best for Founder Communities) ................................ 34
Format 3: Value Post That Mentions Your Product (Best for General Subreddits)
................................................................................................................................ 34
Reddit Launch Execution .......................................................................................... 35
Week of Launch ..................................................................................................... 35
Handling Negative Comments .............................................................................. 35
Reddit Post Performance Targets ............................................................................ 36
7. LINKEDIN LAUNCH PLAN ....................................................................................... 37
 Profile Optimization (Do This Before Your Launch)................................................. 37
LinkedIn Content Strategy: The 4-Week Pre-Launch Build .................................... 37
Week -4: Authority Building ................................................................................... 37
Week -3: Social Proof Building.............................................................................. 38
Week -2: Waitlist Push........................................................................................... 39
Week -1: Launch Announcement Prep................................................................. 39
Launch Day LinkedIn Post ........................................................................................ 40
LinkedIn Launch Week Engagement Protocol ......................................................... 41
Day 1 (Launch Day) ............................................................................................... 41
Days 2-7 ................................................................................................................. 41
LinkedIn Launch Performance Targets ................................................................ 41
8. EMAIL LAUNCH PLAN ............................................................................................. 42
Building Your List Before Launch ............................................................................. 42
Pre-Launch List Building Tactics ........................................................................... 42
Minimum List Size to Make Launch Email Worth It ............................................. 42
The Launch Email Sequence (7 Emails) .................................................................. 43
Email 1 — Waitlist Confirmation (Triggered Immediately on Signup)................. 43
Email 2 — Value Email (Sent 1 Week After Signup) ........................................... 43
Email 3 — Social Proof Email (Sent 2 Weeks Before Launch) ........................... 44
Email 4 — Pre-Launch Urgency (Sent 48 Hours Before Launch) ...................... 44
Email 5 — Launch Day Email (Sent at Launch Time) ......................................... 45
Email 6 — Follow-Up for Non-Openers (Sent 48 Hours After Launch) .............. 45
Email 7 — One Week Post-Launch Recap .......................................................... 46
Email Technical Setup for Launch ............................................................................ 47
Launch Email Calendar at a Glance ......................................................................... 47
Email Launch Performance Benchmarks ................................................................. 48
Common Launch Email Mistakes ............................................................................. 48
 1. MVP VALIDATION CHECKLIST
The goal of an MVP is not to ship software. It is to answer a specific
question with the minimum possible effort. Every item on this list exists to
protect you from building something nobody wants.

Phase 0 — Problem Validation (Before Writing Code)

The Problem Is Real
● I have spoken to at least 10 potential customers about the problem (not the
solution)
● At least 7 of 10 confirmed this is a real, recurring pain point
● At least 3 of 10 are currently paying money (time or cash) to solve it with a
workaround
● I can describe the problem in one sentence that resonates when I say it to
strangers
● I have documented the exact workflow of a customer experiencing this problem
(step by step)
● I know when the problem occurs (trigger event) and how often (frequency)
● I know who the primary sufferer is (job title, company size, industry)
● I know why existing solutions fail them (not just "they're too expensive")

The Market Is Large Enough

● I have estimated the Total Addressable Market (TAM) with a bottom-up
calculation
● TAM is large enough to support a $1M+ ARR business (minimum viable market)
● I can name at least 5 companies who are my ideal first customers
● I know the buying process: who decides, who influences, who pays
● I understand the buying frequency: is this a one-time or recurring purchase?
The Solution Hypothesis Is Defined
● I have written a one-sentence product hypothesis: "We believe [customers] will
use [product] to [job to be done] because [reason they'll choose us over
alternatives]"
● I have defined one primary assumption that, if wrong, kills the business
● I have defined the minimum experiment to test that assumption
● I have set a binary success criterion: "We will proceed if X, stop if not X"
● I have set a time box: "We will know in [X weeks/months]"

Phase 1 — Solution Validation (Prototype Before

Product)
Fake It Before You Build It
● I have created a landing page describing the product (no code, just copy and a
CTA)
● The landing page has a clear value proposition in the headline (outcome, not
feature)
● The landing page has a working signup or waitlist form that captures email
● I have driven at least 100 visitors to the landing page through targeted channels
● Landing page conversion rate is above 5% (visitors → signup) — if not, the
messaging is wrong
● I have shown the landing page to 5 target customers and they said "I want this"
unprompted
● I have a Figma mockup or Loom demo video showing what the product will do
● At least 3 potential customers have seen the mockup/video and asked "how
do I sign up?"

Pre-Sell Before You Build

● I have asked at least 5 potential customers: "Would you pay $[price] for this
today?"
● At least 2 have said yes with a specific number
● I have attempted to collect payment (credit card or signed LOI) before building
● I have collected at least 1 paying customer or 1 signed letter of intent
○ If you cannot get anyone to commit to paying, do not build yet. Iterate on the
problem.
Competitive Landscape
● I have listed every direct competitor (same solution, same customer)
● I have listed every indirect competitor (different solution, same customer)
● I have listed "do nothing" as a competitor and why customers switch away from it
● I can articulate one specific reason a customer would choose me over each
competitor
● I have personally used every major competitor's product for at least 1 hour
● I have read 100+ reviews of competitors on G2, Capterra, or Trustpilot
● I have documented the top 3 complaints about each competitor (my opportunity)

Phase 2 — MVP Definition (What to Build)

Scope the MVP Ruthlessly
● I have listed every feature I want to build eventually (the full vision)
● I have applied the "if we removed this, would the first customer still pay?"
test to each feature
● I have a written MVP scope document that a developer could build from
● The MVP addresses one primary job to be done — not three
● I have explicitly written a "Not in MVP" list with reasons for each exclusion
● A customer can experience the core value of the product in under 10 minutes
of signing up
● The MVP can realistically be built in under 8 weeks by the available team
● I have identified the one metric that will tell me if the MVP is working

Technical Readiness
● Tech stack is chosen and justified (not just "what I know")
● Auth strategy defined (Supabase / Auth0 / custom)
● Data model sketched (ERD exists, even if rough)
● Hosting platform chosen (Vercel / Railway / [Link] / AWS)
● Payment processing chosen (Stripe — almost always)
● Domain acquired and email configured (no @[Link])
● Source control and CI/CD configured before writing a line of code
● Staging environment exists and is separate from production

Phase 3 — MVP Validation (After Shipping)

Activation Metrics
● I have defined the activation event: the first action that signals a user got value
● Activation event tracking is live in PostHog, Mixpanel, or Amplitude
● At least 5 users have completed the activation event within the first week
● Activation rate (signup → activation) is measured (target: >30% in first month)
● I have watched at least 5 users use the product (Loom recordings or live sessions)
● I have documented every point where users got confused or quit

Revenue Validation
● At least 1 user is paying (even if manually invoiced)
● At least 3 users are actively using the product weekly
● 0 users have asked for a refund (or if they did, I understand exactly why)
● I can describe the "aha moment" — the exact thing that makes users say "this is
worth paying for"
● The product works without me being present (not demo-ware)

Pivot or Proceed Decision

● I have set a go/no-go date for the MVP experiment
● I have defined what "enough traction" looks like to proceed to launch
● I have defined what failure looks like that requires a pivot
● I have a pivot hypothesis ready if the primary assumption is wrong
● I have at least 5 learnings from the MVP documented regardless of outcome
 2. LAUNCH CHECKLIST
Launch is not a moment. It is a process. This checklist covers the 6 weeks
before launch and 4 weeks after. An unchecked item at launch is a known
liability.

T-42 Days — Foundation

Product
● Core user flows work end-to-end without bugs (signup → activation → value)
● All P0 bugs resolved (no crashes, no data loss, no payment errors)
● Product works on Chrome, Firefox, Safari, and Edge
● Product works on mobile (responsive design or native)
● Loading states exist for every async operation
● Empty states are designed and implemented (first-time user sees guidance, not
blank screens)
● Error states show helpful messages (not stack traces)
● 404 and 500 pages are branded and helpful
● Performance: core pages load in under 3 seconds on a 4G connection

Infrastructure
● Production environment is separate from staging
● SSL certificate configured (HTTPS everywhere)
● Custom domain configured (not *.[Link] or *.[Link])
● Database backups configured and tested (restore tested, not just backup)
● Uptime monitoring configured (Better Uptime / Pagerduty / UptimeRobot)
● Error monitoring configured (Sentry)
● Log aggregation configured (Logtail / Axiom)
● Environment variables documented and rotated from development values

Security
● All API endpoints require authentication (tested without token)
● SQL injection protection in place (parameterized queries or ORM)
● Webhook signatures verified on all inbound webhooks
● Rate limiting on authentication endpoints
● Rate limiting on AI/expensive endpoints
● Service role key never exposed in client-side code
● npm audit run and critical/high vulnerabilities resolved

T-28 Days — Marketing Foundation

Brand and Website
● Product name finalized (domain available, no trademark conflicts)
● Logo designed (minimum: wordmark)
● Brand colors and typography defined
● Landing page live with: headline, subheadline, 3 benefits, CTA, social proof
● Landing page converts at >5% (measure with Plausible / GA4)
● About page or founder story page live
● Pricing page live with 2-3 tiers clearly explained
● Contact page with working email
● Privacy policy live (use a generator + legal review)
● Terms of service live
● Cookie consent (if serving EU users)
● [Link] and [Link] configured

SEO Foundation
● Meta title and description on every page
● Open Graph image for social sharing
● Google Search Console verified
● At least 1 blog post live targeting a relevant keyword
● Google Analytics or Plausible installed

Email Infrastructure
● Custom domain email configured (you@[Link], not gmail)
● SPF, DKIM, DMARC DNS records set and verified
● Welcome email automated (triggers on signup)
● At least 3 transactional emails working: welcome, payment confirmation, password
reset
● Unsubscribe mechanism works

T-14 Days — Billing and Operations

Stripe
● Stripe account in live mode (test mode only until this point)
● Products and prices created in live mode
● Checkout flow tested with a real card in live mode
● Webhook endpoint registered in live mode with correct events
● Webhook secret updated to live mode value in production env vars
● Failed payment flow tested (use Stripe test card 4000000000000341)
● Customer Portal configured and tested
● Stripe tax configured (or explicitly decided not to collect tax yet)
● Stripe account details complete (business info, bank account for payouts)
● Stripe has verified your business (check for any outstanding action items)

Customer Support
● Support email address set up and monitored (support@[Link])
● Help documentation: at least 5 articles covering the most common questions
● FAQ page live (answering the top 5 pre-sales questions)
● Response time SLA defined and publicized (e.g., "We respond within 24 hours")
● Support ticket system configured (even if just a shared inbox)
● Refund policy written and linked from pricing page

Legal and Compliance

● Privacy policy reviewed by a lawyer or validated service (Termly / Iubenda)
● Terms of service reviewed
● GDPR compliance: cookie consent, data deletion flow, privacy policy disclosures
● Data Processing Agreements in place with: Stripe, Supabase, OpenAI, Resend,
Slack
● If collecting EU user data: lawful basis documented for each data type
T-7 Days — Launch Preparation
Product Final Checks
● Full end-to-end smoke test in production (signup → upgrade → use feature →
cancel)
● Data import tested (if you offer migration from competitors)
● Onboarding flow optimized: user reaches activation event in <10 minutes
● In-app onboarding checklist or guided tour implemented
● Keyboard shortcuts and accessibility spot-checked

Marketing Preparation
● Launch blog post written and scheduled
● 5 social posts drafted and scheduled for launch week
● Launch email drafted for waitlist (if you have one)
● Press kit created: logo files, product screenshots, founder bio, key stats
● Outreach list of 50 people to personally notify on launch day
● Any paid ads set up but paused (ready to enable on launch day)
● Product Hunt submission drafted (see Section 5)
● Reddit post drafted (see Section 6)
● LinkedIn post drafted (see Section 7)

Operations
● Monitoring dashboards open and baseline metrics documented
● On-call plan for launch day: who responds if the site goes down
● Rollback plan documented: how to revert if a critical bug is found post-launch
● Status page configured (even a simple one at [Link])
● Capacity tested: can the infrastructure handle 10x normal load?
T-0 — Launch Day
Morning (7am–9am)
● Final smoke test: can you sign up and complete the core flow right now?
● Monitoring dashboards open on a second screen
● Error monitoring (Sentry) checked for overnight issues
● Stripe dashboard open
● Slack/Discord #ops channel watched
● Team briefed on their launch day roles
● Coffee obtained

Launch (9am–12pm)
● Product Hunt submission goes live (if applicable — see Section 5)
● Blog post published
● Social media posts published
● Launch email sent to waitlist
● Personal outreach sent to 50 contacts
● Reddit post published (if applicable — see Section 6)
● LinkedIn post published
● Hacker News "Show HN" post (if developer audience)

Ongoing Monitoring
● Check error rate every 30 minutes for first 4 hours
● Check Stripe for successful payments
● Respond to every comment, reply, and message on launch day
● Triage any support requests within 2 hours
● Document every bug reported (fix critical, log non-critical)
● Post progress updates in public launch threads (maintain momentum)

T+7 Days — Post-Launch Review

● Total signups counted and compared to target
● Total paid conversions counted
● All launch bugs resolved or triaged
● Launch retrospective documented: what worked, what didn't
● Follow-up thank-you sent to everyone who helped promote the launch
● Top 10 pieces of feedback from launch week documented
● Week 2 roadmap adjusted based on launch learnings
● First cohort retention measured (are day-1 users coming back?)
 3. BETA PROGRAM CHECKLIST
A good beta program is not "let some people use it early." It is a structured
research program with clear goals, defined participants, and a graduation
criterion.

Program Design
Define the Beta Before You Run It
● What are you testing? Specific hypotheses written (not just "does it work?")
○ Hypothesis 1: Users can complete [core flow] in under 10 minutes without
guidance
○ Hypothesis 2: [Feature X] is used by >50% of beta users within the first week
○ Hypothesis 3: Users would pay $[price] for this product
● Success criteria defined: what outcomes will graduate this to public launch?
● Failure criteria defined: what would cause you to extend or cancel beta?
● Duration set: [X weeks] with hard end date on calendar
● Size set: [X beta users] — enough for signal, small enough to support personally
● Budget set: compensation, any tooling, your time commitment

Beta User Profile

● Ideal beta user described in detail (not just "anyone who wants to try it")
● 3 must-have criteria that every beta user must meet
● 2 disqualifying criteria (who should NOT be in this beta)
● Target mix defined: [X power users] + [X casual users] + [X skeptical users]
● Company sizes and industries represented in the beta cohort
● At least 2 beta users who are current customers of your primary competitor
Recruitment
Finding Beta Users
● Waitlist from landing page → email everyone who signed up before product
existed
● LinkedIn outreach: 50 targeted messages to ideal customer profile
● Twitter/X: post asking for beta testers with specific criteria
● Communities: relevant Slack groups, Discord servers, Reddit subreddits
● Personal network: founders, colleagues, former coworkers in the target industry
● Existing customers (if you have them): power users get early access

Beta Application Process

● Screening application form created (Google Form or Typeform)
○ What is your current role and company?
○ What is the problem you are trying to solve?
○ How are you currently solving it?
○ How much time per week do you spend on this problem?
○ What would make this a successful beta experience for you?
○ How available are you for weekly 30-minute feedback calls?
● Acceptance email template written
● Rejection email template written (polite, offer waitlist spot)
● Beta agreement / NDA template ready (optional but recommended)
● Acceptance rate target set (aim for 20-30% acceptance to filter for commitment)

Onboarding Beta Users

Beta Kickoff
● Welcome email with all access details
● Beta Slack channel or Discord server created
● Kickoff call scheduled (30-60 min group call for cohort if >5 users)
● Beta welcome doc sent: goals, timeline, how to give feedback, what to expect
● First task assigned: "Do X and tell us what happened"
● Direct line to founder established (Slack DM, email, Calendly link)
Documentation for Beta
● Getting started guide: how to set up and do the first thing
● Known issues list (be transparent — "we know about X, it's on our list")
● Feedback channel: where to report bugs, feature requests, general reactions
● "How to give good feedback" guide (specific > vague, show screenshots)
● Privacy and data handling disclosure

Running the Beta

Week 1
● Every beta user contacted personally within 48 hours of signup
● First usage checked: who has logged in? Who hasn't? Chase the inactive ones
● Day 3 check-in survey sent (2 questions max):
○ Have you been able to complete [core action]? Yes / No / Stuck
○ What one thing would make this better?
● First bug triage: fix P0s within 24 hours, acknowledge all P1s
● Weekly update sent to beta cohort: what you fixed this week

Weekly Cadence (Weeks 2 through End)

● Weekly 30-minute 1:1 calls with at least 3 beta users
● Weekly group update: what changed, what's coming, highlight a piece of feedback
you acted on
● Weekly NPS survey (single question: 0-10, "How likely to recommend?")
● Bug triage: all reported bugs logged and triaged
● Feature request log: every request documented with frequency count
● Usage data reviewed: who is using what, where are drop-offs

Feedback Collection Methods

● In-app feedback widget (Canny / Intercom / custom)
● Weekly email survey (3-5 questions, under 2 minutes)
● User interview recordings (Loom or Zoom) — at least 2 per week
● Session recordings (Hotjar / FullStory) — with beta user consent
● Support ticket analysis: what are they asking for help with?

Beta Graduation Criteria

Go/No-Go Assessment
Before graduating from beta to public launch, confirm:

● Activation rate: >30% of beta users complete the activation event in week 1
● Retention: >40% of beta users still active in week 3
● Willingness to pay: >50% of beta users say they'd pay the planned price
● Net Promoter Score: NPS > 20 (aim for > 30 before launch)
● Critical bug count: 0 P0 bugs, <5 P1 bugs open
● Support burden: Average time to resolve a support request < 24 hours
● Referrals: At least 2 beta users have referred another person organically
● One quote: At least 1 beta user has given a specific, quotable testimonial

If Graduation Criteria Not Met

● Extended beta period defined (specific duration and specific changes)
● Root cause of low metrics identified (product? onboarding? wrong beta users?
wrong problem?)
● Changes to make before re-evaluating

Beta Wrap-Up
Closing the Beta
● Final beta survey sent (comprehensive, 10-15 minutes, worth compensating for)
● Exit interviews scheduled with 5 most and 5 least engaged users
● Beta cohort notified of launch plan and their special access
● Beta discount or lifetime deal offered to beta users who become paying customers
● Thank-you gift or gesture for all beta participants (handwritten note, Amazon gift
card, swag)
● Public recognition: offer to feature beta users in launch materials (with permission)

Beta Learnings Document

● Top 5 product changes made during beta
● Top 5 things users loved (to amplify in marketing)
● Top 5 things users hated (to fix before launch)
● Quotes collected and approved for use
● Case study conversations initiated with 2-3 willing beta users
● Beta user list maintained as priority early adopter community
 4. PRICING FRAMEWORK
Pricing is a product decision, not a finance decision. The right price
communicates value, aligns your incentives with your customers, and
builds a sustainable business. The wrong price is the #1 reason early SaaS
products die slowly.

Step 1 — Know Your Numbers Before Setting a

Price
Cost Floor (Minimum Viable Price)

COST FLOOR CALCULATION

════════════════════════════════════════════════════════════
══

Monthly Infrastructure Costs:

Supabase Pro: $25/mo
Vercel Pro: $20/mo
Redis (Upstash): $10/mo
OpenAI (estimated): $X/mo
Resend (email): $20/mo
Other tools: $X/mo
─────────────────────────────────────────
Total Infrastructure: $[TOTAL]/mo

Cost per customer (at [X] customers):

Infrastructure / Customers: $[X]/customer/mo

Your time cost (opportunity cost):

Hours/week on this product: [X] hrs
Your effective hourly rate: $[X]/hr
Monthly time cost: $[X]/mo
Per customer (at [X] customers): $[X]/customer/mo

COST FLOOR PER CUSTOMER:

Infrastructure + Time per customer: $[TOTAL]/mo
This is the minimum you can charge and not lose money

Value Ceiling (Maximum Justified Price)

VALUE CEILING CALCULATION

 ════════════════════════════════════════════════════════════
══

ROI your product delivers to a customer:

Time saved per month: [X] hours
Customer's hourly rate: $[X]/hr
Monthly time value: $[TIME × RATE]/mo

OR

Revenue generated per month: $[X]/mo

Cost reduced per month: $[X]/mo
Risk reduced (hard to quantify): $[X]/mo
─────────────────────────────────────────
Total monthly value: $[TOTAL]/mo

PRICING RULE: Charge 10-20% of the value you deliver

10% of $[TOTAL] = $[PRICE]/mo (conservative)
20% of $[TOTAL] = $[PRICE]/mo (aggressive)

VALUE CEILING: $[20% OF VALUE]/mo

Step 2 — Competitive Benchmarking

Competitor Entry Price Mid Price Top Price What's

Different
[Comp 1] $X/mo $Y/mo $Z/mo
[Comp 2] $X/mo $Y/mo $Z/mo
[Comp 3] $X/mo $Y/mo $Z/mo
Your Product

Market position:
● Premium (30%+ above median) — requires clear superiority
● Parity (within 20% of median) — compete on features/support
● Value (30%+ below median) — requires volume to work
● Freemium — requires viral coefficient > 1 to be sustainable
Step 3 — Tiering Framework
The Three-Tier SaaS Pricing Structure

TIER ARCHITECTURE

════════════════════════════════════════════════════════════
══

TIER 1 — STARTER / GROWTH $[X]/month

────────────────────────────────────────────────────────────
Who it's for: [SPECIFIC PERSONA — solo founder, small team, etc.]
Job to be done: [SPECIFIC USE CASE]

What's included:
✅ [CORE FEATURE 1]
✅ [CORE FEATURE 2]
✅ [CORE FEATURE 3]
✅ [LIMIT: X users / X items / X API calls]
❌ [PREMIUM FEATURE — upgrade trigger]
❌ [PREMIUM FEATURE — upgrade trigger]

Upgrade trigger: user hits [LIMIT] or needs [PREMIUM FEATURE]

Price psychology: Should feel "obviously worth it" for solo use

TIER 2 — PRO / PROFESSIONAL $[Y]/month ← MOST POPULAR

────────────────────────────────────────────────────────────
Who it's for: [SPECIFIC PERSONA — growing team, agency, etc.]
Job to be done: [SPECIFIC USE CASE]
Price: 2-3x Tier 1

What's included:
✅ Everything in Starter
✅ [KEY DIFFERENTIATOR 1]
✅ [KEY DIFFERENTIATOR 2]
✅ [HIGHER LIMIT: X users / X items / X API calls]
✅ Priority support
❌ [ENTERPRISE FEATURE — upgrade trigger]

Upgrade trigger: needs [ENTERPRISE FEATURE] or hits [LIMIT]

Price psychology: Best value — make this the obvious choice

TIER 3 — BUSINESS / ENTERPRISE $[Z]/month or Custom

────────────────────────────────────────────────────────────
Who it's for: [SPECIFIC PERSONA — large team, enterprise]
Job to be done: [SPECIFIC USE CASE]
Price: 3-5x Tier 2
 What's included:
✅ Everything in Pro
✅ [ENTERPRISE FEATURE 1: SSO, audit logs, etc.]
✅ [ENTERPRISE FEATURE 2: custom contracts, SLAs]
✅ [ENTERPRISE FEATURE 3: dedicated support]
✅ Unlimited [key resource]
✅ Custom integrations
✅ SLA with uptime guarantee

Upgrade trigger: compliance requirements, team size, security needs

Step 4 — Pricing Psychology Checklist

Anchoring and Framing
● Most expensive plan shown first (anchors perception of value)
● "Most Popular" badge on the plan you want to sell most
● Annual pricing leads to monthly pricing (not the reverse)
● Annual savings shown as both % off AND dollar amount saved
● Monthly price shown for annual plans (not just annual total)
● Price ends in 9 or 0 (not 7 or 5 — looks arbitrary)
● Feature list shows what's included, not what's missing (positive framing)

Trial and Risk Reduction

● Free trial length: 14 days (sweet spot — long enough to see value, short enough
to create urgency)
● No credit card required for trial (removes friction at signup)
○ Exception: if you have a high fraud rate or high per-trial cost
● Money-back guarantee stated prominently: "30-day no-questions-asked refund"
● SOC 2 / security certifications shown (if available) — reduces enterprise risk
perception
The Decoy Effect

DECOY PRICING EXAMPLE

════════════════════════════════════════════════════════════
══

WITHOUT decoy (two options):

Starter: $29/mo Pro: $99/mo
→ Split decision, hard choice

WITH decoy (three options):

Starter: $29/mo Pro: $79/mo Business: $99/mo
→ Pro looks like a steal vs. Business
→ Most customers choose Pro
→ You wanted them to choose Pro

Rule: The middle option is the decoy target.

Make it look like the best value vs. the top tier.

Step 5 — Pricing Validation Before Launch

Pre-Launch Pricing Tests
● 5-second test: show the pricing page for 5 seconds to 5 people — can they tell
what each plan does?
● Willingness to pay survey sent to waitlist / beta users:
○ At what price is this too cheap (makes you doubt quality)?
○ At what price is this too expensive (would not consider)?
○ At what price is this getting expensive (but you'd still buy)?
○ At what price is this a bargain (great value)?
● Plot Van Westendorp Price Sensitivity Meter from survey results
● Acceptable price range identified: between "too cheap" and "too expensive"
● Optimal price point identified: where "great value" and "getting expensive"
intersect
Red Flags That Your Pricing Is Wrong

Symptom Diagnosis Fix

Everyone chooses the Tier 1 is too feature- Move key features up
lowest tier complete
No one upgrades from Price jump is too steep Add mid-tier or improve
free trial OR value not clear activation
Everyone wants a Price is too high for Lower price or increase
discount perceived value value communication
Customers upgrade Price is too low (they Raise prices
immediately after signing expected to pay more)
up
Churn spikes at first Customers didn't get Activation problem, not
renewal value from the product pricing problem
No one buys the top tier Top tier not differentiated Add compelling
enough OR over-priced enterprise features

Step 6 — Pricing Change Playbook

Raising Prices (Inevitable as You Grow)
● Grandfather existing customers for at least 6-12 months
● Give 60 days notice before price increase takes effect
● Frame as value increase, not cost increase ("we've added X, Y, Z")
● Offer existing customers a chance to lock in current pricing for 1-2 years
● Update all marketing materials, landing pages, and documentation
● Prepare support team for inbound questions

Lowering Prices (Rare but Sometimes Necessary)

● Understand WHY you're lowering (bad signal — means value perception is
broken)
● Consider adding a new lower tier instead of lowering existing prices
● Communicate clearly: "We're making [product] more accessible"
● Check that lower price still exceeds cost floor from Step 1
 5. PRODUCT HUNT LAUNCH PLAN
Product Hunt is a distribution channel, not a guarantee. A great PH launch
generates awareness, backlinks, and social proof. A bad launch wastes a
day. The difference is almost entirely preparation.

8 Weeks Before Launch

● Create a Product Hunt account if you don't have one (build karma first)
● Engage genuinely on Product Hunt: upvote, comment, follow makers you respect
— for 4+ weeks before your launch
● Identify a hunter to submit your product (a user with >500 followers gets more
visibility)
○ Option A: Submit yourself (fine for most launches)
○ Option B: Ask a respected community member to hunt you (warm ask,
genuine relationship only)
● Study the top 10 launches in your category from the last 3 months
○ What taglines performed best?
○ What gallery images got the most engagement?
○ What first comments drove conversation?

4 Weeks Before Launch

Assets Preparation
● Product name: confirmed, consistent with website
● Tagline: under 60 characters, benefit-led, no buzzwords
○ Bad: "The AI-powered integration platform that transforms your workflow"
 ○ Good: "Ship integrations 10x faster without breaking production"
● Thumbnail: 240×240px logo/icon — clean, recognizable at small size
● Gallery images: 5 high-quality screenshots or feature graphics
○ Image 1: Hero shot — the core value proposition in one screen
○ Image 2: Feature 1 demonstration
○ Image 3: Feature 2 demonstration
○ Image 4: Workflow or use case visualization
○ Image 5: Social proof (metrics, customer quotes, integrations)
● Demo video: 60-90 seconds, no voiceover needed, captions added
○ Opens with the problem (10 seconds)
○ Shows the solution in action (50 seconds)
○ Ends with CTA (10 seconds)
● Description: 260-character listing description written and A/B tested
● Long description: 500-word "About" section that tells the founding story

Copy Templates
Tagline Options (write 5, test with 10 people):

Option 1: _______________________________________________
Option 2: _______________________________________________
Option 3: _______________________________________________
Option 4: _______________________________________________
Option 5: _______________________________________________

Winner: _________________________________________________

First Comment (Maker Comment — most important comment you'll write):

Hi Product Hunt! 👋

I'm [NAME], founder of [PRODUCT].

The story: [1-2 sentences on WHY you built this — the personal pain]

What [PRODUCT] does: [1 sentence, concrete and specific]

Who it's for: [TARGET USER]

The backstory most people don't know: [Interesting or surprising fact

about building this — makes it human and relatable]

We're offering Product Hunt hunters [SPECIAL OFFER IF ANY].

 Happy to answer any questions — AMA!

1 Week Before Launch

Build Your Launch List
● Compile list of everyone who said they'd support your launch:
○ Beta users (warmest audience)
○ Waitlist subscribers
○ Personal network (friends, family, colleagues)
○ Twitter/X followers who engage
○ LinkedIn connections in your target market
○ Other founder communities (Indie Hackers, SaaS communities)
● Target list size: 200-500 people minimum for a competitive launch
● Segment list: "day-of" (notify morning of launch) vs. "morning after" (for follow-up)

Schedule and Timing

● Launch day: Tuesday, Wednesday, or Thursday (highest traffic)
○ Never launch on Monday (hangover from weekend)
○ Never launch on Friday (weekend traffic drop-off)
● Launch time: 12:01 AM Pacific Time (resets at midnight PT — maximizes 24-
hour window)
● Launch scheduled: [DATE]
● Team calendar blocked for launch day: full day of engagement

Community Prep
● Identify 10 Product Hunt community members to personally invite (genuine
relationships only)
● Draft personal messages for each — not a mass blast, a real note
● Join 3 Slack/Discord communities where you can share the launch (check rules
first)
● Write the launch announcement for Indie Hackers forum
● Write the launch tweet thread (10-15 tweets telling the story)
Launch Day Protocol
12:01 AM — Go Live
● Confirm listing is live at [Link]
● Check all links work (thumbnail, gallery, video, website URL)
● Post first maker comment immediately
● Post launch tweet: "We're live on Product Hunt! [link] "
● Post launch LinkedIn post: (see Section 7)

6:00 AM — First Push

● Email "day-of" list with personalized message:Subject: [PRODUCT] is live on
Product Hunt today

Hey [NAME],

Today's the day! [PRODUCT] is live on Product Hunt.

If you've found it useful [or: if you're in [target role] and

deal with [problem]], I'd love your honest support.

Here's the link: [PRODUCT HUNT URL]

Upvoting takes 10 seconds and means a lot at this stage.

Thank you genuinely,

[YOUR NAME]
● DM your most engaged supporters on Twitter/X and LinkedIn
● Post in relevant Slack communities (only where appropriate and welcomed)

Throughout the Day (Every 2 Hours)

● Respond to EVERY comment on Product Hunt within 30 minutes
● Thank every upvoter who leaves a comment
● Answer every question thoroughly (this is your public FAQ)
● Address negative feedback directly and without defensiveness
● Post progress updates on Twitter/X ("We're #X on PH! Here's what we're
learning...")
● Monitor for feature requests (note them for roadmap)
6:00 PM — Second Push
● Send follow-up to anyone who clicked but didn't upvote (if you have data)
● Post in any communities you haven't reached yet
● Send a second tweet highlighting a specific comment or feature

Post-Launch (Day 2 Onwards)

● Thank-you tweet posted the day after ("We ended #X! Thank you...")
● Email sent to everyone who upvoted or commented thanking them
● PH listing updated with any corrections or new information
● Blog post published: "Lessons from our Product Hunt launch" (great SEO and
community content)
● Leads from Product Hunt contacted personally
● Add "Featured on Product Hunt" badge to website
● Results documented: signups, upvotes, revenue, backlinks, press coverage

What to Expect (Realistic Benchmarks)

Ranking Upvotes (approx.) Expected Expected

Signups Press
#1 Product of the 500+ 500-2000 High
Day
Top 5 300-500 200-800 Medium
Top 10 150-300 100-400 Low-Medium
Top 20 50-150 50-200 Low
Not ranked <50 10-50 None

Note: These are ranges. B2B products typically convert lower (1-5%) than consumer
products.
 6. REDDIT LAUNCH PLAN
Reddit is the most powerful organic distribution channel for SaaS if used
correctly. It is also the fastest way to destroy your reputation if you treat it
as an advertising platform. The entire approach must be value-first.

Understanding Reddit Before You Post

The Cardinal Rules
1. You are a community member first, a founder second. Redditors can smell a
promotional post from 200 miles. Lead with value, let the product be a footnote.
2. Read each subreddit's rules before posting. Many ban promotional content.
Violating rules gets you banned and your brand associated with spam.
3. Have karma before you launch. A brand-new account posting about your
product looks like astroturfing. Build 2-4 weeks of genuine participation first.
4. Tell the truth. Redditors will find your Product Hunt page, your Crunchbase, your
LinkedIn. If you misrepresent anything, the thread will become a pile-on.
5. One post per subreddit. Cross-posting the same promotional content across
multiple subreddits gets you shadow-banned.

4 Weeks Before Launch: Build Karma

● Create Reddit account (if new, use your real name or recognizable handle)
● Join the 10 subreddits most relevant to your target audience
● Post genuine, helpful comments daily — answer questions, share knowledge
● Post at least 3 substantive non-promotional posts in relevant communities
● Build to at least 100+ comment karma before posting anything promotional
● Identify which subreddits allow "Show HN"-style launches vs. which are purely
discussion
Key Subreddits by Audience Type

FOR SAAS FOUNDERS / INDIE HACKERS:

r/SaaS — B2B SaaS community, active, promotional-friendly
r/entrepreneur — General entrepreneurship, show-your-work posts
r/startups — Startup community, milestone posts welcome
r/indiehackers — Solo founder community (also Indie Hackers forum)
r/EntrepreneurRideAlong — Journey posts, very engaged

FOR DEVELOPERS:
r/webdev — Web development, tools and resources welcome
r/programming — General programming, be technical
r/devops — DevOps tools, integration-heavy products
r/node — [Link] ecosystem
r/typescript — TypeScript community

FOR YOUR SPECIFIC NICHE (replace with your category):

r/[YOUR_INDUSTRY] — Most verticals have subreddits
r/[YOUR_TOOL] — Communities around tools you integrate with
r/[JOB_TITLE] — Your target buyer's professional community

Reddit Post Formats That Work

Format 1: "I Built This" (Best for Technical/Developer
Audiences)

TITLE: I built [PRODUCT NAME] after spending 6 months debugging

webhook failures in production — here's what I learned

BODY:
[2-3 paragraph origin story — the specific pain you experienced]

After dealing with this problem for months, I couldn't find a

good solution so I built [PRODUCT NAME].

Here's what it does: [concrete, specific description]

[The technical interesting thing about how you built it — developers

love implementation details. This is what gets genuine engagement.]

I've been running it in production for [X weeks] with [X users] and

here are the most interesting things I've learned:

1. [Genuine insight]
2. [Genuine insight]
3. [Genuine insight]
 Happy to answer any technical questions. If you want to try it,
it's at [URL] — free to start, no credit card needed.

What else would you want to see in a tool like this?

Format 2: "Show r/SaaS" (Best for Founder Communities)

TITLE: Show r/SaaS: [PRODUCT] — [ONE-LINE VALUE PROP]

BODY:
Hi r/SaaS,

Long-time lurker, first time posting a launch here.

**The problem I was solving:**

[2-3 specific sentences about the pain — make it relatable]

**What I tried first:**

[Honest account of alternatives and why they didn't work]

**What I built:**
[PRODUCT] does [specific thing] for [specific user].

Here's the quick overview: [Loom link or 3-4 feature bullets]

**Where it stands today:**

- [X beta users]
- [X weeks in production]
- [One honest metric]

**What I'm looking for:**

Honest feedback, especially from anyone who's dealt with [problem].

If you want to try it: [URL]

What did I get wrong? What's missing?

Format 3: Value Post That Mentions Your Product (Best for

General Subreddits)

TITLE: How I reduced Stripe webhook failures by 90%

(with the specific code patterns that worked)

BODY:
[Long-form technical or tactical post that is genuinely useful
regardless of whether the reader uses your product]
 [Cover the problem in depth]
[Share actual code examples or frameworks]
[Give away real, actionable advice]

---

After dealing with this for a year, I built [PRODUCT] to automate

most of this. But even if you don't use it, the patterns above
will help you.

Happy to answer questions on any of this.

Reddit Launch Execution

Week of Launch
● Monday: Post a "build in public" progress update (karma-building, not
promotional)
● Launch day: Post the main launch thread in r/SaaS or r/indiehackers
● Launch day: If appropriate, post a separate value post in 1-2 niche subreddits
● Respond to every comment within 2 hours for the first 24 hours
● Do NOT delete negative comments — address them directly
● Do NOT upvote your own post with alt accounts — this is detectable and gets you
banned

Handling Negative Comments

Comment Type Response Strategy

"This exists already — "Great point — [COMPETITOR] does X well. We
[COMPETITOR]" differ in [specific way]. Thanks for the
comparison."
"This is too expensive" "Fair feedback. Can I ask what you'd expect to
pay? Genuinely helpful data."
"I wouldn't use this because "That's valuable. [REASON] came up in beta too.
[REASON]" We've addressed it by [HOW] / it's on our
roadmap."
Comment Type Response Strategy
Technical criticism Engage technically, never defensively. If they're
right, say so.
Pure negativity / no substance One polite response, then ignore.

Reddit Post Performance Targets

Metric Good Great Outstanding

Upvotes 50+ 200+ 500+
Comments 20+ 50+ 100+
Signups from post 25+ 100+ 300+
Conversion rate 2-5% 5-10% 10%+
 7. LINKEDIN LAUNCH PLAN
LinkedIn is the highest-quality B2B distribution channel available to most
founders. The audience is smaller than Twitter but has higher purchasing
power. One great post reaches the right people.

Profile Optimization (Do This Before Your Launch)

● Profile photo is professional and approachable (not a logo)
● Headline is benefit-led: "[Title] at [Company] — helping [target customer] do
[outcome]"
● About section tells your founder story and why you built this
● Banner image updated to reflect your product
● Featured section includes: your product demo, a key blog post, a customer result
● Company page created and linked from your personal profile
● Connect with 50 people in your target customer profile before launch week

LinkedIn Content Strategy: The 4-Week Pre-Launch

Build
Week -4: Authority Building
Post 1: The Problem Post

FORMAT: Story post (no carousel, no video)

GOAL: Establish credibility and attract target audience

Hook (line 1, visible before "see more"):

"I spent 6 months building the wrong solution to a real problem.
Here's what I learned."

Body:
- Tell the story of experiencing the problem personally
- Share the failed attempts
- Share the insight that changed your direction
- 3 specific lessons others can apply

Close:
"If you work in [target role], I'm curious: how are you handling [problem]?"
 ENGAGEMENT TIP: A question at the end dramatically increases comments.

Post 2: The Insight Post

FORMAT: Numbered list (high engagement format)

GOAL: Demonstrate expertise in your domain

Hook: "[NUMBER] things I wish I knew before building [YOUR PRODUCT CATEGORY]"

Format:
1. [Insight with specific detail]
2. [Insight with specific detail]
3. [Insight with specific detail]
4. [Insight with specific detail]
5. [Insight with specific detail]

Close: "What would you add to this list?"

Week -3: Social Proof Building

Post 3: Beta Results Post

FORMAT: Story with metrics

GOAL: Build anticipation and credibility

"We've been running a private beta for 6 weeks.

Here's what we learned — the good, the bad, and the surprising.

THE GOOD:
[1-2 specific positive results with numbers]

THE BAD:
[1 honest challenge you faced — builds trust]

THE SURPRISING:
[1 unexpected finding that's genuinely interesting]

We're [X weeks] away from public launch.

If you want early access: [WAITLIST LINK]"
Week -2: Waitlist Push
Post 4: The Waitlist Post

FORMAT: Value-first, soft CTA

GOAL: Grow waitlist before launch

"[SPECIFIC RESULT] in [SPECIFIC TIME].

That's what [BETA USER TYPE] are getting from [PRODUCT].

Before I tell you how:

We built [PRODUCT] because [SPECIFIC PROBLEM].

The existing solutions [SPECIFIC REASON THEY FAIL].

What we built instead: [SPECIFIC SOLUTION IN ONE SENTENCE]

We're opening to a limited number of users next week.

If [TARGET CUSTOMER] is you, I'd love to show you a demo.
Comment 'interested' or DM me directly."

Week -1: Launch Announcement Prep

Post 5: Behind the Scenes

FORMAT: Behind-the-scenes story

GOAL: Humanize the launch, build anticipation

"Tomorrow we launch publicly.

6 months ago this was a Notion doc and a prayer.

Here's what building it actually looked like:

- [Honest challenge 1]
- [Honest challenge 2]
- [Turning point moment]
- [What we're most proud of]

To everyone who beta tested, gave feedback, and told us when

we were wrong: thank you.

Tomorrow at [TIME]: [PRODUCT] is live. 🚀"

Launch Day LinkedIn Post

FORMAT: Full storytelling post + clear CTA

LENGTH: 1,200-1,500 characters (fills the preview, doesn't require expansion)
TIME: 8:00-9:00 AM in your time zone (peak LinkedIn engagement)

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
━━━━━━━

[HOOK — The first line is everything. Make it stop the scroll.]

"We just launched [PRODUCT].

Here's the honest story of why we built it — and why it almost didn't happen."

[PARAGRAPH 1 — The Problem]

Two years ago, I was [doing specific thing] and [specific frustration happened].
I asked around. Turns out [X]% of [target role] deal with this every week.
The existing solutions were [honest description of why they fail].

[PARAGRAPH 2 — The Journey]

So I spent [TIME] building [PRODUCT].

The first version was terrible. [Beta user] told us [honest criticism].
We rebuilt it. [Second beta user] said [honest criticism].
We rebuilt it again.

[PARAGRAPH 3 — What It Does Now]

Today, [PRODUCT] does [SPECIFIC THING] for [SPECIFIC PERSON].

[Concrete result]: [SPECIFIC METRIC FROM BETA]

[Concrete result]: [SPECIFIC METRIC FROM BETA]
[Concrete result]: [SPECIFIC METRIC FROM BETA]

[PARAGRAPH 4 — The Offer]

We're offering the LinkedIn community [SPECIFIC OFFER]:
[Free trial / Extended trial / Special price / Early access]

[URL]

[CLOSING LINE — Personal and direct]

If you're a [TARGET ROLE] dealing with [PROBLEM], I'd love to hear
what you think. DMs are open.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
━━━━━━━

HASHTAGS (3-5, relevant and specific):

#[INDUSTRY] #[TOOL TYPE] #[RELEVANT TERM] #SaaS #[SPECIFIC TAG]
LinkedIn Launch Week Engagement Protocol
Day 1 (Launch Day)
● Post launch post at 8am
● Respond to every comment within 1 hour for first 4 hours
● DM everyone who comments with: "Thanks for the support! If you know anyone in
[ROLE] dealing with [PROBLEM], I'd love an introduction."
● Share the post to your Company Page
● Ask 5 close connections to reshare with their network
● Post an update comment on your own post at 6pm: "6 hours in — [X signups]
Most common question so far: [FAQ answer]"

Days 2-7
● Post one short follow-up each day (momentum posts):
○ Day 2: "What we learned from day 1 of launch"
○ Day 3: Feature spotlight with screenshot
○ Day 4: Customer result or testimonial (with permission)
○ Day 5: "Most common question from launch week + answer"
○ Day 6: Behind-the-scenes of what you built
○ Day 7: Week 1 metrics recap (honest, with learnings)

LinkedIn Launch Performance Targets

Metric Good Great

Post impressions 2,000+ 10,000+
Engagement rate 3%+ 8%+
Comments 20+ 80+
Profile visits 200+ 800+
Connection requests 20+ 100+
Signups attributed 20+ 100+
 8. EMAIL LAUNCH PLAN
Email is the channel you own. Social media algorithms change. Product
Hunt rankings fade. Your email list is the one asset that belongs entirely to
you.

Building Your List Before Launch

Pre-Launch List Building Tactics
● Waitlist landing page live at least 60 days before launch
● Lead magnet: offer something valuable for an email (guide, template, checklist,
early access)
● Exit intent popup: capture visitors about to leave your landing page
● Build in public: every blog post, social post, and podcast mention links to signup
● Communities: participate in Slack groups, Discord servers, subreddits — link to
waitlist in bio
● Content upgrades: if you have blog posts, offer a downloadable version for email
● Guest posts: contribute to newsletters in your space, include a CTA

Minimum List Size to Make Launch Email Worth It

List Size Expected Open Expected Clicks Expected Signups

Rate
< 100 60%+ 30%+ 10-20
100-500 50% 25% 30-80
500-2000 40% 20% 70-250
2000-10000 30% 15% 200-1000
10000+ 25% 10% 700-3000

Target: 500+ subscribers before launch day.

The Launch Email Sequence (7 Emails)
Email 1 — Waitlist Confirmation (Triggered Immediately on
Signup)

FROM: [YOUR NAME] <you@[Link]>

SUBJECT: You're on the list — here's what happens next

PREVIEW TEXT: We'll notify you the moment doors open.

Body:
Hey [FIRST NAME],

You're on the list.

When we launch, you'll get:

• 48-hour early access before the public
• [SPECIFIC BETA BONUS: extended trial, discounted price, etc.]
• Direct line to me for questions and feedback

While you wait — here's the quickest way to understand what

we're building: [LOOM VIDEO LINK or ONE-SENTENCE DESCRIPTION]

If you have questions before launch, just reply to this email.

[YOUR NAME]

P.S. If you know someone who deals with [PROBLEM], forward them
this link: [WAITLIST URL]. We're keeping the launch cohort small.

Email 2 — Value Email (Sent 1 Week After Signup)

SUBJECT: The [PROBLEM] mistake I see [TARGET ROLE] make every week

PREVIEW TEXT: And how to avoid it without buying anything.

Body:
[FIRST NAME],

Quick value drop — no pitch.

The most common mistake I see when [TARGET ROLE] handles [PROBLEM]:

[SPECIFIC, CONCRETE, ACTIONABLE INSIGHT — 200-300 words]

This works regardless of what tools you use. Happy to go deeper

if you reply with questions.
 [YOUR NAME]

P.S. We're 3 weeks from launch. Still a few early access spots left:
[WAITLIST URL]

Email 3 — Social Proof Email (Sent 2 Weeks Before

Launch)

SUBJECT: What [BETA USER TYPE] said after 30 days

PREVIEW TEXT: The result surprised even us.

Body:
[FIRST NAME],

We've been running a quiet beta for 6 weeks.

The result that stood out most:

"[VERBATIM CUSTOMER QUOTE — specific, with a number]"

— [FIRST NAME, JOB TITLE, COMPANY TYPE]

Here's what [PRODUCT] did for them:

• [Specific result 1]
• [Specific result 2]
• [Specific result 3]

We launch in [X days].

Early access list gets in first. You're already on it.

[YOUR NAME]

Email 4 — Pre-Launch Urgency (Sent 48 Hours Before

Launch)

SUBJECT: 48 hours — you're getting early access

PREVIEW TEXT: Doors open [DAY] at [TIME].

Body:
[FIRST NAME],

Two days.
 On [DAY] at [TIME], [PRODUCT] opens to the public.

You're getting 48-hour early access because you signed up early.

Here's what you get as an early adopter:

• [SPECIFIC EARLY ADOPTER BENEFIT 1]
• [SPECIFIC EARLY ADOPTER BENEFIT 2]
• [SPECIFIC EARLY ADOPTER BENEFIT 3]

The early adopter offer expires when we open to the public.

You'll get your access link at [TIME] on [DAY].

[YOUR NAME]

P.S. Questions before then? Just reply. I read everything.

Email 5 — Launch Day Email (Sent at Launch Time)

SUBJECT: 🚀 [PRODUCT] is live — your early access link

PREVIEW TEXT: You're in. Here's how to get started in 5 minutes.

Body:
[FIRST NAME],

It's live.

Your early access link: [PERSONALIZED LINK OR SIGNUP URL]

To get started in 5 minutes:

1. [FIRST STEP]
2. [SECOND STEP]
3. [THIRD STEP — the activation event]

The first thing most people get wrong: [COMMON MISTAKE + FIX]

The thing that makes the biggest difference fastest: [QUICK WIN]

If you get stuck anywhere, reply to this email. I'll personally help.

[YOUR NAME]

P.S. We're live on Product Hunt today too, if you want to support:
[PRODUCT HUNT URL]

Email 6 — Follow-Up for Non-Openers (Sent 48 Hours After

Launch)
 SUBJECT: Did you miss this? [PRODUCT] launched

PREVIEW TEXT: Your early access link is still active.

Body:
[FIRST NAME],

Resending this in case launch day was hectic for you.

[PRODUCT] launched on [DATE]. Your early access is still active.

[SIGNUP URL]

Here's what the first users are doing with it:

[1-2 SPECIFIC USE CASES OR EARLY RESULTS]

Early adopter pricing expires [DATE].

[YOUR NAME]

Email 7 — One Week Post-Launch Recap

SUBJECT: Week 1: what we learned (honest numbers inside)

PREVIEW TEXT: [X] signups, [X] surprises, [X] things we're fixing.

Body:
[FIRST NAME],

One week since launch. Here's the honest recap.

THE NUMBERS:
• [X] signups in week 1
• [X]% trial-to-paid conversion
• [X] pieces of feedback received
• [X] features requested that we didn't have

THE SURPRISES:
[1-2 things that genuinely surprised you about how people used the product]

WHAT WE'RE FIXING:

[1-2 honest callouts of things that need improvement]

WHAT'S COMING:
[1-2 specific features shipping in the next 2 weeks]

If you haven't tried [PRODUCT] yet, the early adopter pricing

is still available until [DATE]: [URL]

[YOUR NAME]
Email Technical Setup for Launch
● Sending domain authenticated: SPF, DKIM, DMARC all green
● From name consistent: "[YOUR NAME] from [PRODUCT]" not just
"[PRODUCT]"
● Reply-to set: forwards to a monitored inbox (not a no-reply address)
● Unsubscribe link: working and one-click (legal requirement)
● Mobile rendering: all emails tested on iOS Mail and Gmail app
● Plain text version: exists alongside HTML (improves deliverability)
● List segmentation: separate sequences for (a) never signed up, (b) signed up
free, (c) paying
● Suppression list active: bounced and complained addresses never receive email

Launch Email Calendar at a Glance

EMAIL LAUNCH CALENDAR

════════════════════════════════════════════════════════════
══

T-60 days: Waitlist opens, Email 1 (confirmation) triggers automatically

T-14 days: Email 2 sent (value email) to entire waitlist

T-7 days: Email 3 sent (social proof / beta results)

T-2 days: Email 4 sent (48-hour early access notice)

T-0: Email 5 sent at launch time (live link)

T+2 days: Email 6 sent to non-openers of Email 5

T+7 days: Email 7 sent (week 1 recap) to all subscribers

T+14 days: Ongoing nurture sequence begins

(separate from launch sequence)

POST-LAUNCH ONGOING SEQUENCE:

Week 2: Feature spotlight #1
Week 3: Customer story (with permission)
Week 4: "Most asked question this month"
Monthly: Product update and what's coming
Email Launch Performance Benchmarks

Metric Below Target On Target Excellent

Open rate (launch email) <25% 35-45% 50%+
Click rate <5% 10-15% 20%+
Trial start rate (openers) <10% 15-25% 30%+
Trial → paid (30 days) <10% 20-30% 35%+
Unsubscribe rate >5% 1-2% <0.5%
Spam complaint rate >0.5% <0.1% <0.05%

Common Launch Email Mistakes

Mistake Why It Kills Results Fix

Sending from a no- Kills engagement, tells users Always use a human
reply address you don't want to hear from name and monitored
them inbox
Too many CTAs in Divides attention, reduces One email = one CTA
one email click rate
Feature-focused Nobody opens "Check out Benefit or curiosity-gap
subject lines our new dashboard" subject lines only
Sending too Cold list = low engagement 4+ touchpoints before
infrequently before on launch day asking for anything
launch
Batch-sending at 2am Email clients deliver at odd Schedule for 8-9am
times, open rate suffers recipient time zone
No plain-text version Spam filters treat HTML-only Always include plain text
as suspicious
Forgetting mobile 60%+ of emails opened on Test every email on
optimization mobile iPhone before sending
End of The SaaS Founder's Complete Launch Kit

The Next Step

You have the checklist. The question is execution discipline.
Print Section 2 (Launch Checklist). Pin it to your wall. Work through it from top to
bottom. When a box is empty, that is your job today.
Ship the thing. Then iterate.
Part of The SaaS Founder's Integration Cookbook series.