The Lag vs Lead Mistake That Cost This SME Owner 3 Months

Kingsbridge Partners. A management consultancy. 18 staff, 7 years old, well-run by most measures. Monthly P&L reviews. Quarterly board updates. Weekly utilisation tracking. The kind of business that takes its reporting seriously.

In February, revenue was down 22% on the prior year. The MD called an emergency board meeting. Everyone was surprised.

They shouldn't have been. The problem started in November. It just wasn't measured.

A business that tracked everything — except what mattered

Kingsbridge's reporting covered the metrics a well-managed professional services business would run: revenue by month, project delivery rates, staff utilisation, client retention. Solid, consistent, reviewed regularly.

The problem wasn't the quality of the reporting. It was the type. Every single metric was a lag indicator — a measure of what had already happened. Revenue tells you what you billed. Utilisation tells you how the team was deployed. Delivery rates tell you what was completed.

None of those metrics tell you what's coming.

If the distinction between lag and lead is unclear, read this guide first — it covers the concept in full and will make the rest of this case click.

What actually happened in November

In November, Kingsbridge's new business pipeline quietly dried up. Four things drifted together — not one dramatic signal, four small ones compounding:

Combined, forward revenue coverage for the next 90 days had collapsed by roughly 40% against the prior quarter. The data to see this existed — it sat in the CRM, largely unexamined. The monthly pack didn't touch any of it. The P&L was still clean (projects in-flight were still billing). Utilisation was fine (the existing book of work kept the team busy). Nothing in the reporting screamed.

So nothing was caught. By December, the pipeline was thin. By January, gaps appeared in the schedule. By February, the shortage hit the P&L — and a November pipeline problem became a February revenue crisis, with 90 days of compounding in between.

The data was there. The problem was that nobody was measuring the right things — so nobody saw the warning until it was already three months too late.

Why this pattern is structural

Kingsbridge isn't unusual. Most SMEs run lag-heavy reporting not because they chose to, but because of what the tooling produces:

• Accounting software (Xero, QuickBooks, Sage) outputs financial history.
• Project and time tools (Harvest, Toggl, resource planners) output what was delivered.
• Bookkeeping outputs what was billed and paid.

Every one of these looks backward. Lead indicators — pipeline coverage, proposal velocity, rolling win rates, qualified meeting counts — sit in the CRM, the sales spreadsheet, the ad platform. They're often already there, rarely aggregated, almost never reviewed on the same cadence as the financials.

The result: a reporting stack that reflects what the software produces, not what the business needs to know. It's a structural blind spot, not an operator failure.

The lead indicators Kingsbridge added

After the February review, the MD built a simple forward-looking dashboard alongside the existing financial reporting. Five metrics, reviewed weekly:

• Proposals sent per week
• Time from first meeting to proposal submitted
• Win rate on proposals (rolling 8 weeks)
• Average deal value across active pipeline
• Qualified meetings booked for the next four weeks

None of these are complicated. None require specialist data skills. They are counts and averages, drawn from a CRM the team already used. What changed wasn't the data — it was the discipline of reviewing it on a fixed cadence, tied directly to a forward revenue forecast rather than reported after the fact.

The lag/lead stack — side by side

Ten metrics total. Weekly cadence on the five leads. Monthly cadence on the five lags. Same scorecard. Same meeting.

What changed

Within one quarter of running both lag and lead indicators together, Kingsbridge could see a potential revenue shortfall coming 8 to 12 weeks before it hit the P&L. That's not a small thing. Eight weeks is enough time to:

• Accelerate outbound business development activity
• Bring forward conversations with existing clients about follow-on work
• Adjust resource planning before gaps become costly
• Have a calm, strategic board conversation instead of an emergency one

The difference between reacting and responding is almost always time. Lead indicators buy that time.

Where lead indicators fit in the Method

Lead indicators don't come first. The sequence matters.

In the BIP Method™, lead indicators are Stage 4 work — Evolution. They follow Baseline (is the reporting trustworthy?), Foundation (are definitions and core metrics agreed?), and Rhythm (is the monthly meeting stable?). Trying to add lead indicators before the core rhythm is settled almost always fails — they get added, ignored, then quietly dropped because there's no established muscle for reviewing them.

Kingsbridge's fix worked partly because the financial rhythm was already there. The lag reporting was good. The meeting existed. Adding lead indicators to a functioning stack is Evolution. Adding them to a broken stack is decoration.

The lesson

Kingsbridge wasn't bad at reporting. It was thorough, disciplined, and consistent. The mistake was structural: a reporting stack built entirely around lag indicators gives a perfect rear-view mirror and no windscreen.

Most SMEs are in exactly this position. The financial reporting is handled. The operational metrics cover what already happened. The forward-looking signals — the ones that would actually let a business be managed rather than just observed — are nobody's job.

That's a BI problem. And it's one of the most fixable ones there is — once the groundwork underneath it is in place.

Where to start

If the monthly pack currently runs on lag alone, the BI Baseline Score is the two-minute diagnostic that identifies exactly where the reporting stack sits today — including whether Evolution (lead indicators) is the right next step, or whether earlier stages need attention first. For the full mapping — lag to lead, gaps to metrics, metrics to meeting — see the Review.