Writing Conversion Copy
Overview
Write credible decision-oriented copy around a real offer, real audience need, and real evidence. Conversion quality comes from relevance and reduced uncertainty, not hype or coercion.
Establish the Decision
Before drafting, identify:
- the audience and situation;
- the offer and the concrete outcome it provides;
- the primary decision or next action;
- supplied proof: product facts, demonstrations, pricing, guarantees, research, customer evidence, or constraints;
- likely objections, risks, switching costs, and missing information;
- any approved brand voice from
writing-brand-voice-and-messaging.
If these are materially unclear, use planning-written-communication first.
Build the Copy
- Lead with the most relevant outcome or problem-to-progress connection, not a generic superlative.
- Explain what the offer is before stacking benefits around it.
- Convert features into benefits only when the causal link is defensible.
- Place proof next to the claim it supports. Distinguish measured evidence from illustrative examples.
- Resolve important objections explicitly: price, effort, fit, timing, risk, compatibility, commitment, or alternatives.
- Use hierarchy for scanning: promise, explanation, proof, objections, offer terms, then a clear next action.
- Give one primary CTA a label that describes the real next step. Secondary actions should represent genuinely different paths.
- For experiments, state the hypothesis and measurable behavior; never present an untested variant as guaranteed to convert better.
Integrity Contract
Never invent or embellish:
- testimonials, customer counts, logos, ratings, statistics, research, awards, guarantees, scarcity, deadlines, savings, comparisons, or product capabilities;
- urgency that is not operationally real;
- consent or cancellation framing designed to make refusal harder than acceptance.
Do not use deceptive interface patterns, hidden costs, preselected consent, obstruction, false scarcity, or shame-based copy. If a persuasive request conflicts with an informed user decision, preserve the user's ability to understand and choose.
Boundary With Other Writing
- Durable voice and messaging systems belong to
writing-brand-voice-and-messaging.
- Buttons inside a product flow, errors, empty states, permissions, and operational UI belong to
writing-product-and-ux-copy.
- Structural page implementation belongs to
building-conversion-product-pages.
- Revision whose goal is clarity rather than persuasion belongs to
editing-for-clarity-and-tone.
Review Checklist
Verify that every material claim is supported, the offer terms are understandable, the CTA matches the next state, the copy can be scanned without losing the decision logic, and removal of persuasive language would not expose missing product substance.
Reference Signals
Plain-language and user-needs guidance from GDS/ONS informs clarity and action structure. FTC enforcement and guidance on deceptive interface patterns define an important boundary: persuasion must not become manipulation or coerced consent.
1---2name: writing-conversion-copy3description: Use when writing or revising landing pages, sales pages, promotional emails, ads, product offers, calls to action, or other marketing copy whose job is to help a reader make a specific decision.4---56# Writing Conversion Copy78## Overview910Write credible decision-oriented copy around a real offer, real audience need, and real evidence. Conversion quality comes from relevance and reduced uncertainty, not hype or coercion.1112## Establish the Decision1314Before drafting, identify:1516- the audience and situation;17- the offer and the concrete outcome it provides;18- the primary decision or next action;19- supplied proof: product facts, demonstrations, pricing, guarantees, research, customer evidence, or constraints;20- likely objections, risks, switching costs, and missing information;21- any approved brand voice from `writing-brand-voice-and-messaging`.2223If these are materially unclear, use `planning-written-communication` first.2425## Build the Copy26271. Lead with the most relevant outcome or problem-to-progress connection, not a generic superlative.282. Explain what the offer is before stacking benefits around it.293. Convert features into benefits only when the causal link is defensible.304. Place proof next to the claim it supports. Distinguish measured evidence from illustrative examples.315. Resolve important objections explicitly: price, effort, fit, timing, risk, compatibility, commitment, or alternatives.326. Use hierarchy for scanning: promise, explanation, proof, objections, offer terms, then a clear next action.337. Give one primary CTA a label that describes the real next step. Secondary actions should represent genuinely different paths.348. For experiments, state the hypothesis and measurable behavior; never present an untested variant as guaranteed to convert better.3536## Integrity Contract3738Never invent or embellish:3940- testimonials, customer counts, logos, ratings, statistics, research, awards, guarantees, scarcity, deadlines, savings, comparisons, or product capabilities;41- urgency that is not operationally real;42- consent or cancellation framing designed to make refusal harder than acceptance.4344Do not use deceptive interface patterns, hidden costs, preselected consent, obstruction, false scarcity, or shame-based copy. If a persuasive request conflicts with an informed user decision, preserve the user's ability to understand and choose.4546## Boundary With Other Writing4748- Durable voice and messaging systems belong to `writing-brand-voice-and-messaging`.49- Buttons inside a product flow, errors, empty states, permissions, and operational UI belong to `writing-product-and-ux-copy`.50- Structural page implementation belongs to `building-conversion-product-pages`.51- Revision whose goal is clarity rather than persuasion belongs to `editing-for-clarity-and-tone`.5253## Review Checklist5455Verify that every material claim is supported, the offer terms are understandable, the CTA matches the next state, the copy can be scanned without losing the decision logic, and removal of persuasive language would not expose missing product substance.5657## Reference Signals5859Plain-language and user-needs guidance from GDS/ONS informs clarity and action structure. FTC enforcement and guidance on deceptive interface patterns define an important boundary: persuasion must not become manipulation or coerced consent.
jhonatan-oliveiradev