Spiff lives or dies by your Salesforce data.
We fix that part first.
Now part of Salesforce, Spiff reads your CRM closely. That tight coupling is the appeal, and it means every gap in your opportunity data becomes a commission dispute.
Where Spiff gets hard.
Three things that decide whether a Spiff build stays maintainable.
Your CRM becomes the comp system
Ownership changes, split records, closed-won hygiene and custom fields all move straight into payout. Spiff will faithfully calculate from bad data.
Logic split across two systems
Some rules belong in Salesforce, some in Spiff. Deciding which lives where, and documenting it, is the difference between a maintainable setup and a guessing game.
Life after the acquisition
Being inside Salesforce changes roadmap, packaging and integration assumptions. Worth planning around rather than discovering mid-cycle.
The same Spiff project, two ways.
What usually separates a Spiff build that holds up from one that quietly becomes someone’s problem.
Without specialist support
Salesforce data problems become commission problems
Ownership changes and splits quietly corrupt payouts
Logic scattered between Salesforce and Spiff with no map
Closed-won hygiene assumed rather than verified
Nobody owns the boundary between the two systems
Every dispute starts with an argument about the CRM
With OnCentive on the build
CRM data audited and cleaned before Spiff goes live
Ownership, split and credit rules defined explicitly
A documented decision on what lives in Salesforce and what lives in Spiff
Opportunity hygiene checks that run every period
One team accountable across both systems
Disputes answered from the data, not from memory
Tell us what your Spiff has to do.
We will tell you what it takes.
First rollout, a migration on or off Spiff, or a new requirement on a system already paying people. We have done all three for more than ten years.
Start a conversation