The One Dashboard Every Department Needs to Share. Nobody Has Built It.

Gohvio · 2026-05-18

Every department has a dashboard.

Marketing has their lead and pipeline view. Sales has the pipeline and forecast. Finance has ARR, burn, and AR aging. Customer Success has health scores and NRR. Legal has a contract tracker in a spreadsheet nobody else can access.

None of these dashboards show the same company.

Marketing's pipeline number is different from Sales'. Finance's revenue number doesn't match the CRM. CS's NRR metric uses a different definition than what Finance reported last quarter.

And nobody has a single view that shows all of them together.

That view -- the one the CEO actually needs -- almost never exists. Here is what it looks like, why it's hard to build, and what it takes to get there.

What the org-wide dashboard shows

Six numbers. Updated continuously. All traceable to a source.

1. Revenue: recognized this month vs. plan Not ARR. Not bookings. Revenue recognized -- what you actually earned and can report. With variance explained: which deals over or under-performed, and why.

2. Pipeline: committed vs. total, with freshness indicator The total pipeline number everyone reports. And next to it, the number filtered for activity in the last 30 days -- the version the CEO would commit to. The gap between the two is the phantom pipeline signal.

3. Burn: actual vs. plan, by department Where the money is going, against where it was supposed to go. Not just the total -- the breakdown. If marketing is over by $80K and engineering is under by $20K, the CEO needs to see that, not just the net $60K variance.

4. NRR and GRR: rolling 12-month, with churn breakdown Is the business growing from its existing customers or contracting? And within the churn, which segments are churning, at what size, and with what renewal pattern?

5. CAC and LTV: by channel, trending How much does it cost to acquire a customer through each channel, and what is the lifetime value from each? Is the ratio improving or deteriorating?

6. Data confidence score This is the one nobody shows -- and it is the most important.

A number in the bottom corner of the dashboard: how confident is the team in the underlying data quality for each metric above? Are the pipeline numbers based on validated, de-duped accounts? Is the NRR calculated on clean cohort data? Is the revenue reconciled between the CRM and the billing system?

Without this, the dashboard shows six numbers. The CEO privately adjusts two of them. The board adjusts three more. Nobody operates from the same reality.

Why this dashboard doesn't exist at most companies

Building this dashboard is technically straightforward. Any modern BI tool can display these six metrics.

The problem is the data infrastructure:

Revenue requires a clean CRM-to-billing link. The closed-won deal in Salesforce needs to connect to the invoice in NetSuite, which needs to connect to the revenue recognition schedule in the finance system. At most companies this chain has at least one manual step. The manual step is why reconciliation takes 48 hours at month-end.

Pipeline quality requires continuous dedup and activity monitoring. The phantom pipeline number requires knowing which deals haven't had activity in 30+ days and which accounts are duplicates. Most CRMs have this data -- it's just not surfaced continuously.

Burn by department requires consistent cost tagging. Every expense needs to be tagged to the right cost centre at the time of the transaction, not during the close. Most companies clean this up monthly during finance close. Until then, the burn view is inaccurate.

NRR by cohort requires clean customer acquisition dates. If your CRM has duplicate accounts, wrong close dates, or customers who appear in multiple cohorts because of data entry errors, the NRR calculation is wrong from the start.

CAC by channel requires clean attribution. Attribution requires that every deal has a documented originating source that is consistent with how marketing tracks it. Most companies have this for 60% of deals. The other 40% are "direct" or "unknown."

Data confidence requires an audit process. Someone has to check the data quality of each metric before the dashboard goes live. Most companies have no systematic process for this.

The sequence for building it

You cannot build the org-wide dashboard before fixing the data. But you can start building both simultaneously.

Step 1: Pick one metric and make it trustworthy. Pipeline is usually the best starting point because it touches the most teams and creates the most cross-functional benefit when it's clean. Deduplicate the accounts. Remove stale deals. Add a freshness indicator. Get sales leadership to commit to the filtered number. That one trustworthy number creates the template for every other metric.

Step 2: Document the definitions. Pipeline, MQL, closed-won, churn, NRR -- one written document, one version, all teams reference it. This sounds simple. It is the step most companies skip. Without it, every metric will be recalculated differently by every team, and the org-wide dashboard will have a different number than each department's own view.

Step 3: Build the data links. CRM to billing. Billing to finance. Finance to the dashboard. Automate as much as possible. Every manual data transfer step is a place where the org-wide dashboard goes out of date.

Step 4: Add the data confidence indicator. Even before everything is fully automated, publish the data confidence level for each metric. "Pipeline: 85% confidence (3 dedup issues under review)." "Revenue: 100% confidence (reconciled against billing)." This creates accountability for improving data quality -- and honesty about where the gaps still are.

To understand the data work that goes into company-wide reporting, read: EBITDA Reporting for Exit-Ready Companies, Board Decks: Finance KPIs That Actually Matter, and How to Reverse-Engineer Your Data Problems.

The org-wide dashboard is not a project for next quarter. It starts today, with one metric, one clean definition, and one trustworthy number that everyone in the company can look at and agree on.

Everything else follows.

Gohvio is free to try -- gohvio.io