Revenue leaks in B2B: why your funnel isn’t the problem

Revenue leaks in B2B are almost always blamed on the funnel. That’s the wrong place to look. The funnel is where the outcome becomes visible, not where the motion breaks. By the time a stage-to-stage conversion rate drops, the leak has been happening for weeks in the parts of the buyer journey most teams never instrument: the micro-conversions between stages, the intent signals that never trigger action, the stakeholder engagement that never expands.

In a recent webinar, Brandi Starr of Tegrita and N.Rich CRO George Storm unpacked what actually drives pipeline loss in B2B, and how revenue teams can find and fix leaks before they show up in the dashboard. Our State of ABM report reinforces the gap. 77% of respondents said ABM increases pipeline, but only 26% described their programs as truly successful. That delta is the leak. Generating movement is not the same as building a motion that consistently converts.

The funnel shows the symptom. The motion reveals the problem

When revenue dips, most teams instinctively turn to the funnel. It’s the most visible part of the system and gives a structured view of how accounts move from one stage to another. But while it’s useful for identifying where performance drops, it rarely explains why. A declining conversion rate might suggest a marketing issue, a sales issue, or a pricing problem — but in many cases the real cause sits earlier in the journey and stays hidden.

What makes this challenging is that multiple breakdowns lead to the same visible outcome. A deal might stall because follow-up was delayed, because qualification was weak, because the first meeting failed to establish a clear next step, or because key stakeholders were never engaged at the right time. All of these show up as a drop in conversion, yet each requires a very different response. Teams that rely only on funnel metrics react to symptoms instead of diagnosing the actual problem — and surface-level fixes don’t hold.

Where revenue leaks actually start: the signals your funnel can’t see

Stage-based funnels register leaks after they’ve hardened. By the time “Discovery” accounts stop converting to “Proposal,” the drop happened two to four weeks earlier, when an in-market account stopped engaging, when a key stakeholder never showed up, when a post-demo follow-up took three days instead of three hours. To catch leaks early, the right system to instrument is not the sales funnel but the buyer journey — which moves faster, updates continuously, and shows you the quality of the motion, not just the outcome.

In N.Rich, the buyer journey is built around four explicit stages with defined score thresholds. Accounts move between them based on real engagement behaviour, not on internal pipeline milestones:

• Cold (score of 0): no intent or engagement, first or third party

• In Market (score 1–29): third-party intent signals firing — the account is researching, but not yet engaging with you

• Engaged (score 30–60): ABM ad engagements — the account is actively interacting with your content

• Hot (score 60+): quality website engagements and direct sales engagement — strong intent, high likelihood of conversion

Scores refresh weekly and drop immediately when engagement stops — there’s no gradual decay. That property alone makes the buyer journey more useful for leak detection than the funnel. Three leak signatures become visible this way, each with a specific place to intervene.

Leak 1: Hot accounts that go quiet

An account that scored 65 last week and 30 this week has not gently cooled off — something stalled. The drop is concrete and dated, and it sits in the Engagement Analytics dashboard days before the pipeline stage reflects it. The dashboard shows which content the account was last interacting with, so the next sales touch isn’t guesswork. This is the micro-conversion the blog post’s earlier point calls for: a concrete signal of lost momentum, not a delayed stage update.

Fix: treat Hot → Engaged or Engaged → In Market transitions as intervention triggers, not reporting events. An intent-based workflow can auto-move the account into a “re-engage” segment and notify the account owner the day the score drops.

Leak 2: In-Market accounts that never become Engaged

If an account is firing third-party intent signals but never crosses into the Engaged stage, the leak isn’t pipeline — it’s creative or targeting. Crossing into Engaged requires engagement quality thresholds, not just impressions: 50% scroll depth on articles, 20 seconds of in-screen video playback, or a click on cross-channel display. Accounts that see the ads but don’t cross those thresholds are telling you the content isn’t landing. The funnel will never flag this, because these accounts were never in the funnel to begin with.

Fix: segment the stuck In-Market cohort, review which creatives they’ve seen, and rotate to a different angle or proof point. The threshold data in Engagement Analytics shows exactly where attention drops — article scroll curves or video in-screen duration — so you know whether the hook, the proof, or the CTA is the weak link.

Leak 3: Engaged accounts that never appear in sales

Marketing sees engagement climbing. Sales sees an empty pipeline. That’s not a lead-quality problem — it’s a handoff problem, and it’s the single most common source of misalignment between the two teams. The signal is in the marketing platform, the action needs to happen in the CRM, and no automation connects the two. By the time a weekly report surfaces the gap, the account has already moved on.

Fix: CRM-based workflows in N.Rich push accounts that cross into Engaged or Hot into a connected HubSpot company list or a Salesforce account segment on a daily cadence. Sales sees the same signal marketing sees, on the same day. The point isn’t the automation itself — it’s that every signal has a defined next action attached to it. No signal should die in a marketing dashboard.

What to focus on to improve execution quality

The principle underneath all three leak fixes above is the same: shift the system from tracking activity volume to tracking movement quality. The patterns that actually predict revenue outcomes are small, specific, and observable.

• Identify a small set of micro-conversions that reflect real progress and review them consistently — buyer-journey transitions are a good starting point

• Measure response time after intent signals so opportunities are acted on the same day, not the same week

• Track meeting show rates and second-meeting rates to assess whether engagement is strong enough to continue

• Monitor stakeholder expansion to see if deals are building internal alignment within the account, not just running on a single champion

• Ensure every interaction ends with a clearly defined next step — the absence of one is the single most common cause of stalled deals

• Look beyond stage progression and focus on what happens between stages and within each interaction

• Use these signals to spot where execution is breaking down and intervene early, before it impacts pipeline

Misalignment and finger-pointing are signs of a broken system

Many revenue leaks are not caused by a lack of effort, but by a lack of alignment. Marketing may believe it has generated sufficient engagement, while sales expects accounts to be further along in their buying journey. SDRs may not be clear on how much effort is required before passing an account forward, and account executives may inherit conversations without the context needed to advance them. Each team is doing its job, but the handoff between them is fragile.

This misalignment becomes most visible when performance drops. Without a clear diagnosis, teams default to blame. Sales questions lead quality, marketing points to slow follow-up, leadership pushes for more activity. These reactions are understandable, but they rarely address the root cause. Revenue is not created by one team in isolation, and when the system breaks, the issue almost always spans multiple functions.

A more effective approach is to treat revenue challenges as shared problems. When teams align around a single underperforming metric — response time, second-meeting rate, Engaged-to-Hot conversion — and collectively examine what influences it, the conversation shifts from defending individual performance to improving the system itself. The buyer-journey signals from the previous section give everyone the same shared view, which is often the missing piece in resolving persistent pipeline issues.

Start with the math, then fix the motion behind it

When revenue performance becomes uncertain, opinions surface quickly. Different teams bring different perspectives, and without a clear framework it’s hard to separate assumptions from reality. Returning to the fundamentals of the revenue equation helps. Revenue is driven by a sequence of measurable inputs: accounts entering the pipeline, meetings created, meetings converting to opportunities, opportunities closing, and deal value.

Break the performance drop into these components. Instead of asking what feels wrong, identify which part of the equation is underperforming. From there, understand what’s influencing that specific number. A decline in opportunity creation points to weak discovery or misaligned targeting. A drop in close rate suggests deals are entering the pipeline too early, or stakeholder alignment is insufficient. A decrease in deal value suggests trust hasn’t been built strongly enough to support pricing.

This approach creates focus. Instead of trying to fix everything at once, teams concentrate on improving one lever at a time, tracing the issue back to execution rather than reacting to outcomes. That discipline is often what separates reactive teams from ones that build predictable revenue systems.

Enterprise revenue leaks are driven by risk, trust, and clarity

As organisations move into higher-value deals, the nature of revenue leaks changes. In lower-value transactions, buyers are motivated by clear benefits and quick outcomes. In enterprise environments, the decision-making process becomes more complex and far more risk-driven. Buyers aren’t only evaluating whether a solution delivers value, but whether it’s safe, credible, and defensible within their organisation.

This shift introduces new challenges. More stakeholders become involved, each bringing their own priorities. Decision cycles lengthen, scrutiny increases, and internal alignment becomes as important as external engagement. In this context, trust isn’t a secondary factor — it’s a core driver of whether deals move forward or quietly stall.

Enterprise motions need to actively reduce perceived risk by building credibility early, providing relevant proof points, and equipping internal champions with the materials they need to advocate. Without this, even well-qualified opportunities lose momentum. AI can help here — it can process large volumes of engagement data, identify patterns across accounts, and surface insights that are difficult to spot manually. But AI only works on clarity. When the underlying problem isn’t well defined, AI adds noise, not signal. The buyer-journey model above is the clarity layer: once stage transitions and engagement thresholds are defined, AI can accelerate diagnosis rather than replace it.

When pressure hits, don’t break the system. Fix the motion behind it

Periods of revenue pressure, especially toward the end of a quarter, often trigger reactive decision-making. Leaders feel urgency to act quickly: push for more activity, introduce discounts, and change processes mid-cycle. These actions create the appearance of progress but rarely address the underlying issue — and they often introduce new problems into an already fragile system.

Short-term fixes may help close a handful of deals, but they weaken long-term outcomes. Aggressive discounting erodes deal value and sets expectations that are difficult to sustain. Sudden process changes disrupt deals already in motion. Increased activity without stronger execution adds more noise, not more conversion. In many cases, these reactions don’t fix the leak — they move it further down the line.

Separate immediate action from long-term correction. In the short term, focus on what can still move: strengthen stakeholder alignment on live deals, sharpen execution on the deals with the highest buyer-journey scores, and act on engagement signals within 24 hours instead of within the week. Beyond that, shift back into diagnosis. Where is the motion breaking? Where is momentum being lost? Which part of the system needs to improve so the same issue doesn’t repeat next quarter?

Because the funnel itself is not the problem. It’s simply where the outcome becomes visible. The real drivers of revenue sit underneath it — in execution quality, speed to action, alignment between teams, stakeholder engagement, and the level of trust built across the buying journey. Revenue leaks rarely come from one major failure. They come from a series of small, missed moments that compound over time: a delayed response, an unclear next step, a stakeholder left out of the conversation. Individually, they seem minor. Together, they define whether pipeline holds or breaks.

Teams that consistently perform well are the ones that spot these moments early and fix them before they compound. They move beyond surface-level metrics and focus on how the system operates in practice. They stop reacting to the funnel and start improving the motion behind it. That’s what turns revenue from something reactive into something you can build on.

FAQ

What’s the difference between a revenue leak and normal funnel drop-off?

Normal drop-off is expected attrition between stages — not every opportunity closes. A revenue leak is avoidable loss: deals that should have moved but didn’t, usually because of a motion-quality issue (slow response, weak discovery, missing stakeholder, broken handoff). Leaks show up as unexplained variance in stage-to-stage conversion and as score drops in the buyer journey that aren’t followed by sales action.

How do I know if a leak is a marketing, sales, or handoff problem?

Trace the buyer-journey transition where the leak appears. If accounts are stuck in In Market and never becoming Engaged, it’s a creative or targeting problem (marketing). If Engaged accounts never appear in CRM, it’s a handoff problem (sync and process). If Hot accounts are getting sales touches but deals still stall, it’s a sales-execution or discovery problem. Looking at the transition, not the stage, tells you which team needs to respond.

Can AI fix revenue leaks?

AI makes leak detection faster, not automatic. It can cluster accounts with similar drop-off patterns, surface which intent signals precede stalls, and reduce the time between signal and action. But AI works on clarity — it multiplies whatever definition of “motion quality” you’ve already built. If the buyer-journey stages aren’t defined and the handoffs aren’t instrumented, AI produces more output without producing more revenue.

What’s the first leak to fix?

The handoff between Engaged and CRM-visible. This is the cheapest fix with the highest upside: a single CRM-based workflow surfaces existing engaged accounts to sales without any change to campaigns or creative. If that workflow isn’t in place, every other leak gets worse because even the accounts you do engage are invisible to the team who needs to close them.

How does N.Rich surface leaks specifically?

Through three layered mechanisms: Buyer Journey Intent Reports classify accounts into Cold / In Market / Engaged / Hot with score thresholds; ABM Progression Analytics shows transition rates between stages; and the Engagement Analytics dashboard exposes which content drove (or failed to drive) those transitions. Intent-based and CRM-based workflows then attach a defined action to each transition, so signals convert into sales activity instead of sitting in a report.

See how N.Rich turns intent signals into pipeline

Most ABM platforms watch. N.Rich moves. If you’re running ABM and still relying on funnel stage reports to diagnose revenue leaks, there’s a faster loop available — one grounded in buyer-journey signals, engagement-quality thresholds, and synced handoffs into your CRM.

See how N.Rich works for teams like yours

Sources: Buyer Journey Intent Reports, Getting Started With Progression Analytics, Engagement Analytics, Intent-Based Workflows, CRM-Based Workflows, Webinar: Revenue Leaks