Why marketing, sales and finance report different numbers, and the one document that fixes it
Three teams, three definitions of a lead, a customer and revenue. The KPI definitions document — what each metric means, where it comes from, who owns it — and how to keep it enforced by the reporting itself.
23 Dec 2025 · 2 min read · by HeiSyn
The marketing deck says two hundred leads; the sales report says eighty; finance recognises revenue on a different date from the CRM. Nobody is lying — each team defined the word differently and built its report from a different system. The argument recurs every month until the definitions are written down once and the reports are built from the same source.
Write the definitions
For every metric on the Monday page: the name, the plain-language definition, the exact rule (which records, which statuses, which dates), the source system, the owner, and the known limitations. 'Lead: a contact created in the CRM with a work email and a source, excluding existing customers and internal test records.' One page per metric is too much; one line each, in one document, is right.
Build reports from the definitions
Each definition maps to one query in the reporting layer, and every dashboard uses that query. When marketing and sales both read 'leads' from the same query, they get the same number. If a team wants a different number, it is a new metric with a new name, not a redefinition.
Version and date the document
Definitions change — a new stage, a new product line, a change in what counts as active. Each change gets a date and a note, and the reports show a marker at the change so trends are not misread. The document is owned by whoever owns revenue operations, and reviewed quarterly.
Make disagreement productive
When numbers still disagree, the document makes it a specific question — 'which definition is this report using?' — rather than a turf dispute. Most of the time the answer is a report that drifted from the definition, and the fix is a query, not a meeting.
Questions people ask next
- Who arbitrates when teams disagree on a definition?
- The owner of revenue operations, or the finance lead where money is involved, with the decision written into the document. The argument should happen once, in the document, not monthly in the meeting.
- How detailed should each definition be?
- Detailed enough that two people could build the same query from it: which records, which statuses, which date field, which exclusions. If a definition fits in one clear sentence plus a rule, it is right; if it needs a page, the metric is probably two metrics.
- What if finance's revenue and the CRM's revenue can never match?
- They should not match exactly — recognition timing differs — and the document says so, with the expected difference explained. What must match is the list of customers and contracts behind them; reconcile that, and the timing difference is understood rather than argued about.
Want this built for your team?
A free scoping call: we map your motion, name the number that should move, and quote a fixed-scope build.
Related
- Reporting go-to-market to a board or investors: the numbers, the cadence and the honesty
- Data quality monitoring for GTM systems: catching the silent failures
- Sales activity metrics without the micromanagement: what to track, what to show, what to leave alone
- Alerts on revenue metrics: knowing on Tuesday what you would otherwise learn at quarter end
