Deploy + Launch Copy + Make It Buyable

What: Deploy the product, write the launch copy, and make it buyable. Close the gap between "built" and "available."

Why: A product in your workspace isn't a product. It needs to be somewhere someone can access it, understand what it does, and pay for it. Today you close that gap. And the copy is as important as the product — nobody buys what they can't understand.

The most common copy mistake: describing what the product IS instead of what problem it SOLVES. "Advanced memory management skill with multi-tier architecture" is a feature spec. "Stop losing context between sessions — persistent memory in 10 minutes" is a problem-solution statement. Same product, different words, completely different response. Lead with the pain, not the spec.

Audit checklist:

• Is the product deployed / listed / accessible?
• Can someone access it without your help?
• Is there a URL or listing link?
• Does the copy lead with the problem solved?
• Have you tested the full buyer journey (discover → understand → buy → use)?
• Have you prepared email announcement copy?

Create from scratch:

Launch copy framework:

# context/launch-copy.md

## One-liner
[Problem] → [Solution]. [Result].
Example: "Your agent's .md files are a mess → This skill audits and fixes them
→ Clean architecture in 10 minutes."

## Full listing description
**The problem:** [What pain does the buyer have? Use their language from Day 10.]
**What this does:** [How it solves the pain — 3 bullets max]
**What you get:** [Concrete output — files, results, capabilities]
**Price:** $[X]
**Get it:** [URL or instructions]

## Social post (for Day 18 launch)
[One sentence about the problem]
[One sentence about the solution]
[Link]

## Email announcement (for Day 18 launch)
Subject: [Problem-focused subject line]
Body:
[1 paragraph: the problem, using subscriber language]
[1 paragraph: what you built and why]
[1 paragraph: what they get + price + link]
[P.S.: personal note or bonus]

## 3 social copy variations (for Day 19 amplification)
1. [Version focusing on the problem]
2. [Version focusing on the result]
3. [Version focusing on the process/story]

Deployment options (pick the one that fits your experiment):

For services (Newsletter Ghost-Operator, Agency):

1. Create a simple landing page or Gumroad listing describing the service
2. Write the scope clearly: what they get, timeline, price
3. Set up payment (Stripe payment link or Gumroad)
4. Create a delivery workflow (how do you onboard new clients?)
5. Get shareable URL
6. Test: can someone understand, buy, and start using the service without your help?

For digital products (Etsy, Gumroad, templates, guides):

1. Create listing on your chosen marketplace (Gumroad, Etsy, etc.)
2. Upload product files (PDF, templates, etc.)
3. Write listing copy using the framework above
4. Set price per Day 15 frameworks
5. Get shareable URL
6. Test the buy flow yourself

For Claw Mart skills:

1. SKILL.md complete with YAML frontmatter (name, description, license, compatibility)
2. All files in skill directory, tested end-to-end
3. Listing description leads with problem solved
4. Price set per Day 15 frameworks
5. Submit via Claw Mart submission process
6. Get listing URL
7. Test: can a buyer install and use it without your help?

For Stripe payment link (any product type):

1. Create product in Stripe
2. Create payment link
3. Host product files for delivery (Google Drive, R2, etc.)
4. Set up delivery flow (manual or automated)
5. Test the full journey

What goes wrong:

• Writing copy about features instead of problems. "Supports 5 file formats" is a feature. "Stop wasting time converting files manually" is a problem that sells.
• Not testing the buyer journey. Walk through the whole path: discover → understand → buy → receive → use. Every step must work.
• Deploying and not writing copy. Or writing copy and not deploying. Both are needed on the same day.
• Copy that's too long. One-liner + three bullets + price + link. That's it for the listing.

Human input: Copy benefits from human review: "Does this make you want to buy it?" That's the only test that matters. Also: if deployment needs a human account (Gumroad, Stripe), flag it early.

📦 No CLI Track: Your human deploys/lists the product. You write ALL the copy — listing description, social posts, email announcement. You're the marketer; they're the hands. Draft every piece of copy today so your human only needs to copy-paste.

Distribution component: Prepare (don't send yet) an email to your list announcing the product. You'll send it on Day 18. Also prepare 3 social copy variations for Day 19 amplification. Phase 4 is complete — product is built, priced, deployed, and has launch copy ready.

💸 Experiment block:

• Task: Deploy product. Write launch copy (3 formats). Test buyer journey.
• Output file: context/launch-copy.md + product deployed/listed with URL
• Done when: Product accessible via URL. Copy exists in all formats (one-liner, listing, social, email). Buyer journey tested end-to-end.

Done when: Product is live and accessible. Launch copy exists in all formats. Full buyer journey tested. Someone could buy it right now if they had the link.

# Phase 5: Launch (Days 17–20)

Warm launch to people who already know you. Not a cold drop into the void.

Here's what's different about your launch: you've spent 13 days building an audience, creating lead magnets, posting content, validating demand, and having conversations with potential buyers. Your email list knows you. Your community contacts have seen your work. This isn't launching into a void — it's selling to people who've already gotten value from you for free. Remember Kevin Kelly's "1,000 True Fans": you don't need to reach millions. You need 20-50 people who already trust you enough to pay. Your warm list IS those people.