Back to InsightsCase Study /// B2B SaaS · $14M ARR · Series A · 12-person sales team

The Pipeline Was Full. Revenue Was Flat. Nobody Could Explain Why.

A $14M ARR SaaS company had four times pipeline coverage, a high-performing sales team, and hadn't hit a quarterly number in eighteen months.

Pipeline Quality·11 weeks

Before → After

Win Rate
14%22%
YoY Growth
6% YoY31% YoY
CAC Payback
28 months17 months

1. Context

The company sold workflow automation to mid-market operations teams. The product was strong — NPS in the mid-60s, low churn, good expansion once accounts were live. Founder-led sales had gotten them to $8M. Then they hired a VP of Sales, built out the team, and set up the CRM properly. By every visible indicator, the machine was working.

Pipeline coverage was 4.1x. The team was running 60–80 discovery calls a quarter. Marketing was generating 200+ MQLs a month. And yet the last six quarters had averaged 71% of target. The board was asking questions nobody had good answers to.

2. The Misdiagnosis

The VP of Sales had a clear theory: the marketing leads weren't good enough. Too many SMBs sneaking into the funnel, too many tire-kickers, too much time wasted on deals that were never going to close. The solution, in his view, was a tighter MQL definition — fewer leads, better qualified.

Marketing pushed back. Their view was that the leads were fine. The sales team wasn't following up fast enough, and when they did, the pitch wasn't resonating. They wanted better sales enablement and stricter SLAs on follow-up time.

Both teams were presenting data. Both data sets were accurate. And both were completely missing the actual problem.

3. Why It Seemed Right

The lead quality argument made sense on the surface. When you looked at closed-won deals, they did skew toward a particular company profile — certain industries, certain team sizes, certain tech stacks. And the pipeline did include a lot of accounts that didn't match that profile.

The sales execution argument also had merit. Response time data showed some leads waiting 48–72 hours for first contact. A few reps were clearly underperforming on conversion from discovery to proposal.

The problem was that both explanations were downstream symptoms. They were real. They just weren't the constraint. Fixing either one in isolation — which is what both sides were lobbying for — would have produced marginal improvement at best and significant internal conflict at worst.

4. What the Diagnostic Revealed

When we pulled the full pipeline dataset and mapped every deal through stages over the past four quarters, one number stopped the room: 68% of deals that entered Stage 3 ("Solution Presented") never moved again. They didn't close lost. They didn't close won. They just sat there, aging.

We then looked at what Stage 3 actually required to enter. The answer: a demo had been delivered and the rep had marked it complete. That was it. No confirmed next step. No identified economic buyer. No agreed evaluation timeline. Just: demo done, advance the stage.

The pipeline wasn't full of bad leads. It was full of deals where there had been a conversation but no buying process. The company had built a system for tracking seller activity — demos delivered, calls logged, proposals sent — and called it a sales pipeline. It wasn't. It was a record of what the reps had done, not a measure of where buyers actually were.

The 4.1x coverage figure was fictitious. Adjusted for deals with confirmed next steps and identified decision-makers, real pipeline coverage was closer to 1.6x.

5. Structural Changes

Stage criteria were rebuilt from the buyer's perspective. Each stage now required evidence of buyer action, not seller action. Stage 3 required a confirmed evaluation sponsor, an agreed next step with a date, and documented criteria the buyer was using to make a decision. Reps couldn't advance a deal by delivering a demo. They had to get something back.

The weekly pipeline review changed its question. Instead of "what did you do this week," it became "what did the buyer do this week." Deals with no buyer movement in 21 days were flagged. Deals with no buyer movement in 35 days were moved to a separate nurture track and removed from active pipeline.

The MQL definition was adjusted — but not in the way marketing expected. We didn't tighten the criteria at the top. We added a 30-day re-engagement check at Stage 2. Leads that had gone cold before any meaningful two-way exchange were recycled rather than staying in the active funnel and inflating coverage metrics.

Forecasting moved to a committed/likely/possible framework with hard rules about what qualified for each tier. Committed required a verbal close date from the buyer, not from the rep.

6. The Outcome

The first thing that happened was uncomfortable: pipeline coverage dropped from 4.1x to 1.9x overnight. Not because deals disappeared, but because the new stage definitions accurately reflected where buyers actually were. For about two weeks, the VP of Sales was not happy with us.

Then the quarter closed at 94% of target — the first time in seven quarters they'd been within 10 points of plan. The following quarter closed at 107%.

Win rate moved from 14% to 22% within two quarters. Not because the team got better at selling — they hadn't changed. Because the denominator (deals entering late-stage) was now made up of real buying opportunities instead of a mix of real deals and stalled conversations that had been sitting in the system for months.

CAC payback came down from 28 months to 17 months, primarily because sales cycle length on real deals dropped once reps stopped spending time resurrecting zombie pipeline and focused on deals with actual momentum.

7. Why This Matters

This pattern — stage criteria that track seller behaviour instead of buyer commitment — is one of the most common sources of pipeline inflation in B2B companies between $10M and $40M ARR. It develops gradually, usually as a well-intentioned effort to give reps clear, measurable activities to complete. The problem is that a deal doesn't move forward because a rep sent a proposal. It moves forward because a buyer decided to keep evaluating.

The fix isn't complicated. But it requires accepting that your pipeline coverage number is probably wrong — which is a hard thing for a VP of Sales to say to a board, and a hard thing for a CEO to hear. The companies that make this change fastest are the ones with leadership willing to look at the system instead of the people inside it.

Where teams usually start

Pipeline coverage that looks healthy but isn't is one of the most common constraints we find. A short diagnostic tells you if that's what's happening in your system.

Start with a Diagnostic →