Offer stack
The core product, bonuses, support, and guarantee grouped into one easy-to-scan package before the price and buy button.
See it
What it is
An offer stack presents the core product, bonuses, support, and guarantee as one package before revealing the price. It is the written form of the Ronco infomercial move, where every bonus is named and added to the pile before the host says the number. Direct-response sales pages keep the pattern because buyers can scan the whole exchange: what arrives, what risk comes off them, and what they pay.
Reach for it when an offer has several real parts that are easy to miss when scattered across a long page. Name each part, state the specific job it does, then place the guarantee and one total price under the list. The stack should clarify the package, not manufacture complexity.
Gotcha: fake crossed-out values make the entire offer feel fake. A bonus is not worth $497 because that number makes the arithmetic look dramatic. Use prices you actually charge separately, or leave the individual values out and sell the usefulness of the package.
Ask AI for it
Build an offer-stack section for [offer] using only these approved components, prices, bonuses, and guarantee terms: [inputs]. For each component, write a concrete name and one sentence explaining the job it does. Show a separate value only when the supplied inputs prove that item is sold separately at that price. Then show the package price, guarantee, reassurance line, and one purchase CTA. Implement the stack as semantic HTML with a responsive CSS `grid-template-columns` layout, and return the final copy plus markup. Do not invent bonuses, list prices, savings, scarcity, testimonials, or guarantee terms.