# Sales incentive plan for a small team: write only what your CRM can prove

https://salesbond.app/blog/sales-incentive-plan-small-team/
Published: 2026-10-24 · Updated: 2026-10-24

A sales incentive plan for a small team is a short written agreement: what behavior or result is rewarded, how much, and the exact CRM field and date that decide whether a deal counts. If a condition cannot be read from a report in the CRM, either move it to a manager decision you write down in advance or drop it from the plan.

The usual definition is broader. Gapp Group calls a sales incentive plan “a structured reward system designed to encourage sales representatives to achieve specific performance targets” ( [Gapp Group](https://gappgroup.com/blog/how-to-create-sales-incentive-plan/)), and Everstage notes that a commission plan is usually one part of that broader plan ( [Everstage](https://www.everstage.com/sales-incentive/sales-incentive-plan-examples)). Both are written for teams with a compensation analyst. With three to ten reps, the person who designs the plan also pays it out, and the only arbiter at quarter end is a CRM report.

## A sales incentive plan is a promise you can check: five lines

We write incentive plans as five lines, and next to each one we note where in the CRM the answer lives.

1. Who is in: which reps, by CRM user, and from which date.
2. What is rewarded: one behavior or result, and the field that records it.
3. What counts: the stage, the date field that puts a deal inside the period, the amount field, and how shared deals are credited.
4. How much, and the ceiling.
5. When it ends, when the report is run, and the one person who rules on anything the CRM cannot answer.

Line three is where most plans fail. “Closed deals in Q4” sounds precise until a rep asks whether the deal she marked won on October 1, with a September close date, is in or out. You need that answer before anyone sells a thing.

Here is one filled in. It is an illustration, not a recommendation: a hypothetical team of five, one quarter, one behavior.

- Who is in: the five account executives who are CRM users on January 1. Later hires join the next plan.
- What is rewarded: won deals with a new customer, marked “New business” in a deal type field.
- What counts: stage Won, won date from January 1 to March 31 in the account’s time zone, the Amount field as first-year value without services, credited to the owner at the moment of Won.
- How much: one fixed bonus per qualifying deal, for no more than four deals each.
- When it ends: the sales manager runs the report on April 15; a deal cancelled before then does not count. Anything else, the sales manager decides and logs in a note on the deal.

![One-page Q1 incentive plan: five plan lines, each matched to the CRM field or report that proves it.](https://salesbond.app/wp-content/uploads/2026/10/sales-incentive-plan-small-team-2.png)

## Quarter bonus, product push or contest?

Most plans a small team runs on top of commission take one of a few shapes. A quarter bonus pays once a rep crosses a threshold. A product push pays per deal that includes the line you want moved. A contest pays the top of a ranking, which is fair only if everyone is ranked from the same report. A SPIFF is the short version of any of these, measured in weeks, and we cover it in [sales SPIFFs for a small team](https://salesbond.app/blog/sales-spiffs-small-team-pipedrive/). Accelerators raise the commission rate above a threshold, so they belong in the commission plan: see [commission structures for a small team](https://salesbond.app/blog/sales-commission-structures-small-team/).

The same goes for the “70/30 pay structure” people search for. It is the split between base salary and variable pay in on-target earnings, and Everstage notes that 50/50 is a common ratio in SaaS, with 60/40 and 70/30 also appearing ( [Everstage](https://www.everstage.com/sales-incentive/sales-incentive-plan-examples)). That is a compensation decision, made once a year. The incentive plan sits on top of it and expires with the quarter.

## Pick the one behavior the plan pays for

An incentive on top of commission should pay for a single thing you want more of this quarter. Reward new logos, and upsells, and shorter cycles all at once, and no rep can tell what you want.

Our test: can you name the field that changes when the behavior happens? New customers, that is a deal on a new organization or a “new business” deal type. A product push, that is a line item or a deal label. Faster closing, that is the gap between creation date and won date. If the behavior has no field, add the field now and start the plan next month.

Then look at what the field cannot see. A plan on new logos rewards a rep who splits one customer into three organizations. That does not make reps dishonest; it makes them good at reading teh rule, which is what you hired them for.

## Define “counts” before the quarter starts

Line three holds four definitions, one sentence each. The date is the won date the CRM records when the deal moves to Won, not the expected close date a rep types and moves around all quarter. The amount names a field and what is in it: first-year value or one-time fee, with or without services. The owner is whoever owned the deal when it was won, so reassigning a closed deal never moves a bonus. For splits, either the CRM records split credit before the deal is won, or shared deals go to the owner.

The mechanics behind each, from edited won dates to annual and monthly contracts in one report, are in [commission tracking from CRM data](https://salesbond.app/blog/sales-commission-tracking-crm-reconciliation/#edge-cases-that-change-a-payout-split-credit-won-date-edits-cancelled-orders-and-clawbacks) and [where commission plans break](https://salesbond.app/blog/sales-commission-structures-small-team/#where-plans-break-cliffs-splits-and-deals-that-slip-a-quarter).

## Caps, windows and what happens to deals that slip across the line

A cap is a ceiling on what one rep can earn from the plan in the period. On a small team we are in favor of one: it protects the budget the owner had in mind, and it stops a single outlier deal from turning a team contest into a one-horse race by week three. If you run a [leaderboard](https://salesbond.app/blog/sales-leaderboard-small-team-pipedrive/) alongside the plan, the cap keeps the other reps looking at it.

The edge of the window is where arguments start. Take a deal won on March 28 that the customer cancels on April 10. Was the bonus earned on the day it was won, or only if the deal survives a stated number of days? The plan should already say, along with which clock decides a deal won late on March 31 (we use the account’s time zone) and the date the report is run. Short windows for a campaign of a week or two are in [the SPIFF rule that fits on one line](https://salesbond.app/blog/sales-spiffs-small-team-pipedrive/#the-rule-fits-on-one-line).

![Quarter timeline with three deals around the Mar 31 end: one won in time, one signed Apr 3 and out, one at risk of cancellation.](https://salesbond.app/wp-content/uploads/2026/10/sales-incentive-plan-small-team-3.png)

The quota and the incentive plan are different documents. The quota is the annual expectation and moves slowly; how we set it is in [how to set sales quotas](https://salesbond.app/blog/how-to-set-sales-quotas/). The incentive plan is this quarter’s push, and its meant to expire. A plan that quietly renews becomes an entitlement, and an entitlement you later remove is a pay cut in the team’s eyes.

## What the CRM cannot prove, and who decides

The CRM can prove a stage, a timestamp, an amount and an owner. It cannot prove that the customer is a good one, that the discount was necessary, or that the deal will not come back as a refund in month four. Taking a bonus back later is a conversation nobody wants on a team of six, so we design around it.

Two moves. First anything about quality goes into the definition of “counts”, not into a judgment at the end. Don’t want to pay for deals past a certain discount? Put the discount field into line three and let the report exclude them. Second, whatever genuinely needs a human call gets one named person and one written rule: “The sales manager decides disputed splits and records the decision in a note on the deal before the report is run.” Reps accept a decision they can see coming. They do not accept a manager who overrules the report after reading it.

A disclosure, since this is where tools come up: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Its Sales Plan shows the target, current attainment, the forecast for the period and the gap between them. Who earned what stays in your plan and your CRM report.

## Review at quarter end: three questions

Run the report on the date the plan names and send it to the team before you send the money. Then write three answers on the back of the plan.

Did the behavior change, or only the timing? A heavy plan quarter followed by an empty month means deals moved across the line rather than appeared; the [pull-forward test](https://salesbond.app/blog/sales-spiffs-small-team-pipedrive/#did-it-work-or-did-the-window-just-borrow-from-the-next-two-weeks) shows how to check.

How many exceptions did the named person have to decide? Zero means the definitions were right. One or two is normal. More means line three was not specific enough, and the next plan should fix the definition rather than lean on the referee.

Would you run the same plan again, unchanged? Usually the honest answer is “the same behavior, with a tighter definition of what counts”. That is a good outcome: the disagreement was about a field and a date, which you can settle. Write that tighter line three now, while this quarter’s disputes are fresh.