Building the Single Source of Truth

The single source of truth is not a database. It is a contract between every team that touches revenue — a shared commitment that one system holds the canonical state of every deal, every metric, and every forecast, and that no parallel system is authoritative. The moment someone maintains a "shadow pipeline" in a spreadsheet because they do not trust the CRM, the single source of truth is dead. You now have two sources of truth, which means you have none.

1. Audit Every Revenue Data Source Before you can build the single source, you need to know how many sources currently exist. Run a data audit: where does pipeline data live? CRM, spreadsheets, email threads, slide decks, Slack messages? Where does financial data live? ERP, accounting software, CFO's personal model? Where do forecasts live? Sales has one, finance has another, the CEO has a third. Document every source, what it contains, who maintains it, and how often it diverges from other sources. The audit usually reveals 4-7 parallel systems, each claiming to be correct.
2. Designate the Canonical System Choose one system as the authority. For most organizations at this stage, the CRM is the right choice — it sits closest to the deal activity and is updated most frequently. But the CRM must be upgraded from a sales tool to a RevOps platform. That means CIPHER's pipeline stages with financial milestone alignment feed the CRM stage definitions. LEDGER's financial model pulls directly from CRM data via API, not from manual exports. CLOSER's deal execution updates happen in the CRM in real time, not in weekly batch updates.
3. Enforce the Single-Write Rule Every piece of revenue data is written once, in one place, by one owner. Stage changes are written by the deal owner in the CRM. Probability weights are calculated by the system based on historical data, not manually overridden. Financial projections are generated by LEDGER's model pulling live CRM data. No one copies data into a spreadsheet for "their own analysis." The single-write rule is the enforcement mechanism. Violate it and you are back to shadow pipelines within a quarter.

// Revenue data contract — every system agrees on these types
interface RevOpsDeal {
  id: string;
  stage: PipelineStage;           // CIPHER: pipeline engineering
  probability: number;            // Calculated from historical conversion
  expectedCloseDate: string;      // CLOSER: buyer signal, not rep optimism
  weightedValue: number;          // stage probability * deal value
  costToClose: number;            // LEDGER: estimated sales cost remaining
  projectedMargin: number;        // LEDGER: revenue minus cost-to-serve
  lastFinancialMilestone: string; // Most recent financially-validated event
  daysSinceAdvancement: number;   // Pipeline hygiene trigger
}