#offer stack and guarantee

Sales Page Prompt: Long-Form Copy Built From Real Proof

Paste your product facts, buyer, offer terms, real testimonials, and objections to get a full long-form sales page with headline options, offer stack, and FAQ.

Act as a direct-response copywriter who writes long-form sales pages for online courses, templates, and small software products, and who builds every claim from the proof the seller actually has. A sales page has one job, getting the right reader to one action, so you write in sections a reader can scan on a phone. Inputs: - Product facts: what it is, format, length, what the buyer gets, and who made it: [ProductFacts] - The buyer: who they are, the problem in their own words, and what they have already tried: [Buyer] - Offer terms: price, payment plans, bonuses, deadlines, and the exact guarantee or refund policy: [OfferTerms] - Proof I can show: testimonials I have permission to use, numbers I can verify, credentials: [Proof] - Objections I hear before people buy: [Objections] - The action and where the button goes: [CTA] Generate: 1. Headline options: three headlines, each built from a different element of Proof or ProductFacts, plus one subheadline. 2. Lead: an opening of 80 to 120 words that names Buyer's problem in their words and promises only what ProductFacts deliver. 3. Problem and failed fixes: why what Buyer tried did not work, without mocking them. 4. How it works: the method or path inside the product in three to five steps. 5. What's inside: modules or features as benefit-first bullets. 6. Who it is for and not for: two short lists. 7. Proof section: Proof quoted exactly, with names as permitted. When a testimonial describes an outcome, add what buyers can generally expect if Proof supports it, or flag that the seller needs that figure; under the FTC's Endorsement Guides, "results may vary" alone is not enough. 8. Offer stack: every item in OfferTerms, the price, and payment plan math. 9. Guarantee: OfferTerms' refund policy in plain words, without adding conditions or promises. 10. FAQ: one answer per objection in Objections. 11. CTA blocks: button text and a one-line reminder for the top, middle, and end of the page. 12. Claim check: list every claim on the page next to the input it came from, and flag any that rely on testimonials, under the FTC's Consumer Reviews and Testimonials Rule (16 CFR Part 465) and Endorsement Guides.