SPIFF programme template with worked budget maths
A SPIFF is a short-term cash incentive paid on a specific behaviour, sitting on top of normal commission. A defensible SPIFF states one objective, one eligible behaviour, a budget derived as a fixed share of the incremental gross margin it is expected to produce, a payout structure that pays on output above each rep's own baseline, guardrails against discounting and pull-forward, and a measurement plan agreed before launch.
On this page
A SPIFF — Sales Performance Incentive Fund — is a short, targeted cash incentive layered on top of commission to move one behaviour for a fixed period. Most SPIFFs fail on budget derivation rather than design: the amount is chosen by feel, paid on total output rather than incremental output, and never reconciled afterwards. This template gives you the seven components in order, with the budget arithmetic worked in full on a ten-rep team, plus the guardrails that stop a SPIFF being paid for behaviour that would have happened anyway. Before you set the budget, be clear about which activity actually precedes wins on your team — the KPI selection guide covers that step.
The seven components
Fill these in order. Each one constrains the next, and skipping any of them is where SPIFFs go wrong.
| # | Component | The question it answers |
|---|---|---|
| 1 | Objective | What single number should be different at the end? |
| 2 | Eligible behaviour | Exactly what counts, and what does not? |
| 3 | Budget | What is this worth, derived from margin rather than guessed? |
| 4 | Payout structure | How does budget convert into individual payments? |
| 5 | Duration | How long, relative to the sales cycle? |
| 6 | Guardrails | How could a rep hit the number without creating the value? |
| 7 | Measurement | What gets compared to what, and who decides if it repeats? |
1. Objective
One objective. Not three. The written form is: increase [metric] from [baseline] to [target] between [start] and [end].
The worked example throughout this template: increase team closed-won deals from a baseline of 20 per month to 23 during a four-week SPIFF window. Average deal value is $6,000 at 70% gross margin. The team is ten account executives.
If you cannot state a baseline, you cannot state a target, and you should not run a SPIFF yet. Pull the trailing 90 days first and use the median month, not the mean — one exceptional month distorts a mean badly at this sample size.
2. Eligible behaviour
Write the inclusion rule and the exclusion list on the same page. Exclusions are where the disputes live.
- Counts: new-business closed-won deals, signed and countersigned inside the window, minimum contract value $3,000.
- Does not count: renewals, expansion on existing accounts, deals already at proposal stage on day one of the window, deals subsequently refunded or cancelled within 60 days.
The "already at proposal stage" exclusion is the one teams forget. Without it, the first week of any SPIFF is spent paying bonuses on deals that were closing regardless. If excluding them entirely feels harsh, count them at half weight — but decide before launch, in writing.
3. Budget, derived from incremental margin
This is the component that separates a SPIFF from a giveaway. The budget is a share of the margin the SPIFF is expected to create, not a share of total revenue and not a round number someone liked.
Step 1 — gross margin per unit. $6,000 average deal value × 70% gross margin = $4,200 gross margin per deal.
Step 2 — incremental units at target. Target 23 deals, baseline 20 → 3 incremental deals.
Step 3 — incremental margin at target. 3 × $4,200 = $12,600.
Step 4 — discount to the confidence case. Do not budget against your target; budget against the outcome you would actually bet on. If you would bet on +2 rather than +3: 2 × $4,200 = $8,400 incremental margin, confidence case.
Step 5 — apply a share. A working rule of thumb is 20–30% of confidence-case incremental margin. At 25%: $8,400 × 0.25 = $2,100 budget.
Step 6 — set a hard cap. Cap total payout at $2,500 regardless of outcome. Without a cap, an unusually good month costs you more than it earns, and you have no way to stop it mid-flight.
The rule of thumb in step 5 is a rule of thumb, not a finding. Lower it toward 15% when the behaviour is one reps should already be doing; raise it toward 35% when you are asking for genuinely new effort, such as selling into a segment nobody has touched. Below about 10% the SPIFF is too small to change behaviour and you have simply spent money on nothing.
4. Payout structure
Three structures, priced against the same $2,100 budget and the same target outcome. Assume that at target, five reps beat their personal baseline by a combined six deals, three fall short by a combined three, and two land exactly on baseline — net +3.
| Structure | Rule | Cost at target | Share of $12,600 incremental margin | Problem |
|---|---|---|---|---|
| Flat per unit | $100 on every closed deal | 23 × $100 = $2,300 | 18% | $2,000 of the $2,300 buys output that was happening anyway — and it busts the $2,100 budget |
| Above-baseline | $250 per deal above the rep's own baseline | 6 × $250 = $1,500 | 12% | You pay on gross overperformance (6), not net (3); under-performers do not offset |
| Fixed pool | $2,000 split across all above-baseline deals | $2,000, fixed | 16% | Cost is predictable, but a rep cannot calculate their own payout in advance |
Recommended default: above-baseline, per unit. It is the only one of the three where the money tracks the thing you are buying. Every rep can compute their own payout, which is what makes a SPIFF motivating rather than decorative, and the cost scales with performance instead of with headcount.
Two amendments to the default:
- Per-rep cap of three above-baseline units ($750 maximum). One outlier rep otherwise absorbs half the budget, and the outlier was usually going to have a good month anyway.
- Personal baselines frozen before announcement. Baselines calculated after reps know a SPIFF exists can be sandbagged. Freeze the trailing-90-day figure and publish it with the rules.
At target, the recommended structure costs $1,500 against $12,600 of incremental margin — a net contribution of $11,100 before administration. Publish that arithmetic to your own finance team before launch, not after.
5. Duration
Match the duration to the metric, not the calendar.
| Metric type | Duration | Reason |
|---|---|---|
| Leading activity (meetings booked, discovery calls) | 5–10 working days | Feedback is same-day; longer windows produce mid-period drift |
| Pipeline stage movement (proposals sent) | 2–3 weeks | Enough time for a stage transition to register |
| Closed-won | One full sales cycle, minimum | Anything shorter measures your existing pipeline, not new effort |
The four-week window in the worked example assumes a sales cycle of roughly four weeks. If your cycle is 90 days, do not run a four-week closed-won SPIFF — you will pay bonuses on pipeline that was built before the SPIFF existed. Run the SPIFF on the leading activity instead. The contest formats guide covers how to pick the metric when the cycle is long.
6. Guardrails against distortion
For each guardrail: the distortion, and the mechanism that blocks it.
Discounting to close. A rep discounts 20% to pull a deal inside the window. At $6,000, that removes $1,200 of revenue — which at 70% margin is $840 of gross margin, more than triple the $250 payout. Mechanism: deals discounted beyond the standard approval threshold are ineligible, or count at half. Track average discount across the window against the prior period.
Pull-forward. The most expensive failure mode, because it looks like success. If the SPIFF month closes 23 and the following month closes 17 against a baseline of 20, the two-month total is 40 against an expected 40. You bought nothing and paid $1,500 for it. Mechanism: measure the four weeks after the window as a mandatory part of the programme, and make the repeat decision on the combined figure.
Quality decay. Reps chase small, easy deals to raise unit count. Mechanism: the $3,000 minimum contract value, plus a check on average deal size across the window.
Churn. A deal closed on a promise nobody can keep. Mechanism: clawback on refund or cancellation within 60 days, stated in the rules at launch and applied without exception the first time it happens.
Data padding. Where a SPIFF runs on activity rather than revenue, activity counts can be inflated directly. Mechanism: score the activity from CRM fields the rep does not control alone — a meeting with an external attendee and a duration, not a manually created task. Blueprint's gaming-risk audit scores every metric for exactly this and ships the guardrail with the weight, which is the part AI onboarding exists to do.
7. Measurement plan
Agree this before launch. A measurement plan written afterwards is a justification.
| Measure | Window compared | Source | Decision it drives |
|---|---|---|---|
| Closed-won units | SPIFF window vs trailing 90-day median month | CRM | Did the primary number move? |
| Above-baseline units per rep | SPIFF window vs frozen personal baseline | CRM | Total payout, and who to coach |
| Average discount | SPIFF window vs prior period | CRM | Was margin bought rather than earned? |
| Average deal size | SPIFF window vs prior period | CRM | Quality decay check |
| Units, following four weeks | Post-window vs baseline | CRM | Pull-forward check — the repeat decision |
| Refund/cancel rate at 60 days | Post-window cohort vs prior cohort | Billing | Clawback triggers |
Pull all six from the same CRM the scoring runs on — HubSpot, Pipedrive, Salesforce, Zoho, Close or Google Sheets — so the payout figure and the review figure cannot disagree.
Close the loop with a single number: incremental gross margin, minus total payout, minus the post-window shortfall if there was one. If that number is not comfortably positive, the SPIFF does not repeat in its current form regardless of how good the window looked.
When a SPIFF is the wrong instrument
A SPIFF buys a short burst on one behaviour. It does not build a habit, and running them back to back trains a team to wait for the next one before working hard. If the behaviour you want is ongoing rather than one-off — consistent activity levels, consistent pipeline hygiene — a persistent scoring model with visible standings is the cheaper instrument, because it costs the same whether it runs for a week or a year. Recurring competitions and continuous scoring sit at a flat monthly price per team, while every SPIFF cycle costs its budget again. Use SPIFFs for genuine one-offs: a product launch, a quarter-end gap, a segment you need tested.
More fill-in structures are in the template library.
FAQ
How much should a SPIFF budget be?
Derive it, do not guess it. Calculate gross margin per unit, multiply by the incremental units you would confidently bet on (not your stretch target), then spend 20–30% of that figure. On a $6,000 deal at 70% margin, two confident incremental deals give $8,400 of incremental gross margin, and 25% of that is a $2,100 budget. Always set a hard cap so an exceptional period cannot outrun the maths.
What is the difference between a SPIFF and a commission?
Commission is a standing percentage of everything a rep closes, built into the compensation plan and expected. A SPIFF is a temporary, additive payment attached to one specific behaviour for a fixed window — a product line, a segment, a stage of pipeline. Commission pays for the job; a SPIFF pays to redirect attention for a few weeks. Reps should be able to earn both on the same deal.
Should a SPIFF pay on every deal or only above baseline?
Above baseline, in almost every case. Paying flat on every closed deal spends most of the budget on output that was happening anyway — in the worked example above, $2,000 of a $2,300 flat payout buys baseline production. Paying per unit above each rep's own frozen baseline means the money tracks the behaviour change you are buying, and the cost scales with performance rather than headcount.
How do you stop a SPIFF being gamed?
Attach a guardrail to every eligible behaviour before launch. Make deals discounted past the approval threshold ineligible, set a minimum contract value, clawback on refunds inside 60 days, exclude deals already at proposal stage on day one, cap per-rep payouts, and score activity from CRM fields a rep cannot create unilaterally. Then measure average discount and average deal size across the window against the prior period.
How long should a SPIFF run?
Match the window to the metric. Leading activity such as meetings booked works in five to ten working days. Pipeline stage movement needs two to three weeks. Closed-won needs at least one full sales cycle, otherwise you are paying bonuses on pipeline that existed before the SPIFF started. Running a four-week closed-won SPIFF against a 90-day sales cycle is the most common version of this mistake.
How do you know whether a SPIFF actually worked?
Measure the four weeks after the window as well as the window itself. If the SPIFF month closes 23 against a baseline of 20 but the following month closes 17, the two-month total matches what you would have got anyway — the deals were pulled forward, not created. The honest verdict is incremental gross margin minus total payout minus any post-window shortfall.
In the product
A competition, sized from margin
Format, duration, rules and prize split derived from your own numbers, with the break-even lift shown so the spend is defensible.
Prize split
- 1st$563
- 2nd$275
- 3rd$163
- Most improved$250
Sized from margin
$1,250
- Incremental margin
- $5,002
- Break-even lift
- 2.5%
Guardrail: meetings score on held, not booked
Keep reading
Sales contest tracker template and standings layout
The fields a contest tracker needs, a daily standings layout, how to compute most-improved against a frozen personal baseline, and the post-contest review.
30-day sales gamification rollout plan template
A day-by-day rollout template — what to publish before launch, the first callout, the mid-point reset, the week-two dip protocol, payout and scoring review.
Contest announcement templates for Slack and Teams
Kickoff, mid-point and results copy for sales contests, in three tones, with the formatting differences between Slack and Microsoft Teams.