How do you price a SaaS add-on so it doesn't cannibalize the core product but still drives attach?

Question

Pulse RevOps · The Machine · Accepted Answer

## The Add-On Pricing Trap

Add-on cannibalization kills revenue. Set them **too cheap** and users abandon your core plan; **too aggressive** and you train buyers to negotiate. The fix: anchor add-ons to **customer value creation**, not cost-plus math.

## Operator's Framework

**1. Segment by Buyer Type**
- **High-volume users** (add-on as deal sweetener): anchor to **15–25% core LTV**
- **Power users** (add-on as revenue lever): anchor to **30–40% core LTV**
- **Tier-stackers** (upsell risk): tiered pricing, not unlimited add-ons

**2. Avoid These Traps**
- Pricing add-ons below **20% of base plan cost** → cannibalization risk
- Bundling add-ons into core (then raising base plan) → buyer backlash
- Treating add-ons like features (free bundling) → lost **$50K+/year** per 100 customers

**3. Pricing Models That Work**
| Model | When | Attach Rate | Revenue Impact |
|-------|------|------------|----------------|
| **Per-user tier** | Compliance, seats | 35–45% | **+18% ARR** |
| **Usage-based (capped)** | API, overage | 40–50% | **+22% ARR** |
| **Standalone feature** | Advanced reporting, integrations | 20–30% | **+12% ARR** |
| **Bundle discount** | 2+ add-ons purchased | 15–25% | **+8% ARR** |

**Research:** **Pavilion**, **Bridge Group**, and **OpenView** report **$200K+ annual delta** between flat-priced and tiered add-ons at **10–50M ARR scale**. **April Dunford** emphasizes packaging as positioning—misaligned add-on pricing signals product confusion. **ProfitWell** data shows **40% of SaaS companies underprice add-ons by **30–50%**.

```mermaid
graph TD
    A["New Add-On Ready"] --> B{"Customer Segment?"}
    B -->|"High Volume"| C["15-25% of Core LTV"]
    B -->|"Power User"| D["30-40% of Core LTV"]
    B -->|"Tier-Stacker"| E["Capped Usage or Seat"]
    C --> F{"Attach Rate Test"}
    D --> F
    E --> F
    F -->|"<30% Attach"| G["Price Too High"]
    F -->|"30-50% Attach"| H["✓ Optimal Zone"]
    F -->|">50% Attach"| I["Likely Cannibalization"]
    G --> J["Lower or Reposition"]
    I --> K["Raise or Bundle into Core"]
    H --> L["Ship & Monitor"]
```

**TAGS: pricing-strategy,add-on-revenue,cannibalization-risk,saas-metrics,attach-rate,tier-optimization,feature-packaging**

Model	When	Attach Rate	Revenue Impact
Per-user tier	Compliance, seats	35–45%	+18% ARR
Usage-based (capped)	API, overage	40–50%	+22% ARR
Standalone feature	Advanced reporting, integrations	20–30%	+12% ARR
Bundle discount	2+ add-ons purchased	15–25%	+8% ARR

How do you price a SaaS add-on so it doesn't cannibalize the core product but still drives attach?

The Add-On Pricing Trap

Operator's Framework

What does the score mean?