5 Playbooks Every Indie Builder Needs Before Launch Day

Most indie builders launch wrong. Not wrong as in "the product doesn't work" — wrong as in "no one is watching when it goes live."

They spend 90 days on code and 90 minutes on launch. Then they wonder why nothing happens.

The builders who actually get traction treat launch like a campaign, not a deployment. They run playbooks: structured, repeatable processes that remove the guesswork from each phase of building.

Here are the five playbooks that separate shippers who gain traction from those who drift.

Playbook 1: The MVP Launch Checklist

Timeline: 72 hours before launch

Most MVPs are "ready" for weeks before they ship. The founder keeps polishing. One more feature. One more edge case. The real reason is they don't have a launch plan — so shipping feels dangerous.

A launch checklist removes that friction. Here's the one that works:

48 hours out: - Write your one-sentence positioning: "I built [X] for [Y] because [Z]" - Draft your launch post (HN, Reddit, Product Hunt, whatever channel you're targeting) - Record a 90-second demo video showing the core use case - Set up analytics (even just a page_views table — anything that tells you if traffic arrived) - Confirm your payments flow works end-to-end with a test purchase

24 hours out: - Tell 10 people personally — not a blast email, actual messages to actual people - Schedule your posts for peak engagement time (HN: 8-10am PT weekdays; PH: 12:01am PT) - Set up a simple lead capture if you don't have one yet

Day of: - Post everything at the same time - Stay online for the first 4 hours to respond to every comment - Don't push code — what's live is what you're launching

After launch: - Count signups, not upvotes - Email every single person who signed up within 24 hours

The Launch MVP in 5 Days playbook inside CapDeck goes deeper on each step — including the exact outreach scripts and the checklist fields to track.

The key insight: your launch is a one-time traffic event. Maximize signal extraction from that spike, because organic SEO and word-of-mouth take months to build. Don't waste the moment by being offline or unprepared.

Playbook 2: The User Research Playbook

Timeline: Before you write a line of code (or right now, if you've already shipped)

Here's what most indie builders skip: talking to users before building. Here's what the best indie builders do: they talk to users *constantly*, and they have a repeatable process for it.

User research doesn't mean running formal surveys. It means having 20-minute conversations with people who might want your product, and asking questions that reveal their actual behavior — not their hypothetical behavior.

The 5-question script:

1. "Walk me through the last time you [problem you're solving]. What did you do?" 2. "What tools did you use? What was frustrating about them?" 3. "How much time does this take you per week?" 4. "Have you ever paid for a solution to this? What happened?" 5. "Who else on your team deals with this problem?"

The magic is in question 4. If someone has already paid for a solution and stopped using it, you have a motivated buyer who's been burned. That's your best customer.

Run this playbook: - Schedule 5 calls in week 1 (LinkedIn DMs, Twitter replies, your existing network) - Listen for repeated phrases — those are your headline copy - Note every time someone says "I wish there was a way to..." - Don't pitch during the call. Just listen.

After 10 conversations, you'll have more clarity than 6 months of building in isolation. The Validate Your Idea in 48 Hours playbook in the library gives you the exact DM scripts and scoring rubric we use.

The rule: If you can't get 5 people to take a 20-minute call about their problem, you don't have a viable market yet. Don't build.

Playbook 3: The Pricing Strategy Playbook

Timeline: Before your first paying customer

Pricing is where indie builders lose the most money — not by charging too much, but by charging too little.

Charging too little sends three signals simultaneously: it implies low value, it attracts price-sensitive customers who churn, and it makes you work harder for less runway. There is no version of underpricing that helps you.

Here's the playbook:

Step 1: Find the cost of the problem

What does the problem cost your user if they don't solve it? Not "how much would they pay" — what is the actual economic or time cost of the problem existing?

If an indie builder wastes 10 hours/week on manual competitor research, and their time is worth $50/hr, that's $500/week in lost productivity. Your tool could charge $50/month and still be a 10x ROI.

Step 2: Pick an anchor

Name three pricing tiers even if you only plan to sell one. Anchoring psychology is real. A $99/mo plan makes $49/mo look like a deal. A $499/mo plan makes $99/mo look like a steal.

Step 3: Start at the number that feels too high

Then move down only if you're consistently losing conversations at the pricing stage. Most indie builders price low and never test up. That's a mistake you can't easily recover from — early customers lock in expectations.

Step 4: Test with a payment link before building billing

Use a Stripe payment link or a pre-built Stripe integration from the code templates library. Get one person to pay before you invest in subscription infrastructure. One payment validates more than 100 sign-ups.

The Zero to First Customer Playbook covers the full conversation scripts for closing your first paid user, including how to handle the "it's too expensive" objection without discounting.

Playbook 4: The Distribution Playbook

Timeline: Ongoing, starting before launch

Build something. Tell people. That's the whole business. Most indie builders nail step one and skip step two.

Distribution is not marketing. Marketing is paying to acquire attention. Distribution is building systems that bring attention to you repeatedly at near-zero marginal cost.

The three distribution channels that work for indie builders:

1. SEO content (this is one of those pages)

Write about the problems your users search for. Not about your product — about their problem. This article targets "startup playbooks" because that's what indie builders type when they're looking for what CapDeck provides.

SEO takes 3-6 months to compound, but once it compounds, it's the best distribution channel that exists. Zero cost per click. Check the free SEO tools for the exact prompt templates to speed up content production.

2. Community presence

Pick one community (Indie Hackers, a specific subreddit, a Discord, a Slack group) and become genuinely helpful there before you ever mention your product. Reply to 10 posts per week. Share what you're learning. Build before you harvest.

The rule: give value for 60 days before you expect anything back.

3. Direct outreach

Cold outreach still works when it's personal. "I built this, thought of you specifically because of [thing you said/did]" converts. "I built this, check it out" doesn't.

The Cold Outreach That Gets Replies playbook in the library has the exact DM templates with measured reply rates.

What doesn't work:

- Blasting your product to every platform on launch day and never returning - Building an audience on one platform you don't control (algorithm changes kill you) - Waiting until you have a "perfect" product to start distribution

Distribution compounds. Content you write today brings traffic for years. Community reputation you build this month opens doors next year. Start before you're ready.

Playbook 5: The Post-Launch Growth Playbook

Timeline: Days 2–90 after launch

Launch day is a spike. What you do in the 90 days after determines whether that spike becomes a baseline or a one-time event.

Most indie builders treat launch as the finish line. The ones who build real businesses treat it as the starting gun.

Week 1: Talk to everyone

Email every person who signed up. Personally. Not an automation, an actual email. Ask one question: "What made you sign up?" The answers will tell you what's actually resonating.

Weeks 2-4: Find your activation pattern

Look at users who got value vs. users who churned. What did the successful ones do in their first session? That's your activation moment. Everything you do next should push new users toward that moment faster.

Month 2: Double down on the channel that's working

By now, you have some data. Where did your best users come from? What content drove the most signups? Double the thing that worked. Kill everything else.

Month 3: Build your retention engine

Acquisition is expensive. Retention is how you survive. Check the Reduce Churn Below 5% playbook — it covers the exact email sequences, feature triggers, and check-in patterns that keep users around.

The compound effect:

Each month of consistent execution builds on the last. Month 1 is hard. Month 3 is finding your groove. Month 6 is where traction starts to feel real. Most builders quit in month 2.

The Content Marketing Flywheel playbook explains how to build a content system that generates distribution on autopilot by month 6 — so you're not manually hustling every week to keep traffic coming.

Putting the Playbooks Together

These five playbooks aren't sequential — they overlap and reinforce each other.

User research informs your pricing (what does the problem actually cost?). Your pricing informs your distribution (which audience can afford this?). Your distribution informs your post-launch growth (which channel brought your best users?).

The indie builders who ship and grow treat their business like a system, not a project. Each playbook is a component of that system.

Where to start:

If you haven't launched yet: run Playbook 2 (user research) this week, then build your launch checklist (Playbook 1) for the next two weeks.

If you've launched but aren't growing: run Playbook 5 (post-launch) immediately. Find your activation moment. Double down on your best channel.

If you're growing but not predictably: Playbook 3 (pricing) and Playbook 4 (distribution) are where you'll find the leverage.

All five playbooks are available inside CapDeck as step-by-step, copy-paste templates — including the scripts, checklists, and email sequences referenced above.

The free tools page has 9 tools you can use right now without signing up, including AI prompt templates built for exactly this kind of work.

The AI prompts library covers the content and outreach side — use those prompts alongside these playbooks for the full system.

And if you haven't read the earlier articles in this series, AI Prompts That Actually Ship Products and Free Code Templates for Startups cover the tactical building blocks that feed into these playbooks.

Stop building in isolation. Run the playbooks.