landing-copy-objectionlisted

# Landing Copy: Objection handling This section names the reader's actual hesitation and answers it directly. It is not a second proof section, and it is not a place to restate the mechanism — its job is to name a doubt the reader is likely already holding and resolve it in the reader's own terms, not the product's. ## What this section answers One question per objection handled: **what is the specific, nameable reason this reader might not act, and what directly removes it?** A generic FAQ ("How does it work?" restating the mechanism section) isn't this — a real objection is something the reader would say out loud if pushed ("this sounds like it'll take longer than what I do now," "I've been burned by a tool like this before"). If the brief or upstream chain doesn't supply a real, specific objection, that's a gap to flag, not a license to invent a generic FAQ to fill the section. ## The algorithm Paragraph count from the beat count `landing-sequencer` assigned, with one addition specific to this archetype: **one objection per beat**, not one paragraph of general reassurance. A 3-beat objection section handles 3 distinct, named objections, not one objection developed across 3 paragraphs. Per objection: 1. **Name the objection in the reader's own words**, not the product's framing of it — a question or a stated doubt, not a euphemism for it. 2. **Answer it directly**, in one or two sentences. No hedge stacks, no "well, actually" — a direct answer or, if the honest