The MD Dashboard Blueprint

An MD dashboard is a single screen showing the six numbers that determine whether a B2B service firm is growing: pipeline value, new qualified conversations this week, proposals awaiting decision, win rate, revenue booked against target, and delivery capacity. The numbers are read live from the CRM and the tools where work actually happens — not compiled by hand at month end. This guide sets out what a 5–50-staff firm should measure, why those six, and how to build the thing so nobody ever assembles a report again.

Why is reporting usually a monthly guess?

At most firms this size, reporting works like archaeology. Somebody — usually the founder or an office manager — spends an afternoon digging numbers out of the accounting package, a spreadsheet of proposals, an inbox, and memory. The result arrives days after the month it describes, and the sources rarely agree with each other.

Three problems compound:

• The numbers are stale. By the time the report is read, the decisions it should have informed were already taken on instinct.
• The numbers are filtered. When a human compiles figures, they pass through memory, optimism and deadline pressure. The deal that "feels close" gets counted; the one that went quiet in April quietly stays in the pipeline column.
• The compiling itself is a tax. An afternoon a month, every month, spent producing a document that mostly confirms what everyone suspected.

Ask a founder "how's the pipeline?" and you typically get an anecdote about the most recent conversation. That is not reporting. That is mood.

What does "numbers that tell the truth" mean?

A number tells the truth when it is measured from the system where the work happens, not compiled by a person afterwards. When a proposal is logged in the CRM the moment it goes out, then "proposals awaiting decision" is a fact. When it lives in someone's sent folder, it is a recollection.

This is the whole principle behind the blueprint: measured, not compiled. Every number on the dashboard must have a system of record it can be read from automatically. If a number can only be produced by asking someone, it does not go on the dashboard — it goes on the list of processes to fix first.

The obvious prerequisite is a CRM that reflects reality. Most don't. If yours is full of stale deals and contacts nobody has touched in a year, start with the resurrection protocol for a dead CRM — a dashboard wired to a graveyard just reports on graves with confidence.

Which six numbers should a founder see daily?

I've written up the six numbers in full detail, but they belong here as a set, because the set is the point. Each covers a distinct question, and together they cover the whole growth system:

1. Pipeline value — total value of open, qualified opportunities. Is there enough in front of us?
2. New qualified conversations this week — the raw input. Is the top of the pipeline being fed?
3. Proposals awaiting decision — money sitting in other people's inboxes. What needs chasing?
4. Win rate (rolling) — of decided proposals, what fraction we win. Are we priced and positioned correctly?
5. Revenue booked vs target — the scoreboard. Are we on plan this month and this quarter?
6. Delivery capacity — can we actually take on what we're about to win?

Notice what the set does. Numbers 1–3 are about the future, 4–5 are about performance, and 6 is the constraint that stops growth breaking the firm. Remove any one and you get a blind spot; add ten more and you get noise.

How does a live dashboard actually work?

The mechanism is simple, and it is worth stating plainly because most firms assume dashboards require a data team. They don't. They require discipline about where data lives.

1. Every deal lives in the CRM, with a stage, a value, and an owner. No deals in inboxes, no "mental pipeline".
2. Inbound writes itself in. When an enquiry arrives — form, email, call — it creates or updates a CRM record automatically rather than waiting for someone to type it. This is exactly what an Inbound Engine is for.
3. Proposals and invoices are logged as stage changes, so "proposal sent" and "won" are timestamps, not memories.
4. Delivery hours or project load sit in whatever tool the team already uses, exposed through its reporting.
5. A dashboard layer reads all of it live and renders the six numbers. Most CRMs can do a serviceable version natively; a lightweight BI tool does the rest.

When the data lives where the work happens, then reporting stops being a project and becomes a read operation. Nobody compiles anything. The dashboard is simply a window onto systems that were going to hold the data anyway.

What is the difference between leading and lagging indicators?

Lagging indicators tell you what already happened: revenue booked, win rate. You cannot manage them directly — by the time they move, the causes are weeks or months old.

Leading indicators predict what will happen: new conversations this week, pipeline value, proposals out. These you can act on today. If new conversations drop this week, revenue drops in roughly a sales cycle's time — predictably, not mysteriously.

The practical rule: manage the leading indicators, report the lagging ones. A founder who watches conversations and proposals daily almost never gets surprised by a bad month, because the bad month announced itself six weeks earlier at the top of the pipeline.

Follow-up deserves a special mention here, because it is the leading activity firms measure least. Most firms stop following up after two touches; deals typically need five or more. A structured 90-day follow-up framework turns "proposals awaiting decision" from a static count into a worked list.

Why is win rate the price-setting number?

Win rate is the only number on the dashboard that tells you what to charge. The logic is mechanical. When you win more than 60% of the proposals you send, then you are underpriced for the value the market evidently sees — buyers are saying yes too easily. Our standing rule: above 60% win rate, raise prices 15% and watch what happens. Usually the win rate settles back toward 50% and every remaining win is worth materially more.

The reverse also holds. A win rate drifting below roughly 25–30% commonly signals a positioning or qualification problem — you are proposing to people who were never going to buy — and that is fixed at the top of the pipeline, not by discounting.

None of this is available to a firm that cannot state its win rate. In my experience most founders at this size can't, not because they are careless but because proposals were never logged anywhere a percentage could be computed from.

How many numbers is too many?

More than about eight. KPI overload is the standard failure mode of firms that get religion about measurement: a forty-tile dashboard where everything is tracked and nothing is watched. When every number is on the screen, then no number changes behaviour, and within a month nobody opens the page.

The test for any candidate metric is blunt: what decision changes when this number moves? If the honest answer is "none, but it's interesting", it does not earn a tile. Six numbers glanced at daily beat forty numbers reviewed monthly, because the glance actually happens.

That is not to say the other numbers are worthless — email deliverability, positive-reply rate, utilisation by person, aged debtors all matter to somebody. They belong one click down, on the operational views the relevant person owns. The MD dashboard is the layer above: the six numbers that tell the founder whether the machine is working, with everything else available on demand rather than on display.

What cadence should sit around the daily glance?

The dashboard carries the daily layer. Two more layers sit on top:

• Daily (60 seconds): glance at the six numbers. No meeting, no discussion. The value is trend recognition — you notice a drift on day three instead of day thirty.
• Weekly (30 minutes): pipeline review. Walk the open deals, chase the stalled proposals, check that new conversations met the weekly floor. Decisions get made here.
• Monthly (an hour): the lagging view. Revenue vs target, win rate trend, capacity plan for next quarter. This is also where you catch slow rot — a win rate that slid five points, a pipeline propped up by two old deals.

The cadence matters because a dashboard is not the goal; unsurprised decision-making is. Reporting is one of the three systems — alongside pipeline generation and follow-up — that break the pattern where growth depends entirely on the founder's personal attention. It is usually the cheapest of the three to install, and it tells you which of the other two you need first.

---

Next step: the Growth System Audit — £450, seven days, credited against any build — maps where your growth system leaks, which numbers you can already trust, and what to build first.