Objective
Set up analytics, write and post a real launch announcement, and confirm a specific week-1 goal.
Build
The capstone project
Every feature works, it's deployed, it's polished. The single most commonly skipped step in every "I built an AI SaaS in a weekend" story you've read is this one: actually telling anyone it exists.
Where a solo AI SaaS actually launches
Pick one real community, not five half-hearted posts
Hacker News's "Show HN," r/SideProject, Product Hunt, and relevant Discord communities (including this course's own) are all real options — but a single well-written post in the community where your actual target user spends time beats five generic cross-posts. For a proposal generator aimed at freelancers, a freelancer-focused subreddit or Discord matters more than a general tech audience that isn't your buyer.
Writing a launch post that isn't just "I built X"
Show HN: I built an AI proposal generator after writing my 200th client proposal by hand
I freelance, and every new client meant starting a proposal from scratch --
2-3 hours I'd rather spend on actual work. Built this over a weekend:
input a client name and project description, get a polished, sendable
proposal in under a minute.
Free tier: 3 proposals/month. $12/month for unlimited.
Live at: [your-url]. Would love feedback, especially on the AI-generated
proposal quality -- that's the part I'm least sure about.
Notice this leads with a real personal problem ("my 200th client proposal"), not a feature list -- specificity and a genuine story consistently outperform generic "check out my new AI tool" posts. It also explicitly invites feedback on the part you're genuinely unsure about, which reads as honest rather than a pure sales pitch.
Your launch post gets 3 signups in the first hour, and 2 of them hit an error during sign-up that you hadn't seen in your own testing. What's the right response?
Real users, especially the very first ones, will hit things your own testing and even a friend's testing missed — different browsers, different input patterns, different assumptions. A fast, direct response to an early user who hit a bug (fix it, tell them, thank them) often converts a frustrated first impression into a genuinely loyal early user, which matters disproportionately for a brand-new product with zero reputation yet.
Set a real number, and vercel analytics to see it
Add Vercel Analytics (a few lines, already available on your Vercel deployment) so "did anyone actually use this" is a real dashboard, not a guess. Your week-1 goal should already exist — Lesson 1's Product Definition Canvas asked for one.
Ship it
Post your launch announcement to one real community. Share the live URL in Discord too, so other students can be your first real users.
Ship Prompt: Drop the URL. What's your one-sentence pitch? Who's it for? What's the price? Tag a friend who should try it.