LaunchRecipe

Launch guides · 8 min read

How to launch your first product in 30 days (when you're stuck on step one)

You have read the threads. “I made $100k from a side project.” “How my weekend app hit $10k MRR.” You bookmarked twelve of them. And then you closed the tab and did nothing, because none of them told you what to do on Monday morning. This guide fixes that. It is the framework behind LaunchRecipe, distilled from hundreds of real indie launch write-ups on r/SideProject, Indie Hackers, and Hacker News.

Why first launches stall

Three failure modes account for almost every stalled launch. First, vague positioning — you can describe what the product does but not who is desperate for it. Second, blank-page paralysis— you know you should “post on Reddit” but staring at an empty textarea is its own special hell. Third, no plan — without a daily next action, motivation leaks out over a week and the project quietly dies in your closed-laptop graveyard.

Notice what is not on that list: writing code. Most first-time founders over-invest in building and under-invest in selling. The uncomfortable truth from the case studies is that the winners started talking to humans in week one, often before the product was real.

The 30-day shape

A launch is not a single event; it is a sequence. Here is the shape that repeats across the successful stories, compressed into four weeks.

Week 1 — Position and seed (days 1–7)

Lock a one-line positioning statement: “[Product] helps [specific person] get [specific outcome] without [specific pain].” Build the smallest demoable thing — a landing page with a waitlist counts. Then seed five real conversations in communities where your person already hangs out. Do not pitch. Ask about the pain. The first paying customer almost always comes from one of these early threads.

Week 2 — Make it real and ask for money (days 8–14)

Ship the single most-requested feature from week one, post a build-in-public update, and — critically — wire payments and make your first paid ask. Even if it is a pre-sale or a “pay what you want” pilot, getting the first rupee or dollar from a stranger changes everything psychologically and validates the idea faster than any survey.

Week 3 — The big posts (days 15–21)

Now you launch loudly. A “Show HN” on Hacker News, a Product Hunt launch with assets prepared the day before, and a Twitter/X thread that tells the story. The order matters: HN rewards a humble, technical, honest framing; Product Hunt rewards a crisp tagline and an engaged first hour; X rewards narrative. Each needs different copy, which is exactly where most people freeze.

Week 4 — Convert and compound (days 22–30)

Add the one fix that improves conversion, ask happy users for testimonials, publish an SEO cornerstone post (like this one), and reach out to three niche newsletters. End with a retrospective and a plan for the next 30 days. Launches are not finish lines; they are the first loop.

The exact channels, and how to not get banned

r/SideProject and Indie Hackers reward generosity. Lead with the problem, offer to help someone for free in the comments, and reply to every single response in the first two hours. Drop the link only after you have given value. Hacker News punishes marketing speak — write like an engineer explaining a thing they built to other engineers, and stay in the comments all day. Product Hunt is a single-day sprint: line up a few genuine supporters in advance, launch at 12:01am PT, and treat the comment section as a live AMA.

The mistake that kills these posts is treating them as billboards. They are conversations. The founders who win post less polished, more honest content than you think you are allowed to.

Pricing for a first product

Do not agonize. Offer a free tier that delivers one real win, one paid tier priced at the “no-brainer” level (₹999 / $19 one-time works remarkably well for tools), and optionally a recurring tier for ongoing value like accountability or updates. Raise prices later; you almost certainly started too low, and that is fine — early customers reward courage with feedback, not churn.

Turn this into your plan

Reading a framework is not the same as having a schedule. The reason this works inside LaunchRecipe is that the plan is personalized to your ideaand broken into one-sitting tasks with the actual posts written out for you — so on Monday morning you open the checklist, see today's three tasks, and do them. No deciding, no blank page, no re-reading threads for the thirteenth time.

Paste your idea and get your free 7-day plan in about twenty seconds. If it is the clearest launch path you have seen, the full 30-day version is one coffee's worth.

Get your personalized 30-day plan

Free first playbook. No signup to try.

Generate my playbook