Overview
In this episode of The Dashboard Effect, Brick Thompson and Landon Oaks take on a metric that every business tracks and almost every business underestimates: revenue. On the surface it looks like a simple sum. In practice, getting to a number that is accurate, consistent, and agreed upon across the organization requires a level of definitional work that most teams do not anticipate until they are already deep into a reporting project.
The episode is a useful reminder that the complexity in data work is rarely in the technology. It is in the business logic underneath the numbers. See how Blue Margin’s Managed Analytics & Insights brings the discovery process and business logic expertise that turns a deceptively simple metric into a definition the entire organization can trust and report from consistently.
What This Episode Covers
The Discovery Process (1:10 – 1:48)
Revenue is not a universal definition. Even companies in the same industry can have meaningfully different rules for how they handle returns, intercompany sales, or unposted transactions. Before any reporting work begins, there is a discovery process that surfaces those rules and turns them into a consistent methodology. Skipping that step produces numbers that look right until someone asks how they were calculated.
Trade and Quantity Discounts (1:49 – 3:56)
Reporting revenue as gross or net becomes complicated when discounts are conditional, tied to future payment behavior or cumulative volume thresholds that have not yet been reached. Deciding how to handle those cases requires a deliberate choice, and that choice needs to be documented and applied consistently or the same transaction will be reported differently depending on when the report is run.
Seasonal Adjustments
When a sale occurs in one period and delivery happens in another, revenue attribution becomes a timing question with real implications for period-over-period comparisons. The right answer depends on the business model, but there has to be an answer, and it has to be the same answer every time.
Loyalty Programs
Loyalty programs introduce a layer of deferred value that complicates how revenue is recognized. When customers earn points, is that revenue? When they redeem them, how is that treated? These are not edge cases for companies with loyalty programs. They are recurring transactions that need a consistent accounting treatment built into the reporting logic.
Internal Disagreements (3:57 – 4:35)
The CEO, CFO, and head of sales may each have a different mental model of what revenue means, shaped by what they are responsible for and what they are measured on. A unified revenue report requires surfacing those differences and reaching a consensus before the first number is published. A report that different stakeholders interpret differently is not a shared source of truth.
The Impact of Time (4:36 – 5:26)
Retroactive adjustments, like applying a volume discount to past sales after a threshold is reached, can produce confusing and misleading reports if the underlying data model does not account for them correctly. Time-based calculations require careful design to ensure that historical periods remain stable and comparable as new information comes in.
Who It’s For
This episode is worth your time if you are a finance or data leader who has ever had a meeting derailed by two stakeholders citing different revenue numbers, a BI or data engineer about to build a revenue report and wanting to understand the definitional work that needs to happen first, an analyst trying to explain to leadership why a seemingly simple metric is taking longer than expected to get right, or any organization preparing for an audit, due diligence process, or board presentation where revenue figures will face scrutiny.
Why It’s Worth a Listen
Revenue is the metric every organization cares about most, which makes the cost of getting it wrong disproportionately high. This episode does not make the problem seem insurmountable. It makes it visible, which is the first step toward solving it well.
The discussion on internal disagreements is particularly valuable. In most organizations, the revenue definition problem is not a data problem at all. It is a alignment problem that has been deferred because the data team was asked to build the report before the business had agreed on what the report should measure. Brick and Landon name that dynamic clearly and make the case for doing the definitional work first.
For any team that has shipped a revenue dashboard and then watched it become a source of confusion rather than clarity, this episode is a useful diagnostic for understanding what went wrong and how to approach it differently the next time.
