Chapter 1
Gather the inputs before writing
Turn gather the inputs before writing into a conversion-ready page asset in 20–30 minutes, with buyer language, proof, and one clear action—without adding copy that does not reduce buyer uncertainty.
What you’ll get
- Primary copy asset: Create a product-page brief.
- Working section: Build a voice-of-customer bank.
- Exit signal: a new visitor can explain the offer and next action after a short scan.
Before you begin
Bring the actual product, price, delivery method, buyer language, and the proof you can honestly show. Set a 20–30 minutes timer. Do not draft around imaginary features or unsupported outcomes.
| Buyer question | Evidence or copy | Pass condition | Next action |
|---|---|---|---|
| Gather the inputs before writing | Product facts, observed language, preview, or proof | The visitor understands the result and next step | Place it in the page and run the five-second check |
Conversion checkpoint
Every section must answer a buying question: fit, result, contents, proof, price, delivery, or next action. If copy does not reduce uncertainty or support the CTA, shorten or remove it.
Create a product-page brief
Write one sentence for each:
- Audience
- Trigger situation
- Pain or obstacle
- Desired outcome
- Product mechanism
- Included components
- Format and requirements
- Current alternatives
- Proof available
- Price and delivery
- Main objections
If these inputs are vague, copywriting will only hide the product problem. Return to How to Research What Your Audience Will Pay For.
Build a voice-of-customer bank
Collect exact, permission-safe language from interviews, support questions, comments, search queries, and sales conversations. Categorize by problem, desired result, current alternative, objection, and decision criteria.
Use the patterns to write clearly. Do not publish a private quote or imply endorsement without permission.
Build a source-of-truth brief
Separate page inputs into three columns before drafting. Product facts include format, files, delivery, compatibility, price, support, and update policy. Buyer language includes exact phrases from questions, objections, reviews, interviews, and support messages. Claims needing proof include time saved, performance improvements, or outcomes that require an example, demonstration, or customer evidence. Write copy only from those columns. When a fact is missing, assign an owner and deadline instead of inventing a smooth sentence. This brief prevents contradictions between the hero, inclusions, FAQ, checkout, and delivery instructions, and it gives future revisions one reliable reference.
