long-form-sales-copy

name	long-form-sales-copy
description	Use when a defined offer needs a long-form sales page, VSL, webinar pitch, order-page sequence, or funnel copy; use `sales-copywriting` for shorter conversion elements and `content-writing` for non-sales pages.
metadata	{"portable":true,"compatible_with":["claude-code","codex"]}

Long-Form Sales Copy

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, [phone].

Adapt Kennedy-style sales-letter discipline and Brunson-style funnel sequencing to a real offer without fake urgency, fabricated proof, or formulaic excess.

Use When

• A defined product, service, event, course, membership, or application offer needs a long sales page.
• The deliverable is a VSL, webinar pitch, order page, upsell, confirmation page, or connected funnel sequence.
• A current long-form asset has a diagnosed conversion or message problem.

Do Not Use When

• The page is corporate or informational with no direct conversion goal; use content-writing.
• Only a headline, CTA, proof block, or short landing page needs work; use sales-copywriting.
• The offer, price, terms, audience, proof, or regulatory boundary is undefined; stop for offer discovery.

Required Inputs

Artefact	Source or provider	Required?	When missing
Offer, price, inclusions, exclusions, terms, and fulfilment path	Offer owner	yes	Stop; do not invent the commercial exchange.
Audience, awareness, traffic source, and hidden benefit hypothesis	Research/marketing owner	yes	Return a discovery brief instead of writing for a fictional buyer.
Proof, objections, guarantees, deadlines, and compliance constraints	Client and compliance owner	yes	Remove unsupported elements and record the gap.
Brand voice, design, checkout, and measurement constraints	Owning teams	conditional	Produce copy and handoff notes only; mark assumptions.

Workflow

1. Validate the offer, buyer, traffic temperature, regulatory boundary, and authority for every term.
2. Stop if the offer cannot be fulfilled as described or the central promise lacks support.
3. Map features to supported benefits, identify objections, and test the hidden-benefit hypothesis against customer evidence.
4. Choose the page script by asset: Kennedy-style sales letter, Star-Story-Solution VSL, webinar pitch, order-page close, or post-purchase confirmation.
5. Draft the argument: orientation, problem, admission or constraint, promise, mechanism, proof, offer, risk reduction, action, and FAQ.
6. Build a truthful value presentation using actual price and terms; never assign invented component values.
7. Repeat CTAs only at genuine decision points and match each to traffic awareness.
8. Add order, upsell, thank-you, and follow-up copy only where those steps exist in the approved funnel.
9. Run scanner, objection, proof, compliance, mobile-readability, and anti-slop reviews.
10. If a deadline, testimonial, guarantee, or outcome cannot be verified, remove it and rebalance the page.
11. Hand off copy, states, source notes, and measurement hypotheses; publishing and launch remain separate authorities.

Recovery: repair the offer, evidence, or compliance gap, then rerun the claim and release review.

Quality Standards

• The offer and action are understandable from headings and key proof blocks.
• Every promise, testimonial, price, value, guarantee, and deadline is accurate and attributable.
• The structure matches awareness and traffic source rather than blindly maximising length.
• Objections and constraints are addressed with evidence and plain language.
• The page works on a narrow mobile viewport and does not rely on pressure, dark patterns, or hidden terms.
• Order and confirmation copy state fulfilment, payment, cancellation, privacy, and support expectations accurately.

Anti-Patterns

• Opening with company history. Fix: orient the buyer to the problem and offer.
• Assigning invented monetary values to bonuses. Fix: use defensible price or qualitative value.
• Creating fake deadlines or quantity limits. Fix: state only operationally enforced constraints.
• Using anonymous or synthetic testimonials. Fix: obtain attributable proof or remove them.
• Repeating CTAs every few paragraphs regardless of intent. Fix: place them at real decision points.
• Writing a long page because the framework is long. Fix: keep only sections needed for this awareness and risk level.
• Hiding checkout or cancellation terms. Fix: surface them before commitment.
• Claiming regional conversion percentages without evidence. Fix: treat local channel choices as hypotheses to test.

Outputs

Artefact	Consumer	Observable acceptance condition
Long-form page or VSL copy	Design and implementation owners	Complete, ordered, source-backed, and mapped to page or timing cues.
Funnel copy set	Checkout, email, and campaign owners	Each approved step has purpose, action, states, and consistent terms.
Proof and compliance register	Client and release owner	Claims, testimonials, prices, guarantees, and deadlines have evidence and authority.
Scanner and objection review	CRO owner	Headings communicate the offer and material objections are addressed.

References

• Offer and landing-page writing for premium restraint and proof.
• Professional writing quality gate for final review.
• Website messaging framework for claim, proof, and CTA structure.
• Closing and guarantees for honest risk reduction.
• Resistance and objections for buyer concerns.

Evidence Produced

Evidence	Format	Acceptance condition
Offer and claim register	Source-tagged table	Price, terms, proof, guarantee, deadline, and owner are traceable.
Script and funnel map	Page/beat table	Each section or step has a purpose and approved next action.
Release review	Checklist	Compliance, mobile readability, terms, proof, states, and unresolved gaps are recorded.

Capability Contract

Read access to offer, evidence, and constraints is required. Review defaults to read-only; writing to project files requires authority. Publishing, production changes, pricing, guarantees, spending, customer messages, and certification claims require explicit authority from their owners.

Degraded Mode

Without customer evidence, compliance review, rendering, analytics, or implementation access, return a qualified copy deck and exact verification checklist. Do not treat unrendered mobile copy, unverified terms, or assumed conversion outcomes as passed.

Decision Rules

Choice	Action	Failure or risk avoided
Cold traffic and complex high-risk offer	Use fuller education and proof	Asking for commitment before trust
Warm traffic and familiar offer	Use a shorter direct structure	Unnecessary friction and fatigue
Webinar or video is primary medium	Use timed script with on-screen cues	Page prose that fails in speech
Offer or compliance is unresolved	Stop and return discovery gaps	Unfulfillable or unlawful promises
Evidence cannot support a section	Remove or narrow it	Persuasive fabrication

Worked Example

For a Kampala equipment supplier, a genuine stock deadline may be stated only if inventory and reservation rules enforce it. WhatsApp and mobile-money options may be offered when operationally supported, but no conversion lift is claimed without measured project evidence.

Read Next

• sales-copywriting for shorter conversion components.
• premium-commercial-writing for tone, proof, and anti-slop review.
• ecommerce-checkout for transaction flow and state design.
• experimentation for measured message tests after launch.