Skip to content

$ cat prompt.txtDigital Products

Gumroad Sales Page — High-Converting Copy for Any Digital Product

Full Gumroad / Lemonsqueezy sales-page copy: hook, transformation, what's-inside, proof, FAQ, CTA.

20–40 min beginner Claude Sonnet, GPT-5#gumroad#sales-copy#digital-products
intro.md

Your Gumroad product page IS your salesperson. Most creators write a paragraph and a price — and convert at 1%. This prompt writes the full conversion-optimized page (hook → transformation → what's-inside → proof → FAQ → CTA) calibrated to your buyer and price point.

$ cat prompt.txt | pbcopy

The prompt — copy & paste

prompt.txt
You are a direct-response copywriter who's written sales pages for 7-figure digital-product creators. Write the complete Gumroad/Lemonsqueezy sales page for my product.

INPUTS:
- Product name: {{product_name}}
- What it is (format + contents): {{what_it_is}}
- Target buyer (who, their pain, what they've tried): {{target_buyer}}
- Price: {{price}}
- Transformation (before → after): {{transformation}}

WRITE THE PAGE in these blocks:

1. HEADLINE (above the fold)
The outcome, not the product. Pattern: "[Achieve outcome] [without pain / in timeframe]". Plus a one-line sub-headline that adds specificity.

2. THE PROBLEM (60–90 words)
Open inside the buyer's head — the exact frustration they have right now. Make them think "this is for me" in the first sentence.

3. THE SHIFT (40–60 words)
Introduce {{product_name}} as the bridge from before → after. Name it once.

4. WHAT'S INSIDE (bulleted)
Every component, written as benefit + what it is: "• [Outcome] — [the actual asset]". 5–9 bullets.

5. WHO IT'S FOR / NOT FOR
Two short lists. The "not for" list builds trust and filters refunds.

6. PROOF
2 short testimonial placeholders (attributed to persona) + a credibility line. If no testimonials yet, use category-validated phrasing.

7. PRICING + RISK REVERSAL
Frame the {{price}} against the value/time saved ("less than [comparison]"). Add a guarantee line if appropriate.

8. FAQ (5 questions)
The real pre-purchase objections for this product type (format, refunds, updates, "will this work for me", how delivery works).

9. CTA
A final block: short headline + button text + one-line urgency or reassurance.

RULES:
- Second person ("you"). Punchy. Fragments OK.
- Total 350–550 words.
- Ban: "elevate", "unlock", "game-changer", "revolutionary", "supercharge".
- The first 2 lines must work standalone (that's all a scanning buyer reads).

Also output a 150-char meta description for the product's Google snippet.

$ variables_to_fill_in

{{product_name}}{{what_it_is}}{{target_buyer}}{{price}}{{transformation}}

$ man playbook

Step-by-step playbook

How to actually use this prompt for the best results.

  1. 01

    Nail the transformation before writing

    {{transformation}} is the foundation. 'Helps you be productive' is weak. 'Go from a chaotic content backlog to 30 days of scheduled posts in a weekend' is a page that sells. Get specific on before → after.

  2. 02

    Run the prompt, then hand-edit the headline

    The headline carries 60% of conversion. Even when the AI nails the structure, spend 2 minutes making the headline punchier and more specific to your exact buyer.

  3. 03

    Replace placeholder proof with real testimonials fast

    Launch with the AI's placeholder proof if you must, but swap in real buyer quotes within the first 10 sales. Real proof converts 2–4× better.

  4. 04

    Add product screenshots between blocks

    Gumroad pages convert far better with visuals. Drop a screenshot of the actual product after 'What's Inside' so buyers see what they're getting.

$ man tips

Pro tips for better output

  • The 'who it's NOT for' section feels counterintuitive but raises conversion AND cuts refunds — it makes the right buyer feel seen.
  • Price-anchor against a relatable comparison ('less than one freelance hour') rather than discount-stacking.
  • Run the same prompt for 3 different buyer personas to find which positioning converts best — angle beats wording.

$ echo $YIELD

What you'll get

output.md

A complete 350–550 word sales page (headline, problem, shift, what's-inside, who-it's-for, proof, pricing, 5-question FAQ, CTA) plus a 150-char meta description.

$ man faq

FAQ

How long should a digital-product sales page be?

Long enough to overcome objections, short enough to stay scannable — 350–550 words for sub-$100 products. Higher-ticket products ($200+) justify longer pages with more proof and detail.

Will an AI-written sales page hurt my SEO?

No — Gumroad/Lemonsqueezy pages aren't a major SEO play anyway (they're conversion pages). The meta description helps the Google snippet, but these pages live or die by conversion, not ranking.

$ ls /prompts/digital-products

Related prompts