What is a single source of truth in SaaS
Asked how many customers the company has, finance says 1,240, sales says 860 and the product team says 2,100. A single source of truth is where the definitions behind each figure are written down, so anyone can see why they differ.
Signs your definitions aren't shared
- Meetings start by reconciling numbers instead of discussing them.
- A customer renews with more seats, and one team books it as an upsell while another books it as a renewal.
- A metric's name says one thing and its formula another, like a "monthly recurring revenue" that includes one-off setup fees.
- A definition changed, nobody knows when, and this quarter is compared with the last one across the break.
One set of definitions, several right numbers
Back to the customer count: finance's 1,240, sales' 860 and product's 2,100 are all correct. Finance counts each entity it invoices, so the subsidiaries of one group count separately. Sales counts the accounts it owns in the CRM, grouped under the parent company. The product team counts paid instances, and one customer can run several, for different teams or regions. The real problem is one word, customer, for three different counts. Deciding which one the company reports, and giving the others their own names, ends the debate. Pipeline works the same way, with sales reading it deal by deal and marketing through an attribution model that splits each deal across the touches before it.
Keep it single
- The definitions teams read differently, such as customer, active user, MQL or upsell
- The reference system for each figure, such as the CRM for opportunities and revenue
- Rule changes, dated and explained
Let it vary
- Views, from daily detail for campaign owners to a summary for leadership
- Readings, deal by deal, by channel or by account
- Periods and level of detail
Why a shared dashboard isn't enough
Product usage, CRM activity and billing usually live in different tools, and each team reads the one it knows best. When the figures don't line up, the meeting turns from "what should we do?" to "whose number is right?". A shared dashboard doesn't settle that while the definitions behind it stay unclear.
An AI assistant doesn't settle it either. Ask it how many customers you have and it will answer with the finance, sales or product count, without saying which. Written-down definitions are what make its answer comparable with everyone else's.
How to start without overengineering it
Write down the definitions of the few metrics that drive decisions, name the reference system for each one, and log every change with its date and reason. Start with the sources that cause the most disagreement, usually product usage and CRM data. Agreement matters more than speed at this stage: the people who own activation, retention and revenue reporting sign off on each definition before it gets automated. For a first view built from exports, see starting to track your PLG funnel.
How to keep definitions applied
A written definition only helps if every report uses it. Once each tool calculates "active user" or "MQL" its own way, the document and the numbers drift apart. What keeps them together is a single place where each rule is set once and applies to every view.
Funnelsight works that way. Rules such as the activation event, what makes a product qualified lead or the attribution model are set once and apply to every view a team builds. When a rule changes, past periods are recalculated or the break is clearly marked. The CRM stays the reference for pipeline and revenue, and Funnelsight shows where its own figures differ from it, and why.
Set your definitions once, and let every team build its own views on them.
Start free trial