# Spiff implementation cost: Salesforce Spiff licences, connectors and services

Salesforce Spiff lists at US$75 or AU$105 per user per month, billed annually, with connectors and Premium Support on top. The implementation cost is set by your commission plans, not by the software.

**Published:** 2026-05-13
**Canonical:** https://synconai.com/spiff-salesforce-implementation-cost
**Author:** SynconAI Architecture Team

## In short

As at October 2026 Salesforce Spiff lists at US$75 per user per month, or AU$105, billed annually on an annual contract. Each additional connector to a non-Salesforce system adds US$250 (AU$350) a month, and Premium Support is priced as a share of net price. Implementation cost depends on how many commission plans you run, how complex they are, and the payroll and HR data you connect.

## Sources

- **Salesforce Signs Definitive Agreement to Acquire Spiff** (retrieved 2024-02-01)
  https://www.salesforce.com/news/stories/salesforce-signs-definitive-agreement-to-acquire-spiff/
  > Salesforce completed its acquisition of Spiff on February 1, 2024.
- **Salesforce Spiff Pricing** (retrieved 2026-10-11)
  https://www.salesforce.com/sales/incentive-compensation-management/pricing/
  > Incentive Compensation Management can be purchased as an individual SPM add-on for $75 per user, per month.
- **Salesforce Spiff Pricing** (retrieved 2026-10-11)
  https://www.salesforce.com/sales/incentive-compensation-management/pricing/
  > We do not currently offer trial licenses for Salesforce Spiff, but please reach out to us for more information on how Spiff can work for your organization.

## What to take away

- Salesforce Spiff lists at US$75 or AU$105 per user per month, billed annually, as a paid add-on to Sales Cloud.
- Each extra connector to a system outside Salesforce lists at US$250 or AU$350 a month, so your payroll and HR feeds belong in the licence budget.
- The implementation is mostly translating commission plan documents into rules, then proving them against a period you have already paid by hand.
- Commission plans change every year. Budget for the annual re-build, not only the first go-live.

## The guide

Commission software has an unusual property: every bug is paid in real money and noticed immediately by the people it affects. A rep who is short-paid will find the error before finance does. That changes how you should think about the implementation cost of Spiff. The licence is easy to price. The work is in turning plan documents written by humans into rules a machine will apply the same way every month, and in proving those rules against payouts you have already made.

Salesforce completed its acquisition of Spiff on 1 February 2024: "Salesforce completed its acquisition of Spiff on February 1, 2024." Spiff joined Sales Cloud and is now sold as Salesforce Spiff, the incentive compensation management product in Salesforce's Sales Performance Management range.

## What you pay Salesforce for Spiff

Spiff is one of the few acquired products with a public price. As at October 2026 the [Salesforce Spiff pricing page](https://www.salesforce.com/sales/incentive-compensation-management/pricing/) says: "Incentive Compensation Management can be purchased as an individual SPM add-on for $75 per user, per month." The page shows that price in several currencies, all billed annually, and notes that all per user products require an annual contract.

| Item | US price | Australian price | Billing basis |
|---|---|---|---|
| Salesforce Spiff | US$75 | AU$105 | Per user per month, billed annually |
| Additional connector | US$250 | AU$350 | Per connector per month, one-way connection to an external system other than Salesforce |
| Premium Support | Priced as a share of net price | Priced as a share of net price | 24 hours, Monday to Friday, by phone, email, tickets and live chat |

A few details on that page matter for budgeting. Spiff is a paid add-on to Sales Cloud, not a standard feature, so it sits on top of your existing Sales Cloud licences. It can also come as part of the SPM Product Suite or Agentforce 1 Sales Edition, so check whether you already own it before buying it separately. The connector line covers one-way connections to systems outside Salesforce, from a catalogue of more than 50, and Salesforce itself does not need one. And there is no free trial. The page is direct about it: "We do not currently offer trial licenses for Salesforce Spiff, but please reach out to us for more information on how Spiff can work for your organization."

The arithmetic at list price is simple. Forty users at AU$105 a month is AU$4,200 a month, or AU$50,400 a year. Add two connectors, say for your HR system and your payroll provider, at AU$350 each, and that adds AU$8,400 a year. Those are list figures before any discount, and before Premium Support, which scales with the net price you negotiate. The useful question is who counts as a user. Ask Salesforce whether every payee needs a licence, or only the people who build and administer plans, and get the answer in writing, because it is the biggest variable in the licence total.

## The plan document is the real scope

Spiff's own description, from the acquisition announcement, is a product that combines a low-code interface, the familiarity of a spreadsheet and a processing engine to automate commissions at scale. The spreadsheet comparison is apt. Most organisations buying Spiff are replacing a workbook that one or two people in finance or sales operations understand completely, and the implementation is the process of getting that knowledge out of their heads and into rules.

So the best predictor of implementation effort is not company size. It is the plan documents. Count them. For each plan, count the components: base commission rates, tiers and accelerators, quota attainment thresholds, SPIFs and one-off incentives, splits between reps, overlays for specialists and managers, clawbacks when a deal cancels, draws against future commission, and any special treatment of multi-year or renewal deals. Then count the exceptions people make by hand each month. A company with three plans and few exceptions is a small project. A company with fifteen plans, mid-year changes and a long tail of manual adjustments is a large one, even if both have the same number of reps.

Data is the other half of the scope. Spiff calculates from Salesforce records, usually Opportunities and their products, sometimes Orders, and often from data held elsewhere: bookings in an ERP, collections in a billing system, employee start dates and managers in an HR system. If close dates, amounts, product codes or owners are unreliable in Salesforce today, Spiff will calculate the wrong number reliably. Cleaning that data is part of the cost whether or not it appears on the quote.

## What a Spiff implementation is made of

| Work package | What it covers | Effort depends on |
|---|---|---|
| Plan discovery | Collecting plan documents, the current workbook, the exceptions process | Number of plans, how well they are written down |
| Rule design | Translating each plan into rates, tiers, accelerators, splits, clawbacks | Plan count and component count |
| Data sync | Opportunities, products, Orders and related objects from Salesforce | Data quality, custom objects, multi-currency |
| External connectors | HR system for people and managers, payroll or ERP for payouts and bookings | Number of systems, each one a licensed connector |
| Teams, quotas and effective dating | Hierarchies, territories, quota assignments, changes that take effect mid-period | Reorganisations, frequency of mid-year changes |
| Parallel run | Calculating at least one historical period and reconciling it with what was paid | Number of discrepancies, availability of finance staff |
| Statements, approvals and disputes | Rep statements, approval routes, the dispute and adjustment process | Approval layers, audit requirements |
| Commission expensing | Treatment of commission as a cost of obtaining a contract for accounting purposes | Whether finance already capitalises commissions |
| Training and launch | Admin training, rep communication, the first live pay cycle | Number of admins and payees, change appetite |

The parallel run is the package that matters most. Take a period you have already paid, calculate it in Spiff, and reconcile every payee to the cent. Each difference is either a configuration error, a data problem or an undocumented exception someone has been applying by hand. Finding them before go-live is cheap. Finding them after the first live statement goes out is expensive in a way no quote captures, because reps lose trust in the numbers and go back to their own spreadsheets.

Commission expensing deserves a mention because it is often forgotten. Under the accounting standards most Australian companies follow, the incremental cost of obtaining a contract, which usually includes sales commission, may need to be capitalised and spread over the life of the contract rather than expensed when paid. Spiff includes commission expensing features. Whether you use them, and how, is a decision for your finance team and auditors, and it changes the scope.

## A scoping example

Take a hypothetical software company with 60 payees across new business, account management and solution engineering, paid in Australian and New Zealand dollars. It runs four plans. New business reps earn a base rate with an accelerator above quota. Account managers earn on renewals and expansion, with a clawback if a customer cancels within the first year. Solution engineers earn an overlay on deals they support. Managers earn on their team's attainment.

The Salesforce data is mostly in good shape, but splits are tracked in a custom object that two admins built at different times, and renewals are flagged inconsistently. Employee start dates and managers live in the HR system, and payouts go to payroll as a monthly file.

That scope implies two connectors, one for HR and one for payroll, a clean-up of the split object and the renewal flag before any rule is built, four plans with perhaps a dozen components between them, multi-currency handling, a clawback trigger fed from contract cancellations, and a parallel run over at least one quarter so the accelerators and the clawback are actually exercised. None of it is exotic. All of it is specific to how this company pays people, which is why two quotes for "Spiff implementation" can differ so widely.

## What the workbook really costs

It is worth pricing the alternative honestly, because the business case for Spiff rests on it. A commission workbook has no licence fee. Its costs are the days each month that one or two skilled people spend building it, the disputes that follow when reps cannot see how a number was reached, the risk that sits with the one person who understands the formulas, and the errors that are found only when someone complains. Those costs are real but rarely written down.

If you want to make the case properly, measure them for a few months before you buy: hours spent calculating, number of disputes, number of corrections after payment. That baseline tells you whether the licence and the implementation pay for themselves, and it gives you a way to judge whether the project worked. It also shows a partner where the pain is, so the implementation can start with the plans that cause the most disputes rather than the easiest ones.

## What pushes the effort up or down

Effort rises with every kind of variation. Multiple currencies need conversion rules and a decision on which rate applies when. Splits and overlays multiply the number of credit records per deal. Retroactive changes, where a plan or quota is changed after the period has started, need effective dating that is configured and tested. Clawbacks need a clear trigger, such as a cancelled Order or an unpaid invoice, and a data feed that tells Spiff it happened. Every external system adds a connector, a licence line and a reconciliation.

Effort falls when plans are simple and written down, when Salesforce data is already trusted for forecasting, and when one person in finance or sales operations has the authority to answer "what does the plan mean here?" within a day. That last point is underrated. Implementation stalls most often while the build team waits for someone to interpret an ambiguous clause.

## Getting quotes you can compare

Give every partner the same pack: every current plan document, the workbook you calculate from today, a list of the exceptions applied in the last two or three periods, the systems that hold people and payout data, and your payee count. Without the workbook and the exception list, a partner can only guess.

Ask each quote to state the number of plans and components it assumes, how many historical periods the parallel run covers and who reconciles the differences, how many connectors it assumes and to which systems, and whether rep communication and the first live pay cycle are included. Ask what happens if the parallel run reveals more exceptions than expected. A fixed-price quote with no allowance for discoveries tends to become a change request in week six.

On the licence side, ask Salesforce to confirm the user definition, whether you already hold Spiff through the SPM Product Suite or an Agentforce 1 Sales Edition agreement, the connector count, and whether Premium Support is included or optional.

## Costs that sit outside the first quote

1. **Connectors.** Each external system is a monthly licence line. Count HR, payroll, ERP and billing separately before you sign.
2. **Premium Support.** It is priced as a share of net price, so it grows with your licence total.
3. **Finance time for the parallel run.** The people who know the current numbers will spend real time reconciling them.
4. **Sales Cloud data clean-up.** Fixing close dates, owners and product codes is often the hidden half of the project.
5. **The annual plan change.** Most companies change commission plans each financial year. Each change is a configuration and test cycle. Budget for it every year, either in-house or with a partner.
6. **Licence overlap.** If you are replacing another commission tool, you may run both for at least one period. Plan the notice period around that.
7. **Admin capacity.** Someone must own plan changes, adjustments and disputes after go-live. Spiff makes that job easier, but it does not remove it.
8. **Rep communication.** Reps need to understand the new statements before the first live payout. A short walkthrough per team, and a clear way to raise a dispute, costs little and prevents a wave of questions in the first week.

## Where to go next

For the product picture, read [Salesforce Spiff and Sales Performance Management](/spiff-sales-performance-management) and [what happened to Spiff](/what-happened-to-spiff). The licence detail is in [Spiff licence cost](/spiff-salesforce-licence-cost). The data connections are covered in [integrating Spiff with Salesforce](/integrating-spiff-with-salesforce), and if you are weighing a move to or from Spiff, [should I migrate from Spiff](/should-i-migrate-from-spiff) sets out the trade-offs. When you are ready to compare partners, [hiring a Spiff Salesforce partner](/hire-spiff-salesforce-partner) lists the questions to ask. Spiff calculates from your Sales Cloud data, so if that data needs work first, our [Sales Cloud](/salesforce-sales-cloud-consulting) team is the place to start.

In short: the licence is published and easy to model. Count your plans, your exceptions and your connectors, insist on a parallel run, and budget for next year's plan change before this year's go-live.

## Questions

### How much does Salesforce Spiff cost?

As at October 2026 Salesforce lists Spiff at US$75 per user per month, or AU$105, billed annually on an annual contract. Additional connectors to non-Salesforce systems list at US$250 or AU$350 per connector per month. Premium Support is priced as a share of net price. Check whether you already own Spiff through the SPM Product Suite or Agentforce 1 Sales Edition.

### Can we trial Spiff before buying?

Not through a trial licence. Salesforce's pricing page says it does not currently offer trial licences for Spiff and invites you to contact them instead. Ask for a demonstration using one of your own plans, simplified, so you can see how its rules would be configured before you commit to an annual contract.

### Do we need a connector for Salesforce data?

No. The connector line on the pricing page covers one-way connections to external systems other than Salesforce. You will need connectors for systems such as HR, payroll, ERP or billing if Spiff must read people, bookings or payment data from them. Count those systems early, because each one is a monthly licence line.

### How long should the parallel run be?

At least one full pay period, and longer if your plans include quarterly accelerators or annual true-ups that a single month would not exercise. The goal is to reconcile every payee to the amount actually paid and explain every difference. Stop when the remaining differences are understood and signed off, not when the calendar says so.

### What costs come back every year?

The licence and connectors, Premium Support if you buy it, and the annual commission plan change. New plans, new tiers or a reorganisation each need configuration and testing before the first period of the new year. Budget for that cycle every year, whether your own admins do it or a partner does.

---

SynconAI is a Salesforce Select Partner and an OpenAI Select Partner, delivering architect-led Salesforce and AI programmes across the United States and Australia. Related service: Sales Cloud (https://synconai.com/salesforce-sales-cloud-consulting).