conversion-copy
Conversion Copy
Write headlines, CTAs, and value props that move people to act.
How to use
/conversion-copyApply copy constraints to this conversation./conversion-copy auditAudit existing copy against these constraints.
Constraints
Headlines
- MUST communicate the core benefit in 6-12 words
- MUST use specific language over abstract language ("Save 4 hours/week" not "Save time")
- SHOULD start with what the user gets, not what the product does
- NEVER use jargon the target user wouldn't use in conversation
- Test: would this make sense on a billboard at 60mph?
Value Propositions
- MUST answer "so what?" for every claim
- MUST include at least one specific number, timeframe, or outcome
- SHOULD use the user's language, not product language
- NEVER stack adjectives without evidence ("fast, easy, powerful")
- Formula: [Who] can [outcome] by [mechanism] in [timeframe]
Audit Checklist
- Remove every adjective. Does the copy still communicate value?
- Replace every "we" with "you". Does it still work?
- Read it aloud. Does it sound like a human talking?
- Show it to someone unfamiliar. Can they explain what this product does?
- If any answer is no, rewrite.
Anti-Patterns
- Starting with the company name or "Welcome to"
- Using "solution" as a noun (what problem? for whom?)
- Passive voice in CTAs ("Your account will be created" vs "Create your account")
- Copy that describes what the product is instead of what it does for the user
- Marketing superlatives without proof ("Best-in-class", "World's leading")
More from dragoon0x/product-skills
prd-writing
Write product requirement documents that engineers want to read and can actually build from. Covers structure, scope discipline, and the balance between clarity and over-specification. Use when writing PRDs, reviewing spec quality, or when engineering keeps asking clarifying questions.
1freemium-vs-paid-gate
Decide whether a product should offer a free tier, free trial, or go straight to paid. Structured decision framework based on economics, distribution model, and competitive landscape. Use when launching a new product or reconsidering your pricing model.
1error-recovery
When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.
1cta-patterns
Design calls-to-action that people actually click. Covers button copy, placement logic, urgency without manipulation, and progressive commitment. Use when reviewing pages for conversion potential or when CTA copy feels generic.
1onboarding-flow
Design first-run experiences that create the aha moment fast. Reduces time-to-value by sequencing actions, progressive disclosure, and contextual guidance. Use when building signup flows, product tours, or empty states.
1user-psychology
Apply motivation, friction, and trust patterns to product decisions. Maps cognitive biases and behavioral triggers to specific UI and copy choices. Use when reviewing flows for drop-off points or when something feels right but doesn't convert.
1