Three systems, one metric, three answers. All three were right.
By Meet Patel · 2026-08-31 · updated 2026-08-31
Summary
Net revenue retention read 104%, 111% and 97% across three systems, all computed correctly. They disagreed about a denominator, not a bug. A fourth dashboard adds a fourth number; reconciling the definition before reporting is the step that is missing.
Net revenue retention read 104% in the warehouse, 111% in the CRM and 97% in the finance model.
All three were computed correctly.
That is the sentence that took me longest to accept, because the instinct in the room was to go looking for the broken one. There was no broken one. Three competent systems, three correct calculations, three different answers.
They disagreed about a denominator
The specific argument was what a mid-term downgrade does to the base you are measuring against.
The CRM treats the account as it was sold, so a customer who downgraded in month seven is still measured against what they originally signed. Generous, and defensible if you think of retention as an account-level story.
Finance treats the downgrade as the moment the contract changed, so the base moves. Conservative, and defensible if you think retention should reflect what you are actually going to bill.
The warehouse landed somewhere in between, because whoever wrote that model made a reasonable choice about edge cases two years ago and then left.
Nobody was wrong. Nobody had been asked.
A fourth dashboard makes this worse
The natural response is to build the real one. A single source of truth. One place everyone looks.
Unless the definitional argument is settled first, that produces a fourth number, and now there are four positions in the room instead of three. The plumbing was never the problem. Pointing every tool at one warehouse relocates the disagreement into the warehouse, where it becomes a modelling decision made by whoever writes the query.
The edge cases still have to be ruled on by a person, out loud, and written down somewhere the next person can find. That is governance work wearing a data hat, and it is nobody's favourite afternoon, which is exactly why it does not happen.
Reconcile before you report
The ordering matters more than it looks.
If you monitor first and reconcile later, every alert fires on a figure that at least one other system disagrees with. Somebody says "that's not what the CRM shows" and the next twenty minutes go on establishing facts rather than deciding anything. The alert made the meeting worse.
Reconcile first and the alert means something, because the number it fired on is the number the company has agreed to use. That is the entire difference between a monitoring tool and something worth acting on.
It is also why I put reconciliation ahead of monitoring in how I think about this whole category. The full definition is here: autonomous decision intelligence.
The cheap version you can run this week
Pick your most-quoted metric. One.
Ask three people who own three different systems to send you their number for the same period, separately, without discussing it. Do not warn them what it is for.
If the three agree, you have learned something good and it cost you an email. If they do not, you have found the argument nobody has had, and you now know which one it is. Either outcome is worth more than the dashboard you were about to commission.
We ran it. They did not agree. We were nine days from putting one of those numbers in front of people whose job is to check.
Frequently asked questions
Why do the CRM, the warehouse and finance report different numbers?
Usually because each encodes a different business definition rather than because one has a bug. Systems are bought at different times for different jobs, each makes reasonable local choices about edge cases like mid-term downgrades, and nobody ever ruled on which choice is the company's.
Does a single source of truth fix conflicting metrics?
Only if the definitional argument is settled first. Pointing every tool at one warehouse moves the disagreement rather than resolving it, because the edge cases still have to be decided by a person and written down. Reconciliation is a governance act, not a plumbing one.
Written by Meet Patel — founder of Company 8, building Dan (usedan.com). Dubai, UAE.