CASE FILE 12CLIENT GENERALISEDALL DATA MOCKED

The whole business on one page.

A marketing agency had five departments reporting in five different tools. This project built the single page the leadership meeting now starts with: revenue, clients, costs and people.

CLIENTMARKETING AGENCY · C-SUITE
MODELWHOLE-BUSINESS REPORTING
STACKMKTG · SALES · FIN · HR · LOOKER
ENGAGEMENT5 PHASES · FULL SYSTEM
STATUSLIVE · AUTOMATED
THE BOARD — OVERVIEWAI-BUILT · LIVE HTML
EXHIBIT A
1

The big chart shows revenue and costs over twelve months.

2

The donut shows how much revenue is recurring vs one-off projects.

3

Costs, people and top clients all sit on the same page as growth.

The Brief

Five departments, five versions of the truth.

Marketing had a deck, sales had a deck, finance had a spreadsheet. The leadership meeting spent its first half arguing about whose numbers were right.

We pulled every department into one model and calculated the tricky numbers — client revenue, churn, margins — once, in SQL. Now everyone works from the same page.

THE GOAL: start every leadership meeting on the same page — literally.

✗ THE PROBLEMS

  • Five departments, five sources of truth
  • Client MRR and churn hand-calculated monthly
  • Revenue predictability (recurring vs project) unknown
  • Labour cost vs revenue never on one screen
  • Client concentration risk unmeasured
The System

How the system works.

Data from marketing, sales, finance, HR and payroll is pulled on one schedule. SQL calculates revenue, margins, churn and cost per employee, and Looker Studio shows it as one overview page.

Dept Sources

Marketing · sales · finance · HR · payroll extracts.

Pipelines

Scheduled extracts, one calendar, one refresh.

Models

Client MRR · churn · margin · rev/employee · concentration.

Looker Studio

The one-page bento + a master client tracker.

Action Layer

Variance alerts + a Monday exec digest.

The Process

The process, step by step.

01

Audit

  • Reconciled the five competing revenue numbers
  • Mapped which metrics were hand-made monthly
02

Measurement Plan

  • One definition each for MRR, churn, margin
  • The leadership page designed first
03

Implementation

  • Five-department extraction on one calendar
  • Complex metrics modelled once, in SQL
04

Dashboard Build

  • Bento one-pager mirroring the meeting agenda
  • Master client tracker for account reviews
05

Automate & Optimise

  • Budget-variance alerts
  • Monday exec digest, auto-written
The Build

Clients and costs, in detail.

Two more pages: the client table and the alerts page. Built in HTML with sample data.

PAGE 02 / 06 — CLIENTS × MARGINLIVE HTML · MOCK DATA
EXHIBIT B
Client Deep-Dive

The client list, with profit attached.

  • The table shows each client’s monthly revenue, margin and workload.
  • The chart tracks profit margin against the agreed 20% minimum.
  • Hiring progress sits on the same board as budgets.
PAGE 06 / 06 — ALERTS + AILIVE HTML · MOCK DATA
EXHIBIT C
Automation Layer

Problems ping before month-end.

  • Rules watch project budgets and client margins continuously.
  • The Monday summary opens the leadership meeting, already aligned.
  • Every flag comes with the move: review scope, reprice, or close the hire.
Deliverables

What was delivered.

The Results

The results.

ONE OPENING PAGE.

The leadership meeting starts aligned. The whose-number-is-right debate is gone.

NUMBERS, ONCE.

Client revenue, churn and margin are calculated once in SQL and trusted everywhere.

RISKS IN VIEW.

Client concentration and cost structure sit next to growth, with nothing hidden.

NOTE: CLIENT DETAILS GENERALISED · ALL NUMBERS ARE SAMPLE DATA · DASHBOARDS ARE HTML RECREATIONS

Next Steps

Want this for your business?

If your leadership meetings start with an argument about numbers, this page ends it.