The sales lead says the month was strong, and the CRM agrees. The bookkeeper says revenue was lower, and the accounting software agrees. The project manager says a big job is nearly done, and the project tool shows a completely different picture of what’s been billed.
Three reports. Three numbers. Three people, each sure theirs is right. And the owner in the middle, trying to make a decision with numbers that won’t agree.
What the owner thinks
“One of these is wrong. Which one?” It’s the natural question. Sometimes one really is wrong. A sync broke, a field got entered badly, something got deleted.
But very often, all three are right. They’re just answering different questions.
Tracing why they differ
Here’s where the same “revenue” turns into three numbers:
- Definition. The CRM counts a deal when it’s signed. Accounting counts revenue when it’s invoiced, or when it’s paid. The project tool might count work completed. Same word, three meanings.
- Timing. A deal signed on the 29th shows up in sales this month and in accounting next month. A late invoice shifts revenue across months.
- Scope. One report includes change orders, another doesn’t. One includes deposits, another excludes them. One counts a canceled deal until someone updates it.
- Who enters it. The CRM is updated by salespeople, who are optimistic and busy. Accounting is updated by the bookkeeper, who is careful and behind. The project tool is updated by whoever remembers.
- Actual errors. A broken sync, a duplicate, a missed entry. Real, but usually smaller than the first four.
When I see three reports disagree, I trace the history behind the number instead of arguing with the current total. The answer is almost always in the definitions and the timing.
What I’d investigate
For one important number, I’d sit down with each report and ask:
- What exactly does this count?
- As of when?
- What’s included, and what’s left out?
- Who enters the data, and when?
Then I’d pick a few specific items, a few deals or jobs, and follow them through all three systems. Where they diverge tells you which of the reasons above is driving the difference.
What’s underneath it
Nobody decided which system answers which question. So every system answers every question a little, and everyone trusts the one closest to their own work.
That’s why “which number is right?” is sometimes really a question about how the systems are set up to work together.
What I’d change
- Define the key numbers in plain words. “Booked revenue means a signed agreement.” “Billed revenue means an invoice was sent.” Write them down.
- Assign each number to one system. The CRM answers “what did we sell?” Accounting answers “what did we bill and collect?” The project tool answers “where does the work stand?”
- Reconcile on a schedule. Once a month, compare them and explain the differences. Differences you can explain are fine. Differences you can’t are where the real errors are.
- Retire the reports nobody should use. Every business has one spreadsheet that’s half-right and widely trusted.
What I’d leave alone
Reports that answer a different but valid question. Booked versus billed are both useful. The goal isn’t one number. It’s knowing which number to use for which decision.
The tradeoff
Writing definitions forces conversations people have been avoiding, like what counts as “sold.” Some favorite reports get retired. And monthly reconciliation is one more recurring task. But it’s a lot less work than arguing about it every time a decision comes up.
The pattern
When reports disagree, people pick a team. The fix isn’t picking the right team. It’s deciding what each report is for.
So try this with one number you care about. Write down what it means, in one sentence. Then ask two other people to do the same, separately. If you get three sentences, you’ve found the problem.
If the numbers in your business are fighting, bring them to a Systems Fit Call. If they’re job numbers, Job Cost Ready is built for exactly that.
