Stress-test a plan
Plans → Stress Test runs a plan against deals you have already closed and tells you what it would have paid.
It is the cheapest error-detection you get. A plan looks fine on the page; it looks different when you see it pay €40k on last quarter's actual deals.
Running one
- Go to Plans → Stress Test and pick the plan.
- Start the run. It executes in the background — results appear when it finishes.
- Read the findings.
What it reports
Each run lands on one of five results, stored on the plan version:
| Result | Meaning |
|---|---|
not_run | Never tested |
passed | Nothing flagged |
warnings_present | Worth a look, not necessarily wrong |
anomalies_present | Something looks genuinely off |
skipped | Could not run — usually not enough historical data |
Typical findings: an accelerator that everyone reaches (so it is your real base rate, not an accelerator), a threshold nobody clears (so the plan pays nothing and demotivates everyone), a cap that binds only on your best rep, total payout cost well above the OTE you designed for, or a rule paying full rate on renewals you meant to exclude.
Custom scenarios
Beyond the standard run you can define a scenario — a hypothetical shape of the quarter — and see what the plan does with it. Useful for the questions a historical run cannot answer: what happens if one rep closes a deal five times the usual size, or if the whole team lands at 130%.
Suppressing a finding
If a finding is a deliberate design choice rather than a mistake, dismiss that finding type permanently so it stops appearing on every future run.
Suppress sparingly. A suppressed anomaly is invisible from then on, including to whoever inherits this plan after you.
It never blocks you
The Stress Test is advisory by design. It will not stop you activating a plan, and a result
of anomalies_present is not a failure state — sometimes you know something the test does
not.
But activating a plan with unexamined anomalies is how a comp plan quietly costs more than the team it pays for. Read them first.