How do you compensate a sales manager whose reps overperform — pay them on team total or on personal stretch goals?

Answer

Pay the manager 60% on team total, 30% on rep-development outcomes, 10% on personal stretch, motion-adjusted: enterprise tilts to 70/20/10, velocity stays at 60/30/10, mid-market splits 65/25/10. The plan only works when four conditions hold simultaneously: (a) the rep-development pool is gated on median rep attainment, not team aggregate; (b) ramp is measured on the inherited/hired cohort, not who's seated at quarter-end; (c) accelerators are capped at 200% (250% for enterprise) so a single blowout quarter doesn't break annual planning; and (d) the manager can recite the entire plan from memory in under 90 seconds — if they can't, redesign it.

Fail any one of these and the plan produces the wrong behavior even when the dashboard reads green.

First-Principles Defense (Why This Isn't Just a Benchmark)

This framework isn't 'because Pavilion said so.' The behavioral logic underneath: a sales manager has roughly 5–8 reps, sees pipeline daily, and makes ~50 micro-decisions per week (which deal to inspect, which rep to ride along with, which slow ramp to PIP). Each decision is a coin flip between *help the team* and *help me*.

Comp design picks which side lands face-up. Weight personal at 60%+ and the manager systematically chooses 'help me' — the math reveals itself in 18 months as B-player churn and territory imbalance. Weight team at 60%+ and 'help the team' becomes the rational play, because the manager's paycheck literally depends on the median rep, not the top one.

As David Cichelli writes in *Compensating the Sales Force* (3rd ed.): *'Sales compensation must answer one question — what behavior do we want, and at what cost?'* — every benchmark below (Pavilion, Bridge Group, WorldatWork, Alexander Group, SBI) just confirms this independently because the underlying behavioral physics are identical.

Postmortem: Seed-Stage SaaS, 80/20 Personal/Team Plan

A Series-A SaaS company (5 AEs, 1 manager, $4M ARR target) ran 80/20 personal/team for two quarters in 2023:

• Q1: manager personally closed $620K. Team finished at 78% of $1M quarterly quota. Manager paid 172% OTE.
• Q2: manager closed $410K personally. Three reps missed quota. Two voluntarily left citing 'manager won't help on deals.' Manager paid 138% OTE while team printed 64%.
• Q3 reset to 60/30/10: manager personal close dropped to $180K (deliberately routed deals to reps). Team printed 102%. Retention stabilized. Manager paid 108% — lower personal number, healthier team economics, founders kept their AEs.

The number that ended the experiment: $87K cost-per-rep replacement × 2 = $174K the 80/20 plan 'saved' in manager comp but spent twice over in churn. See [/knowledge/q119](/knowledge/q119) for ramp-cost math.

Industry-Specific Weighting Deltas

Executive Summary (Board Deck)

Manager comp is the highest-leverage lever in revenue ops because the manager is the only person with daily access to *all* rep behavior. A team-total-weighted plan converts the manager from a competing rep into a coach with skin in the game. Industry benchmarks converge on 60–70% team-weighted for high-retention orgs.

Sub-questions — motion, ramp, churn, deal concentration, team size, industry — calibrate inside that band.

Counter-Position: When Team-Total Weighting Fails

1. Early-stage <4 reps: 'team' is hidden personal comp. Use 50/30/20 with explicit kicker on manager deal involvement until rep count crosses four.
2. Founder-led sales ([/knowledge/q05](/knowledge/q05)): founder is the team. Use revenue-share or equity refresh tied to ARR milestones.
3. Sole-AE territories: pay manager on multi-territory aggregate with rep-development weighted 40%+.

Outside these three, 60/30/10 framework applies.

The CFO-vs-CRO Tension

CFO wants comp line predictable; CRO wants manager motivated to overperform. The 200% accelerator cap (250% enterprise) is the negotiated peace: it lets the CRO point to upside without the CFO modeling unbounded comp. Without the cap, a single team printing 180% of quota produces a payout that breaks the annual plan and gets the comp scheme cancelled the following year.

Accelerator Math — Why 200% Cap Matters

Manager OTE $200K ($120K base, $80K variable), mid-market 65/25/10, team posts 180%:

• Uncapped linear: team pool $52K × 1.80 = $93,600 + $20K rep-dev + $12K stretch = $125,600 variable → $245,600 total comp.
• Capped at 200%: team pool $52K × 2.00 = $104,000 + $20K + $12K = $136,000 annualized; quarterly = $34,000.

Cap costs ~$15K of upside in a blowout quarter; CFO gets a comp line that doesn't blow up annual planning past 200%. That's the trade — and it's the conversation that gets the plan approved.

Migration Risk Register

The Decision Tree

1. Average rep ramp >120 days? Weight rep-development ≥30%.
2. Top 3 reps drive >60% of revenue? Raise stretch ceiling to 15%.
3. Voluntary churn >25%? Gate all variable on retention >85%.
4. Forecast accuracy <80%? Add 5–10% pillar on forecast deviation. [/knowledge/q302](/knowledge/q302).
5. Team size <4? Apply Counter-Position.
6. Industry = PLG or Channel? Use deltas table above.

Upstream: [/knowledge/q73](/knowledge/q73) (territory design), [/knowledge/q201](/knowledge/q201) (manager hiring rubric).

Why Team Total Wins (Primary)

• Shared accountability: Pavilion&#39;s 2024 Sales Compensation Benchmark — team-weighted managers retain reps 6–9% longer, lift cohort attainment 8–12%.
• Retention signal: trust compounds when manager bonus tracks rep wins. [/knowledge/q47](/knowledge/q47).
• Quota integrity: Bridge Group&#39;s 2024 SDR Metrics Report — personal-comp managers drive #1 cause of B-player churn (18-month vs. 31-month tenure).
• Industry validation: WorldatWork&#39;s 2024 Sales Compensation Survey — median enterprise sales manager 65% team-weighted; high-retention quartile 72%. SBI&#39;s 2024 sales effectiveness benchmark confirms.

The 60/30/10 Layering Model — Motion-Adjusted

Alexander Group&#39;s 2024 sales leadership study — long-cycle motions reward patience, why enterprise window is 4Q. Force Management and OpenView corroborate.

Year-One Rollout Calendar

• Days 0–30: Audit existing plan vs diagnostics. Communicate change in writing.
• Days 30–60: Run parallel calculations in Spiff/Anaplan/Captivate. Show managers both numbers.
• Days 60–90: Cutover at quarter boundary. Lock dashboards.
• Mid-year (Q3): Review. If >20% pegged to floor or ceiling, recalibrate.
• Year-end: Compare retention, ramp, median attainment YoY. Tie to [/knowledge/q418](/knowledge/q418).

Real-World Example (Reconciled, Mid-Market)

$2M ARR team, $1.5M quota, manager OTE $200K ($120K base + $80K variable, 65/25/10):

• Team pool ($52K, 65%): 130% attainment → $67,600.
• Rep development ($20K, 25%): 91% retention + 108-day ramp + 75% reps at quota → $20,000.
• Personal stretch ($8K, 10%): closed $400K logo → 150% cap = $12,000.
• Total variable: $99,600 → Total comp: $219,600.

Next quarter at 72%:

• Team: $0 (below 75% floor).
• Rep dev: 60% partial — retention 90%, ramp slipped to 145 days = $12,000.
• Stretch: $0.
• Total comp: $132,000 — $87,600 swing forces the CFO/VP Sales conversation ([/knowledge/q156](/knowledge/q156)).

Bear Case — Six Failure Modes

1. Territory hoarding (team-total <50%): manager self-assigns top accounts. Fix: hard floor team-total at 60%, audit territory carve quarterly.
2. B-player neglect (no median gate): rides two A-players, ignores bottom four. Fix: gate rep-development on median rep attainment.
3. Ramp-time gaming: PIPs slow rampers to keep ramp <120 days. Fix: lock ramp to inherited/hired cohort at 6-month milestone.
4. Coaching-weight inflation: managers manufacture activity counts. Fix: measure on outcomes only.
5. Manager collusion (multi-team): cross-team stretch-deal credit swaps. Fix: own-segment only with audit trail.
6. Over-engineered plan: if manager can't recite from memory, they can't optimize toward it. Fix: one page, four metrics, one cap, one floor — that's the limit.

Diagnostics Checklist

• [ ] Team-total ≥60%?
• [ ] Rep-development gated on median?
• [ ] Ramp tied to inherited/hired cohort?
• [ ] Personal stretch ≤15% of total comp?
• [ ] Retention floor (>85%) before team-total payout?
• [ ] Coaching metrics outcome-based?
• [ ] Measurement window matches motion?
• [ ] Accelerator capped at 200% (250% enterprise)?
• [ ] Plan fits on one page; manager recites from memory?
• [ ] Industry weighting delta applied if PLG/Channel?

More than two unchecked = redesign.

How This Answer Could Be Wrong (Epistemic Humility)

This framework rests on assumptions that may not survive your context: (1) it assumes you have *enough rep volume* (≥4) for team-total math to mean something; (2) it assumes rep churn is the dominant cost — if your customer churn is the dominant pain, manager comp should weight retention/expansion not new logo; (3) it assumes a manager has organizational power to actually shift behavior — in matrixed orgs where the manager is a 'pod lead' without hire/fire authority, the comp signal is muted.

If any of these don't hold, treat the framework as scaffolding rather than recipe and adjust the weights. The decision tree handles most edge cases; the rest requires judgment.

Pitfalls Beyond Bear Case

• Full personal comp: managers compete with reps.
• Zero stretch: disengagement on $500K+ deals.
• No quality gates: pipeline padding, discounting, sandbagging.
• Annual-only measurement: smooth with trailing-quarter.

Benchmarks (Inline Sources)

Force Management: team-weighted managers deliver 8–12% faster new-rep ramp. Bridge Group: personal stretch ≤15% total comp. Pavilion and OpenView: high-retention manager median 60–70% team-weighted.

WorldatWork and Alexander Group: enterprise tilt to 70% team-weighted dominant. SBI: confirms across mid-market and enterprise. Tooling: Spiff for parallel-calculation modeling during migration.

TAGS: sales-management,compensation,sales-ops,team-alignment,quota-management,bonus-structure,sales-leadership,retention

Recently Added — Related

• [How do you design a sales contest that doesn't tank pipeline quality after it ends?](/knowledge/q251)