Dueling Dashboards Were Never About the Tools

Gohvio · 2026-06-01

Same week. Same company. Two numbers.

Marketing pulls up their attribution dashboard. They generated $50,000 in revenue from the spring campaign.

Finance pulls up the bank reconciliation. They saw $30,000 hit the account from those same customers.

Both teams are in the same meeting. Both teams are looking at their own dashboards. Both teams are right, by their own definitions, against their own data sources, using their own attribution windows.

The CEO asks: "Which is it?"

Nobody knows. The meeting becomes about reconciliation instead of decisions. The product launch gets delayed. The marketing budget review gets postponed. The forecast gets fudged to split the difference.

This is the dueling dashboards problem. And it has almost nothing to do with the dashboards themselves.

Where the disagreement actually comes from.

Marketing's $50,000 number includes:

• Every deal that touched a campaign asset in the last 90 days, attributed at the time the deal closed
• Multi-touch credit divided across the customer journey
• Revenue counted at the contract value
• Customers grouped by acquisition campaign, not by parent account

Finance's $30,000 number includes:

• Only cash that hit the bank during the reporting period
• One customer per legal entity, regardless of parent-child relationships
• Recognized revenue per the revenue policy, not contract value
• Net of refunds, credits, and any clawbacks already processed

Both numbers are correct. They're answering different questions.

Marketing is answering: "What revenue did my campaigns influence?" Finance is answering: "What money did we collect this period?" Those are two different metrics. The fact that they're both labeled "revenue" on two different dashboards is the bug.

Buying a better dashboard doesn't fix this.

This is the trap most companies fall into. They see two dashboards disagreeing and they assume the answer is one bigger, better dashboard. So they license Tableau, or Looker, or whatever the latest unified BI vendor is selling. They invest six months migrating everyone's reports. They run a launch event.

And then, six months later, Marketing pulls up the new dashboard and Finance pulls up the new dashboard, and the numbers still don't match.

Because the dashboards weren't the problem. They were the display layer for a problem that lives upstream.

The problem is that two teams used the same word, "revenue", without ever agreeing on the underlying definition, the source of truth, or the attribution rules. A new dashboard inherits all of those disagreements. It just inherits them in a prettier interface.

What actually solves it.

The fix is a definition contract that lives upstream of every dashboard.

A definition contract for revenue might read:

Recognized Revenue (Company Standard) The value of services delivered in the reporting period, per ASC 606. Source of truth: NetSuite GL, account 4000-series. Refresh: daily at 02:00. Owner: VP Finance. Excludes: contract value not yet delivered, refunds, clawbacks. Includes: usage-based revenue at the rate billed.

Campaign-Influenced Revenue (Marketing View) Recognized Revenue for any customer who touched a tracked marketing asset within the trailing 90 days before close. Uses Recognized Revenue as the base number, then filters by campaign touch. Source of truth: HubSpot + NetSuite join. Refresh: weekly. Owner: VP Marketing. Excludes: customers with zero tracked touches.

Two definitions. One foundation. The same Recognized Revenue number sits underneath both.

When Marketing reports "$50,000 of campaign-influenced revenue," Finance can see exactly which dollars are being counted, and confirm that they're the same dollars Finance is reporting at the company level. The disagreement disappears. Not because someone won. Because the math is reconciled at the source.

Why this is so rarely done.

Writing definition contracts is unglamorous. It's not a tool. It's not a launch. It's not a project anyone gets promoted for kicking off.

It's a series of uncomfortable conversations between Marketing and Finance about what they actually mean when they each say "revenue." It's the documentation work that everyone agrees should happen and nobody schedules.

But every quarter you skip it, the gap compounds. Definitions drift further. New tools get plugged in with new pre-built schemas. New people inherit the disagreement without anyone telling them it exists.

The companies that finally do it are usually the ones who got embarrassed in a board meeting. The ones that get ahead are the ones who do it before the embarrassment.

A 90-minute starting wedge.

You don't need a project. You need a meeting.

Pull Marketing, Sales, Finance, and Customer Success leads into a room for 90 minutes. Bring a list of the ten terms your dashboards most disagree about. Customer. MQL. Revenue. Pipeline. Churn. ARR. Deal. Account. Active user. Renewal.

For each term, ask each team: what do you mean by this? Write down their answer verbatim.

You will find disagreement on most of them. That's the point. Mark which ones are the most expensive disagreements, the ones that affect forecasts, headcount, board decks. Pick the top three to standardize first.

For each of the three, write a one-paragraph definition contract. Source of truth. Owner. Refresh cadence. What's included. What's excluded.

That's the document that has to exist before any dashboard can be trusted.

The bottom line.

Dueling dashboards aren't a tooling problem. They're a definitions problem with a tooling symptom. You can't out-spend the disagreement. You have to write it down, reconcile it, and operationalize the reconciled version.

The dashboards then become what they were always supposed to be, views of an agreed truth, not arenas for arguing about what truth is.

Download the Gohvio Data Scoring Framework, free, no email gate.