Spiff licence cost after the Salesforce acquisition

Salesforce's announcement of the close is brief: "Salesforce completed its acquisition of Spiff on February 1, 2024." What matters for a buyer is that the product that came out of it, now called Salesforce Spiff and described on Salesforce's site as Incentive Compensation Management, has a price list. That is unusual among the products Salesforce has acquired, and it makes this the easiest licence in the group to model. The services side of a Spiff project, meaning plan design, data feeds and testing, is a separate cost and is covered on the Spiff implementation cost page. Here we deal only with the seats.

#What the price list says

Salesforce's Spiff pricing page lists a single product at one price per user per month, billed annually, with a currency converter. These were the figures on 13 October 2026.

The page states the headline in its FAQ in one sentence: "Incentive Compensation Management can be purchased as an individual SPM add-on for $75 per user, per month." Beneath the price it lists feature groups, including the Commission Estimator, Spiff Designer, tracing and audit trails, real-time rep statements, a mobile app, dispute resolution, approval workflows, commission expensing and direct data syncs with automated payouts. Those groups describe what the one product does. They are not separate tiers with separate prices, so you should not expect to buy a cheaper version without, say, the estimator.

Two caveats appear in Salesforce's own footer. The page is provided for information and is subject to change, and a sales representative is the route to detailed pricing. Take the list price as the ceiling you negotiate down from, and as the number to hold a quote against, not as a promise.

#Turning a seat price into an annual figure

Because the unit is a seat, the arithmetic is simple, and it is worth doing before the first call so you recognise a good or bad quote when it arrives. The figures below are list prices multiplied by seat count, before any discount and before tax. They are an illustration, not an offer.

A team of 60 on the Australian price therefore starts from AUD 75,600 a year. If a quote lands far above that for the same seat count, ask what else is in it. It may include a bundle, a larger edition or the Sales Cloud licence itself. If it lands far below, check the term, the currency and whether the seat count is what you think it is.

#Who needs a seat

The pricing page prices per user and does not define the word. We could not find a Salesforce statement that says whether every person who only views a commission statement counts as a paid user, so treat this as the most important question to put to your account team in writing.

There are four groups to separate. Payees are the sellers whose commission is calculated. Managers see their team's numbers and approve exceptions. Finance users review calculations, audit logs and expensing reports. Plan administrators design and maintain plans. A sensible licence would charge for those who do work in the product, and would be generous about those who only read a statement. Whether Salesforce's contract works that way is exactly what you need to establish, along with how contractors, partner sellers and people on non-commission pay are counted.

Count the people honestly before the conversation. A commission plan often covers more people than the sales team: sales development, customer success, channel and overlay roles may all be paid on variable pay. Equally, people in the Salesforce org who are not paid on commission should not be paying for a seat.

#An add-on, but not only to Sales Cloud

Salesforce's FAQ is blunt that "No, Incentive Compensation Management is a paid add-on to Salesforce Sales Cloud." It is a separate product that you buy in addition to the Sales Cloud licence. The same FAQ adds that Incentive Compensation Management can be bought as an individual add-on at the list price, as part of the SPM Product Suite, or as part of Agentforce 1 Sales Edition. If you are on that edition, or considering it, check what is already included before you buy the add-on separately, since that is how organisations end up paying twice.

The FAQ also says that Spiff can be purchased without Sales Cloud and has many additional integrations. Those two statements sit together on the same page, and they pull in slightly different directions. Ask your account team which applies to you, and whether the other systems you integrate need their own licences. Spiff connects to CRM, ERP, HCM, payroll and other systems, and Salesforce's FAQ notes that sources without a built-in integration can be reached through MuleSoft licences, integration partners or AgentExchange apps. A payroll feed can add cost on the other side of the connector, so price the whole chain.

#Contract and renewal mechanics

The commercial facts that are published are thin and clear. Salesforce says that "Most Salesforce products use annual contracts, but Salesforce subscription terms vary." and that per-user products require an annual contract. It also says there are no trial licences for Spiff, so a proof of concept has to be negotiated as a pilot rather than taken as a free trial. On growth, the FAQ reads: "You can add products or upgrade at any time, but some products may need to scale together." The phrase about scaling together is worth a question. Ask whether adding seats requires a related product to be raised as well, and what the rule is.

Beyond that, your order form should answer several questions. How are seats added mid-term, at what price and with what co-termination? Is there a minimum seat count? Can seats be reduced at renewal, and by how much? How is the currency fixed, and what happens at renewal if the exchange rate has moved? What is the uplift at renewal?

Commission plans have their own calendar. Most run on a fiscal or calendar year with design work in the weeks before it starts. A subscription whose term starts in the middle of the plan year forces you to renew while you are trying to change the plan. Where you can, align the subscription term with the plan year, so the renewal decision falls at the same time as the plan design decision and not in the middle of a quarter.

#How to right-size the seat count

Start from the payroll or variable-pay list, not from the CRM user list. Mark each person as a payee, a manager, a finance user or an administrator, and note the start and end of their eligibility during the year. Then apply the rule you have agreed with Salesforce about who needs a seat.

Consider phasing. If you plan to migrate a plan at a time, a regional launch may justify buying seats for one region first, provided the price per seat holds when you add the rest. Get that price held in writing, since the page tells you only that you can add products or upgrade at any time.

Allow for churn and seasonality. A sales team with high turnover will see people join and leave within a year, so ask how leavers are handled and whether a seat can be reassigned. Build a small buffer rather than a large one, since a buffer is paid for every month.

Finally, reconcile the seat count against the plan documents. Each plan lists the roles it covers, and the sum of those roles, after removing duplicates, is the number you should be able to defend. If the finance team cannot reproduce your seat count from the plan documents and the payroll list, the number is not ready to take to Salesforce, and the first discount you are offered will be on a figure nobody has checked.

#Three seat scenarios

Consider a business with 60 sellers on a single commission plan, five sales managers and two finance users. If every one of the 67 people needs a seat, the list price is 67 times USD 900, which is USD 60,300 a year, or AUD 84,420 on the Australian price. If the contract only charges for the 60 payees and the administrators, the figure is closer to the first line of the earlier table. The difference between those two numbers is the value of the definition of a user, which is why the definition is worth a conversation with your account team.

Now consider a distributor with 250 field sellers, many of them part-time or on short contracts. Here the risk is churn. If seats are annual and cannot be reduced mid-term, a leaver is a stranded cost. Ask how seats are reassigned and whether a seat can move to a replacement. Ask also whether seasonal sellers can be covered by a smaller group of seats, since that depends on how Salesforce defines a user.

Finally consider a group planning to add overlay roles and customer success after the first year. The licence should be modelled with the second-year seat count in view, with a price held for additions. A first-year discount that disappears on the seats you add later is a poor deal, even when the year-one number looks good.

#Traps worth naming

The first trap is the seat count built from the CRM. A Salesforce user list includes people who will never earn commission, and buying seats for them is pure waste. The second is the bundle that looks like a saving. Agentforce 1 Sales Edition may include the product, and may not suit your other needs, so compare the whole package, not the line. The third is the missing proof of concept. With no trial licences, a team can sign an annual contract before testing its hardest plan, so build a test plan with your three most complicated rules and have it agreed before you sign. The fourth is the currency. A price in AUD fixed for a year is safer than one converted at invoice, so ask which applies.

#How to compare two offers

Another incentive compensation tool will price differently, usually per payee or per plan participant, with different inclusions. Put the offers on one page and compare the unit, the definition of the unit, the minimum commitment, what is in the base price, the cost of integrations, the implementation estimate, and the term. Include the cost of change as well. A tool that is cheaper per seat but needs a consultant for every plan change may cost more across three years than one with a higher price and an administrator-friendly designer.

Spiff's own selling point, as Salesforce describes it, is that administrators can build and change plans themselves. Test that claim in a pilot with one of your real plans, with accelerators and tiers, before you let it justify a higher price.

#Where the other questions sit

The services fee and the plan you already pay people on belong on the Spiff page. Who bought the company belongs on what happened to Spiff. How a calculation reads an opportunity, and the failure when the numbers do not match, belong on integrating Spiff with Salesforce. Whether to move a plan belongs on should I migrate from Spiff.