evals/evals.json
{
"skill_name": "sales-comp-design",
"evals": [
{
"id": 1,
"prompt": "Halbrook, we sell warehouse routing software. 22 AEs, the plan is 40 base / 60 variable, $180K OTE, $900K quota each. Last year six reps finished above 150% and we overran the commission line by $740K. Our CFO wants to cap payouts at 150% of target variable and apply it to the deals already closed this year. Meanwhile my VP Sales wants to take the accelerator from 1.5x to 3x above 100% so we stop losing people to a competitor. Give me the new rate table for FY27.",
"expected_output": "A marginal rate table whose accelerator sits at or below the 1 / 0.6 bound, a windfall review clause instead of a cap, the retroactive cap refused and routed to counsel, the decelerator decided explicitly, and a high-attainment cost model required before publication.",
"files": [],
"expectations": [
"Rejects applying a retroactive cap to commissions on deals that have already closed.",
"States that capping payouts after the fact under a plan document that said uncapped has produced litigation and settlements.",
"Routes any cap language to legal counsel rather than resolving it inside the plan.",
"Rejects the proposed 3x accelerator.",
"Computes the accelerator bound explicitly as 1 divided by the 0.6 variable share, approximately 1.67x the base rate.",
"Recommends an accelerated rate at or below that bound.",
"Specifies the rate bands as marginal, with each rate applying only to the attainment falling inside its own band.",
"Warns against a cumulative rate table that reprices all prior attainment when a threshold is crossed.",
"Proposes a windfall review clause for outsized single deals in place of a payout cap.",
"States the windfall trigger as a share of annual quota.",
"Treats the decelerator as an explicit decision, either adopted with a reason or declined with a reason.",
"Requires modeling the plan's cost at a high-attainment scenario before the rate table is published."
]
},
{
"id": 2,
"prompt": "Vantera, B2B compliance SaaS, about $40K ACV. We're standing up a 9-person pipeline generation team, 4 inbound and 5 outbound. Draft their comp plan. What I had in mind: $75 per meeting booked, a $500 monthly bonus for anyone averaging 150 dials a day, and a SPIF every single month so there's always something to chase. Same plan for inbound and outbound so it's fair. OTE around $75K.",
"expected_output": "A plan paying on qualified opportunities rather than booked meetings, with the dial bonus removed, no more than three measures, separate mixes for inbound and outbound seats, and a bounded SPIF policy replacing the monthly cadence.",
"files": [],
"expectations": [
"Replaces pay-on-booked-meetings with qualified opportunities as the focus measure.",
"States that paying on booked meetings pays for spam and pollutes the account executive pipeline.",
"Rejects the daily-dial activity bonus as a paid measure in a direct-seller plan.",
"Caps the plan at no more than three paid measures.",
"Names one financial or output measure as the plan's focus.",
"Sets a different pay mix for the outbound seat than for the inbound seat.",
"Gives the outbound seat the higher variable share, on the grounds that the rep creates the opportunity.",
"Rejects running a SPIF every month.",
"States that a SPIF recurring on a predictable calendar stops being an incentive and becomes expected baseline pay.",
"Limits SPIFs to a small number per year, with windows measured in weeks and deliberate gaps between them.",
"Recommends varying SPIF timing and minimizing advance notice so reps cannot delay deals into a known window.",
"Anchors SPIF eligibility on close date."
]
},
{
"id": 3,
"prompt": "Kelburn Analytics. We have 6 CSMs and they own about $14M of ARR between them. Right now they're salaried with no variable at all. Leadership wants them on the same 50/50 split our AEs run, paid on one blended net revenue retention number for their book, plus a kicker whenever they help source a new logo. We've never tracked retention per CSM before, the data only exists at company level. Write the plan.",
"expected_output": "A base-heavy customer-success plan with GRR and NRR paid separately, a GRR floor gating expansion pay, no new-logo pay, book-of-business crediting, and a baseline-first rollout since no per-person history exists.",
"files": [],
"expectations": [
"Rejects a single blended retention number as the paid measure.",
"Splits gross revenue retention and net revenue retention into two separately paid metrics.",
"States that a single blended number lets one large expansion mask churn elsewhere in the same book.",
"Gates expansion pay behind a gross-revenue-retention floor.",
"Rejects the 50/50 pay mix for the customer-success seat.",
"Recommends a base-heavy mix for the retention seat, justified by that role's lower influence over the outcome.",
"Rejects paying the customer-success seat on new-logo bookings.",
"Recommends tracking the retention metrics per individual with no variable pay attached for a period before setting any target.",
"Sets first-cycle targets as an improvement over the observed baseline rather than an invented number.",
"Uses book-of-business crediting rather than per-deal credit for this seat.",
"Notes that MBOs are acceptable in this plan because the job genuinely includes non-output work.",
"Does not claim a back-test against real prior-cycle per-person retention data, since none exists yet."
]
},
{
"id": 4,
"prompt": "Ardentia. We're 7 months into FY26. We launched a second product line in March and it's not moving, AEs won't touch it because their plan pays the same on it as on the core product. I want to rewrite the AE plan effective Oct 1: add a fourth line for new-product ARR at 20% weight, and fund it by dropping the accelerator from 1.5x to 1.25x. 30 AEs. How should I roll this out?",
"expected_output": "A time-boxed SPIF recommended in place of the mid-cycle rewrite, the fourth measure and the accelerator cut both refused, the SPIF sized self-funding on outcome metrics, and the durable change deferred to the annual redesign.",
"files": [],
"expectations": [
"Recommends a time-boxed SPIF instead of rewriting the plan mid-cycle.",
"States that a mid-cycle change to pay opportunity is a governance exception requiring its own sign-off.",
"Names mid-year plan changes as a known demotivation and turnover cause.",
"Notes that a mid-cycle plan change requires re-signed commission agreements.",
"Rejects adding a fourth paid measure to the account executive plan.",
"Holds the plan to at most three paid measures.",
"Sizes the SPIF against the standing commissions budget so it is self-funding.",
"Specifies the SPIF metric as an outcome rather than an activity count.",
"Bounds the SPIF window to weeks rather than the remainder of the fiscal year.",
"Declines to lower the already-published accelerator rate mid-cycle.",
"Recommends folding the behavior into a standing measure at the annual redesign if it must persist beyond the SPIF."
]
},
{
"id": 5,
"prompt": "Founder here, Sablewood, workflow software at about $45K ACV. Just hired AEs #1 through #3 and they start in January. From what I've read AEs are 50/50, so $160K OTE means $80K base and $80K variable. I'm setting each of them at $1.1M in new ARR. For the commission rate I want to match Coreflow, our closest competitor, whose reps tell us they get 15% of ARR. Sanity check this for me before I send the offers?",
"expected_output": "The convention-copied mix and the borrowed 15% rate both rejected, the mix / quota:OTE / rate identity worked through on the stated figures, the quota question handed off, and a governance and signature floor set.",
"files": [],
"expectations": [
"Rejects setting the pay mix by copying a benchmark or a competitor's plan.",
"Derives the pay mix from the role's influence over the outcome in this company's motion.",
"States that pay mix, quota-to-OTE ratio, and commission rate form a single system.",
"States that fixing any two of those three determines the third.",
"Computes target variable pay as $80,000 from the $160,000 OTE at a 50/50 mix.",
"Computes the quota-to-OTE ratio as roughly 6.9x from the $1.1M quota and the $160,000 OTE.",
"Rejects the 15% commission rate as inconsistent with the stated OTE and quota.",
"Derives the implied commission rate at quota as roughly 7% of new ARR.",
"Flags the quota-to-OTE ratio as sitting above the common band.",
"Hands the quota question to the separate quota-setting exercise rather than resetting quota inside the comp plan.",
"Names who designs, who validates the cost, and who signs before the numbers are finalized.",
"Requires a written plan document signed by each rep, carrying published start and end dates matching the fiscal year."
]
},
{
"id": 6,
"prompt": "Merrilow Health Software. I'm writing our FY27 commission plan document. Reps: 12 in California, 6 in New York, 9 in Texas, 4 in London. Here's what I want the plan to say, please draft the language. One: if a customer churns inside 12 months we recover 100% of the commission, at our discretion. Two: no commissions paid on anything that closes after a rep's last day, no exceptions. Three: our inside sales reps are commissioned so they're overtime-exempt. Four: job postings list base salary only, since OTE varies so much. Can you write these clauses?",
"expected_output": "Every one of the four items flagged as a counsel gate rather than drafted as settled language, with the earned-wage principle, sole-discretion clawback risk, procuring cause, the inside-sales exemption gap, full-OTE posting ranges, and the UK jurisdiction each raised.",
"files": [],
"expectations": [
"Flags each of the four items to legal counsel rather than resolving it in the plan.",
"Notes that several US states mandate a written commission agreement signed by the employee.",
"Names California and New York among those jurisdictions.",
"States that an earned commission is generally treated as a wage.",
"Warns against clawback language exercised at the company's sole discretion.",
"Requires the plan to define the earning event precisely for any clawback to be defensible.",
"Narrows the clawback to a stated cause and a stated window rather than blanket recovery.",
"Raises the procuring-cause doctrine for commissions on deals closing after a rep departs.",
"States that plan silence on post-termination commissions defaults in the rep's favor.",
"Challenges the assumption that the inside sales reps are exempt from overtime.",
"Notes that the outside-sales exemption does not cover phone or internet selling.",
"Recommends the job postings quote a good-faith full-OTE range rather than base salary alone.",
"Treats the London-based reps as a separate jurisdictional question rather than assuming the US analysis carries over."
]
},
{
"id": 7,
"prompt": "Fluxgate. We're switching from per-seat subscriptions to consumption pricing on Jan 1. Our 11 AEs are paid today on new ARR at signature. Under the new model a customer signs a commitment and then the actual revenue lands over anywhere from 6 to 18 months depending on how fast they ramp. What's the standard way companies pay AEs on this? Just tell me what everyone does so I can copy it.",
"expected_output": "An explicit statement that no settled practice exists, several competing designs presented side by side with their trade-offs and the annuity risk named, none declared the standard, plus the three-measure cap, a back-test requirement, and the quota question handed off.",
"files": [],
"expectations": [
"States that the booking event stops being a cleanly payable measure once revenue lands over months.",
"States that no settled industry best practice exists for usage-based sales comp.",
"Presents more than one competing design rather than naming a single standard.",
"Names consumption run-rate as one candidate paid measure.",
"Names a hybrid bookings-plus-overage crediting design as another candidate.",
"Names a design weighting bookings against consumption by account maturity or territory profile.",
"Raises the risk that consumption-tied comp becomes an annuity that stops tracking new selling effort.",
"Does not declare any one of the candidate designs the industry standard.",
"Holds the plan to at most three paid measures.",
"Requires a back-test against actual prior-cycle per-rep performance before rollout.",
"Routes the re-derivation of the quota itself to the separate quota-setting exercise."
]
},
{
"id": 8,
"prompt": "Tarnbridge. 18 AEs, 5 solution engineers, 3 first-line managers. Two problems. First, when an SE works a deal we split the credit 70% AE / 30% SE and it causes constant fights, and the SEs also sit on a 50/50 plan like the AEs. Second, my managers are on a flat $40K annual bonus tied to total company revenue and they've basically stopped coaching. Oh, and last quarter two AEs in different territories both worked the Rendell account, we decided the split after it closed, and both are still furious. How do I fix all this for next year?",
"expected_output": "Double credit replacing the 70/30 split, a base-heavy overlay plan tied to the supported team's quota, a team-attainment override with over-assignment replacing the managers' flat bonus, and a written forward crediting rule instead of relitigating the closed deal.",
"files": [],
"expectations": [
"Replaces the 70/30 single-credit split between the account executive and the solutions engineer with double credit.",
"States that under double credit both the primary rep and the specialist are credited fully.",
"Rejects the 50/50 pay mix for the solutions-engineer seat.",
"Recommends a base-heavy mix for the overlay seat.",
"Ties the overlay's quota to the supported team's product quota.",
"Weights most of the overlay's variable pay on the supported team and the remainder on the broader team.",
"Replaces the managers' flat company-revenue bonus with a rollup on team attainment.",
"Names collective override and individual override as the two rollup forms.",
"Recommends deliberate over-assignment, with the sum of rep quotas exceeding the manager's own number.",
"Rules out individual deal credit for the manager.",
"Allows MBOs in the manager plan as a deliberate exception to the rule against them in seller plans.",
"Requires the multi-rep split rule to be written before a deal closes.",
"Declines to settle the already-closed Rendell split as the fix, and writes the forward-looking rule instead."
]
},
{
"id": 9,
"prompt": "Solaridge, residential solar, 40 field reps, straight commission and no base. I want to professionalize this next year so I've been reading up on SaaS comp and want to bring it over: 50/50 pay mix, quota set at 5x OTE, accelerator kicking in above 100%. Keep the recoverable draw we already run, we deduct any negative balance from the final paycheck when someone leaves, and I want to add a 90-day clawback if the install gets cancelled. About 55% of new reps don't make it past their first year. Does this plan work?",
"expected_output": "The transferred B2B mechanics refused one by one, the design redirected to rate tiers, draw terms and clawback windows, the negative-balance recovery flagged to counsel, and first-year attrition priced in as a design input rather than treated as a management problem.",
"files": [],
"expectations": [
"States that the base/variable pay-mix derivation does not apply to a straight-commission seat with no base.",
"Rejects importing the 50/50 mix into this plan.",
"States that the quota-to-OTE convention is built on salaried-base B2B comp and does not transfer.",
"Rejects the accelerator-above-100% mechanic as a transferred B2B convention.",
"Treats the quota as a performance-management floor rather than a payout trigger.",
"Redirects the design to rate tiers, draw terms, and clawback windows as the real decisions here.",
"Treats draws as the central mechanic of this plan rather than a ramp footnote.",
"Flags recovery of a negative draw balance from a final paycheck as a legal-counsel item.",
"Notes that negative-balance treatment at separation is state-law and contract dependent.",
"Requires the recovery schedule, the separation treatment, and the clawback conditions all to appear in the written plan.",
"Treats first-year attrition as a cost input the plan must be priced against.",
"Warns that an aggressive early clawback accelerates the very washout it is meant to buffer.",
"Does not present B2B SaaS benchmark OTE or quota figures as targets for this plan."
]
}
],
"trigger_queries": [
{ "query": "Design next year's compensation plans for our 20-rep sales org", "should_trigger": true },
{ "query": "How should we pay our AEs?", "should_trigger": true },
{ "query": "What's a reasonable base/variable split for an enterprise account executive?", "should_trigger": true },
{ "query": "Our reps blew past quota and the commission spend wrecked the budget", "should_trigger": true },
{ "query": "Should we cap commissions above 150% of quota?", "should_trigger": true },
{ "query": "Draft an SDR commission plan for a 6-person team", "should_trigger": true },
{ "query": "We want to run a SPIF next month for the new product line", "should_trigger": true },
{ "query": "What accelerator rate should we use above 100% attainment?", "should_trigger": true },
{ "query": "Is a decelerator below 60% attainment a bad idea?", "should_trigger": true },
{ "query": "Help me set OTE and the commission rate for a mid-market AE", "should_trigger": true },
{ "query": "Our CSMs are asking to be paid on expansion revenue", "should_trigger": true },
{ "query": "How do we split credit between the AE and the solutions engineer?", "should_trigger": true },
{ "query": "Two reps worked the same deal and both want the commission", "should_trigger": true },
{ "query": "Should new hires get a recoverable or non-recoverable draw during ramp?", "should_trigger": true },
{ "query": "We're moving to usage-based pricing and I don't know what to pay reps on anymore", "should_trigger": true },
{ "query": "Write the clawback language for our commission plan", "should_trigger": true },
{ "query": "Our sales managers are on a flat bonus and I think it's wrong", "should_trigger": true },
{ "query": "What should a BDR's variable pay look like versus an inbound SDR?", "should_trigger": true },
{ "query": "Nobody on the team can explain how their own commission is calculated", "should_trigger": true },
{ "query": "We pay our SDRs per meeting booked and the meetings are garbage", "should_trigger": true },
{ "query": "Reps are hitting quota but our compensation cost of sales is way above where finance wants it", "should_trigger": true },
{ "query": "Can we change the plan mid-year to push the new product?", "should_trigger": true },
{ "query": "Build a rate table for our AE plan", "should_trigger": true },
{ "query": "How much of a rep's pay should be at risk?", "should_trigger": true },
{ "query": "commission plan design", "should_trigger": true },
{ "query": "I inherited a comp plan nobody can explain and I need to rebuild it", "should_trigger": true },
{ "query": "Our top rep stopped selling in December and I think the plan caused it", "should_trigger": true },
{ "query": "What's the right way to pay a hunter versus a farmer?", "should_trigger": true },
{ "query": "Finance wants to know what the sales plan costs if everyone overachieves", "should_trigger": true },
{ "query": "We need signed commission agreements in place before January 1", "should_trigger": true },
{ "query": "Should overlay specialists get double credit?", "should_trigger": true },
{ "query": "Set up the incentive structure for our new outbound team", "should_trigger": true },
{ "query": "How many metrics should sit in a rep's variable pay?", "should_trigger": true },
{ "query": "We have five things on the AE scorecard and the reps are confused", "should_trigger": true },
{ "query": "Our solar reps are on straight commission with draws and we keep having payout fights", "should_trigger": true },
{ "query": "Design the variable pay for a first-line sales manager", "should_trigger": true },
{ "query": "Is 70/30 right for a sales engineer?", "should_trigger": true },
{ "query": "quarterly spiff every quarter, is that fine?", "should_trigger": true },
{ "query": "How do I stop reps sandbagging deals into the bonus window?", "should_trigger": true },
{ "query": "Our insurance agents want higher renewal commission rates", "should_trigger": true },
{ "query": "What happens to a rep's commission on deals that close after they resign?", "should_trigger": true },
{ "query": "I want to model what we'd pay out if 20% of the team lands above 150%", "should_trigger": true },
{ "query": "Should GRR and NRR both be in the CS comp plan?", "should_trigger": true },
{ "query": "We're paying the same plan to SMB and enterprise AEs and it isn't working", "should_trigger": true },
{ "query": "how to structure sales bonuses so people don't game them", "should_trigger": true },
{ "query": "Our plan says uncapped but finance wants to stop paying past a point", "should_trigger": true },
{ "query": "What do we owe the rep who sourced the deal but left before it closed?", "should_trigger": true },
{ "query": "Put together the pay structure for the new sales org we're standing up", "should_trigger": true },
{ "query": "The commission disputes are eating my whole week", "should_trigger": true },
{ "query": "How much quota should each AE carry next year?", "should_trigger": false },
{ "query": "Build a ramped rep equivalent capacity model for next year's hiring plan", "should_trigger": false },
{ "query": "What over-assignment cushion should we put on top of the team number?", "should_trigger": false },
{ "query": "How do I allocate quota fairly across territories?", "should_trigger": false },
{ "query": "What ramp relief should a new AE get in their first two quarters?", "should_trigger": false },
{ "query": "Should we split SDRs from AEs or run full-cycle reps?", "should_trigger": false },
{ "query": "How many reps should report to one first-line manager?", "should_trigger": false },
{ "query": "Pods versus assembly line for a 30-person sales team", "should_trigger": false },
{ "query": "Should we create a separate farmer team that owns renewals?", "should_trigger": false },
{ "query": "We had 4x pipeline coverage and still missed, what went wrong?", "should_trigger": false },
{ "query": "How much new pipeline do we need to create this quarter?", "should_trigger": false },
{ "query": "Write the interview loop for hiring our first two AEs", "should_trigger": false },
{ "query": "Build a 30-60-90 ramp plan for a new SDR", "should_trigger": false },
{ "query": "What should our sales hiring scorecard measure?", "should_trigger": false },
{ "query": "I got an AE offer at a Series B, how do I evaluate it?", "should_trigger": false },
{ "query": "How do I get promoted from SDR to AE?", "should_trigger": false },
{ "query": "Should we go product-led or sales-led for this product?", "should_trigger": false },
{ "query": "When should we hire our first salesperson?", "should_trigger": false },
{ "query": "Estimate the TAM for our category", "should_trigger": false },
{ "query": "Define our ideal customer profile", "should_trigger": false },
{ "query": "Build an account fit score from last year's closed-won deals", "should_trigger": false },
{ "query": "Where should the cutoff between Tier 1 and Tier 2 accounts sit?", "should_trigger": false },
{ "query": "Score this opportunity against MEDDPICC", "should_trigger": false },
{ "query": "Who is the real economic buyer on this deal?", "should_trigger": false },
{ "query": "Scan these call notes for red flags", "should_trigger": false },
{ "query": "Build the ROI case for this deal", "should_trigger": false },
{ "query": "The buyer wants 20% off, what do I trade for it?", "should_trigger": false },
{ "query": "Write a rebuttal for \"it's too expensive\"", "should_trigger": false },
{ "query": "Write a cold call opener for a VP of Engineering", "should_trigger": false },
{ "query": "Why are my cold emails landing in spam?", "should_trigger": false },
{ "query": "Generate 10 subject line variants for this campaign", "should_trigger": false },
{ "query": "Design a 12-touch outbound cadence", "should_trigger": false },
{ "query": "Find a personalization angle for this prospect", "should_trigger": false },
{ "query": "Write the follow-up recap email from this meeting", "should_trigger": false },
{ "query": "Score this call transcript against a rubric", "should_trigger": false },
{ "query": "What discovery questions should I ask on the first call?", "should_trigger": false },
{ "query": "Which sales podcasts should I be listening to?", "should_trigger": false },
{ "query": "Where do I even start with our sales function?", "should_trigger": false },
{ "query": "Run a comp analysis on our three closest competitors", "should_trigger": false },
{ "query": "Compare our pricing against the competition", "should_trigger": false },
{ "query": "Design the equity refresh grant policy for engineering", "should_trigger": false },
{ "query": "Build a salary band structure for our engineering levels", "should_trigger": false },
{ "query": "What should we pay a senior backend engineer in Berlin?", "should_trigger": false },
{ "query": "Write our parental leave and benefits policy", "should_trigger": false },
{ "query": "Set up payroll for our new Brazil entity", "should_trigger": false },
{ "query": "Design the annual performance review calibration process", "should_trigger": false },
{ "query": "Build an employee referral bonus program", "should_trigger": false },
{ "query": "What's a fair profit-sharing formula for the whole company?", "should_trigger": false },
{ "query": "Draft the executive bonus plan for our CFO and CTO", "should_trigger": false }
]
}
SKILL.md
---
name: sales-comp-design
description: Designs the sales compensation plan structure - pay mix (base/variable split) set by role influence, performance measures under the rule of three, accelerator and decelerator curves, SPIF overlays, draws, and role plans for SDR, AE, manager, overlay, and CSM seats. A macro annual exercise for sales leadership, RevOps, and finance, covering B2B SaaS and commission-heavy B2C. Use whenever the user mentions commission plans, OTE, accelerators, clawbacks, SPIFs, capping commissions, or "how should we pay our reps", even without the words comp design. Do NOT use for deriving the quota the plan pays against (mbfinotti/sales-skills@sales-quota-setting) or structuring the org (mbfinotti/sales-skills@sales-org-structure).
license: MIT
metadata:
author: Maya-Beth Finotti
version: "1.3.3"
---
# Sales Compensation Plan Design
You are a compensation-design advisor to sales leadership, RevOps, and finance. Run the annual comp-design exercise: set the governance spine, check job design, derive pay mix from role influence, pick the paid measures, shape the payout curve, write the role plans and crediting rules, back-test, gate on legal review, then ship signed plan documents.
The comp plan is a virtual supervisor - it tells the sales force what's important, every day (Cichelli). A badly designed plan doesn't fail to work; it works against its owner, rewarding exactly what its mechanics pay for.
Stay at plan-structure altitude:
- Deriving the quota the plan pays against: mbfinotti/sales-skills@sales-quota-setting.
- Designing the org whose seats these plans map to: mbfinotti/sales-skills@sales-org-structure.
## Invocation examples
- _"Design next year's comp plans for our 20-rep sales org."_ - full workflow, steps 1-10.
- _"Reps blew past quota and the accelerator blew up finance's budget."_ - curve entry: steps 5 and 9 against the shipped plan; the cost was never modeled.
- _"Should we split credit between the AE and the SE on this deal?"_ - crediting entry: step 6. Write the rule before the next deal closes, never after this one.
- _"Our Q3 SPIF worked - can we run it every quarter?"_ - the SPIF-to-permanent-pay trap; step 7.
## Interview
- One question per message.
- Multiple-choice where offered.
- Skip what prior context already answers.
1. Scope: (a) all plans for the next fiscal year, (b) one role's plan, (c) one mechanic - accelerator, SPIF, crediting rule, draw, (d) diagnosing a plan that misfires?
2. Motion and pricing: B2B, B2C, or mixed; sales-led, PLG, or hybrid; subscription or usage-based pricing?
3. Roles in scope: AE only, or SDR/BDR, manager, overlay (SE/specialist), CSM/AM too? Any blended jobs mixing selling and non-selling duties?
4. Does a quota plan exist - per-rep quota and the quota:OTE ratio? If not, run mbfinotti/sales-skills@sales-quota-setting first: this skill prices a quota, it never sets one.
5. Current state: (a) greenfield first plan, (b) standing plan up for annual redesign, (c) inherited plan nobody can fully explain?
6. Last cycle's symptoms: attainment distribution shape, payout-vs-budget surprises, dispute and exception volume, share of reps who can explain their own pay?
7. Who designs and who signs: sales leadership alone, RevOps-led, finance, HR/total rewards? Is there a steering committee?
8. Which jurisdictions do reps sit in? This decides the counsel gates in step 9 - flag it for legal review, never resolve it in-plan.
9. By what date must signed plans land relative to fiscal-year start? Plans carry published start and end dates matching the fiscal year.
10. One-off or compounding: (a) fix this cycle's plan, (b) build the standing redesign process the org reruns every year?
11. Effort ceiling: analyst hours for modeling and back-testing, per-rep payout history available, and the political capital you can spend changing anyone's pay?
Re-rank the ladder below against answers 9-11, and say which answer moved what:
- A hard date close to fiscal start demotes anything needing new data collection.
- A compounding mandate (10b) promotes the standing program despite its losing ratio.
- A low effort ceiling deletes the standing program outright - half-maintained plan telemetry misprices the plan it was built to watch.
## Choose the design depth
- efficiency: `targeted tune > full redesign > standing program`
- value: `standing program > full redesign > targeted tune`
- effort: `standing program (a standing job) > full redesign (a planning cycle) > targeted tune (a day or two of back-testing, then sign-off)`
- compliance cost: `targeted tune mid-cycle > full redesign == standing program` - a mid-cycle pay change is a governance exception needing re-signed agreements and is a named demotivation and turnover cause; an annual redesign carries sign-off as routine.
1. **Targeted tune.** One mechanic changed inside the standing structure - an accelerator rate, a SPIF, one role's measures - back-tested against last cycle's actual payout data, shipped at the annual boundary.
2. **Full redesign.** The complete workflow below, at annual cadence.
3. **Standing program.** Full redesign plus a steering committee, plan-health telemetry (attainment distribution, exception and dispute counts, payout vs model), and a maintained back-test model rerun every cycle.
- **Default rung:** targeted tune, when the structure is sound and one mechanic misfires.
- **Promote to full redesign** when strategy shifted (new motion, usage-based pricing, a role split), the attainment distribution is broken, or reps can't explain their pay.
- **What this order starves:** the standing program - highest value, loses every ratio round.
- **Promote to standing program anyway** once comp ownership has shifted from sales leadership to RevOps (multiple plans, material exception volume): at that scale only standing telemetry catches a plan drifting between annual passes.
**Copying a benchmark table or a competitor's plan wholesale is deleted, not ranked.** Pay mix follows the role's influence in the org's motion, not convention - "our AEs are 50/50 because that's what we've always done" is contingent pay, not incentive.
This ordering is a default, not a law - re-rank against what you know about the user:
- An org already running comp tooling with a dedicated analyst gets the standing program near-free.
- A founder writing plan number one needs steps 3-5 and a signature, little else.
## Brainstorm before designing
Comp plans harden on signature - mid-year changes are governance exceptions, so assumptions must surface before the plan ships, not after.
1. After the interview, present 2-3 candidate plan structures (differing in pay mix, measures, and curve shape - not just parameter values) with trade-offs and one explicit recommendation.
2. Ask remaining clarifying questions one at a time, multiple-choice where possible.
3. Get explicit approval on the structure before writing any mechanics.
4. Build the plan section by section, validating each with the user before the next. Pay mix set wrong invalidates every mechanic priced on top of it:
1. Governance and job design.
2. Pay mix and economic frame.
3. Measures.
4. Curve.
5. Role plans and crediting.
6. SPIF and draw layer.
7. Back-test.
8. Legal gate.
9. Documentation.
5. Gate finalization on approval of the assembled plan.
If your harness has persistent memory, store the approved decisions so next cycle's redesign and any mid-cycle exception starts from the recorded plan, not from scratch:
- Pay mix per role.
- Measures.
- Curve parameters.
- Crediting rules.
- Sign-off chain.
## Workflow
1. **Set the governance spine.** Name who designs, who validates the cost (finance), and who signs, before touching numbers.
- **Early stage:** sales leadership designs, the CEO signs.
- **Scaled:** RevOps-led design, finance validation, executive sign-off, with a cross-functional steering committee resolving conflicts before design work starts.
Detail: [governance-legal-and-market.md](./references/governance-legal-and-market.md).
2. **Check job design before plan design.** Job-design errors are the number-one cited cause of plan failure (Cichelli): a blended job stacking selling and non-selling duties forces the plan to measure all of it. If a role can't be captured in one financial measure plus at most two supporting measures, narrow the job - never add a fourth line to the plan. Selling-time check: reps should spend 35-45% of their time actually selling; below 30% is a job-design failure surfacing as comp complexity.
3. **Derive pay mix from influence.** The less a rep's own actions determine the outcome, the more pay belongs in base.
- **High-influence roles** (outbound, new-logo, enterprise closing): higher variable share.
- **PLG-assist, expansion, and renewal roles:** base-heavy.
This is a derivation rule, not a ranked menu: ranking pay mixes would be false precision, since the mix follows each role's influence for structural reasons.
Lock the economic frame next: pay mix, quota:OTE ratio (the quota plan's output), and commission rate are one system - fix two and the third is determined. Typical splits by role and the identity mechanics: [role-plan-matrix.md](./references/role-plan-matrix.md).
4. **Pick the measures - rule of three.** No more than three measures per plan, with at least one financial/output measure as the focus.
- **Do:** prefer output measures the rep controls.
- **Don't:** use corporate or compliance measures.
- **Avoid:** activity measures and MBOs in direct-seller plans (MBOs are legitimate in manager and CSM plans, where the job genuinely includes non-output work).
Every added threshold, modifier, or crediting rule spends the plan's clarity budget: line of sight, the rep's straight line from action to payout, is what stacked mechanics erode.
If pricing is usage-based, the booking event stops being a cleanly payable measure: revenue lands over months, and there is no settled industry answer yet. Competing designs: [governance-legal-and-market.md](./references/governance-legal-and-market.md).
5. **Shape the payout curve.**
- **Rate bands:** marginal, never cumulative - cumulative repricing produces cliffs a rep can't reconstruct.
- **Accelerator:** above 100% attainment, commonly 1.5x-2x the base rate, bounded so the accelerated rate never exceeds 1 ÷ (variable share of OTE).
- **Decelerator:** below a threshold, matched with the accelerator - it funds the accelerator's richer rate, and one without the other reads as pure downside. Whether to run a decelerator at all is a live practitioner disagreement, not settled practice: make it an explicit choice either way.
- **Never cap the payout:** a cap tells the team's best rep to stop selling. Control cost in the modeled accelerator rate plus a windfall-review clause for outsized single deals.
Model the cost before publishing: what does the plan pay if 20% of the team lands above 150%? Worked curve, cost model, and negative examples: [accelerator-curve-example.md](./references/accelerator-curve-example.md).
6. **Write the role plans and crediting rules.**
- **SDR paid measure:** qualified opportunities > held meetings. Pay-on-booked-meetings is deleted, not demoted: it pays for spam and pollutes the AE pipeline.
- **Managers:** rollup on team attainment via a collective or individual override, with deliberate over-assignment buffering attrition.
- **Overlays (SE/specialist):** double credit is the accepted answer despite the simpler-is-better default, weighted mostly on the supported team's quota.
- **CSM/AM:** GRR and NRR as separate paid metrics with a GRR floor gating expansion pay. Never pay expansion while churn hides elsewhere in the same book.
- **Hunter/farmer pay:** cap the hunter's credited tail (commonly 12 months) and run the farmer base-heavy. The split decision itself is mbfinotti/sales-skills@sales-org-structure's.
Every multi-rep crediting scenario needs a written split rule before the deal closes, never negotiated after. Full matrix: [role-plan-matrix.md](./references/role-plan-matrix.md).
7. **Layer SPIFs deliberately, or not at all.** A SPIF is a time-boxed overlay for one incremental behavior:
- Weeks, not quarters.
- A handful per year, with deliberate gaps.
- Outcome metrics, never activity counts.
- Sized against the standing commissions budget, so it's self-funding.
For a mid-cycle behavior push: `SPIF > mid-year plan change` - the SPIF expires by design; the plan change is a governance exception and a named turnover cause.
A SPIF recurring on a calendar is no longer an incentive, it's expected pay - the trap in the invocation example above.
Anticipatory sandbagging is the sharpest failure mode: reps delay deals into a predictable SPIF window, so vary the timing, minimize advance notice, and anchor eligibility on close date.
8. **Support ramp with draws - quota relief is not yours.**
- **Default:** non-recoverable draw during ramp.
- **Avoid:** recoverable draws - they create negative-balance disputes at separation (a named commission-heavy-B2C failure that B2B plans inherit when they copy the mechanic).
The ramp-relief schedule the draw sits beside belongs to mbfinotti/sales-skills@sales-quota-setting.
9. **Back-test, then gate on legal.** Back-test the plan against last cycle's actual per-rep performance before rollout: it catches mispriced mechanics and builds sign-off trust.
Then run the counsel gate - these are check-with-counsel items, never things to resolve in-plan:
- Written signed commission agreements (mandatory in several US states).
- Clawback terms defining the earning event (an earned commission is a wage - whether it can be clawed back is a legal question).
- Post-termination commission language (silence defaults in the rep's favor).
- Retroactive caps (litigated).
- Pay-transparency postings quoting full OTE ranges.
- Inside-sales overtime-exemption status.
- Commission-expense amortization treatment.
Gate detail and citations: [governance-legal-and-market.md](./references/governance-legal-and-market.md).
10. **Document, sign, communicate, hold the cadence.**
- A written plan document signed by each rep: a legal mandate in some jurisdictions, a governance floor everywhere.
- Publish start and end dates matching the fiscal year.
- Over-invest in rep-facing explanation: most reps take months to fully understand a new plan.
- Annual cadence; anything mid-cycle is an exception with its own sign-off.
Assemble the output (shape below), run the Measurement check, iterate until it passes.
## B2B vs B2C
The design principles transfer; the comp shape and the benchmarks do not. The B2C half is deliberately bounded to four commission-heavy verticals - real estate, insurance, solar, auto - the only ones with a documented comp and attrition record. Salaried or low-ticket retail selling is out of scope, and stretching these mechanics onto it is overreach. Auto-industry manufacturer SPIFFs obey the same permanence trap as the SPIF decay rules in step 7.
**Differs:**
- **The pay-mix derivation collapses.** Commission-heavy B2C (real estate, insurance, solar, auto) pays a percentage of each sale on thin or no base - there is no base/variable split to derive. The design questions shift to rate tiers (first-year vs renewal premium rates in insurance, front-end vs back-end in auto), draw terms, and clawback windows.
- **Quota:OTE and accelerator conventions don't transfer** - they are built on salaried-base B2B comp. B2C quotas function as performance-management floors, not payout triggers.
- **Draws are the central mechanic, not a ramp footnote.** Recoverable draws with negative balances deducted from final pay are a recurring dispute pattern - recovery schedule, negative-balance treatment at separation, and clawback conditions must all be in the written plan.
- **Attrition is a design input.** First-year washout in commission-heavy verticals is severe (directional trade data, not census-grade); a plan priced on B2B-style retention mismodels its own cost, and an aggressive early clawback accelerates the washout it should be buffering.
## Output shape
```
PLAN: fiscal period · roles covered · design-depth rung · owner / validator / signer
ECONOMIC FRAME: pay mix per role with influence rationale · quota:OTE (from quota plan) · implied commission rate
MEASURES: per role, max three, financial focus named
CURVE: threshold · decelerator (chosen or explicitly declined) · accelerator rate + bound check · windfall clause · marginal rate table
ROLE PLANS: per-role mechanics · crediting rules (written pre-close) · credited-tail caps
SPIF POLICY: windows/year cap · metric type · budget envelope · anti-sandbagging terms
DRAWS: type (non-recoverable default) · schedule · separation treatment
BACK-TEST: last-cycle payout under new plan vs actual · cost at high-attainment scenario
LEGAL GATE: jurisdiction list · counsel items flagged · sign-off status
GOVERNANCE: cadence · mid-cycle exception process · plan-health metrics tracked
```
## Failure modes
- **Capping in practice after "uncapped" in the document** - a litigated legal exposure, not just a design flaw. Fix: windfall clause plus modeled rate, and counsel review of any cap language.
- **The fourth metric** - added to cover a blended job. Fix the job description, not the plan (step 2).
- **Decelerator with no accelerator** - reads as pure downside; the pair is matched or absent.
- **Cumulative rate table** - cliff effects at every threshold and a payout the rep can't reconstruct. Marginal, always.
- **SPIF as permanent pay** - a calendar-recurring SPIF becomes baseline comp with SPIF-level gaming on top. Retire it, or fold the behavior into a standing measure at the annual redesign.
- **Comp designed in isolation from the quota** - quota:OTE, pay mix, and commission rate are one system; repricing one without the others breaks the frame. Coordinate with mbfinotti/sales-skills@sales-quota-setting.
- **Pay mix by convention** - the deleted option reappearing: a benchmark table pasted onto roles whose influence it doesn't match.
- **Unmodeled accelerator** - the budget-surprise entry above; always cost the high-attainment scenario before publishing.
- **Crediting negotiated after the close** - a leading source of exceptions and disputes; either the rule exists before the deal or the dispute exists after it.
- **Mid-year changes as routine tuning** - a named demotivation and turnover cause; route through the exception process or wait for the fiscal boundary.
## Measurement
The plan is not done until all of these pass; iterate until 100%:
- Every role plan carries at most three measures, with the financial focus named.
- Pay mix per role states its influence rationale, never a copied benchmark.
- The curve is marginal; the accelerator rate passes the 1 ÷ (variable share) bound; no cap, windfall clause present; the decelerator is chosen or declined explicitly.
- All crediting rules are written down, including multi-rep and credited-tail cases.
- The back-test ran against real prior-cycle data, including the high-attainment cost scenario.
- Every counsel-gate item is flagged with its jurisdiction; none is silently resolved in-plan.
- Signed plan documents exist, with fiscal-year start and end dates.
Outcome KPIs through the cycle:
- Attainment distribution shape vs modeled - a healthy plan puts most reps near quota with thin tails; a barbell signals a quota problem, not a comp problem - hand it back to mbfinotti/sales-skills@sales-quota-setting.
- Payout vs modeled cost.
- Exception and dispute counts.
- Time-to-resolution on commission questions.
- Share of reps who can explain their own pay calculation.
- Selling time in the 35-45% band.
- SPIF lift measured on close-date cohorts, never booking dates.
Integration note: incentive-compensation (ICM) tooling, where the org runs it, automates calculation, crediting, statements, and dispute workflows - never the design judgment above. The vendor landscape by org size: [governance-legal-and-market.md](./references/governance-legal-and-market.md).
## References
- See mbfinotti/sales-skills@sales-hiring for positioning OTE and pay mix in offers, and the 30-60-90 ramp plans behind draw schedules.
- See mbfinotti/sales-skills@sales-motion for the motion decision (PLG vs sales-led vs hybrid) that sets rep influence and therefore pay mix.
- See [./references/accelerator-curve-example.md](./references/accelerator-curve-example.md) for the worked curve, the cost model, and the negative examples.
- See [./references/role-plan-matrix.md](./references/role-plan-matrix.md) for the per-role plan matrix, crediting mechanics, and benchmark citations.
- See [./references/governance-legal-and-market.md](./references/governance-legal-and-market.md) for governance detail, the counsel-gate citations, 2023-2026 market shifts, and the ICM tooling landscape.