Add-on: what it is and how to use it to expand SaaS revenue

By Tiago Costa · Updated on July 9, 2026

Illustration of add-ons: a base plan with extra modules clipped on top, such as seats and storage.

Definition

An add-on is a module, feature or capacity billed on top of a SaaS base plan, such as extra seats, storage or a standalone premium feature.

  • It grows ARPA without the customer changing plan.
  • It is expansion within the same product, a neighbor of cross-sell.
  • It makes pricing modular: the customer assembles the package.

What an add-on is

An add-on is any module, feature or capacity a customer buys on top of the base plan, paying an extra recurring amount for it. Extra seats, a larger storage block, an advanced report or a premium connector are classic examples: none of them replaces the plan the customer holds, they all stack on top of it.

The core idea is modular pricing. Instead of pushing the customer into a larger fixed bundle, the add-on lets them assemble their own configuration and pay only for what they actually use. Each active add-on raises the recurring value of that account and therefore ARPA, feeding expansion of the base without relying on new customers.

Add-on, upsell and cross-sell: where each fits

All three are ways to grow revenue inside the base, but they describe different moves. An upsell takes the customer to a bigger or more expensive version of what they already have, usually a higher plan. A cross-sell sells an adjacent product, often from another line or SKU. The add-on sits in the middle: it is an extra piece bought within the same product, without changing the base plan.

  • Upsell: same need, higher tier (from Pro to Business).
  • Cross-sell: a new need, an adjacent product.
  • Add-on: a modular increment on the current product (more seats, more space, a standalone feature).

In practice, the add-on tends to be the lightest gateway to expansion, because the customer extends what they already use without facing the bigger decision of switching plans.

Add-on infographic: base plan plus additional modules summing to a higher recurring value per account.
The add-on adds recurring value to the base plan and grows the account ARPA.

Types of add-on

Add-ons usually fall into a few families, and recognizing them helps you design a coherent catalog.

  • Capacity per unit: extra seats, users or licenses, billed by quantity.
  • Limits and storage: more space, more records, more API calls or processing volume.
  • Standalone premium features: a reporting module, single sign-on, advanced automations or a specific dashboard.
  • Service and support: priority SLA, dedicated onboarding or an account manager.

Some of these add-ons carry a fixed monthly price, others scale with usage. What they share is that all of them represent additional recurring revenue tied to the same contract as the base plan.

Add-on or plan upgrade?

Add-on and plan upgrade solve similar needs through different paths, and picking the right one changes the buying experience. The upgrade repackages everything into a higher tier: the customer gets a set of improvements at once and starts paying the price of the bigger plan. The add-on keeps the current plan intact and only adds the missing piece.

The rule of thumb is simple. When the need is specific and one-off (three more seats, a single feature), the add-on tends to carry less friction and convert better. When the customer has outgrown the plan on several fronts, an upgrade is usually cleaner than stacking ten add-ons. Good catalogs use both: the add-on captures incremental expansion in the short term and signals when it is worth proposing the plan jump.

Illustration of add-on types: seats per unit, storage, standalone premium features and service.

How add-ons grow MRR and ARPA

Every add-on activated is an expansion of revenue: it enters as an increment to the recurring value of that account and, added across the base, pushes ARPA up. Because it does not depend on winning a new customer, it is one of the most efficient ways to grow, since the acquisition cost was already paid on the initial sale.

This is the engine behind net revenue retention above 100%, when expansion of the base outweighs what is lost to churn and downgrades. The private SaaS survey by KeyBanc Capital Markets shows exactly companies with net retention above that mark, and a well-designed add-on catalog is one of the direct paths to get there.

How to price and package add-ons

A good add-on has its own price, transparent and proportional to the value it delivers, without cannibalizing the base plan or turning the pricing page into a maze. The recurring industry reference, argued by the likes of OpenView in its pricing research, is to use a clear value metric: charge for what grows alongside the customer success, such as active seats or processed volume.

  • Keep each add-on optional and easy to turn on and off, without renegotiating the whole contract.
  • Anchor the price to a value metric, not an arbitrary internal cost.
  • Avoid too many options: a few clear add-ons sell more than a confusing menu.
  • Track adoption and revenue per add-on to know which one deserves to become part of the plan.

Well calibrated, the add-on becomes a quiet mechanism of expansion: the customer grows, assembles the package at their own pace and revenue follows that growth without friction.

Frequently asked questions

It is a module, feature or capacity billed on top of the base plan, such as extra seats, more storage or a standalone premium feature. It stacks on the plan instead of replacing it.

An upsell moves the customer to a bigger or more expensive plan. An add-on adds a standalone piece within the same plan, without changing tier.

They are neighbors, but not the same. Cross-sell sells a product from another line; an add-on is a modular increment within the same product.

For specific, one-off needs the add-on usually carries less friction. When the customer has outgrown the plan on several fronts, an upgrade tends to be cleaner.

Yes. Each active add-on raises the recurring value of the account, so ARPA rises and the base expands without relying on new customers.

Extra seats, more storage, additional API calls, single sign-on, an advanced reporting module or support with a priority SLA.

Related concepts