One system of record per fact

A single source of truth means every fact in the business has exactly one system where it is created, updated and trusted — one home for deal values, one for invoices, one for delivery status — and every other place that fact appears is a read-only copy. The rule is "one system of record per fact", not "one system for everything": the failure mode is not having five tools, it is having the same number live in three of them. When two systems disagree about a fact, someone spends an afternoon reconciling them, and the firm quietly stops trusting both.

What goes wrong without it?

The symptoms are familiar in any 5–50 person firm. The pipeline number in Monday's meeting differs from the CRM because two deals live only in a director's spreadsheet. Revenue in the board pack differs from the accounts because someone updated a proposal but not the invoice schedule. A client emails a change and it is recorded in the inbox, nowhere else. None of these are software failures; they are jurisdiction failures — nobody decided which system owns which fact. The cost compounds in three ways: reconciliation labour (hours per month of humans comparing lists), decision latency (numbers are stale by the time they are argued over), and — most corrosive — the moment a leader is caught out by a wrong number, they stop believing all numbers, and management by data quietly reverts to management by anecdote. Trustworthy automated reporting of the kind described in The MD Dashboard Blueprint is impossible on top of contested facts, because a dashboard that draws from two disagreeing systems just publishes the disagreement faster.

Why does this happen to sensible firms?

Because tools arrive one at a time, each carrying its own copy of everything. The CRM holds contacts; so does the mailing platform, the accounts package, and the delivery tool. Each seemed reasonable at adoption. Nobody ever ruled on precedence, so precedence gets decided ad hoc, per person, per Tuesday. Spreadsheets make it worse by being frictionless: exporting a list to "just analyse something" takes seconds, and the export immediately begins to diverge from its source. Commonly, the firm then considers consolidating onto one giant platform — the instinct behind many open-source CRM vs HubSpot evaluations — but platform choice is secondary. A firm that has not assigned ownership of facts will corrupt any platform; a firm that has can run cleanly on modest tools.

How do you install a single source of truth?

The mechanism, step by step:

1. List your fact types, not your tools. Deals and stages, contacts, invoices and payments, delivery status, marketing activity, support history. A whiteboard and an hour.
2. Assign one system of record per fact type. When a fact type has two plausible homes, then pick the system where the fact is born or acted on: deals belong to the CRM, money to the accounts package, delivery to the project tool.
3. Declare everything else a copy. When a fact appears anywhere other than its home — a spreadsheet, a slide, another tool — then it is read-only and disposable, and everyone knows it.
4. Sync one way where copies are needed. When the mailing tool needs contacts, then it receives them from the CRM on schedule, and edits made in the mailing tool do not travel back. One-way flows are boring and debuggable; two-way sync is where data integrity goes to die.
5. Kill the shadow copies. When a recurring spreadsheet exists because a system is awkward, then fix the awkwardness or formally hand the fact to the spreadsheet — a spreadsheet can be a system of record; it just cannot be one of two.
6. Route the edge cases home. When a client confirms a change by email, then the update is entered in the owning system that day; the inbox is a channel, never a record.

The whole exercise fits inside a fortnight for most firms, and most of it is decisions rather than software.

How does reporting change once facts have homes?

Reporting stops being an act of compilation and becomes an act of reading. Because each number has exactly one origin, dashboards can be wired straight to the owning systems and trusted at a glance, which is what makes a sane daily glance, weekly review, monthly close cadence workable — nobody can review weekly what takes a week to compile. Meetings change shape too: when the number on screen is definitionally the number, then discussion moves from "whose figure is right?" to "what do we do about it?", which is the only discussion that was ever worth having.

Where should a growing firm start?

Start with the pipeline, because it is usually the most contested fact set and the one feeding revenue decisions. This matters double for firms switching on systematic demand generation: a working outbound engine — the kind argued for in cold email isn't dead, bad cold email is — produces a steady flow of replies, meetings and deals, and if those land in three inboxes and a spreadsheet, the engine's output evaporates on contact. Give every fact one home, make every copy read-only, and the numbers start telling the truth without anyone compiling them.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks and what to build first.