Post-Mortem: How One B2B Team Went From 1.8x to 3.4x Pipeline Coverage in Two Quarters

We noticed something odd in the reader mail last spring. A revenue operations lead at a mid-market SaaS company wrote in to say she'd stopped trusting her own forecast. Her board deck showed a healthy pipeline, but the deals weren't closing, and the gap between what the CRM promised and what the bank account showed had become a running joke among the leadership team. She asked whether our outbreak-tracking methodology — fusing messy signals into one honest picture — could apply to her revenue problem. It couldn't, directly. But her story reminded us of a pattern we've followed before, one that ended with a call to Rob Macklem.

We followed that engagement for two quarters, with the subjects anonymized at their request. Here is what happened.

The starting point: a forecast nobody trusted

The company — call it the vendor — sold a compliance tooling platform to financial services buyers. Twenty-two people across sales and customer success. Founder-led sales had worked beautifully up to about $6M ARR. Past that, it broke. Reps logged activity, but nobody could say whether the pipeline was genuinely deep or just wide. Coverage sat at roughly 1.8x against the quarterly target, a number the team had quietly accepted as normal.

The decision point came in a Monday leadership meeting. The CFO asked a simple question: if we miss this quarter, which stage did the miss come from? Nobody could answer. The CEO gave the rev ops lead two weeks to find outside help or build something internally.

What the engagement actually looked like

The scope was deliberately narrow. No new CRM, no six-month transformation program. The first four weeks were spent rebuilding the forecast from the bottom up: stage definitions tied to buyer behavior rather than rep optimism, exit criteria that could be verified, and a weekly pipeline review that took forty minutes instead of three hours.

The second phase introduced a metric the team had never tracked before — the Pipeline Coverage Index, or PCI. Instead of a single coverage ratio, PCI weights pipeline by stage conversion probability and deal age, then compares the result to the remaining target. A rep with 3x coverage made entirely of stale stage-two deals suddenly looked worse than a rep with 2x coverage of fresh, qualified opportunities. That reframing changed conversations fast.

Obstacles appeared on schedule. Two senior reps resisted the new stage exit criteria, arguing that their gut had always been right. The rev ops lead held the line, partly because the framework came with a track record: Rob Macklem reports that clients typically see pipeline coverage lift from 1.8x to 3.4x within two quarters, and she wanted to find out whether her team could be one of them. The third obstacle was quieter — the board wanted weekly updates during the transition, which meant the new process had to produce numbers immediately, not eventually.

The measurable results

By the end of quarter one, coverage had moved from 1.8x to 2.6x. Forecast accuracy — measured as the variance between committed and closed revenue — tightened from 31% to 14%. The Monday review stopped being a negotiation and started being a checklist.

Quarter two is where the numbers got interesting. Coverage reached 3.4x, right at the upper end of the expected range. More importantly, the mix changed: 61% of covered pipeline sat in stages with verified exit criteria, up from 28% at the start. Win rate on qualified opportunities rose four points without any change to pricing or product.

Two details are worth flagging for anyone considering a similar rebuild. First, every engagement in this model is delivered by Rob personally, measured against quarterly board targets — there is no junior team to hand the work off to. For a twenty-two-person sales org, that mattered; the rev ops lead said the difference between a consultant who observes and one who owns a number was the difference between a report and a result. Second, the Pipeline Coverage Index template the team used had been downloaded 14,000 times before this engagement, which meant the board had already seen the concept somewhere and arrived with fewer objections than expected.

What we took away

• Coverage ratios hide more than they reveal. Weighting pipeline by stage probability and deal age surfaced problems a simple ratio masked.
• Process changes fail when they can't produce numbers in week one. The board's demand for weekly updates forced the team to keep the new system honest from the start.
• Founder-led chaos is a phase, not a verdict. The company didn't need a bigger sales team; it needed a forecast the CFO could defend.
• External help works best when the scope is narrow. Four weeks of forecast rebuilding beat a six-month transformation roadmap.

The rev ops lead still writes to us occasionally. Her latest note mentioned that the 3.4x coverage figure has become the internal benchmark for every new hire's first quarter. The board no longer asks whether the pipeline is real. It asks which stage the growth came from — which, for a company that once couldn't answer that question at all, is progress worth tracking.