← All case studies
Volume 1 · Chapter 2 · Case Study · Business Intelligence & Analytics

Enterprise Revenue Intelligence Platform

Business Intelligence & Executive Reporting

Leadership lacked a unified, real-time view of revenue performance, utilization, and delivery health. This engagement replaced fragmented manual reporting with a governed, automated executive reporting layer built on SQL, BigQuery, and Looker Studio.

Context
LearningMate (Straive) — Executive Leadership
Period
2022 – 2025
Tools
SQL, BigQuery, Looker Studio, REST APIs

$3–5M

Annual revenue recovery unlocked

Business Challenge

Reporting was assembled by hand from disconnected spreadsheets, and every analyst kept a slightly different version of the truth. Two people looking at "this quarter's revenue" in the same meeting could easily be looking at two different numbers, refreshed on two different days, built on two slightly different rules for what counted.

Discovery & Approach

Work began with stakeholder interviews to pin down exactly what executive reporting needed to answer, and which KPIs actually drove decisions rather than simply being available to look at. Current-state reporting processes were mapped end to end, pain points were logged, and success criteria were defined in terms leadership would actually recognize as "solved."

  • Conducted stakeholder interviews to define reporting requirements and executive KPIs
  • Mapped business processes and designed future-state reporting workflows
  • Defined data models spanning SQL and BigQuery, feeding executive dashboards built in Looker Studio
  • Automated reporting workflows to improve visibility and reduce manual effort

Business Outcomes

  • Improved executive decision support through centralized, single-source-of-truth reporting
  • Enabled proactive revenue monitoring and stronger operational governance
  • Recovered revenue that the old spreadsheet reporting had been quietly losing track of
  • Cut manual reporting effort and turnaround time, freeing analysts to spend their week on analysis instead of data assembly
  • Established a reusable analytics architecture — SQL feeding BigQuery feeding Looker Studio — that later reporting projects could build on directly

Exhibit 2.1

Illustrative executive dashboard layout (sample data, representative of the Looker Studio reporting surface)

Lessons learned

  • A dashboard is only as trustworthy as the data model underneath it. Most of the actual effort in this engagement went into agreeing on definitions, long before a single chart got built.
  • Automating a report doesn't just save time; it removes the quiet, cumulative risk of every analyst maintaining a slightly different version of "the numbers."
  • Executive buy-in came less from the visuals and more from the fact that, for the first time, everyone in the room was looking at the same figure.

Consultant's note

"The unglamorous part of this project was reconciling three different definitions of "active client" across three teams, and it took longer than building the dashboard itself. That's usually where the real value in a BI engagement hides: not in the chart, but in the argument you have before the chart gets built."

Skills demonstrated

  • Stakeholder Management
  • Requirements Gathering
  • Business Intelligence
  • Dashboard Design
  • Executive Reporting

Part of Volume 1Business Transformation & Technology Consulting.