$ cat prompt.txt — Digital Products
Digital Product Validator — Find a $500/mo Product in One Hour
Stress-test a digital product idea against real demand signals before you build it.
80% of failed digital products fail at validation, not execution. This prompt runs your idea through 6 brutal-honest validation gates (demand evidence, willingness-to-pay, competitive moat, distribution channel, support cost, refund risk) and either green-lights you to build, sends you back to ideation, or — most usefully — tells you the exact pivot that turns a marginal idea into a strong one.
$ cat prompt.txt | pbcopy
The prompt — copy & paste
You are a digital-product strategist who has shipped 30+ products on Gumroad and Lemonsqueezy. Your job is to validate (or kill) the product idea below using a structured 6-gate framework. Be HONEST — most ideas fail one of these gates and shouldn't be built.
MY PRODUCT IDEA: {{product_idea}}
TARGET BUYER: {{target_buyer}}
MY STRENGTHS / UNFAIR ADVANTAGES: {{your_strengths}}
EXECUTE THE FOLLOWING ANALYSIS:
GATE 1 — DEMAND EVIDENCE
Find evidence this problem actually causes my target buyer enough pain to pay for a solution. Look for:
- Existing paid products solving the same problem (yes = good — proves demand)
- Reddit / Twitter / Facebook group posts with people complaining about this pain
- Existing free solutions people are hacking together (templates, scripts, manual processes)
- YouTube tutorials with high view counts in this problem space
Output: GREEN / YELLOW / RED + a 2-sentence justification + 3 specific evidence points (you can synthesise from your training data).
GATE 2 — WILLINGNESS TO PAY
What's a realistic price for this product? Anchor against:
- What similar products charge (find 3 comparable products + their prices)
- What the time-savings or revenue-impact is worth to the buyer (a product that saves a freelancer 4 hours/week is worth $100+; one that saves an employee 30 min once is worth $9)
- Whether this is an impulse buy (<$25), considered purchase ($25–$99), or B2B sale ($100+)
Output: Recommended price range + which pricing tier it falls into.
GATE 3 — COMPETITIVE MOAT
Why won't the obvious competitor crush me 6 months in? Acceptable moats:
- A specific niche the incumbent doesn't serve well
- A bundled deliverable (template + video walkthrough + community access) the incumbent doesn't offer
- A trust/reputation signal (your existing audience, credentials, or case studies)
- Distribution channel access (your newsletter, your social audience)
NOT acceptable moats: "I'll be better" / "I'll be cheaper" / "I'll add AI"
Output: One sentence stating my actual moat, or "NO MOAT" + recommendation to pivot.
GATE 4 — DISTRIBUTION CHANNEL
How will my first 100 customers find me? Be specific. Acceptable channels:
- Existing audience (newsletter, Twitter, YouTube — minimum size for this niche?)
- Niche SEO content (which 3 keywords would I rank for? realistic ranking timeline?)
- Marketplace traffic (Etsy / Gumroad discovery — only works for high-margin templates)
- Communities I can authentically participate in (which 2 communities?)
- Paid ads (only viable if LTV is $50+)
NOT acceptable: "I'll post on Twitter" / "I'll do Product Hunt" / "It'll go viral"
Output: A specific 90-day distribution plan with at least 2 channels.
GATE 5 — SUPPORT + DELIVERY COST
What's the ongoing cost to keep this product alive?
- Email support questions per sale (rough estimate)
- Updates needed every 3–6 months
- Customer-success time per buyer
- Platform costs (Gumroad fees, hosting, anything recurring)
Output: Estimated hours/month of support time at 100 sales/month.
GATE 6 — REFUND + REPUTATION RISK
What could go wrong that costs me money or reputation?
- Promises I can't deliver on with the current product scope
- Customer use cases the product won't cover (which create refund requests)
- Risk of the AI / platform / API the product depends on changing or shutting down
Output: Top 2 risks + how to mitigate.
FINAL VERDICT
- GREEN LIGHT (all 6 gates pass): Build it. State the MVP scope.
- YELLOW LIGHT (1–2 gates marginal): Pivot. State the specific pivot that fixes the marginal gates.
- RED LIGHT (3+ gates fail): Kill it. State what category of idea I should look at instead.
Be honest, not nice. Killing a bad idea early is the highest-value thing this analysis can do.$ variables_to_fill_in
$ man playbook
Step-by-step playbook
How to actually use this prompt for the best results.
- 01
Write your idea in a single sentence
Be specific. 'A Notion template for freelancers to track client projects' is workable. 'A productivity tool' is not — the AI can't validate without specifics.
- 02
Identify your real target buyer
Skip demographics. Describe them by their CURRENT WORKFLOW: 'Freelance designers who currently track projects in a messy spreadsheet and miss invoice dates'. The narrower the buyer description, the sharper the validation.
- 03
List your unfair advantages honestly
Existing audience? Domain expertise? Connections? Production speed? If you have none — that's important data for the moat analysis. Don't invent strengths.
- 04
Run the prompt and resist defensive reasoning
If the AI flags a YELLOW or RED light, the natural reaction is to argue. Don't. Either accept the pivot it recommends, or test the same idea again with a different target_buyer (sometimes the pivot is the audience, not the product).
- 05
If GREEN — build a 7-day MVP
Don't polish. Ship the minimum viable version of the product within 7 days. Real customer feedback beats theoretical product perfection 10 out of 10 times.
$ man tips
Pro tips for better output
- ›Run the prompt 2–3 times with slightly different framings — sometimes the model gives different verdicts and the disagreement reveals the real risk.
- ›The 'no moat' verdict is the single most useful output — most failed digital products are 'me-too' executions of products with already-strong incumbents.
- ›Pair this prompt with manually checking 3–5 Reddit posts in the target audience's communities for unprompted complaints about the problem.
- ›Don't pre-commit emotionally. The whole point of this prompt is to find out you SHOULDN'T build something before you sink 40 hours into it.
$ echo $YIELD
What you'll get
A 6-gate scored analysis of your product idea ending in a clear GREEN/YELLOW/RED verdict with — for yellows and reds — the exact pivot that fixes the marginal gates.
$ man faq
FAQ
How accurate is AI validation vs talking to actual customers?
AI validation is ~60% as accurate as 10 real customer interviews. Treat it as a fast filter: if it says GREEN, still do 5 interviews before building. If it says RED, trust it — saving 40+ hours on a bad idea is the point.
Can I validate a service / coaching offering with this?
Yes, with minor adjustments — replace 'sales' references with 'engagements' and adjust the pricing tier in Gate 2. The 6 gates apply identically.
$ ls /prompts/digital-products
Related prompts
$ cd /prompts — explore all 48 free AI prompts on ClaudeSkill