A number nobody can define is worse than no number at all — it lends false confidence to the wrong decision.
We’ve all seen this kind of report in Bangladeshi real estate sales reporting. A big number. A label underneath it. That’s it.
Say it reads — “Total leads — 161”
Now, a very simple question. What is this 161? Leads for the whole company? Or just that one area? 161 new leads that came in this month? Or a total of 161 leads currently sitting in that area right now?
It sounds like a minor question. But a different answer to each of these leads to a different decision. And this is exactly where a report’s biggest problem begins.
If a number doesn’t come with a clear scope, a clear time window, and a clear definition of what’s actually being measured, then no matter how clean it looks, it isn’t clear at all.
There are two kinds of numbers. One answers — “how many exist right now?” That’s a stock. For example, you currently have 161 active leads in hand today.
The other answers — “how many came in or happened within a given period?” That’s a flow. For example, 161 new leads arrived in August.
Both numbers can happen to be 161. But they’re not the same thing. One is a snapshot of right now. The other is what happened across a stretch of time.
The trouble starts when a report blends the two together.
Say a card reads — “August Leads: 161” — but the 161 is actually the count of leads active right now. Management could easily read that as 161 new leads arriving in August.
From there, the numbers for marketing performance, salesperson performance, and conversion rate can all end up skewed.
One mislabeled number is enough to send the entire discussion in the wrong direction.
Say a dashboard proudly displays — “Contact Rate: 90%” — sounds great. But 90% of what?
90% of leads that came in this month? Or 90% of every lead that’s ever entered the system in the past year? Or 90% of currently active leads?
Say 100 leads came in this month. 90 of them got contacted. Contact rate: 90%. Fine.
But at that same company, if 5,000 leads came in over the past year and 4,500 of them got contacted at some point, that also works out to a 90% contact rate.
The same percentage. But a completely different story.
So a percentage on its own isn’t really information. You need to know — 90% of what? Where’s the denominator?
Because a percentage without a denominator isn’t a metric. It’s the start of an argument.
There’s something else we rarely see in a report — when was this number last updated?
Say a manager builds the report on the last day of the month. Collects the data. Reconciles it in Excel. Calls a few salespeople to check on some numbers. A few hours later, the report is ready. Then it goes into the management meeting.
But in that time, new leads have come in. Some leads have been contacted. Some have been lost. Some customers have done site visits.
Which means by the time the report reaches the table, the business is no longer in the state the report is describing.
And decisions still get made on top of that report anyway. And nobody’s asking one particular question —
“How old is this data, really?”
Accuracy isn’t the only thing at stake here. How much of someone’s time it takes to build this report is a cost too.
When a manager or coordinator sits for hours at month-end collecting data, matching Excel sheets, reconciling numbers, and building the report by hand — the company is really having a person do a reporting system’s job.
Doing it once isn’t a problem. But every month? By year-end, you’ll find several full working days of one person’s time have gone into nothing but building this report.
And the strange part is — someone has to sit down at month-end for something a system could do instantly.
A good report doesn’t just show numbers. Every number carries a clear identity — is it a stock or a flow? What’s its scope? Which period’s data? And if it’s a percentage — a percentage of what?
When these are clear, management looking at the same number understands the same thing.
And another important job of a good system is consistency. If the same metric shows up in two places on a dashboard, both places need to show the same number with the same meaning. Because —
One number can’t mean two different things.
In Sofia, every metric’s definition is fixed in a single place and used consistently across every dashboard.
So when management looks at a number, they’re not just looking at a number. They know what’s being measured, whose data it is, which period it covers, and what the number is actually saying.
In the end, good reporting isn’t complicated. Showing the right number isn’t enough — what that number means has to leave no room for misunderstanding either.