Case study: Fixing funnel leakage by syncing lead scoring with CRM routing rules

# Case study: Fixing funnel leakage by syncing lead scoring with CRM routing rules

This case study uses a realistic B2B operating pattern built from public benchmarks and common CRM-routing failure modes. The mechanics are specific. The company name is anonymized because the lesson matters more than the logo.

Problem

The team did not have a traffic problem. It had a handoff problem.

Paid social and search were driving form fills, demo requests, and pricing-page visits into the CRM, but conversion quality dropped the moment leads crossed from marketing automation into sales routing. High-intent leads were being scored one way in the MAP, routed another way in the CRM, and reviewed a third way by SDR managers. The result was classic funnel leakage: good leads sat untouched, low-fit leads were over-routed, and reporting made the damage look smaller than it was.

That operational gap matters more than most teams admit. Gartner has estimated that B2B buying groups involve 6 to 10 stakeholders, which means routing delays compound fast once follow-up loses momentum (Gartner). Separate research from InsideSales found that responding to a lead within 5 minutes made qualification outcomes dramatically better than delayed follow-up (Harvard Business Review summary). In other words: if routing logic is wrong, the cost is not just admin friction. It is lost revenue.

In this scenario, the company was seeing three symptoms at once:

• marketing-qualified leads were being created based on engagement score thresholds that sales did not trust
• enterprise accounts were sometimes routed to the wrong region or owner because CRM assignment rules prioritized incomplete firmographic fields
• campaign reporting showed healthy lead volume, but sales-accepted rates stayed weak because the handoff logic rewarded activity instead of fit plus intent

The team initially treated these as separate issues. They were not. They were one systems problem: lead scoring and CRM routing had drifted apart.

Solution

The fix was not a net-new martech purchase. It was alignment between the score that decided who mattered and the rule set that decided who got the lead next.

First, the RevOps lead pulled one month of lead history and mapped four checkpoints for every inquiry: source campaign, score at creation, owner assigned, and first sales action. That exposed the hidden mismatch. Marketing scoring gave heavy weight to content engagement and page depth, while routing logic gave priority to sparse firmographic fields and a legacy territory tree. A lead could look hot in the MAP and still be assigned like a cold inbound record in the CRM.

Second, the team simplified the scoring model. Instead of adding more behavioral points, they reduced the model to a smaller set of signals with direct sales relevance:

• high-intent conversion events such as demo requests and pricing-page return visits
• ICP fit markers such as employee band, geography, and business model
• negative scoring for student, competitor, partner, and job-seeker patterns
• recency decay so old engagement did not keep weak leads artificially warm

Third, they rebuilt CRM routing rules to mirror the scoring logic instead of competing with it. If a lead crossed the MQL threshold and met ICP-fit conditions, it routed directly to the correct SDR queue by region and segment. If the score was high but fit data was incomplete, the record moved to an enrichment-and-review queue instead of being sprayed to sales immediately. If the lead fit the ICP but showed only light intent, it stayed in nurture instead of inflating sales pipeline coverage.

That single change removed the false binary that hurts many B2B teams: route everything fast, or qualify everything slowly. The better model is conditional speed. Route fast when fit and intent are both clear. Slow down when either signal is incomplete.

The implementation work was practical:

1. Audit every field used in both lead scoring and assignment rules.
2. Remove scoring inputs that sales could not explain or defend.
3. Define one shared MQL contract owned by marketing and RevOps, not by campaign managers alone.
4. Rebuild routing with explicit exception queues for missing firmographics, partner leads, and non-ICP hand-raisers.
5. Add weekly QA on records where score, segment, and owner assignment looked contradictory.

The reporting layer changed too. Instead of judging the fix by top-of-funnel lead counts, the team tracked four operational measures: speed-to-first-touch, MQL-to-SAL rate, reroute rate, and disqualification reasons. That made the impact visible quickly. It also stopped the usual political argument where marketing points to volume and sales points to anecdotes.

Results

Within the first month, the company had a clearer picture of where qualified demand was being lost and which routing rules were responsible. The most immediate gain was lower response friction. Once high-fit, high-intent leads went straight to the right queue, sales follow-up became more predictable and fewer leads required manual reassignment.

The company also changed how it read campaign performance. Before the fix, some campaigns looked efficient because they created cheap MQLs. After the fix, those same campaigns produced weak sales-accepted rates and high reroute volume. Meanwhile, a smaller set of campaigns that targeted tighter ICP segments generated fewer raw leads but stronger downstream conversion quality. That is the difference between lead generation reporting and revenue reporting.

Public benchmarks support that direction. LinkedIn has reported that proving campaign impact across longer B2B cycles is getting harder, not easier, for marketers, which is exactly why operational handoff quality matters in attribution discussions (LinkedIn). And Norwest's 2024 B2B benchmark showed sales cycles stretching to roughly 9 months in the $50K-$100K ACV band, making early-stage routing mistakes more expensive over time (Norwest).

The practical outcome was not just better hygiene. It was better budget confidence. Once the team could separate high-volume campaigns from high-conversion campaigns, spend shifted toward channels and audiences that created qualified pipeline instead of dashboard noise.

What this case study actually proves

Most funnel leakage is not caused by weak creative or low traffic quality alone. It is caused by system disagreement. If the model that scores leads and the system that routes leads are optimizing for different definitions of quality, the funnel will leak no matter how much demand generation you buy.

The fix is usually less glamorous than marketers hope. You do not need another intent vendor before you align field logic, handoff criteria, and queue design. Start there. That is where recoverable revenue usually sits.