Skip to content
Ocean Lyra Analysis
Back to Blog

Case Studies

From 40 Dashboards to 4: A SaaS Company's Data Consolidation

By Ocean Lyra Analysis · Aug 17, 2026 · 3 min read

We detail how one SaaS client achieved significant data clarity by drastically reducing their operational dashboards, improving decision-making and efficiency.

We recently guided a SaaS client through a necessary, if initially painful, data consolidation project. They came to us with 40 distinct dashboards.

Forty dashboards. For a company with fewer than 100 employees.

This was not unique data. This was often the same metric, presented slightly differently, on different platforms. A sales dashboard, a marketing dashboard, a product usage dashboard, and then a combined 'executive summary' dashboard that pulled from all three, often with conflicting numbers.

The Problem: Data Proliferation

Our initial audit. The sheer volume created more confusion than clarity. Teams spent hours reconciling numbers instead of analyzing them. Trust in the data eroded steadily.

  • One metric, 'new user sign-ups', appeared on five different dashboards, each sourced differently.
  • Sales leadership had their own custom reports, bypassing the official dashboards entirely.
  • Engineers built bespoke monitoring tools, duplicating efforts already handled elsewhere.

Our Approach: Ruthless Prioritization

We started with a simple question: What are the three most critical business questions this company needs to answer daily, weekly, and monthly?

This exercise forced a confrontation with what was truly essential versus what was merely 'nice to have.' It cut through the noise quickly.

The consensus: Revenue, customer retention, and product engagement. Everything else, we argued, was a supporting detail or a deeper dive.

The Outcome: Four Core Dashboards

We consolidated. After weeks of interviews and data mapping, we built four dashboards:

  • A 'Revenue Health' dashboard, covering sales, ARPU, and churn.
  • A 'Customer Experience' dashboard, tracking retention, support tickets, and NPS.
  • A 'Product Engagement' dashboard, detailing feature usage and activation.
  • A 'Strategic Overview' dashboard, combining high-level metrics from the other three.

The process was not without resistance. Some teams felt their specific needs were being overlooked. We showed them how their metrics, while important, were derivatives of the core four.

Now, the company operates with a clear, unified view. Decision-making is faster. Discussions are rooted in shared, consistent numbers. This wasn't about less data; it was about more effective data.

Want this kind of clarity on your own reports?

We rebuild executive packs and dashboards for a living. Send us what you've got. We'll tell you, honestly, what we'd change.