Lesson 4: Launch Day
Course: Ship Your First AI App
Estimated time: 25 minutes to read, 30 minutes for the exercise
Difficulty: Beginner Builder
Most builders delay launch for the wrong reasons. "It's not ready yet" usually means "I'm scared." Your app doesn't need to be finished to launch. It needs to work well enough that one real user can get value from it today.
That's the bar. Ship to that bar.
The Landing Page That Actually Converts
You have maybe 8 seconds. That's how long someone will spend on your landing page before they decide to sign up or leave. Your landing page's job is to answer three questions in that window:
- What is this?
- Who is it for?
- Why should I try it?
That's it. You don't need a long scrolling page on day one. You need those three answers to be immediately obvious.
The structure that works:
Headline: What it does for the specific person you built it for. Not clever. Specific.
Bad: "AI-powered proposal magic for the modern creative"
Good: "Generate client proposals in 60 seconds. No blank page."
Subheadline: Who it's for and the main mechanism.
Example: "For freelance designers who spend hours writing proposals that clients barely read. Paste your project brief, get a professional proposal, done."
Primary CTA: One button. What happens when they click it should be clear from the button text.
Bad: "Get started"
Good: "Generate your first proposal free"
Social proof: If you have none, get some before launch. Send it to 3-5 people you know in the target audience. Ask for one sentence of honest feedback. Put that on the page.
How it works: Three steps max. Show the input, show the output. A GIF or screenshot of the actual product is worth 300 words of explanation.
Secondary CTA: Another chance to sign up at the bottom of the page.
Don't add pricing, an FAQ section, a team page, or a blog. That's all noise. You can add it after you have users who are asking for it.
Writing Launch Copy That Gets Clicks
The single biggest mistake in launch copy is making it about you and your product instead of about the user and their problem.
Your copy should describe the problem more accurately than the user can describe it themselves. When someone reads it and thinks "how did they know exactly what I was struggling with," they're already half-sold.
Problem-first structure:
Start with the pain. Name it specifically.
"Writing client proposals is one of those things that should take 20 minutes and somehow takes 3 hours. You stare at the blank page. You write a paragraph, delete it, start over. Then you second-guess the pricing section. Then you realize you said 'we' instead of 'I' and you go fix all of them."
Then show the contrast.
"With [Product], you paste your project brief, click Generate, and have a draft proposal in 60 seconds. Edit what you want, copy it out, send it."
Then the outcome.
"Designers on the beta have been sending proposals in under 5 minutes. One said it's the first time she's actually enjoyed the new client process."
Notice what's not in that copy: feature lists, technical details about how it works, vague claims about being "the best" or "the only."
Where to Launch
You don't need to be everywhere. You need to be in the right place for your specific audience. Here are the actual channels and what they're good for.
Product Hunt
Best for: getting your first visibility, getting feedback from other builders, early adopters who try everything new.
Not great for: finding your actual target user unless they happen to be PH-active.
Reality check: a median Product Hunt launch gets 50-200 upvotes and maybe 50-200 signups. That's not failure, that's a real number of real users. Top launches get thousands, but those usually have existing audiences or extraordinary timing.
How to do it right:
- Launch on Tuesday, Wednesday, or Thursday (Tuesday is typically highest traffic)
- Prepare your listing the day before: thumbnail, tagline, description, first comment
- Your first comment should explain the backstory and what problem you're solving
- Ask 20 people in your network to support the launch on the day (upvote, comment)
- Respond to every comment during launch day
Indie Hackers
Best for: the builder community. If your target users are makers, solopreneurs, or indie builders, IH is genuinely good.
Post a "Show IH" thread. Be honest about where you are (just launched, 0 paying users, looking for feedback). The IH community rewards transparency.
Depends entirely on which subreddits your audience is in. This is the highest-upside channel if you pick right.
Find the subreddit where your target user actually hangs out. Not r/entrepreneur (too broad). Not r/startups (wrong motivation). The specific community: r/freelancedesigners, r/SaaS, r/ChatGPT, whatever fits.
Read the rules first. Most subreddits allow product posts in specific formats. A transparent "I built this, would love feedback" post outperforms a marketing-speak announcement every time.
Don't spam multiple subreddits on the same day. Pick one, post honestly, respond to every comment.
X (Twitter)
Works best if you already have an audience. Building in public for 3 months before launch genuinely helps, because you have followers who are already invested in your success.
If you don't have an audience, you can still get traction by:
- Tagging relevant builders or communities
- Using the right hashtags (#buildinpublic, #indiedev, #SaaS)
- Posting your thread in replies to larger accounts discussing the problem you solve
Email your list
If you ran a waitlist during validation (Lesson 1), these are your highest-intent users. Email them first, before the public launch. Give them early access. Ask for feedback. These people opted in - they're the most likely to try it and tell you what's wrong.
Launch Day Checklist
Run through this before you announce anything:
Technical
- [ ] App is deployed to production (not localhost, not staging)
- [ ] Signup flow works end to end
- [ ] Core feature works for a new user who's never seen it before
- [ ] Error states show something useful, not a stack trace
- [ ] Stripe is connected (if paid) or there's a clear free tier
- [ ] You have a way to see errors in production (Vercel logs, Sentry, whatever)
Landing Page
- [ ] Headline is specific to the problem and audience
- [ ] Primary CTA is above the fold
- [ ] At least one screenshot or GIF of the actual product
- [ ] At least one piece of social proof (even a beta tester quote)
- [ ] Privacy policy exists (Clerk auto-generates most of what you need)
Copy Ready
- [ ] Product Hunt listing written and scheduled
- [ ] Tweet/thread drafted
- [ ] Indie Hackers or Reddit post drafted
- [ ] Email to waitlist drafted
Monitoring
- [ ] You can see how many people sign up in real time
- [ ] You have a way to contact early users (email, Discord, whatever)
- [ ] You've cleared your schedule for the day to respond to feedback
Mental
- [ ] You've accepted that there will be bugs
- [ ] You've accepted that some feedback will be harsh
- [ ] You have a plan for what you'll do if it goes great (more servers, outreach)
- [ ] You have a plan for what you'll do if it goes quietly (Lesson 5)
Real Launch Numbers to Calibrate Expectations
Most first launches are smaller than you expect. That's fine. Here's what real is:
- 50-200 Product Hunt upvotes: solid launch
- 100-500 signups on day one: really good
- $0 in revenue on launch day: normal
- 5-20 paying customers in week one: excellent for a new product
- 1-3 paying customers in week one: still progress, not failure
The builders who succeed after launch are the ones who use those first 10-50 users to learn what's actually valuable, not the ones who give up because the numbers weren't huge.
One real user who finds genuine value in your product and tells you why is worth more than 1,000 passive signups from a viral launch.
Exercise: Write Your Launch Copy in 30 Minutes
Use AI to draft, then edit by hand. The editing is where you find the voice that sounds like you.
Open Claude or ChatGPT and use this prompt:
I'm launching [brief description of your product].
Audience: [specific audience]
Core problem it solves: [specific problem]
How it works: [1-2 sentence mechanism]
Best result from a beta user: [if you have one]
Write:
1. A landing page headline (under 10 words, problem or outcome focused)
2. A landing page subheadline (1-2 sentences, who it's for + mechanism)
3. A Product Hunt tagline (under 60 characters)
4. An opening paragraph for a Product Hunt description (3-4 sentences)
5. A tweet announcing the launch (under 280 characters)
6. An email subject line for my waitlist (under 50 characters)
Keep everything specific. No marketing buzzwords. Write like you're texting someone who has the problem.
Read the output. Take the parts that sound right and rewrite the rest in your own voice. A good AI-written draft takes 10 minutes to get to 70% of the way there. Your edits take it the rest of the way.
Then pick your top launch channel and write the full post. Have someone else read it before you hit publish.
Key Takeaway
Launch day isn't about perfection - it's about getting real users in front of a working product so you can learn what to build next.
What's Next
You launched. People signed up. Now what? Lesson 5 covers the week after launch - what signals actually matter, how to talk to your first users, and when to keep building vs. when to move on.