Compass
Where the forecast lives.
The forecast isn't a number someone typed into a slide. It's a composition — renewal base, pipeline-weighted new business, expected churn, expansion assumptions, timing adjustments. Compass builds the forecast from those layers, traces every dollar to a contract, and explains what moved when something changes.
The forecast is a spreadsheet that nobody fully trusts — including the person who built it.
Most SaaS forecasts are assembled manually. Someone pulls pipeline from the CRM, renewal expectations from a tracker, churn estimates from memory, and expansion guesses from conversation. They merge it in a spreadsheet, adjust the numbers until they feel right, and present it as a plan. A week later, something moves, and the whole process starts over.
The problem isn't the math. The problem is that the forecast has no architecture. No traceable inputs. No versioned assumptions. No way to explain what changed or why. It's a number that exists because someone decided it should — not because a system constructed it from evidence.
Built from layers, not guesses.
Compass constructs the forecast from discrete, traceable layers: renewal base ARR from active contracts approaching term, pipeline-weighted ARR from Current, confirmed and expected churn, and expansion assumptions. Each layer connects back to specific contracts.
The total is a composition, not an assertion — and every component is independently auditable.
Adjust assumptions. See the forecast move.
Operators don't just read the forecast — they shape it. Compass lets you adjust timing assumptions, probability overrides, risk posture, and renewal confidence. Change a close date from June to August and watch the period forecast recalculate. Flag a renewal as at-risk and see the churn estimate adjust.
Every scenario is grounded in the same contract data — the assumptions change, not the evidence.
What moved. Why it moved. Which contracts changed.
When the forecast changes, Compass doesn't just show the new number — it explains the movement. Variance analysis breaks down the delta between any two points in time: which contracts were added, which churned, which changed amounts, which shifted timing, which moved stages.
The CFO never has to reconstruct the story manually. The system preserves it.
A forecast should be a system, not a ritual. Every number should trace to a contract. Every change should be explainable.
Compass reads from Contracts and Current. It feeds Portolan for historical snapshots and Beacon for interrogation.