Three regional forecasts became one, and the commit number went from ±34% to ±11% in four months — without a new CRM and without adding a single dashboard.
Three regions forecast three different ways, so the roll-up was a negotiation and the board stopped believing the commit number.
Forecast variance
±34%
Week-three commit against closed-won, trailing six quarters.
Stage models in use
3
One per region, with the same stage names meaning different things.
Stage-2 data completeness
52%
Opportunities at stage 2+ carrying all six required fields.
Live dashboards
19
Of which leadership opened four in the trailing quarter.
Median cycle time, core segment
94 days
Qualified to closed, segment-held.
The seam sat between the stage definition and the forecast category. A stage advanced when a rep felt good about it, so the roll-up was a negotiation, and the board had quietly stopped believing the commit.
Quarterly plan re-cut against a wrong commit
$2.3M
Hiring and spend committed against a forecast that missed by more than 20% in three of six quarters.
Late-quarter discounting to close the gap
$1.9M
Discount above policy granted in the final three weeks of a quarter, trailing four quarters.
Rep time in forecast reconciliation
$640K
Modelled: 6 hours a week across 43 reps and 3 managers, at fully loaded cost.
$4.84M a year spent absorbing a forecast nobody trusted.
01
Weeks 1–2
Sampled 180 open opportunities against the written stage criteria in each region. Scored how many would survive an exit-criteria test.
What we read
41% of stage-3+ pipeline did not meet its own region's stage definition. The number was presented once, without commentary.
02
Weeks 3–6
Collapsed three stage models into one with a written, testable exit criterion per stage. Separated forecast category from stage so commit is a judgement a manager owns, not a side-effect of a picklist.
What we read
Pipeline fell 18% on the first re-scored read. That drop was expected, published in advance, and never restated.
03
Weeks 7–11
Cut required fields from 22 to 6 and enforced those at the stage gate. Retired 14 of 19 dashboards and rebuilt the two leadership actually reads.
What we read
Stage-2 completeness 52% → 94% in five weeks. Dashboard usage concentrated instead of scattered.
04
Weeks 12–17
Same four questions per deal, same day, same attendees. Ran with a Nuvello operator for six weeks, then handed the agenda to the regional sales operations leads.
What we read
±11% variance on the same read point. Two consecutive quarters called within band before we left.
Forecast accuracy
±34% → ±11%
23 points of variance removed, same week-three read point throughout.
Stage-2 data completeness
52% → 94%
+42 points on the six fields that survived the cull.
Cycle time, core segment
94 → 81 days
−13 days, segment-held so a mix shift cannot flatter it.
Above-policy discounting
−38%
Final three weeks of quarter, trailing two quarters against the prior four.
The stage model, the inspection agenda and the two surviving dashboards are owned by the regional sales operations leads.
This is an illustrative composite. The numbers, phases and outcomes show how we baseline a motion, read a delta and hand the cadence back — they are modelled on the shape of RevOps work delivered through the network, not lifted from one named client. We publish nothing under a client's name without written sign-off.
Two enterprise deals closed early in the final quarter. We reported cycle time with and without them; the delta above is the figure excluding both.
The sales management in fullWe start the same way every time: one baseline, one written definition, one cadence you keep after we leave.