Landing Page Copywriter

Landing Page Copywriter

Write landing page copy that makes one reader take one action. The copy is the deliverable; layout and code are out of scope unless asked.

Workflow

1. Build the brief. Pull these from the conversation, attached docs, or the product's existing site before asking anything. Ask only for what is missing and blocking:

   • Product and the one action the page drives (buy, book, sign up, join waitlist)
   • Who lands here and where they came from (ad, search, email, referral) - this sets how much context the hero must carry
   • The problem in the reader's words, and what they use today instead
   • The real differentiator versus that alternative
   • Proof that actually exists: numbers, named customers, reviews, guarantees

2. Write the message hierarchy before any sections. One sentence each:

   • Promise: the outcome the reader gets
   • Mechanism: why this product delivers it when alternatives do not
   • Proof: the strongest real evidence
   • Action: the CTA and what happens right after clicking

   If you cannot fill one of these, flag the gap instead of papering over it. Every section below expands one of these four lines.

3. Pick the framework from the reader's awareness:

   • Reader feels the pain but has not looked for fixes: PAS
   • Reader is comparing options or cold from an ad: AIDA
   • Brand-led, story-heavy, or services business: StoryBrand

   Section-by-section guidance for each framework is in references/frameworks.md.

4. Draft the page in the order hero, problem, solution/features, how it works, proof, pricing (if relevant), FAQ, final CTA. Cut sections the product does not need; a waitlist page may be hero + three benefits + CTA.

5. Write variants where they matter: 3 headline options (different angles: outcome, pain, mechanism) and 2 CTA options. Say which you would test first and why.

6. Run the checks below, fix what fails, then deliver using references/output-template.md.

Checks before delivering

• No invented proof. Never make up testimonials, customer names, logos, user counts, or percentages. Use a labeled placeholder like [TESTIMONIAL: ops lead at a customer, quote about time saved] and list every placeholder at the end.
• Headline test. Could a competitor paste your headline onto their page unchanged? If yes, it is too generic. Anchor it to the mechanism or a specific outcome.
• Benefit test. Every feature line answers "so what?" for the reader. "Real-time sync" becomes "Your team sees the same numbers, no more version-hunting."
• One primary action. Every CTA on the page points to the same action. Secondary links (docs, pricing) stay visually secondary in your notes.