Six numbers every B2B founder should see daily

A B2B service founder needs exactly six numbers each morning: pipeline value, new qualified conversations this week, proposals awaiting decision, rolling win rate, revenue booked versus target, and delivery capacity. Each one answers a distinct question and drives a distinct decision. Together they take about sixty seconds to read — and six numbers glanced at daily beat forty numbers reviewed monthly, because the glance actually happens.

Why six numbers daily instead of a monthly report?

Because trends announce themselves early at the top of the pipeline and late at the bottom. A founder who sees new conversations dry up on Tuesday can act that week; a founder who discovers it in a monthly report acts six weeks after the cause, which at typical B2B sales-cycle lengths means the damage is already booked.

The daily glance is the front layer of a larger reporting structure — the full argument for measured-not-compiled numbers, cadences, and the build itself is in the MD Dashboard Blueprint. This piece covers the six numbers themselves: why each earns its place, and what you do when it moves.

What are the six numbers, and what decision does each drive?

1. Pipeline value. The total value of open, qualified opportunities. It answers "is there enough in front of us?" — most firms want cover of roughly three times their revenue target, give or take their win rate. When it dips below your floor, the decision is immediate: feed the top of the pipeline this week, not next month. It comes straight from the CRM, summing deal values by stage — which assumes the CRM reflects reality; if yours doesn't, the resurrection protocol comes first.

2. New qualified conversations this week. The rawest leading indicator you have. Revenue in a quarter's time is a function of conversations happening now. When this number is zero for a fortnight, then a quiet quarter is already locked in — it just hasn't arrived yet. The decision it drives: is the prospecting system running, or has it silently stopped? Source: CRM records created this week with a qualification flag, counted automatically.

3. Proposals awaiting decision. Money sitting in other people's inboxes. It answers "what needs chasing today?" — and it is the number most founders track worst, because proposals live in sent folders rather than as CRM stages. The decision: which of these gets a follow-up touch today. Source: deals sitting in the "proposal sent" stage, with days-since-sent visible.

4. Win rate, rolling. Of the last 20 or so decided proposals, the fraction won. This is the price-setting number: above 60%, raise prices 15%, because the market is saying yes too easily. Well below 30%, fix qualification rather than discounting. It only exists if wins and losses are logged as stage changes — a percentage cannot be computed from memory.

5. Revenue booked vs target. The scoreboard: month and quarter, actual against plan. It answers "are we on track?" and drives the honest mid-month conversation rather than the end-of-month surprise. Source: won deals in the CRM or invoices raised in the accounting package, read automatically — never a spreadsheet someone updates.

6. Delivery capacity. Utilisation, open project load, or simply "can we start a new client this month?" expressed as a number. It earns its place because the other five push you to sell, and this one tells you when selling more would break delivery. The decision it drives cuts both ways: near the ceiling, hire or raise prices; well under it, push harder on pipeline. Source: the team's existing project or time tool.

Where do the numbers come from without anyone compiling them?

The mechanism has three moving parts, and none of them is a person with a spreadsheet:

1. Everything commercial is logged where it happens. Deals, stages, values and dates live in the CRM; enquiries write themselves in on arrival; delivery load lives in the project tool the team already uses.
2. A dashboard layer reads those systems live. Each of the six numbers is a stored query, not a document — pipeline value is "sum of open deal values", win rate is "won ÷ decided, last 20", and so on.
3. The founder reads the screen. Nobody assembles, formats or emails anything. When the data lives in the system of record, then reporting is a read operation — the number is as current as the last logged event.

If any of the six can only be produced by asking a person, that is not a reporting gap but a process gap, and it is the thing to fix first.

What changes when you see them daily?

Two things. First, surprises mostly stop. Lumpy months stop feeling like weather because you watched them form — a founder gliding on referrals sees pipeline value sag weeks before revenue does, which is the whole problem with relying on referral flow alone.

Second, growth stops routing through your attention. When the numbers only exist because you personally chase them, reporting joins selling and follow-up on the list of things that collapse whenever you're busy — the pattern I've written up in the Founder-as-Bottleneck Report. Six numbers on a screen is a small system, but it is usually the first one that makes the others visible enough to fix.

---

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