The plan change package — what goes to the governance committee
Every proposed plan change above a materiality threshold requires a formal plan change package submitted to the SIC governance committee. The analytics team owns the financial modeling section, which includes: current plan cost baseline (P50 from Monte Carlo), proposed plan cost (P50 and P90), ΔCost decomposition waterfall, behavioral response assumption with source, ΔRevenue estimate with confidence bounds, ROI ratio, break-even attainment lift, and cost of sales % under old vs. new plan.
Materiality thresholds
Not every plan tweak requires a full package. Microsoft uses materiality thresholds: changes with expected ΔCost below $500K at P50 can be approved by VP Finance. $500K–$5M requires SVP Finance + HR. Above $5M requires CFO-level sign-off. The analytics team calculates the expected ΔCost as part of initial triage — determining which approval level applies is the first deliverable.
Cost of sales monitoring — monthly cadence
The analytics team tracks cost of sales % monthly against the plan target. If actual cost of sales tracks above the P50 forecast by more than 1.5 percentage points for two consecutive months, it triggers an early warning report to finance. This report includes: current trajectory, projected full-year cost at current run rate, variance decomposition (is the overrun from higher attainment, plan mechanics, or headcount growth), and recommended actions.
Windfall and sandbag analysis
Windfall: identify reps whose payout is driven by a single large deal rather than sustained performance. Flag for windfall review — the deal may have landed regardless of rep effort. Analytics deliverable: regression of payout on deal count and deal size to separate "one big deal" reps from "sustained high performers."
Sandbagging: identify reps who consistently hit quota in Q4 but underperform in Q1–Q3. This is a plan timing signal — reps are holding pipeline to manage their attainment trajectory. Analytics deliverable: quarterly attainment pattern analysis by rep cohort.
The ROI conversation with sales leadership
Sales leaders want higher TI and steeper accelerators. Finance wants lower cost. The analytics team is the neutral party that quantifies both sides. The ROI model is the common language. When sales says "raising the accelerator will drive 15% more revenue," the analytics team's job is to test that assumption against data and either validate, modify, or challenge it — with evidence, not opinion.