Skill: Bonus Stack Generator (Objection Killer)

Purpose

Design bonuses that increase perceived value and remove reasons to say no.

This skill:

• turns objections into assets
• increases value without heavy cost
• makes the offer feel complete
• strengthens the value stack

Goal: make the buyer think
“I’d be stupid not to take this”

When to Use

Activate this skill when:

• the offer feels weak or empty
• price resistance is high
• objections are blocking sales
• you want to increase perceived value
• you need differentiation
• conversion rates are low

Inputs

This skill works with:

• an OFFER.md
• a product or service
• a value stack
• known objections (or inferred ones)
• target audience

Core Outcome

The assistant produces:

• a list of high-value bonuses
• bonuses tied directly to objections
• clear bonus descriptions
• delivery formats
• perceived value for each bonus
• a structured bonus stack

Assistant Behavior

1. Identify key objections

List the main reasons someone would not buy:

Common objections:

• “I don’t have time”
• “This won’t work for me”
• “It’s too complicated”
• “I don’t have enough experience”
• “It’s too expensive”
• “I might fail”
• “I don’t trust this”

If not provided, infer based on:

• audience
• offer type
• price point

2. Map objections to solutions

For each objection, define:

Objection → What removes it

Example:

• “I don’t have time” → reduce effort or speed up process
• “I don’t know how” → provide guidance or templates
• “I might fail” → add support or guarantee

3. Turn solutions into bonuses

Convert each solution into a tangible asset.

Format:

• clear name
• specific outcome
• delivery format

Examples:

• “Done-For-You Setup Pack”
• “Step-by-Step Execution Checklist”
• “Plug-and-Play Templates”
• “Live Audit Session”
• “Private Support Channel”

4. Maximize perceived value

For each bonus:

• make it feel specific
• give it a clear result
• name it clearly
• avoid generic labels like “extra content”

Bad:

• “Bonus videos”

Good:

• “30-Minute Client Acquisition Script Library”

5. Choose delivery formats

Assign formats that feel valuable:

Options:

• templates
• checklists
• swipe files
• audits
• live calls
• async support
• community access
• dashboards
• tools

Prefer:

• low cost to deliver
• high perceived value

6. Stack bonuses strategically

Order matters.

Structure:

1. biggest objection first
2. highest perceived value early
3. logical progression
4. variety in format

7. Assign value to each bonus

Estimate perceived value:

• based on outcome
• based on time saved
• based on difficulty

Then:

• show total bonus value
• compare to price

8. Avoid overloading

Too many bonuses reduce clarity.

Rules:

• keep only high-impact bonuses
• remove low-value items
• focus on relevance

9. Align bonuses with core offer

Ensure:

• bonuses support the main outcome
• bonuses remove friction
• bonuses speed up results
• bonuses reduce effort

10. Suggest “fast action” bonuses (optional)

Add urgency if needed:

• limited-time bonuses
• early-buyer rewards
• deadline-based extras

Output Format

# BONUS_STACK.md

## 1. Core Offer Summary
- What the offer does
- Who it’s for

## 2. Key Objections
1. Objection
2. Objection
3. Objection

## 3. Objection → Bonus Mapping
- Objection → Bonus idea

## 4. Bonus Stack

### Bonus 1
- Name
- What it does
- Outcome
- Format
- Value

### Bonus 2
- Name
- What it does
- Outcome
- Format
- Value

### Bonus 3
- Name
- What it does
- Outcome
- Format
- Value

## 5. Total Bonus Value
- Sum of all bonuses

## 6. Stack Strategy
- Why this order
- What objections are removed

## 7. Optional Fast Action Bonuses
- Bonus
- Condition (time/limit)

## 8. Final Notes
- What was removed
- Why this stack works

⸻

Decision Rules

Add a bonus when: • it removes a clear objection • it increases speed or ease • it improves perceived value

Avoid a bonus when: • it adds confusion • it’s low value • it doesn’t support the outcome

Prioritize bonuses that: • save time • reduce effort • increase certainty • simplify execution

⸻

Before vs After Example

Before • core product only

After • core product • • templates • • checklist • • audit • • support

⸻

Style Guidelines • be specific • focus on outcomes • avoid generic names • keep it clean • prioritize value over quantity

⸻

Success Criteria

The skill works when: • objections are neutralized • value feels higher than price • the offer feels complete • the buyer has fewer doubts • conversions increase