Stats
Actions
Tags
From rmbc-skills
Design irresistible offer stacks — core offer, bonuses, guarantee, urgency, and price anchoring structured to hit a 10:1 perceived-value-to-price ratio using RMBC principles.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rmbc-skills:offer-stacksonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design irresistible offer stacks that make the price feel like a steal. An offer stack is the complete package a prospect receives — the core offer plus bonuses, guarantee, urgency, and price anchoring. The target: 10:1 perceived value to actual price. If the product costs $97, the stack should feel worth $970+. This skill structures every component with a name, description, retail value, and a...
Design irresistible offer stacks that make the price feel like a steal. An offer stack is the complete package a prospect receives — the core offer plus bonuses, guarantee, urgency, and price anchoring. The target: 10:1 perceived value to actual price. If the product costs $97, the stack should feel worth $970+. This skill structures every component with a name, description, retail value, and a reason it matters to the ICP. The offer stack is where Mechanism meets money — every bonus reinforces the core mechanism and removes a specific objection.
| Input | Required | Description |
|---|---|---|
core_product | Yes | What the main product/service is, what it does, key features or deliverables |
price_point | Yes | Actual price the customer pays, plus any payment plan options |
target_audience | Yes | Who the buyer is — demographics, pain points, desires, awareness level |
num_bonuses | No | Number of bonuses to include (default: 3, range: 2-5) |
guarantee_type | No | Preferred guarantee: money_back, conditional, better_than_money_back, performance, double_money_back (default: money_back) |
Read rmbc-context/SKILL.md to load RMBC framework definitions. Offer stacking applies RMBC at the deal level — Research reveals which objections the bonuses must neutralize, the Mechanism determines what "only we" bonuses make sense, the Brief structures the stack for maximum perceived value, and Copy names each component compellingly.
Before building the stack, map the prospect's decision framework:
| Factor | Question | How It Shapes the Stack |
|---|---|---|
| Core desire | What outcome do they want most? | Core offer messaging leads with this |
| Primary objection | Why would they NOT buy? | Guarantee and key bonus address this |
| Secondary objections | What else holds them back? | Remaining bonuses address these |
| Comparison set | What else could they spend this money on? | Price anchoring uses this as reference |
| Time to value | How quickly do they need results? | Fast-start bonus accelerates perceived time to value |
Each bonus must pass three tests:
Bonus types ranked by perceived value:
| Type | Perceived Value | Fulfillment Cost | Best For |
|---|---|---|---|
| Live session/call | Very high | Medium (time) | High-ticket, coaching, services |
| Video training | High | Low (one-time creation) | Courses, info products |
| Template/toolkit | High | Very low | Any product with implementation |
| Digital guide/PDF | Medium | Very low | Supplements, physical products |
| Community access | High | Low (ongoing moderation) | Subscriptions, courses |
| Checklist/cheatsheet | Medium | Very low | Quick wins, fast-start items |
For each bonus:
Frame the guarantee as confidence, not risk — "We're so confident because [mechanism-based reason]."
| Guarantee Type | Copy Frame | Best For |
|---|---|---|
| Money-back | "Try it for [X] days. If you don't [outcome], we refund every penny." | Standard, low-risk |
| Conditional | "Follow the [system] for [X] days. If you don't [outcome], we refund you." | Courses, coaching (filters tire-kickers) |
| Better-than-money-back | "If it doesn't work, keep [bonus] AND get your money back." | High-confidence offers |
| Performance | "If you don't [specific measurable result], we [specific compensation]." | Results-based services |
| Double-money-back | "If you don't [outcome], we'll refund double your investment." | Very high-confidence, attention-grabbing |
Only include if the urgency is genuine. Types:
Never fabricate urgency. If no genuine urgency exists, skip this component and note that the offer is evergreen.
Structure the value reveal to make the price feel small:
Check the complete offer against these criteria:
## Offer Stack: [Core Product Name]
**Target Audience:** [ICP summary]
**Price:** [actual price]
**Target Value Ratio:** 10:1
---
### CORE OFFER
**[Product Name]** — Retail Value: $X,XXX
[2-3 sentence description focused on transformation]
Key deliverables:
- [Deliverable 1]
- [Deliverable 2]
- [Deliverable 3]
---
### BONUS 1: [Bonus Name] — Value: $XXX
[1-2 sentence description]
**Kills objection:** "[specific objection]"
### BONUS 2: [Bonus Name] — Value: $XXX
[1-2 sentence description]
**Kills objection:** "[specific objection]"
### BONUS 3: [Bonus Name] — Value: $XXX
[1-2 sentence description]
**Kills objection:** "[specific objection]"
---
### GUARANTEE
**[Guarantee Name]** ([type] — [duration])
[2-3 sentence guarantee copy]
---
### URGENCY
[Urgency element — or "Evergreen offer: no artificial urgency"]
---
### PRICE ANCHOR
| Component | Value |
|-----------|------:|
| [Core Offer] | $X,XXX |
| [Bonus 1] | $XXX |
| [Bonus 2] | $XXX |
| [Bonus 3] | $XXX |
| **Total Value** | **$X,XXX** |
| **You Pay** | **$XX** |
| **Value Ratio** | **X:1** |
---
### STACK VALIDATION
- Value ratio: [X:1 — pass/fail]
- Every bonus kills an objection: [pass/fail]
- Guarantee duration adequate: [pass/fail]
- Retail values defensible: [pass/fail]
- Mobile-scannable: [pass/fail]
Value ratio must hit 10:1 minimum — below this the offer doesn't feel irresistible
Every bonus must name the specific objection it neutralizes — "nice to have" bonuses dilute the stack
Retail values must be defensible — if someone Googled the bonus, the value should hold up
Guarantee must be specific about duration, process, and conditions — vague guarantees feel like loopholes
Urgency must be genuine or explicitly omitted — fake scarcity is worse than no urgency
The stack must be presentable on a mobile sales page — if the value table is unreadable on a phone, it fails
Specificity gate: Every claim in the copy must include a number, name, or timeframe — no "get results" or "improve your business"
Mechanism quantification: When referencing the mechanism, include at least one specific data point (number, timeframe, study reference)
Audience journey: The copy must reference where the reader IS (what they've tried, what's failing) — not just who they are demographically
Proof diversity: Use at least 2 different proof types (testimonial, statistical, authority, case study) — do not rely on a single proof mode
Objection handling: The copy must address at least 2 likely objections with concrete responses (ROI math, proof of similar result, risk reversal)
/bonus-stack for deeper bonus design with fulfillment cost analysis/guarantee-writer for extended guarantee copy variations/lander-copy to write the sales page that presents this offer stack/hook-battery for headlines that lead into the offer reveal/mechanism-ideation to ensure bonuses reinforce the core mechanism/rmbc-copy-auditGenerated using RMBC framework by Stefan Georgi. Learn more: copyaccelerator.com/join
npx claudepluginhub coleschaffer/copywritingskills-rmbcDesigns offers for services, courses, coaching, and high-ticket B2B with value framing, bonus stacking, guarantees, scarcity, and payment structure.
Design bonus stacks that increase perceived value without increasing fulfillment cost — 3-5 bonuses with name, description, perceived value, actual cost, and core offer complement rationale using RMBC principles.
Create an irresistible offer using Hormozi's 5-step Grand Slam Offer framework