獨立 SaaS 發佈清單：涵蓋發佈前、發佈週及發佈後

Most launch advice is about a single day. You pick a date, post everywhere, refresh the dashboard, and then... it's quiet again by Thursday.

I'm building a launch platform for SaaS makers, so I spend a lot of time looking at launches that worked and launches that fizzled. The difference is rarely the product. It's usually the boring prep work before launch, and the follow-through after it. Here's the checklist I'd hand to any indie founder shipping in the next month.

Part 1: Two weeks before launch

1. Rewrite your headline around the outcome, not the feature.
"AI-powered multi-platform scheduling engine" describes what your product is. "Your social posts, done in 30 seconds" describes what happens for the user. Visitors decide in a few seconds whether to keep reading. Read your hero text out loud and ask: "Could a stranger picture the result?"

2. Record a 30–60 second demo.
No script, no fancy editing. Just you using the product to solve the core problem. A short screen recording answers "does this actually work?" faster than any copy. Put it above the fold.

3. Fix the technical basics.
This one gets skipped constantly:

• [ ] sitemap.xml exists and is submitted to Google Search Console
• [ ] Every page has a unique <title> and meta description
• [ ] Open Graph image set (test the link in a Slack or X preview)
• [ ] robots.txt isn't accidentally blocking everything (it happens)
• [ ] Signup works on mobile, in an incognito window, with a fresh email

4. Make your product easy for AI assistants to read.
More people now ask ChatGPT, Claude, or Perplexity "what's a good tool for X?" Help them understand you:

• A one-sentence description that says who it's for and what it does
• A pricing page in plain text (not just inside images or JS-only widgets)
• An llms.txt file at your root summarising the product and linking key pages
• Docs and FAQs that work as plain markdown

5. Write down your first 20 people.
Not "the internet". Twenty actual names: past colleagues, people who've complained about this problem in public, people who replied to your build-in-public posts. They're your launch day, and they'll give you honest feedback.

Part 2: Launch week

6. Treat launch as a week, not a day.
A 24-hour launch is all about timing and mobilising people at once. A week-long window gives you room to post in different communities on different days, respond thoughtfully, and fix things people report. Spread it out:

• Day 1: your email list and personal network
• Day 2: one or two founder communities where you already take part
• Day 3: a launch board or two
• Day 4–5: niche communities where your buyers (not other makers) hang out
• Day 6–7: write up what you learned

7. Pick launch platforms that match your audience.
Product Hunt is huge but covers all of tech. Hacker News works for technical and genuinely novel products. Smaller launch boards and directories are calmer and often give you a lasting listing and backlink. Choose two or three you'll actually show up for, rather than spraying 40 submissions you'll never check.

8. Reply to everything, personally.
Every comment is a potential user and a public signal to the next reader. Answer questions specifically. Thank people for criticism. If someone reports a bug, fix it and reply "shipped".

9. Track where signups come from.
Add UTM parameters to every link you share (?utm_source=indiehackers). By the end of the week you want to know which channel brought active users, not just visits.

Part 3: After the launch

10. Follow up with every signup.
A short, plain-text email from you: "Hey, I saw you signed up. What were you hoping this would help with?" The replies are worth more than any analytics dashboard.

11. Keep the listings alive.
The launch spike fades, but product pages, directory listings, and backlinks keep sending trickle traffic and help search engines find you. Make sure each listing has your current tagline, screenshots, and pricing.

12. Write the post-mortem in public.
"What worked, what didn't, real numbers" posts do well on Dev.to, Indie Hackers, and X, and they quietly bring a second wave of visitors. Be honest, including when the numbers are small.

The short version

[ ] Outcome-first headline
[ ] 30-60s demo video
[ ] sitemap, meta tags, OG image, robots.txt
[ ] One-line description + llms.txt + plain-text pricing
[ ] List of 20 real people
[ ] Launch spread across a week
[ ] 2-3 platforms that match your audience
[ ] Reply to every comment
[ ] UTM links on everything
[ ] Personal follow-up to every signup
[ ] Keep listings updated
[ ] Public post-mortem

None of this is glamorous, but it's the difference between "I launched and nothing happened" and "I launched and learned exactly who my users are."

I'm building DodoLaunch, a free weekly launch board for SaaS and AI tools where launches run for a full week. If you're shipping soon, it might be a useful stop on your list. Either way, I'd love to hear what's on your own launch checklist in the comments.