- Analyze the Request:
- Product/Topic: "Solo Creator Handover Protocol Pack"
- Format: Complete public web page copy in markdown (headings, short paragraphs, bullet lists)
- Goal: Free downloads of the protocol pack
- Plan Details:
- Goal metric: number of free downloads
- Checkpoint: 48 hours
- Kill rule: max 3 iterations without revenue
- Boost rule: min $5 revenue (but price is $0, so this might be about referred signups or something else, but I'll stick to the brief)
- Clone rule: min $20 revenue
- Channel: owned-site
- Price: $0
- Distribution: Landing page on owned website, free PDF download, capture emails via signup form, promote via existing social channels, niche forums, Discord/Slack communities
- Track: Google Analytics, email list growth
- Maintenance Plan: Quarterly updates based on email list feedback, keep landing page functional, fix links, refresh SEO metadata monthly, review after each checkpoint
- Constraints:
- Be honest and specific about what it is and who it's for
- No fake testimonials, numbers, or claims
- Don't invent prices, links, or payment buttons
- Venture/Stage/Task Info: Provided but seems like metadata; I'll focus on the web page copy.
- Deconstruct the "Solo Creator Handover Protocol Pack":
- What is it likely? A checklist/system for solo creators to hand over their business/projects/assets to someone else, or a handover protocol for transitioning work, or a "done-for-you" or "here's how I organize things" document.
- Given the name "Handover Protocol Pack," it's probably a set of templates/docs for solo creators to hand over their work to a successor, collaborator, or assistant.
- I need to be honest and specific. I'll define it clearly without making up features or fake stats.
- Determine the Web Page Structure (Markdown):
- Standard landing page sections:
- Headline/hero
- Sub-headline/brief intro
- What's included (bullet list)
- Who it's for (bullet list/short paragraph)
- How it works (brief)
- Download/email capture CTA
- Footer maybe
- Must be markdown format with headings, short paragraphs, bullet lists.
- No fake numbers. I'll just say "free PDF download" etc.
- No invented links or payment buttons. I'll use placeholders like
# or relative paths but the prompt says "Do not invent prices, links or payment buttons." I'll avoid actual URLs or make them generic like [download-link] but maybe better to just not force links that aren't specified. I'll use markdown link syntax but keep it generic or omit actual URLs. The prompt says "Do not invent prices, links or payment buttons." I'll avoid putting real URLs. I can use [Download Protocol Pack] but maybe just say "Download" without a fake href. I'll keep it clean.
Actually, re-reading: "Do not invent prices, links or payment buttons." I should not create fake URLs like https://example.com/download. I can use markdown syntax for links that are placeholders or just text. I'll likely just write the copy and use [Download] but maybe avoid href. I'll see. I'll just not include href attributes or use #. Better to just have the text and mention the download is available, but not fake a link. I'll structure it so the CTA is descriptive.
Let's plan the sections:
- Hero headline
- Brief what it is
- What's inside (bullet list)
- For whom (paragraph + bullets)
- How to get it (paragraph)
- Footer/terms
I need to integrate the plan details? The prompt says "Write the complete public web page copy for 'Solo Creator Handover Protocol Pack' (markdown: headings, short paragraphs, bullet lists). Plan: { ... }". It might want the web page copy to reflect the plan's goals, but the plan is metadata for the venture. The actual web page copy should be for the public, honest, specific. I'll incorporate the essence: free PDF, for solo creators, handover protocol. I won't clutter with the kill/boost rules unless it fits, but the prompt says "Be honest and specific about what it is and who it is for; no fake testimonials, numbers or claims." So I'll keep the web page copy focused on the product, not the internal venture metrics. The plan is likely for the system running it, not necessarily displayed on the page. I'll make the web page copy clean and focused on the pack.
Let's draft the markdown:
# Solo Creator Handover Protocol Pack
A practical, ready-to-use framework for solo creators who need to hand over their projects, assets, and workflows—whether transitioning to a collaborator, assistant, or simply taking a break.
...
I'll make sure:
- No fake numbers
- No fake testimonials
- Clear description
- Who it's for
- What's inside (bullet points, honest)
- How to download (free, email capture implied but not fake)
- Simple, professional tone
Let's draft carefully. I'll avoid any URL invention. I'll use markdown headings properly. I'll keep paragraphs short. I'll use bullet lists for features/what's inside.
Structure:
- H1: Solo Creator Handover Protocol Pack
- H2: What is this?
- Paragraph
- H2: What's included
- Bullet list (honest, specific items like "Project inventory template", "Asset index", "Workflow handover checklist", "Communication log", "Financial snapshot")
- H2: Who it's for
- Paragraph + bullet or just paragraph
- H2: How to get it
- Paragraph: "Enter your email below to receive the PDF instantly. No payment required."
- Maybe a form placeholder but without fake href. I'll just say "[Download Protocol Pack]" as text, or use
[Download] with no href, or just "Download the Protocol Pack". The prompt says "Do not invent links". I'll avoid href="...". I'll just have the text "Download the Protocol Pack" and maybe note it's a free PDF.
Actually, I can use markdown link syntax with a relative path like ./protocol-pack.pdf but that's inventing a link. Better to just not have a clickable link, or use [Download] without href, or just plain text. I'll stick to plain text CTA: "Download the Protocol Pack" and describe the process.
Let's draft.
I'll make sure the copy aligns with the venture's plan indirectly but the page itself is just the public copy. I'll keep it honest.
Draft:
# Solo Creator Handover Protocol Pack
A minimal, practical framework for solo creators who need to hand over their projects, assets, and workflows—whether you're transitioning to a collaborator, taking a break, or wrapping up your work.
What’s inside
• Project inventory template – List ongoing projects, status, and next steps in one place.
• Asset index – URLs, logins, and ownership notes for your digital and physical assets.
• Workflow handover checklist – Step-by-step guide for transferring tasks without guesswork.
• Communication log – Capture context, decisions, and pending items for a smooth handoff.
• Financial snapshot – Quick overview of revenue, expenses, and recurring subscriptions.
Who this is for
• Solo entrepreneurs handing over a business, newsletter, or side project.
• Creators transitioning to a manager, assistant, or business partner.
• Anyone who needs a clear, repeatable process for passing the baton.
How to get it
Enter your email address below to receive the Solo Creator Handover Protocol Pack as a free PDF. No payment required. No spam. Just a single download link sent to your inbox.
[Download the Protocol Pack]
Wait, the [Download the Protocol Pack] line might be considered a link. I'll make it plain text without markdown link syntax, or I'll use markdown but with mailto: or something? The prompt says "Do not invent links". I think it means don't make up URLs or payment buttons. A download CTA is expected. I'll just keep it as text: "Download the Protocol Pack" and maybe on the actual site it would link, but in the markdown copy, I'll just have the text. To be safe, I'll avoid []() or just use Download the Protocol Pack as plain text. I can also say "Sign up here" but that might imply a form. I'll keep it simple.
Let's refine to match the "short paragraphs, bullet lists" requirement and the honesty constraint.
I'll produce the final markdown now. I'll make sure there are no fake numbers, no invented links (I'll just have the CTA text without an actual href), and it's specific about what the pack is.
One thing: the plan mentions "Capture visitor emails via a signup form". I can mention that in the copy: "Enter your email below" but I won't invent a form layout