ChatGPT
Claude
Google AI
Copilot
Platform & ArchitectureA sales operations lead was told Spiff would set the commission rate, and the room had already agreed. Salesforce had bought it, the team had joined Sales Cloud, and a demo was ready, so the rate felt like a feature of the close. The demo used a rate nobody in payroll recognised. On payday the figure in the tool and the figure in the pay file disagreed. Sellers opened disputes. The close date on the opportunity had been edited after the period locked, and the tool had treated the edit as a new credit. Nobody had written the plan rules down before the demo.
The agreement is the problem. It is easy to reach from a completion date, and it fits a sample percentage, which payroll does not pay.
The distinction that matters is who authors the plan. Salesforce completed the Spiff acquisition on 1 February 2024. The team joined Sales Cloud. Salesforce owns Spiff. Spiff is incentive compensation. It does not set your commission rate. It is not a CRM migration. You bring the plan rules you already pay people on. The product can calculate from those rules. It does not invent them. Joining Sales Cloud is not a rename of the opportunity, and it is not a new commission percentage. The completion changed the owner of the product. On the facts used here, it did not change what a seller is owed.
What follows are the questions that keep the demo out of the pay file. A good answer names the plan owner, the rule, the completion date, or the contract. A general answer runs a demo on a made-up rate and then tries to make payday match it.
The questions, and what a bad answer signals
| Question | Who has to answer it | What a bad answer usually means |
|---|---|---|
| 1. What the completion changed | The person who approved the demo rate | 1 February 2024 is being treated as permission to invent a percentage |
| 2. Who may change a rate | The plan owner, by name | The product is being treated as the author of the plan |
| 3. What date is the close, and what date is the plan year | Whoever is loading rules | The completion is being reused as the plan year |
| 4. Where the price is written | Procurement, from the contract, and payroll, from the plan | A deal rumour or a demo percentage is about to be paid |
| 5. Whether there is an end date | Whoever proposed throwing out the written plan | The old rules are being treated as finished because the logo changed |
1. What did 1 February 2024 complete?
The question is not whether the acquisition finished. It is whether anyone has added a rate the sentence does not contain.
The cited page states the completion in one sentence: "Salesforce completed its acquisition of Spiff on February 1, 2024." Read it as a date. Completion was 1 February 2024. The sentence does not describe your plan, your accelerators, or your payroll file. It does not say the product sets a rate. It does not say opportunities should be reloaded so a commission can calculate. It does not give a price or an end date. It also does not say why Salesforce acquired Spiff, or why Spiff sold. Write 1 February 2024 in the pack, and stop adding a rate the sentence does not contain.
The team joined Sales Cloud. That is where the parent record this guide follows places them. The parent record does not separate that placement into a second corporate event. Customers who already pay on a written plan keep that plan. If a timeline shows commissions being reset on 1 February 2024, ask for the sentence. The sentence is a completion. It names Spiff. It does not name a percentage.
What happened, for a customer, is a completed acquisition, a team placed with Sales Cloud, and a product that is still incentive compensation. What did not happen is a shutdown, a published price on the cited page, or a rate you can demo because the logo changed. You were not, on the facts used here, given a new commission scheme on that date.
A good answer sounds like the sales operations lead reading 1 February 2024 as the completion, saying the team joined Sales Cloud, and refusing to run the demo until the written plan is in the room.
A bad answer sounds like "Spiff sets the rate now, the team joined Sales Cloud, use the sample so the demo calculates." Payday disagrees with the pay file, and the disputes start from a percentage nobody signed.
Keep one note for a new operations lead. Owner: Salesforce. Completed: 1 February 2024. Team: joined Sales Cloud. What it is: incentive compensation. Sets your rate: no.
2. Who may change a rate?
Salesforce owns Spiff. You do not own the product because you have Sales Cloud. Your organisation owns the plan, the person who may change a rate, and the payroll file that actually pays. Those are different from the vendor's ownership of the product. A risk register that lets a demo rate become the plan will create a dispute you cannot explain to a seller.
Is Spiff owned by Salesforce? Yes. Did Salesforce buy Spiff? Yes. Who owns Spiff? Salesforce. Say the three answers the same way in the steering pack, the vendor form, and the support template. A form that still treats Spiff as an unrelated company, and ignores the completion, is stale. A form that treats Spiff as a field that sets commission on the opportunity is also wrong. Ownership of the company is not a compensation policy.
The acquisition did not make Salesforce the author of your plan. Finance, or whoever already signs the plan, still signs it. The team joining Sales Cloud tells you where the product sits in the vendor's line. It does not tell you the rate. If a supplier asks who owns the product, give them Salesforce, 1 February 2024, and the statement that the team joined Sales Cloud.
A good answer sounds like a named plan owner who has signed the rules you already pay, and who is the only person who may change a rate, with payroll holding the file that actually pays.
A bad answer sounds like "the product authors the plan, and a demo field on the opportunity is the rate." Sellers dispute a credit the opportunity edit created after the period locked.
A rule names who is paid, on which bookings, for which period, and what happens when a deal is clawed back. If the rule is only in a seller's memory, write it down before you configure anything. The tool will not discover it from the opportunity object. The amount on the opportunity is an input only when your plan says it is. A close date edited after lock is a dispute waiting to happen unless the plan says how late edits are treated. Write that sentence. Fair is the plan. The product calculates.
3. What date is the close, and what date is the plan year?
When did Salesforce acquire Spiff? Completion was 1 February 2024. That is the date the cited page states. Do not move the date to a fiscal year start because payroll would prefer it. The completion is not your plan year.
Put 1 February 2024 on the timeline as the completion. Put your plan year on a different line, and label it as yours. A search for a timeline that includes Spiff should return the completion, the owner, the Sales Cloud placement, and the statement that the product does not set your rate. It should not return a commission percentage. The cited page is the completion story. It is not a plan document and it is not a price sheet.
State the completion. Send a reader who wants the legal instrument to the contract. A contract signature and a completion date can both be true. The plan you pay on is a third document. Write all three names in the pack so a later reader does not treat the quoted sentence as a rate card.
A good answer sounds like 1 February 2024 on the corporate line, the plan year on its own line, and the plan document named as the rate card.
A bad answer sounds like the completion date reused as the day the old plan stopped, or a fiscal-year start substituted because it is easier to say. The pay file and the tool then cover different periods.
4. Where is the price written, and where is the rate written?
How much did Salesforce pay for Spiff? The page this guide cites does not publish a purchase price or a licence fee. How much was Spiff sold for? Same answer. A Salesforce Spiff acquisition price does not appear in the quoted sentence. The sentence is a completion on a date. It is not a figure, and it is not a commission rate.
The deal price, even if another document later shows you one, is not your licence and not your seller's pay. A historical figure would not tell you what you pay for the product this year, and it would not tell you what you owe a seller. Your licence is the contract. Your rate is the plan you already use. If either paper is silent, write that the silence is the finding. Procurement can ask the account team for the commercial paper. Payroll can ask the plan owner for the rule.
What you pay a partner to load the rules you already have belongs in a statement of work. That figure is not the 2024 purchase price. A quote that leads with a deal number, and then offers a sample rate so the demo calculates, has invented the thing the product must not invent.
A good answer sounds like procurement stating the fee from the contract, or the silence, and the plan owner stating the rate from the signed plan, with neither number taken from the completion sentence.
A bad answer sounds like a deal figure from a video or a forum, or the demo percentage, pasted into payroll. Do not change the pay file to match a demo.
5. Is there an end date, and what do you test against?
Was Spiff shut down or given a sunset date? No end date is stated here. A completion is not a shutdown. The team joining Sales Cloud is not a retirement. A keyword that pairs the product with sunset is a question. The answer is that no end date is stated. 1 February 2024 is the day the acquisition completed. It is not an expiry, and it is not the day your old plan stopped being the plan.
If a vendor tells you to throw out the written plan because Salesforce bought the tool, ask for the retirement notice. A date in a search box is not a notice. You still ask for Spiff by that name. A support template that has already replaced the plan with a demo rate will pay the wrong people. The plan is the finding. The demo is a picture.
Confirm your own contract term, your plan year, and the person who may change a rate. Those are your dates. They are not a product sunset. A forced recalculation from a sample rate, because someone said the old rules were finished, creates disputes and a payroll file you cannot defend. Leave the written plan in force until you have loaded those rules, tested them against a period you already paid, with the plan owner in the room. That test is a project. It is not a conclusion from 2024.
An opportunity load is a different job. Reloading accounts so a commission screen looks busy is not compensation design. If you implement the product, the first test is a period you have already paid. The result should match the pay file. If it does not, the rule is wrong or the data is wrong.
A good answer sounds like the plan owner in the room for a test against a period already paid, with the result matched to the pay file before anyone changes a rate.
A bad answer sounds like "the old rules finished on 1 February 2024, pay the demo." The disputes are then indefensible, and the pay file has been edited to match a picture.
A DVD, a Reddit thread, a YouTube clip, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown.
Where the decision goes next
The rules you already pay on, and the test against a paid period, live on the Spiff page. Read it before anyone runs a demo on an invented rate. The acquisition question ends when the pack can say the owner, the completion date, the missing price, and the missing end date.
