The Scenario
A professional services company with eighty-five staff across three offices has a leadership team of five: the managing director, the finance director, the operations director, the sales director, and the head of delivery. Every Monday morning, they meet for an hour to review business performance. The meeting is supposed to be about decisions. In practice, it is about data.
Each director brings their own report. Finance has a spreadsheet of revenue, costs, and cash position, updated on Friday afternoon. Sales has a pipeline summary exported from the CRM. Operations has a capacity report compiled from the project management tool and a separate time tracking export. Delivery has a client satisfaction summary built from survey responses and support ticket data.
The first thirty minutes of every meeting are spent reconciling these reports. Revenue figures from finance do not match the closed-deal numbers from sales because of timing differences. The capacity report shows different headcount from the HR system because of a contractor who started mid-week. Someone always has a number that contradicts someone else, and the discussion shifts from “what should we do” to “whose number is right.”
The Problem
The leadership team is flying the business by looking at the instruments one at a time, each with a different update frequency and a different definition of the same metric. Revenue in the finance report is recognised revenue. Revenue in the sales report is contracted value. Both are called “revenue” and neither is wrong, but comparing them without context leads to confusion.
The weekly cadence means decisions are always based on data that is at least two days old and sometimes nine days old (if the meeting is on Monday and the relevant data changed on the previous Tuesday). The managing director has no way to check the health of the business on a Wednesday afternoon without calling three people. By the time the next meeting arrives, the situation may have changed.
The manual compilation is also fragile. Each report depends on one person extracting data from one system. When the finance director is on holiday, the revenue report either does not happen or is produced by someone unfamiliar with the nuances. The data quality degrades silently because nobody questions numbers in a format they are accustomed to seeing.
The Approach
Digital Royalty builds a single executive dashboard that pulls from the company existing systems — the accounting platform, the CRM, the project management tool, the time tracker, the HR system, and the support desk — and presents a unified view of business health.
The dashboard has one primary screen. It shows the numbers the leadership team needs to see together: revenue (recognised and pipeline), gross margin, cash position, utilisation rate, active project count, sales pipeline value by stage, headcount, client satisfaction score, and support ticket volume. Each metric is defined once, sourced from one system, and displayed consistently every time the dashboard is loaded.
The definitions are agreed before the dashboard is built. Revenue means recognised revenue from the accounting system. Pipeline means weighted forecast from the CRM. Utilisation is billable hours divided by available hours from the time tracker. These definitions are documented on the dashboard itself, accessible by clicking any metric, so there is never ambiguity about what a number represents.
Data refreshes automatically. The accounting data syncs daily. CRM and project data sync every fifteen minutes. Time tracking data syncs hourly. The dashboard always shows the most current data available, and each metric displays its last-updated timestamp so the viewer knows the freshness of what they are seeing.
Drill-down is available but not required. The managing director can see that utilisation is at 72% and, if they want to understand why, click through to see utilisation by team, by office, and by individual. But the top-level view is designed to answer the question “is the business healthy?” without requiring any clicks.
Alerts notify the relevant director when a metric moves outside an expected range. If cash drops below a defined threshold, the finance director gets an alert. If the sales pipeline falls below the coverage ratio needed to hit quarterly targets, the sales director is notified. These alerts are configured by the leadership team, not hardcoded.
The Outcome
The Monday meeting changes character. The first thirty minutes of data reconciliation disappear because everyone is looking at the same numbers from the same source. The meeting starts with the dashboard on screen, and the discussion moves immediately to decisions: the sales pipeline is light for Q3, what are we doing about it? Utilisation in the Manchester office has dropped, is that a staffing problem or a pipeline problem?
The managing director starts checking the dashboard on Wednesday afternoons, then daily. When a potential client asks about the company financial health during a pitch, the managing director can answer with current numbers rather than waiting for the next finance report. When the board asks for a performance update, the data is ready immediately.
The finance director recovers half a day per week that was previously spent compiling the Monday report. The operations director stops maintaining a separate capacity spreadsheet. The sales director stops exporting pipeline data into PowerPoint. Each director now spends their time interpreting data and making decisions rather than assembling it.
One unexpected benefit emerges. Because the dashboard is always visible and always current, the leadership team spots a cash flow issue two weeks earlier than they would have with the old monthly review cycle. The early warning gives them time to accelerate two invoices and defer a discretionary expense, avoiding what would have been an uncomfortable conversation with the bank.
Who This Applies To
This scenario is relevant to any business where the leadership team currently assembles operational data manually for review meetings. It applies whether you have five people or five hundred, whether you operate from one office or ten, and whether your review cadence is weekly, monthly, or quarterly. If your leadership meetings spend more time on “what are the numbers?” than on “what should we do about the numbers?”, this pattern addresses the problem directly.