Chapter 01 · The brief
The numbers were right. The picture was not.
Three tools, three versions of the same number, none of them recent.
A growing enterprise sales organisation had outgrown its first-generation operations stack — a forecasting spreadsheet, a CRM extract, and a separate quota planning workbook that lived on one analyst's laptop.
Each system told a slightly different story. Leadership reviews opened with reconciliation, not decisions. By the time the team agreed on the number, the quarter had moved on.
The brief landed with a clear ask: replace the patchwork with a single operations platform that field, ops, and leadership could trust as the source of truth — without disrupting a live pipeline mid-year.
Chapter 02 · Approach
Map the workflow before the schema.
We started where most operations programmes don't — with the conversation cycle, not the data model. Two weeks of structured sessions with field, ops, and finance produced a current-state map of every decision the team made each month: pipeline review, forecast call, quota change, comp plan tweak.
Only after the workflow was readable did we propose a data model. That sequence kept the platform tied to how the team actually worked, instead of fitting work to a generic SPM template.
Three principles drove the build:
- One canonical pipeline record. Every other system reads from the platform, not the other way around.
- Forecast as a workflow, not a screen. Submit, challenge, sign-off — captured with audit trail.
- Quota and territory under version control. Every change leaves a footprint that survives the next reorganisation.
Chapter 03 · Build
A platform built around the rhythm of the business.
The platform shipped in four releases, each tied to a business event leadership already cared about — quarterly business review, mid-year reset, comp roll-out, planning cycle.
Behind the screens, an event-sourced pipeline core captured every state change on every opportunity, and an entitlements layer made sure field reps saw their own pipeline while leadership saw the rollup. Quota planning ran in its own service so plan changes did not block forecast submission.
Chapter 04 · Roll-out
Shipped in sequence, not in one go.
Replacing a live operations stack mid-year required sequencing. We mapped the four releases to business events the team already owned: the Q2 business review, the mid-year quota reset, the comp plan roll-out, and the annual planning cycle.
Each release added one capability — pipeline visibility, then forecast workflow, then quota planning, then commission transparency. Field adoption was tracked, not assumed. Hypercare ran for six weeks after each release.
Chapter 05 · Outcomes
The reconciliation meeting disappeared.
The new platform eliminated the manual reconciliation cycle entirely. Quota planning moved from quarterly to weekly. Leadership gained a real-time pipeline view they trust enough to act on in board-level discussions.
Commission disputes dropped to near zero — every rep could see the line-item calculation behind their number.
Chapter 06 · Stack
Technology stack.
- Pipeline coreEvent-sourced, append-only, full state history per opportunity
- Data layerDatabricks on Azure, CRM ingestion via webhook + scheduled sync
- Quota engineIndependent service; plan changes propagate without blocking forecast
- Forecast workflowSubmit / challenge / sign-off with full audit trail
- Commission calcLine-item transparency per rep; finance and sales see the same number
- EntitlementsRole-based pipeline scope; field sees own pipeline, leadership sees rollup