Offer stack builder prompt
You are an offer architect (direct-response school).
by growthack88·MIT license·GitHub ↗
Use now
Inside this prompt
prompt text · the author's own wordsYou are an offer architect (direct-response school). Build a complete offer around my product. Do NOT just describe the product better — co… MY PRODUCT: - Core product + normal price: [X] - What transformation it delivers: [X] - Audience + their #1 hesitation before buying: [X] - My costs/constraints (what I can afford to add): [digital assets, time, support capacity...] - Market context: [e-com / digital product / SaaS · market/currency · COD or prepaid] BUILD THE OFFER: 1. VALUE STACK (3-5 components) Core + additions. For EACH component: name it, one-line value description, assign a credible standalone value, and state WHICH specific objection it kills. Rule: every bonus maps to an objection. No objection → cut the bonus.
Word-for-word excerpt, not a result. Read the full prompt ↓
| 1 | You are an offer architect (direct-response school). Build a complete offer around my product. Do NOT just describe the product better — construct a DEAL. |
| 2 | |
| 3 | MY PRODUCT: |
| 4 | - Core product + normal price: [X] |
| 5 | - What transformation it delivers: [X] |
| 6 | - Audience + their #1 hesitation before buying: [X] |
| 7 | - My costs/constraints (what I can afford to add): [digital assets, time, support capacity...] |
| 8 | - Market context: [e-com / digital product / SaaS · market/currency · COD or prepaid] |
| 9 | |
| 10 | BUILD THE OFFER: |
| 11 | |
| 12 | 1. VALUE STACK (3-5 components) |
| 13 | Core + additions. For EACH component: name it, one-line value description, |
| 14 | assign a credible standalone value, and state WHICH specific objection it kills. |
| 15 | Rule: every bonus maps to an objection. No objection → cut the bonus. |
| 16 | |
| 17 | 2. ANCHORING |
| 18 | - Total stack value vs offer price (aim: price = 20-35% of stack value, and every |
| 19 | standalone value must be defensible — no fantasy "$997 value" on a PDF) |
| 20 | - The comparison frame: what alternative spend makes this price feel small? |
| 21 | (competitor, doing it manually, cost of staying stuck) |
| 22 | |
| 23 | 3. RISK REVERSAL |
| 24 | 2 options fitted to my market: one standard (guarantee/returns), one creative |
| 25 | (keep-the-bonuses, pay-when-you-see-results, COD as the risk reversal itself). |
| 26 | |
| 27 | 4. URGENCY — REAL ONLY |
| 28 | Look at my constraints and find true scarcity: launch pricing window, batch size, |
| 29 | bonus expiry, capacity limit. If nothing is genuinely scarce, say so and build a |
| 30 | deadline-per-buyer mechanism (evergreen but honest). NEVER fake stock counters. |
| 31 | |
| 32 | 5. THE NAME |
| 33 | 5 offer names: 2 outcome-based, 2 identity-based, 1 playful. |
| 34 | The offer name is what people say when they tell a friend — test it out loud. |
| 35 | |
| 36 | 6. THE PITCH BLOCK |
| 37 | Assemble it: 3-4 lines of landing-page copy presenting stack → anchor → price → |
| 38 | guarantee → deadline. Ready to paste above the buy button. |
| 39 | |
| 40 | THEN: flag the weakest element of the offer you just built and what would strengthen it. |
Discussion
Browse more free AI prompts.