Bundle everything into tiers
- Niche feature pushes customers to a pricier plan
- Most buyers pay for features they never use
- Tier pages grow long and confusing
Core plans plus targeted add-ons
- Plans cover what most customers need
- Add-ons sold to the segment that needs them
- Each add-on has its own price and value story
- Customers add or remove as needs change
Add-on pricing means selling specialised features as optional extras on top of your main plans. Advanced reporting, extra storage, a compliance pack, phone support or an AI assistant can each be an add-on. It fits SaaS products whose customers share a common core need but differ on a few specialised ones. It avoids pushing everyone into a more expensive tier just to get one feature.
Why it works
In a pure tier model, every new advanced feature has to land in some plan. Over time, the top tier fills with features only some customers need, and the price rises for everyone in it. Customers who need one advanced feature either overpay for a bundle or go without. Add-ons let you charge the customers who get extra value from a feature, while keeping the base price fair for everyone else.
Add-ons also create expansion revenue. A customer who starts on a core plan can add capabilities as their needs grow, without a disruptive plan change. Each add-on is a smaller decision than an upgrade to the next tier.
How to do it
- Find features with uneven demand. Look for features that a clear segment uses heavily and others ignore. Sales calls, support tickets and usage data will show where needs split.
- Check the cost to serve. Features with real running costs, such as storage, AI usage or human support, are strong add-on candidates because heavy users cost you more.
- Define each add-on clearly. Write one sentence on who it is for and what problem it solves. If you cannot, the feature may belong in the core plan.
- Choose a pricing unit. Price per account, per seat or per unit of usage, depending on how value grows. Keep the unit easy to predict.
- Decide plan eligibility. Make each add-on available on the plans where it makes sense, and include it in the top plan only if most buyers there need it.
- Show add-ons on the pricing page. List them below the plan table with a short description and price, so buyers are not surprised later.
- Offer them in context. Surface the add-on inside the product when a user reaches for the feature, with a clear trial or purchase path.
- Review the line-up yearly. Fold add-ons that nearly every customer buys into plans, and retire those that barely sell.
Example
A hypothetical customer support SaaS has three plans. Large customers in healthcare and finance ask for data residency and extended audit logs, which cost money to run. The team creates a compliance add-on with its own price, available on the top two plans. Smaller customers keep their current price, while regulated customers get exactly what they need with a clear invoice line. Sales now raises the compliance add-on during security reviews, and the team tracks how many top-tier accounts buy it.
Metrics to track
- Add-on attach rate. The share of eligible customers who buy each add-on. Very low rates suggest weak value or poor visibility.
- Expansion revenue from add-ons. Monthly recurring revenue added through add-ons on existing accounts.
- Plan conversion rate. Make sure the base plan conversion holds steady after you move features into add-ons.
- Add-on churn. How often customers remove an add-on. High removal suggests the value did not match expectations.
- Gross margin per add-on. Revenue minus delivery cost for add-ons with real running costs.
When it backfires
- Nickel-and-diming. Charging extra for features customers consider basic, such as exports or a second user, damages trust and invites comparisons with simpler competitors.
- Too many add-ons. A long menu makes buying feel like assembling a car and slows deals.
- Removing features from existing plans. Turning something customers already have into a paid add-on feels like a price rise in disguise. Grandfather current customers.
- Messy billing. Pro-rating, plan changes and add-on combinations can break your billing system. Test edge cases before launch.
- Hidden prices. If buyers discover add-on costs only after signing, expect angry renewals.
Growth Marketing Academy
Learn the framework behind this tactic
These lessons explain the math and the mental model, so you can adapt the tactic instead of copying it.
- Track 6 · Monetization Usage Pricing and Upsell Triggers Design usage-based and hybrid pricing, fire upsells from limits, seats, feature gates and PQL signals, and grow D2C order value with bundles and cross-sell.
- Track 6 · Monetization Pricing and the Value Metric Pick the unit you charge for, package it into good/better/best tiers, research willingness to pay and localise prices for India and other PPP markets.
Questions people ask
How many add-ons should we offer?
Start with one or two that solve a clear, specific need. Each add-on adds billing, support and documentation work, and a long list makes buying harder.
Should an add-on be available on every plan?
Not always. Some add-ons only make sense on higher plans, for example advanced security for teams that already use single sign-on. Decide based on who needs the feature and what it costs you to deliver.
How do we price an add-on?
Start from the value it creates for the segment that needs it, and check it against your cost to provide it. Talk to customers who have asked for the feature before you set a number.