Why does my team get different numbers from the same data?

Almost always it comes down to undefined metrics. Revenue can mean gross sales, net of returns, or net of returns plus shipping — all from the same spreadsheet depending on which columns you sum. Until your team agrees on one definition and uses it consistently, every person who pulls the number will get a slightly different answer.

How do I get my team to report the same numbers?

The most reliable fix is to define the metric where the answer is produced, not in a separate document. When every question goes through the same tool and that tool knows your definitions — revenue excludes refunds, active customers means purchased in the last 90 days — every answer comes out consistent without anyone having to remember a style guide.

Is a shared metrics document enough to fix inconsistent reporting?

Rarely. A doc captures intent but breaks down in practice: people forget to read it, it goes stale as the business changes, and it doesn't stop anyone from pulling a number a different way. The definition needs to live in the system that produces the answers, not in a Notion page that's two clicks away.

What is Quiriz Company Context?

Company Context is a feature in Quiriz that lets a company admin define business metrics, key terms, and context about the business in one place. Every answer Quiriz produces — whether in the web app, Slack, Excel, or Google Sheets — uses those definitions automatically. The whole team gets consistent numbers without anyone having to remember how a metric is calculated.

Home / Blog / Why Your Team Gets Different Numbers

Guide · 2026

Why your team gets different numbers from the same spreadsheet

When three people pull revenue from the same file and come back with three different answers, the data is almost never wrong. The definitions are.

By the Quiriz Team · Published August 2, 2026 · 6 min read

It happens in almost every small business eventually. Someone asks for revenue in the Monday standup. One person says $84,000. Another says $91,000. A third — who pulled the number ten minutes earlier from what looks like the same spreadsheet — says $88,500. The meeting stalls. Everyone opens their laptop. Half an hour later, nobody is quite sure which number is right.

The spreadsheet is not broken. The data is probably fine. The problem is that nobody ever agreed on what "revenue" means.

Why this keeps happening

A number like "revenue" sounds unambiguous until you try to write a formula for it. Even in a single spreadsheet, reasonable people will make different choices:

Refunds included or excluded? One person sums the order_total column. Another subtracts the refund_amount column. Both are defensible.
Shipping counted? It's revenue on the books, but some teams strip it out for margin analysis and forget to add it back when reporting top-line.
Date range definition. "This month" could mean the calendar month, a fiscal month, or the rolling last 30 days — all three produce different numbers on the 15th.
Order status. Do pending orders count? Partially fulfilled? Draft orders that were never completed?

None of these are mistakes. They are choices. And when nobody has written down which choice the company made, every person pulls the number using their own assumptions. The spreadsheet returns the correct answer to the question each person actually asked — those questions just weren't the same question.

The "active customers" problem

Revenue is one example but it is rarely the only one. "Active customers" is worse. Is an active customer someone who has ever bought? Someone who bought in the last year? The last 90 days? Someone with a subscription regardless of last purchase date? A company of ten people will produce ten definitions if nobody pins one down.

The same ambiguity shows up in churn rate, average order value, margin, and almost any metric that requires a decision about which rows to include and how to combine them. The spreadsheet answers exactly what you ask. If the question is not precisely defined, the answer will not be either.

Why a shared metrics document doesn't fix it

The usual response is to write a definitions document. A Notion page, a Google Doc, a section in the team wiki: "Revenue = gross sales minus refunds, including shipping, calendar month." It is the right idea and it almost never works.

People forget to read it. It goes stale within six months as the business changes and nobody thinks to update it. New hires skip it. And even people who know the definition still write their own formula from scratch and occasionally miss a column. The document captures intent. It does not enforce anything.

The root problem is that the definition lives in a separate place from where the answer is produced. Someone still has to carry the definition from the doc to the spreadsheet formula, and that handoff is where the consistency breaks.

What actually works: define it where the answer comes from

The reliable fix is to move the definition upstream — into the system that produces the answer — so that the definition is applied automatically every time anyone asks the question, regardless of which tool they are using or whether they remember the style guide.

This is what Quiriz built its Company Context feature to do. A company admin opens the Manage Organization page and writes the metric definitions once:

Revenue: sum of order_total minus refund_amount where order_status = 'complete'. Uses the calendar month unless a date range is specified.
Active customers: customers with at least one completed order in the last 90 days.
Gross margin: (revenue minus cost_of_goods) divided by revenue, expressed as a percentage.

From that point, every answer Quiriz produces uses those definitions — in the web app, in Slack, in the Excel add-in, in Google Sheets. A team member asks "what was revenue last month?" in plain English and gets a number. Another team member asks the same question from Slack two days later. They get the same number, calculated the same way, because the definition is applied at the source, not remembered by the person asking.

You do not write formulas or SQL. You write plain English: "Revenue is gross sales minus refunds, not including pending orders." Quiriz's Company Context reads that, and when it builds the query that answers a question, it applies your definition automatically. The admin writes it once. The team never has to think about it again.

Beyond revenue: context the whole team benefits from

Company Context covers more than metric formulas. You can add plain-English context about the business — your fiscal year, your main product lines, the fact that you have two separate customer segments that should never be compared directly — and Quiriz will account for it in every answer it produces. It is the kind of thing that an experienced analyst would carry in their head, now written down in one place and applied consistently.

The practical result is that a new hire on day one, asking questions through Quiriz, gets answers calibrated to how your business actually works — not generic answers that happen to match your column names.

What changes for the team

Before: someone asks for a number, three people pull it three different ways, and the meeting stops while the team figures out which version to trust.

After: questions go through one tool. The tool knows your definitions. Every answer comes from the same logic. The meeting moves on.

The analyst or ops person who usually resolves these discrepancies stops fielding the "wait, why is your number different from mine?" calls. The team gets faster. And because everyone trusts the numbers, the conversation shifts from debating figures to deciding what to do about them.

How to get started

If your team runs on spreadsheets and you recognize the Monday standup problem, the practical starting point is to write down your three or four most-argued-about metrics in plain English before you do anything else. What is revenue, exactly? What is an active customer? What counts as a churn?

If you use Quiriz, those definitions go into Company Context on the Manage Organization page. If you don't, they still belong somewhere that is part of your toolchain — not a separate doc that requires a deliberate detour to consult.

The free tier at app.quiriz.co/try lets you load a spreadsheet and ask questions in plain English before connecting any definitions. The Company Context feature is available on paid plans. I would appreciate your feedback if you try it, especially if the definitions you write don't produce what you expected — that's the part I most want to get right.

Common questions

Do I have to write SQL or formulas to define a metric?

No. Company Context is plain English. You describe the metric the way you would explain it to a new team member — "revenue is gross sales minus refunds, calendar month, completed orders only" — and Quiriz applies that when it builds the query. You don't need to know which column names are involved; you can reference them if it helps, but a plain description works too.

What if my definition of revenue changes?

You update it in one place on the Manage Organization page. Every answer produced after that uses the new definition. You don't need to retrain anyone or update a dozen separate formulas.

Does this work in Slack too?

Yes. The Quiriz Slack bot uses the same Company Context as the web app, the Excel add-in, and the Sheets add-on. A team member asking in Slack gets the same numbers as someone asking in the app.

What if we don't use Quiriz?

The core advice still applies: write your metric definitions somewhere inside your analytics toolchain, not in a separate document. Whatever tool produces your answers should know your definitions, not rely on the person asking to remember them. That is the structural fix regardless of which software you use.