Indie Dev Client Acquisition Playbook

1. Analyze User Request:

• Goal: Write complete public web page copy for "Indie Dev Client Acquisition Playbook"
• Format: Markdown (headings, short paragraphs, bullet lists)
• Plan Details: Provided in a JSON-like plan structure with goals, checkpoints, rules, distribution, pricing, maintenance, etc.
• Constraints:
• Be honest and specific about what it is and who it's for
• No fake testimonials, numbers, or claims
• Do not invent prices, links, or payment buttons
• The price is already specified as $29 USD
• Must follow the distribution plan: free 5-page checklist as lead magnet, upsell full 40-page playbook on thank-you page and in 3-email nurture sequence
• Traffic: 3 SEO blog posts, Reddit/Dev.to comments linking the checklist
• Maintenance plan specified
• Context: This seems like a product launch/web page copy task, possibly for a startup/indie developer tool/product

1. Deconstruct the Plan/Requirements:

• Product: "Indie Dev Client Acquisition Playbook" (40 pages, $29)
• Lead Magnet: 5-page "Client Acquisition Checklist" (free, email capture)
• Upsell: Full playbook on thank-you page + 3-email nurture sequence
• Traffic: 3 SEO blog posts targeting specific keywords, 10 niche Reddit/Dev.to comments
• Price: $29 USD (given, don't invent)
• Honesty/No fake claims: Must be real, specific, no inflated numbers
• Format: Markdown with headings, short paragraphs, bullet lists
• No invented links/payment buttons: So I won't create actual URLs or HTML form elements, but I can describe the structure/functionality factually
• Maintenance: Quarterly/Monthly/Annual updates as specified

1. Identify What the Web Page Copy Needs to Include:

• Header/hero section
• Problem/why client acquisition is hard for indie devs
• What the playbook offers (40 pages, what's inside)
• The free checklist lead magnet
• Pricing info ($29)
• Social proof? But no fake testimonials - maybe generic statements or "who it's for" description
• How it works / structure
• Target audience
• Call to action for the free checklist, then upsell
• Maintenance transparency (maybe not on public page, but I can note it)
• SEO/blog integration mention (maybe subtle)

Actually, the user asks for "complete public web page copy" - so it's the page that visitors see. It should drive the funnel: free checklist capture -> upsell. I need to write the copy honestly, no fake stats.

Let me structure it logically:

• Hero section
• Section: Why indie devs struggle with clients
• Section: What's in the playbook (bullet points of topics, honest description)
• Section: The free checklist (lead magnet benefit)
• Pricing section ($29 for full playbook)
• How it works / funnel explanation (brief, factual)
• Footer/small print maybe

I need to be careful not to invent success numbers, revenue claims, fake quotes. I'll describe the playbook's content factually based on the title "Client Acquisition Playbook" for indie game devs/freelancers. I'll keep it general but specific enough.

Let's outline the markdown structure:

   # Indie Dev Client Acquisition Playbook

   [Hero headline]
   Short intro paragraph

   Why client acquisition is hard for indie game devs
   - Bullet points of pain points

   What's Inside the 40-Page Playbook
   - Bullet points of actual useful sections (no fake numbers)
   - e.g., "How to identify and research target studios", "Pitch templates that get responses", "Discord/Upwork strategies", etc.

   Get the Free 5-Page Client Acquisition Checklist
   - Brief description
   - Email capture benefit

   $29 Full Playbook
   - One-time purchase, lifetime access

   Who This Is For
   - Bullet list of ideal users

   FAQ
   - A few honest questions

   [Maybe a small note about the funnel, but honestly]

Wait, the user said "Do not invent prices, links or payment buttons." The plan already says priceUsd:29, so I can mention $29 but not create actual payment HTML. I'll just state the price textually.

Also "Be honest and specific about what it is and who it is for" - I'll define it as a practical guide for indie game developers and freelance devs who need to find their first few clients or steady pipeline, without claiming "1000 users made $X".

"No fake testimonials, numbers or claims" - I'll avoid any stats. I might mention "over 200 indie devs have found it useful" only if it's factual from the plan, but the plan doesn't give such numbers. I'll skip any claimed metrics.

Let me re-read the plan carefully:

• goalMetric: playbook_downloads_or_purchases
• checkpointHours: 168
• killRule: maxIterationsWithoutRevenue: 3
• boostRule: minRevenueUsd: 150
• cloneRule: minRevenueUsd: 500
• channel: owned-site
• priceUsd: 29
• distributionPlan: Publish a free 5-page 'Client Acquisition Checklist' as lead magnet on the owned site with email capture gate. Upsell the full 40-page playbook ($29) on the thank-you page and in a 3-email nurture sequence. Drive traffic via 3 SEO-optimized blog posts targeting 'indie game client acquisition', 'freelance game dev portfolio clients', and 'how to pitch game studios', plus 10 niche-relevant Reddit/Dev.to comments linking the checklist.
• maintenancePlan: Quarterly: update platform-specific outreach templates (Upwork, Discord, LinkedIn, GameDev.jobs) and refresh 2 case studies. Monthly: review search console for new keyword opportunities, add 1 FAQ entry from support emails. Annual: major version bump with new channel breakdowns; existing buyers get 50% upgrade discount.

So the web page copy should align with this funnel. I'll write the public page copy that serves as the entry point. It should mention the free checklist, the $29 playbook, and the value. I won't embed the maintenance plan on the public page necessarily, but I can weave in credibility.

Let's draft the markdown. I'll keep sections concise, honest, no fake numbers.

Structure:

• Heading 1: Main title
• Heading 2: Hero subtitle/description
• Paragraph: The problem
• Bullet list: What the playbook covers (honest, specific topics derivable from "client acquisition playbook for indie devs")
• Section: Free Checklist (lead magnet)
• Section: Full Playbook ($29)
• Heading: Who it's for
• Bullet list
• Small FAQ (honest questions)
• Maybe a footnote about the funnel/Maintenance if relevant, but keep it clean.

I need to ensure I don't invent. I'll describe the playbook contents generically but accurately: e.g., "Step-by-step framework for identifying studios that match your skill set", "Email and DM templates refined from real outreach", "Portfolio presentation strategies", "Handling rejection and follow-up". These are reasonable without claiming specific results.

Let's write it.

I'll start with the markdown top. I'll make sure headings use proper markdown (##, ###). Short paragraphs. Bullet lists. No fake testimonials. Price $29 mentioned once. Free checklist described. Traffic methods not needed on the page itself, but I can mention "SEO-driven" or "trusted by community" cautiously.

One thing: the user says "Write the complete public web page copy for 'Indie Dev Client Acquisition Playbook' (markdown: headings, short paragraphs, bullet lists)." So the output should be the full page copy in markdown. I'll produce it now.

Check constraints again:

• Be honest and specific about what it is and who it is for
• No fake testimonials, numbers or claims
• Do not invent prices, links or payment buttons
• Price is $29 (given, I can state it as text)
• Distribution plan involves lead magnet and upsell, I'll reflect that in copy structure (free checklist section, then upsell mention)

I'll make sure the copy doesn't have any "As seen on" or "Join 5000+" etc. unless I make up a reasonable non-specific phrase like "trusted by the indie community" but that might be vague. Better to just describe the product and funnel honestly.

Let's draft.

I'll structure it as a single-page sales/landing copy that naturally funnels to the checklist capture, then the $29 offer. I'll keep it text-only, no HTML forms or URLs.

Draft:

   #

## A Simple Client-Filtering System

Instead of blasting messages to a generic list, pick one specific problem you solve and identify three companies currently facing it. Send a short, genuine note: *"I noticed you're dealing with X—I've helped teams like yours streamline Y. Would a 10-minute chat be useful?"*

Track the replies in a plain-text file. After about a dozen outreach attempts, you'll notice patterns: who responds, what they care about, and whether they've got budget/authority. That data is more valuable than any polished funnel.

The playbook outlines this exact low-overhead method for turning conversations into contracts without derailing your development work.