# SaaS Add-Ons Pricing: When to Bundle, When to Charge Separately > Strategic guide to SaaS add-ons pricing. When add-ons increase ARPU vs cannibalize tiers, real-world examples, and the bundling math that protects margin. - **Author**: Ayush Agarwal - **Published**: 2026-05-08 - **Category**: Pricing, SaaS, Billing - **URL**: https://dodopayments.com/blogs/saas-add-ons-pricing-strategy --- Add-ons are one of the most misused pricing levers in SaaS. Done well, they expand revenue per customer without breaking the simplicity of your core plans. Done poorly, they cannibalize tier upgrades, paralyze buyers with choice, and leak revenue across the floor. This guide is the strategic framework: when to use add-ons, when to bundle features into tiers, and the bundling math that determines whether each add-on adds margin or just adds complexity. ## What Add-Ons Are For An add-on is an optional feature, capability, or capacity unit that customers buy on top of a base plan. Examples: - Analytics module ($19/month) on top of a Core plan - 10,000 additional API calls ($49) on top of included usage - Priority support ($99/month) on top of any plan - Compliance certification packs ($299/month) on top of Enterprise Add-ons work because they let customers shape the product to their needs without forcing them into a higher base tier. > The right way to think about add-ons is as the pricing equivalent of conditional logic. Most customers don't need all your features. Add-ons let those who do pay for them, without bloating the base price for everyone else. > > - Ayush Agarwal, Co-founder & CPTO at Dodo Payments For broader pricing context, see our companion guides on [SaaS pricing strategy](https://dodopayments.com/blogs/saas-pricing-strategy-guide), [tiered pricing model guide](https://dodopayments.com/blogs/tiered-pricing-model-guide), and [SaaS pricing calculator](https://dodopayments.com/blogs/saas-pricing-calculator). ## When Add-Ons Make Sense ```mermaid flowchart TD A[Feature Decision] --> B{Customer Demand Pattern} B -->|Universal demand| C[Bundle in base tier] B -->|Common but not universal| D[Bundle in higher tier] B -->|Niche / variable| E[Add-on] B -->|Power users only| F[Enterprise tier feature] C --> G[Simple, broad value] D --> H[Drives tier upgrades] E --> I[Captures power-user willingness to pay] F --> J[Sales-led pricing] ``` Use add-ons when: 1. **Demand is highly variable.** 30 to 60 percent of customers want the feature. Below 30%, it's a niche feature for Enterprise. Above 60%, just bundle it into the base. 2. **The feature has clear cost-of-goods.** Compute add-ons (more API calls), human-supported add-ons (priority support), or third-party costs (advanced integrations) all map cleanly to add-on pricing. 3. **Customers self-segment.** Some customers want analytics; others don't care. Add-ons let each pay for what they value. 4. **Cross-sell opportunity exists.** Customers who upgrade through add-ons often have higher LTV than those who upgrade through tiers. ## When Add-Ons Don't Work Skip add-ons when: - **The feature is universally needed.** Bundle it into the base. Don't make customers think. - **The feature is "table stakes" in your category.** Charging separately for what competitors include feels predatory. - **You only have 3 add-ons total.** Add-on management has setup costs (UI, billing, marketing). 3 add-ons is too few to justify. - **You have more than 8 add-ons.** Choice paralysis kicks in. Customers either buy nothing or buy way more than they need and churn. - **The add-on cannibalizes a tier upgrade.** If your $99/month Pro tier includes feature X, do not also sell X as a $30 add-on to the $29 Starter tier. Customers do the math. ## The Add-On vs Tier Decision Framework A simple decision tree: | Feature Adoption | Recommendation | |---|---| | 80%+ of customers want it | Base tier feature | | 50-79% want it | Mid or higher tier feature | | 30-49% want it | Add-on | | 10-29% want it | Enterprise feature | | Under 10% want it | Custom Enterprise pricing or skip the feature | These are starting numbers. Tune based on your customer base. ## Common Add-On Patterns That Work ### Pattern 1: Capacity Add-Ons Sell more of something the customer already pays for in the base. Examples: - More users / seats - More API calls / credits - More storage / bandwidth - More projects / workspaces Capacity add-ons are the simplest and most defensible. They scale linearly with customer success. ### Pattern 2: Capability Add-Ons Sell a feature module that some customers need and others don't. Examples: - Analytics dashboard - API access (to existing accounts that started UI-only) - Multi-currency or multi-language - Custom branding / white-label Capability add-ons have higher margin than capacity add-ons but require careful positioning to avoid cannibalizing tier upgrades. ### Pattern 3: Service Add-Ons Sell human-supported services on top of the SaaS. Examples: - Priority support - Onboarding services - Dedicated CSM - Custom training sessions Service add-ons are often the highest-revenue per customer but lowest gross margin. Use sparingly to avoid drifting into a services business. ### Pattern 4: Compliance Add-Ons Sell compliance certifications or features for regulated industries. Examples: - HIPAA compliance pack - SOC2 compliance pack - GDPR data residency options - ISO 27001 features Compliance add-ons are typically high-margin and customer-sticky. Most appropriate for SaaS targeting enterprise or regulated verticals. ## How to Price Add-Ons The pricing question for add-ons differs from base-tier pricing. Three rules: ### Rule 1: Anchor to Customer Value, Not Cost Add-on pricing is value-based, not cost-based. A compliance pack that lets a customer close a $50K enterprise deal can charge $99/month easily. The pack costs you almost nothing. The customer cares about the deal, not your cost. ### Rule 2: Price Add-Ons at 20-50% of Base Tier Add-ons should feel like meaningful but not dominant additions to the base subscription. A $99/month base tier should have add-ons in the $19 to $49 range. A $499/month base tier should have add-ons in the $99 to $249 range. If an add-on is more than 50% of base price, customers think it should be in a higher tier. If under 20%, customers don't perceive enough value. ### Rule 3: Test Add-On Pricing Aggressively Unlike base tiers (where pricing changes are disruptive), add-on prices can be tested without affecting the existing customer base. Run A/B tests on price points for new signups. Iterate based on attach rate and revenue impact. For more on pricing experimentation, see our companion guides on [pricing page conversion optimization](https://dodopayments.com/blogs/pricing-page-conversion-optimization), [pricing psychology](https://dodopayments.com/blogs/pricing-psychology), and [psychological pricing](https://dodopayments.com/blogs/psychological-pricing). ## Implementation: Add-Ons in the Billing Stack Add-ons add complexity to your billing logic. The key implementation patterns: ### Independent Billing Lines Each add-on should appear as its own line on the invoice. Bundling add-ons into the base subscription line confuses customers and breaks revenue accounting. ### Independent Proration If a customer adds an add-on mid-cycle, prorate the add-on charge to the cycle anchor. Same for add-on removal. Each add-on should prorate independently of the base subscription. For more on this, see the [subscription management documentation](https://docs.dodopayments.com/features/subscription-management). ### Independent Tax Each add-on may have a different tax treatment in some jurisdictions. Service add-ons (priority support) may be taxed differently from feature add-ons (analytics). Use a Merchant of Record or proper tax automation. ### Webhooks for Add-On Lifecycle Subscribe to add-on attached, modified, and removed events so you can trigger feature gating in your product. ## Common Add-On Mistakes Patterns that consistently destroy add-on programs: - **Too many add-ons.** Choice paralysis. Stop at 4 to 6 active add-ons. - **Add-on cannibalizing tier upgrade.** A $30 add-on that delivers what the next tier includes for $50 trains customers to never upgrade. - **Pricing add-ons cheap.** Customers undervalue cheap add-ons. $9/month feels like a freebie that customers ignore. - **Bundling add-ons into base over time.** "Including more in the base plan" sounds like generous customer success but slowly erodes upgrade revenue. - **No usage analytics on add-ons.** Without knowing which customers use which add-ons, you cannot optimize the program. - **Mandatory add-ons.** "Required to use the product" should be in the base, not an add-on. > The biggest add-on mistake is treating them as a pricing afterthought. Add-ons should be designed with the same rigor as your base tier pricing. They drive 20 to 40 percent of revenue in mature SaaS companies. That is too much to wing. > > - Rishabh Goel, Co-founder & CEO at Dodo Payments ## Real-World Add-On Examples | Company | Add-On Strategy | Notes | |---|---|---| | Slack | Per-seat pricing only, no add-ons | Simple but leaves money on table | | Notion | AI add-on at $10/seat | High attach, clear value, scales with usage | | Zoom | Webinar, Phone, Rooms add-ons | Each unlocks a separate use case | | HubSpot | Hub-based modular add-ons | Heavy add-on stacking, Sales/Marketing/Service Hubs | | Salesforce | Cloud-specific add-ons | Most extensive add-on catalog in SaaS | The pattern: simpler products keep fewer add-ons; complex enterprise products have many. Match your add-on count to your customer's complexity tolerance. ## How Dodo Payments Handles Add-Ons Dodo Payments supports add-ons natively in the subscription engine: - Native add-on attachment to subscription products - Independent billing line items per add-on - Proration on add-on attach, modify, and remove (all three modes supported) - Per-add-on tax calculation across 220+ countries - Webhook events for add-on lifecycle changes - Customer portal that surfaces add-on options to customers - Itemized invoices showing each add-on as its own line - Full Merchant of Record coverage so global tax stays accurate - Transparent pricing at 4% plus 40 cents per transaction with no monthly fees For implementation patterns, see the [add-ons feature documentation](https://docs.dodopayments.com/features/addons), [hybrid billing documentation](https://docs.dodopayments.com/features/hybrid-billing), and [subscription engine documentation](https://docs.dodopayments.com/features/subscription). ## FAQ ### What are SaaS add-ons? SaaS add-ons are optional features, capabilities, or capacity units that customers buy on top of a base subscription. Examples include extra users, additional API calls, premium features (analytics, advanced integrations), and service upgrades (priority support). Add-ons let customers shape the product to their needs without paying for features they do not use. ### When should I use add-ons vs higher tiers? Use add-ons when feature demand is variable (30 to 60 percent of customers want it). Use higher tiers when demand is broader (50 to 80 percent want it). Bundle into the base when demand is universal (80%+ want it). Reserve features for Enterprise tier when only 10 to 30 percent need them. ### How many add-ons should I offer? 4 to 6 active add-ons is a healthy range. More than 8 starts triggering choice paralysis where customers either buy nothing or over-purchase and churn. Fewer than 3 doesn't justify the operational complexity of managing add-on billing. ### How should I price SaaS add-ons? Price add-ons at 20 to 50 percent of the base tier price. A $99/month base should have $19 to $49 add-ons. Below 20% feels too cheap to be valuable. Above 50% feels like it should be a tier upgrade. Test add-on pricing aggressively since changes don't affect existing customers. ### Can a Merchant of Record handle add-ons? Yes. A Merchant of Record like Dodo Payments handles add-ons as line items within subscriptions, with independent proration, tax calculation, and webhook events per add-on. This is especially valuable for global SaaS where different add-on types may have different tax treatments per jurisdiction. ## The Takeaway Add-ons are a powerful pricing lever when used strategically and a damaging one when sprayed at every feature. The right approach: identify features with variable demand (30 to 60 percent of customers want them), price at 20 to 50 percent of base tier, keep the catalog under 8 active add-ons, and test pricing aggressively. If you want a billing platform that handles add-ons natively with independent proration, tax, and webhooks, [Dodo Payments](https://dodopayments.com) ships them as part of the subscription engine. See the [pricing page](https://dodopayments.com/pricing) and [add-ons feature documentation](https://docs.dodopayments.com/features/addons). --- - [More Pricing articles](https://dodopayments.com/blogs/category/pricing) - [All articles](https://dodopayments.com/blogs)