Why Your Team Gets 3 Different Answers to the Same Question

Ask your finance team "what was revenue last month?" Then ask your sales team the same question. Then check the dashboard.

If you got three different numbers, you're not alone. This is one of the most common — and most quietly damaging — data problems in growing companies across Singapore and Southeast Asia. It erodes trust, wastes time in meetings, and leads to decisions made on whichever number the loudest person in the room happens to quote.

The good news: the fix is simpler than you'd think. And it has nothing to do with buying better tools or hiring a data engineer.

Why It Happens

The root cause is almost never bad data. It's undefined terms.

"Revenue" Means Different Things

Take the word "revenue." Depending on who you ask:

• Sales counts it when the deal is signed (bookings)
• Finance counts it when the invoice is paid (cash received) or when the service is delivered (accrual accounting)
• The dashboard might count it when the order is placed (gross transaction value)

All three numbers are "correct" — they're just answering slightly different questions. The problem isn't that anyone is wrong. It's that nobody agreed on which definition to use when.

It Gets Worse at 30-50 People

Small teams don't usually have this problem. When five people sit in the same room, everyone knows what "revenue" means because they've all been talking about the same spreadsheet for months.

But as companies grow past 20-30 people, teams start building their own reports with their own definitions. Marketing defines "customer" differently from support. Product defines "active user" differently from sales. Nobody realises they've diverged until someone puts all the numbers in one presentation and the board asks why nothing adds up.

The Hidden Costs

This problem is expensive even though it doesn't show up on any invoice:

• Reconciliation meetings — hours spent each month figuring out why numbers don't match
• Delayed decisions — "let's table this until we figure out the real number"
• Dashboard distrust — people stop checking dashboards because "the numbers are always wrong" (and when nobody trusts the dashboards, you end up with dashboard sprawl as teams build their own)
• Duplicate work — multiple teams building their own reports because they don't trust each other's

The 1-Hour Fix: A Metric Definition Exercise

You can resolve the most common disagreements in a single meeting. Here's how.

Before the Meeting

Pick your 5-6 most important business metrics. These are typically:

1. Revenue (monthly/quarterly)
2. Customer count (active customers)
3. Customer acquisition cost (CAC)
4. Churn or retention rate
5. Gross margin or profitability
6. One metric specific to your business (e.g., average order value, utilisation rate, NPS)

Invite one representative from each team that uses or reports these numbers. Keep it small — 4-6 people is ideal.

The Meeting: 60 Minutes

First 10 minutes: For each metric, have every person write down their definition independently. Don't discuss yet — just write.

Next 30 minutes: Go metric by metric. Read each person's definition aloud. You'll quickly see where definitions diverge. For each metric, agree on:

• Name — What do we call this? (Sounds obvious, but "revenue," "sales," and "bookings" are often used interchangeably and shouldn't be.)
• Definition — One plain-language sentence. "Monthly revenue is the total value of invoices issued in the calendar month, excluding refunds and credits."
• Source — Which system is the source of truth? "Xero is the source for revenue. Not the CRM, not the sales spreadsheet."
• Owner — Who is responsible for this number being correct? "Finance owns the revenue number."
• Frequency — How often is it updated? "Monthly, finalised by the 5th business day."

Last 20 minutes: Document everything in a shared spreadsheet or document. Assign someone to circulate it. Agree on a date to review (quarterly works well).

What the Output Looks Like

A simple table is all you need:

This isn't a data warehouse. It's not a BI tool. It's a shared agreement about what words mean. And it solves 80% of the "different teams, different numbers" problem.

What Changes After

Companies that go through this exercise typically see three immediate improvements:

Meetings get shorter. When everyone agrees on definitions and sources, you skip the 20-minute preamble of "wait, where did you get that number?"

Dashboard trust goes up. When there's one agreed source for each metric, dashboards become reliable. People actually start checking them.

Better decisions, faster. When the leadership team can look at a number and trust it, they spend their energy on "what should we do?" instead of "is this even right?"

When Definitions Aren't Enough

The metric definition exercise solves the most common problem, but sometimes the issue goes deeper:

• Data is genuinely wrong — typos, missing entries, broken integrations. If the underlying data has quality issues, agreed definitions won't help. You need a data quality cleanup — our guide on running a data audit in a week covers how.
• Systems don't talk to each other — if you need to combine data from three tools manually, errors creep in. This is an integration problem that needs technical work.
• Nobody maintains the definitions — if you do the exercise and then never revisit it, definitions drift as the business changes. Put a quarterly review on the calendar.

Start With Revenue

If one hour feels like too much to commit, start with just one metric: revenue. Get finance and sales in a room for 20 minutes. Write down the definition, the source, and the owner. Put it somewhere everyone can find it.

Once you've done it for revenue, you'll see the value — and the next four metrics will follow naturally.

If your team can't agree on the numbers, the problem isn't the data — it's the definitions.