Sales Compensation Aside—SPIFF Programs: How to Design B2B Sales Incentives That Drive Short-Term Behavior Without Wrecking Margin
By Rick Elmore ·
Every sales leader has done it. A quarter is closing soft, a new product isn't moving, and someone says "let's throw a spiff on it." Money gets spent, reps get loud for a week, and then nobody can tell you whether it actually worked. That's the difference between a spiff and a spiff program.
A sales spiff program is a short-term, targeted cash incentive layered on top of base compensation to move a specific behavior—like selling a particular product, closing before quarter-end, or booking a certain deal type. Unlike commission plans, spiffs are temporary, tactical, and designed to expire.
What is a sales spiff program, and how is it different from commission?
SPIFF originally stood for "Sales Performance Incentive Fund" (the spelling varies, and honestly nobody agrees). The acronym matters less than the function. A spiff is a deliberate, time-boxed reward for a narrow action you want to see more of, right now.
Base commission answers the question "how do I pay reps for doing their job over the long run?" A spiff answers a different question: "how do I get reps to change what they focus on this month?" Those are not the same tool, and treating them the same is where margin damage starts.
Here's the distinction that trips teams up:
| Dimension | Base commission plan | SPIFF program |
|---|---|---|
| Time horizon | Ongoing, annual | Days to a quarter, then it ends |
| Purpose | Reward total production | Redirect focus to one specific behavior |
| Budget source | Cost of sale baked into pricing | Discrete, capped fund |
| Payout logic | Percentage of revenue or margin | Flat bounty per qualifying action |
| Risk if misdesigned | Reps over-index on easy deals | Reps game the metric, margin erodes |
The key takeaway: a spiff is a scalpel, not a raise. When you fold spiff logic into base comp, you make it permanent and expensive. When you treat comp changes like a spiff, you create constant churn and reps who can't trust their own paychecks. Keep them separate.
When a spiff actually makes sense (and when it doesn't)
Spiffs work when there's a specific, addressable behavior gap that money can close in a short window. They fail when they're used to paper over a structural problem.
Good candidates for a spiff:
- Launching a new product reps aren't yet comfortable pitching. A spiff buys attention while enablement catches up.
- Clearing aging inventory or expiring licenses where the margin math still works even after the bounty.
- Pulling deals forward into a quarter that would otherwise close soft—useful for board optics or cash flow timing.
- Pushing a strategic attach, like a services add-on or annual prepay, that improves retention or unit economics.
- Rewarding a leading indicator during a rebuild—qualified meetings booked, multi-threaded opportunities created—when pipeline is the real constraint.
Bad reasons to run a spiff:
- Reps are underperforming across the board. That's a coaching, hiring, or territory problem. Cash won't fix a broken motion.
- Your product doesn't sell without a discount. If you constantly spiff the same thing, it isn't a spiff anymore—it's a pricing decision you're avoiding.
- Someone panicked at end of quarter. Reactive spiffs train reps to sandbag deals and wait for the bounty. You teach them the incentive by running it, whether you meant to or not.
That last point is the one operators underestimate. Reps are pattern-matchers. Run an end-of-quarter spiff two quarters in a row and you've just built a permanent incentive to hold deals until the spiff shows up. You didn't buy behavior. You mortgaged it.
How to design a spiff program that doesn't wreck margin
Every spiff has a break-even point where the cost of the incentive exceeds the value of the behavior it drove. Most teams never calculate it. Here's the design sequence I use.
1. Define one behavior, precisely
A spiff with two goals has zero goals. Pick the single action: "sell the new tier," "book annual-billed deals," "close by March 31." Write the qualifying criteria so tightly that there's no argument about who earns it. Ambiguity in a spiff always resolves in the rep's favor, and that's where your budget leaks.
2. Set the payout against margin, not revenue
The cardinal sin is spiffing a percentage of top-line revenue on a low-margin product. You can literally pay reps to lose you money. Anchor the bounty to the gross margin of the qualifying deal, and make sure the spiff plus base commission still leaves the deal profitable. If a $200 spiff turns a 30% margin deal into a 12% margin deal, you need to know that before you launch, not in the QBR.
3. Cap the total fund
A spiff without a ceiling is an open bar tab. Set a total budget—"$15,000 across the team this quarter"—and communicate it. This does two things: it protects margin no matter how the program performs, and it creates urgency because reps know the pool isn't infinite.
4. Use flat bounties, not percentages, where you can
Flat amounts per qualifying action ("$150 per new-tier deal closed") are easier to budget, easier to explain, and harder to game than percentage payouts. Percentages tempt reps to inflate deal size in ways that hurt you. A flat bounty rewards the behavior, not the size, which is usually what you actually want from a spiff.
5. Set a hard expiration and a clawback
The end date is the whole point. Write it down, and don't extend it—extensions destroy the credibility of every future spiff. Add a clawback clause for deals that cancel or refund inside a defined window, so reps can't earn a bounty on a deal that evaporates in 30 days.
How to budget and forecast a spiff before you launch it
Run the numbers before the announcement, not after. A defensible spiff budget answers four questions:
- What's the maximum payout? Multiply your best-case volume by the bounty. If every rep hits it, can you afford it? If the answer is no, lower the bounty or cap the fund.
- What's the incremental behavior worth? Estimate the deals that only happen because of the spiff—not the ones you'd have closed anyway. Paying a bounty on deals that were already coming is pure margin donation.
- What's the cannibalization risk? If you spiff Product A, do reps stop selling higher-margin Product B? Model the trade, at least directionally.
- What's the break-even? At what number of incremental deals does the program pay for itself? If you need 40 incremental deals and your realistic ceiling is 15, kill it now.
Teams consistently overestimate the incremental lift of a spiff because they credit the program with deals that would have closed regardless. Discount your own optimism. Assume a meaningful share of qualifying deals were already in motion, and budget for the honest incremental slice.
How to measure a spiff program and avoid perverse incentives
Most spiffs are measured on a single number: did we hit the target? That's not enough, because the target can be hit in ways that hurt you. You need to watch the metric you're paying for and the metrics you might be quietly damaging.
Track at minimum:
- Incremental lift vs. baseline. Compare qualifying deal volume to a comparable prior period. This is the number that tells you if the spiff did anything.
- Blended margin during the spiff window. If volume went up but average deal margin dropped, you may have just moved profit into reps' pockets.
- Displacement. Did revenue in non-spiffed products or segments dip? Reps have finite hours. A spiff redirects attention, and attention pulled toward one thing is attention pulled away from another.
- Post-spiff cliff. Watch the period right after expiration. A sharp drop tells you that you pulled demand forward rather than creating it. Sometimes that's fine. Sometimes it means you just borrowed from next quarter.
- Cancellation and refund rate on spiffed deals. Rushed deals close worse. If spiffed deals churn faster, the bounty bought you low-quality revenue.
The perverse incentives to guard against are predictable once you name them: reps discounting to force a deal into the spiff window, stuffing weak deals to hit a threshold, ignoring everything that isn't spiffed, and sandbagging deals to wait for the next bounty. Every one of these is a design failure, not a rep failure. Tight qualifying criteria, margin-anchored payouts, and clawbacks close most of the loopholes before they open.
Where automation makes spiffs actually work
The reason most spiff programs feel murky is operational, not strategic. Someone announces the spiff in Slack, tracking happens in a spreadsheet nobody updates, and payout is settled from memory at the end of the quarter. By then no one trusts the numbers, and the whole program leaves a bad taste.
A spiff is a data problem, and data problems are solvable. When your CRM tags qualifying deals automatically, calculates running payout against the capped fund in real time, and shows every rep their standing on a live leaderboard, the program does what it's supposed to do. Reps see the pool shrinking. Finance sees the margin impact as it happens. Leadership sees incremental lift versus baseline without building a report by hand.
This is the layer we build for clients—the RevOps plumbing that turns a spiff from a hopeful announcement into a measurable lever. The strategy is only half of it; the tracking is what makes it repeatable. If you want the mechanics done properly, that's what our packages are built to install.
Frequently asked questions
How often should we run a sales spiff program?
Sparingly, and never on a predictable schedule. The power of a spiff comes from being an exception. If reps can set their calendar by your spiffs, they'll start managing their pipeline around the bounty instead of the customer. Use them for genuine, specific pushes—a launch, a strategic attach, a real timing need—not as a recurring crutch.
Should spiffs be paid in cash or non-cash rewards?
Cash is the strongest short-term motivator and the easiest to model against margin, so it's the default for revenue-driving spiffs. Non-cash rewards—trips, gear, experiences—can create memorable competition and often stretch the budget further per dollar of perceived value. For pure behavior change on a deadline, cash wins. For culture and morale, non-cash has a place.
What's the biggest mistake teams make with spiffs?
Paying a percentage of revenue on a low-margin product without checking the math. It's entirely possible to design a spiff that pays reps to shrink your gross margin, and plenty of teams do exactly that without realizing it. Always anchor the payout to margin, and confirm the deal is still profitable after both base commission and the bounty come out.
How do I know if a spiff actually worked?
Compare qualifying deal volume against a matched baseline period, then check three things: whether blended margin held during the window, whether non-spiffed revenue dipped, and whether there was a demand cliff after it ended. If volume rose, margin held, other products didn't crater, and the lift didn't vanish the day it expired, the spiff earned its budget.
If your last spiff left you guessing whether it worked, the problem is the system underneath it, not the incentive itself. Book a Revenue Systems Audit and we'll show you how to design, track, and measure spiffs that move behavior without touching your margin.