See what a scheme pays before you commit it.
Write an incentive scheme in plain terms, watch the payout curve as you edit, and try it on a real earner before anyone is told.
| Scheme | Status | Action |
|---|---|---|
| Field incentive, H2 2026 field-h2-2026, v2 | committed | Open |
| Coverage kicker coverage-kicker, v1 | draft | Open |
Secondary sales rolled up for the earner's territories, against the sum of that territory's targets for the period. Measured in money.
| From (%) | To (%) | Pays (% of the basis) |
|---|---|---|
| 0 | 60 | 0 |
| 60 | 80 | 50 |
| 80 | 100 | 80 |
| 100 | 120 | 100 |
| 120 | and above | 120 |
Drawn by the same code that will compute the payout, so what you see here is what an earner gets.
Runs the stored scheme against real data for one earner and one period, and shows the whole working. It changes nothing.
| What was measured | |
| Run through the payout curve | |
| Converted to money | |
| Rounded, once | whole dollar |
| Amount owed |
A scheme is a definition, not a payment.
You choose how often it pays, what is measured and the shape of the payout. Measures include territory sales against target, team sales for a manager, named SKUs, the territory's own SKU portfolio, doctors covered on cadence, tour plan adherence and growth on an earlier period.
The payout can be a target amount per earner, a value per point or a fixed pool shared across the team, on a linear, slab or step curve. For slabs you pick how a band is paid: the whole amount at the band's rate, or slice by slice like a tax bracket. The screen explains the difference in money, because the two modes pay different amounts.
The curve is drawn by the code that pays.
"What this pays" redraws as you edit the bands. It uses the same evaluator settlement uses, so the line on screen is what an earner will get.
"Try it on one person" runs the saved scheme against real data for one earner and one period and shows every step of the working. It changes nothing, so you can try as many versions as you like before anyone is told. A pool scheme, where each share depends on everyone else, is priced with the whole team.
Committed versions never change.
Schemes are versioned. Only a draft can be edited; committing it fixes that version so runs can cite it. To change a committed scheme you clone it, which creates the next version as a fresh draft. Runs that cited the old version still resolve to exactly what they cited.
Questions people ask.
Can we test a scheme on real numbers before launching it?
What is the difference between band and marginal slabs?
Can a scheme measure activity as well as sales?
What happens to a scheme once it is committed?
Works well with.
Incentive runs
A run prices every earner a scheme covers, flags anyone the plan cannot pay, and becomes the record a period is settled against.
Read moreSettlement and payroll
Freeze the numbers, record who approved them, publish to earners, then export the payroll file. Corrections are disclosed, never quietly edited.
Read moreSee it on your own team.
Tell us your fleet and we will size a proposal. Complete roll-out may take up to 4 months, counted from signed requirements and first payment.