Salesforce add ons in 2026. What they cost and how to keep them tied to real use.

Salesforce add ons bill on top of the edition and, in a mature org, grow into the largest part of the contract. Inventory them, price each one to proven use and negotiate them together at renewal.

The base edition is the part of Salesforce that buyers study hardest, and it is rarely where the money goes. In a mature org the per user seat is a fraction of the invoice. The growth sits in the add ons, which look small on their own order forms and together become the majority of the spend.

What add ons does Salesforce sell, and how does each one bill?

Salesforce sells its add ons in three broad families: data and AI, platform and trust, and cloud specific extras. Each family bills on a different unit, which is why one headline discount rate never tells you what the whole contract costs.

Data and AI add ons

Data Cloud and Agentforce are the fastest growing lines in most Salesforce contracts. Both bill on consumption, so usage sets the price and headcount does not. Salesforce now markets Data Cloud as Data 360, and both products can be bought with Flex Credits.

• Data Cloud (Data 360): billed on credits that are consumed as the platform processes, unifies, segments and activates data. Flex Credits list at $500 per 100,000. Salesforce now lists batch ingestion as free, while streaming and real time pipelines draw credits. See Data Cloud.
• Agentforce: billed per conversation for autonomous agents, at $2 per conversation at list. Salesforce also sells it on Flex Credits, as per user add ons at $125 per user per month for Sales and Service ($150 for the Industries versions), and inside Agentforce 1 Editions from $550 per user per month. See Agentforce.
• Einstein: AI features that either come with the edition or bill as a separate platform add on.

Platform and trust add ons

These add ons extend the platform and its controls. They appear on the Salesforce editions and pricing pages, and most of them price as a percentage of what you spend on other Salesforce products.

• Shield: event monitoring, field audit trail and platform encryption. The full suite lists at 30 percent of net spend. Bought one by one, Platform Encryption lists at 20 percent, Data Detect at 15 percent, and Event Monitoring and Field Audit Trail at 10 percent each. See platform pricing.
• Sandboxes: full and partial copies of production for testing, priced by type. A Full Copy lists at 30 percent of net spend, a Partial Copy at 20 percent and a Developer Pro at 5 percent. Developer sandboxes come with CRM licenses.
• Premier Success: a support tier priced at 30 percent of net license fees. Unlimited Edition and Agentforce 1 Editions already include it.

Cloud specific add ons

Each cloud carries its own extras. Service Cloud has Digital Engagement and Field Service. Sales Cloud has CPQ and Inbox, and Marketing Cloud sells engagement and message volume tiers.

CPQ needs a note of its own. Salesforce no longer sells CPQ to new customers and points them to Revenue Cloud Advanced instead. Existing customers can still renew CPQ and add users, and no end of life date has been announced, so treat any migration proposal as a separate commercial negotiation with its own price.

Why do Salesforce add ons end up costing more than the base edition?

Three forces push the add on bill up in 2026: consumption meters that grow with adoption, lines priced as a percentage of everything else you buy, and capacity bought for a peak that never recurs. None of the three shows up in a per user price comparison.

The consumption meter

Consumption add ons reopen the commercial conversation every year. Data Cloud credits and Agentforce conversations grow with adoption, so last year's commitment rarely fits next year's use. Salesforce sells Flex Credits as a prepurchase, as pay as you go or as a pre commit, and each option shifts the forecasting risk differently.

The percent of spend trap

Shield, paid sandboxes and Premier Success are all calculated on your net Salesforce spend. Every other line you add raises them too, an uplift that few buyers model when they approve a new cloud or a block of seats. Salesforce defines the Shield base as spend on other applicable products, so check which products your order form counts.

A worked example on a $2,000,000 base

Say you run Sales Cloud and Service Cloud on Enterprise Edition with $2,000,000 a year of net license spend. You add the full Shield suite, one Full Copy sandbox and Premier Success, plus a modest Data 360 and Agentforce commitment. The figures below use Salesforce list percentages before any discount, calculated on the license base only.

In the quoted column the add ons equal the license base, half of the $4,000,000 total. The right sized column saves $450,000 a year without touching a seat.

That saving assumes two Shield components meet your audit and encryption needs and a second Partial Copy fits your test cycle, so get your security and release teams to confirm both in writing. Enterprise Edition already includes one Partial Copy, so check first whether it covers the need.

What a $500,000 mid term order really costs

Now add $500,000 of Service Cloud seats. Unless the order form fixes the base, the three 30 percent lines in the quoted column each grow by $150,000 a year once they are repriced, which happens at renewal if not before. On those assumptions the $500,000 order really costs $950,000 a year, and that figure rarely appears on the approval request.

Capacity bought for a peak

Sandboxes and credits are usually sized for a project such as a data migration, a large release or an Agentforce pilot, and they stay on the contract after it ends.

A Full Copy can be refreshed every 29 days and a Partial Copy every 5 days. If your team refreshes a Full Copy once a quarter for a release, test whether a Partial Copy would cover the cycle at two thirds of the list price. Our sandbox strategy guide covers sizing by release cadence.

What have we seen in Salesforce add on reviews in 2024 and 2025?

Across roughly 35 to 45 Salesforce customers we benchmarked in 2024 and 2025, add ons made up 40 to 60 percent of total Salesforce spend, well above the base editions. The median share in our benchmark file of 42 customers was 55 percent. Three patterns came up again and again.

• Consumption overruns. Consumption add ons such as Data Cloud ran 20 to 40 percent over the first forecast within two quarters.
• Idle peak capacity. Shield and sandbox capacity was bought for a peak that arrived once and then sat idle.
• Inventory pays. Customers who inventoried their add ons before the renewal cut add on spend by 15 to 25 percent, with a median saving of 22 percent from the add on review.

Why we advise against buying capacity ahead of demand

The usual advice is to buy add on capacity ahead of demand so that teams are never blocked. We disagree. In roughly seven out of ten customers we benchmarked, prepurchased Data Cloud credits and sandbox capacity sat idle while the customer still paid for the peak.

The order form locks the spend whether or not anyone uses the capacity. Commit instead to a low baseline you can prove from current usage, attach an expansion option at a fixed rate, and grow on evidence. Capacity bought on a forecast shifts the risk to you, and the price does not fall to reflect it.

Price every add on to the use you can show today, and buy the right to grow at a fixed rate.

How do you check which Salesforce add ons you actually use?

Start with the contract, then compare it with what the org reports. Most of the gap between capacity and use shows up in the five places below, which your admin and procurement teams can pull without Salesforce's help.

• Order forms. Collect every order form in the current term, including mid term add on orders. List each add on, its unit, its quantity and its price.
• Company Information in Setup. This page lists user licenses, permission set licenses and feature licenses with the number assigned against the number purchased.
• Sandboxes in Setup. Compare the sandboxes you own with the ones in use, and note the last refresh date of each Full and Partial Copy.
• Digital Wallet. Salesforce's consumption view for Data 360, Agentforce and other credit products, with configurable alerts as usage approaches set thresholds.
• Shield settings. Check whether encryption policies, Event Monitoring log files and Field Audit Trail retention policies are switched on and feeding a real process.

Our guide to Salesforce shelfware covers unused licenses in more detail, and Salesforce hidden costs covers the storage, API and support charges that grow alongside the add ons.

How do you cut Salesforce add on spend at renewal?

Tie every add on to measured demand, and negotiate them together inside the main renewal. That work has four parts, set out below in the order we run them.

Inventory every add on before the renewal

List every add on, its meter, its capacity and its real use over the last four quarters. The gap between capacity and use is your negotiating position, and it is only credible when you bring the usage data yourself.

Cap and monitor consumption

• Cap: set a not to exceed rate on credit and conversation overage.
• Monitor: review usage every month so adoption does not outrun the budget.
• Bundle: negotiate add on volume inside the main renewal and avoid separate mid term orders.

For the credit model in detail, read our guides to Salesforce Data Cloud pricing and Agentforce pricing.

Right size Shield, sandboxes and Premier

Ask your security team which Shield components a regulator or auditor actually requires. Match sandbox types to how often you release and refresh. If you run Unlimited Edition, which already includes Premier and one Full sandbox, make sure no separate Premier or Full sandbox line has survived from an older order form.

Tie add ons to the renewal

Salesforce reports its data and AI momentum in its investor materials, which shows where its sales teams push hardest. Fold every add on into one renewal so the products Salesforce wants to grow sit on the same table as the lines you want to reduce.

What will the Salesforce account team say about add ons, and how should you reply?

• "Buy the credits now. The rate goes up if you add later." Ask for the same per credit rate on any additional purchase for the full term, written into the order form.
• "Shield is sold as a suite." Salesforce publishes component prices, with Event Monitoring and Field Audit Trail at 10 percent each. Ask for the components your requirement names.
• "Consumption cannot be capped." Flex Credits come in prepurchase, pay as you go and pre commit forms. Ask for the overage rate in writing and a monthly alert threshold.
• "Move to Unlimited and Premier is included." Unlimited does include Premier, one Full sandbox and five Developer Pro sandboxes. Price both routes on your own seat count, Enterprise plus the Premier and sandbox lines you need against the Unlimited uplift, and take the cheaper one.
• "This discount expires at quarter end." Salesforce's fiscal year ends on January 31. An add on that can wait for the renewal usually gets a better price there than on a deadline set by the quarter end calendar.

Contract wording to ask for

1. Price hold on add on unit rates. Credits, conversations and percentages stay fixed for the term, including additions, so growth does not reset the price.
2. A defined base for percent lines. Name the products that count toward net spend for Shield, sandboxes and Premier, and exclude consumption lines, so one purchase cannot inflate three others.
3. A not to exceed overage rate. Overage on credits and conversations bills at the committed rate or below.
4. An expansion option. A right to add capacity at a fixed rate during the term, so you can commit to a lower baseline.
5. Coterminous add on orders. Every add on ends on the main renewal date, so all of them can be renegotiated at once.

Our Salesforce Negotiation CIO guide sets these terms in the context of a full renewal, and the Salesforce Knowledge Hub collects the rest of our Salesforce library.

What to do next

1. Build the inventory. List every add on in the current term, with its meter and its purchased capacity.
2. Map capacity against use. Use the last four quarters of usage from Company Information, the sandbox list and Digital Wallet.
3. Flag the gaps. Mark every add on where capacity exceeds use by more than 20 percent.
4. Cap consumption. Set a not to exceed rate on credit and conversation overage.
5. Review monthly. Put all consumption add ons on a monthly usage review with named owners.
6. Scope by risk. Scope Shield and Premier Success to the risk and support requirements you can document, and drop anything sized by default.
7. Negotiate once. Fold every add on into one renewal conversation.
8. Get independent help. Engage independent Salesforce advisory before you sign.

Frequently asked questions