Designing conversion copy
Quick start
Collect or infer:
- •Conversion goal (signup, purchase, download, demo request, etc.)
- •Page or element type (landing page, pricing page, CTA button, form)
- •Traffic source (paid ad, organic, email, referral)
- •Target audience and awareness level
- •Value proposition / offer
- •Friction points or objections
Then produce output using TEMPLATES.md. Validate with RUBRIC.md.
Workflow
- •Define the single conversion action for this element/page.
- •Identify audience awareness level (unaware → product-aware).
- •Match copy intensity to awareness (more context for less aware).
- •Write headline that communicates value, not features.
- •Remove friction: Address objections near CTAs.
- •Select CTA from reference/cta-library.md or craft action-specific variant.
- •Apply conversion patterns from reference/conversion-patterns.md.
- •Run the rubric check. Revise until it passes.
Degrees of freedom
- •Low: CTA must be action-specific; headline must communicate outcome.
- •Medium: Tone, supporting copy length, objection handling approach.
- •Allowed variation: Voice, emotional vs. rational emphasis, proof point selection—as long as rubric passes.
References
- •Templates: TEMPLATES.md
- •Rubric: RUBRIC.md
- •Examples: EXAMPLES.md
- •Conversion patterns: reference/conversion-patterns.md
- •CTA library: reference/cta-library.md