← All Episodes
Merlin Consulting ·

Sales Metrics That Drive Revenue: Stop Tracking the Wrong Data

Merlin exposes why most B2B sales teams track metrics that don't move revenue—and the frameworks that actually predict pipeline and close rates.

Also listen on: Spotify
Contents

Sales Metrics That Drive Revenue: Stop Tracking the Wrong Data

The sales metrics that drive revenue are not call counts, email sequences, or shortened sales cycles—they are metrics that causally connect to business outcomes like pipeline generation, ARR, and retention. Merlin, a veteran VP of Sales and Marketing who built one of the first dedicated BDR functions in the industry 15 years before it became standard practice, argues that most B2B sales organizations confuse trackable data with actionable data. The fix is not more dashboards—it is ruthless prioritization of metrics that tell the story of business health, direction, and progress.


The Problem No One Wants to Admit

Most sales teams are managing to the metric, not to the outcome. Merlin has sat in hundreds of leadership reviews where the data on screen bears no relationship to what is actually happening in the business. That gap—between the numbers being reported and the revenue being generated—is where B2B companies stall.

Merlin brings direct, hard-won perspective to this problem. As VP of Sales and Marketing at 3DR and Cubix, he built a custom CRM called LLO and rolled it out company-wide. Before RevOps was a job title, he earned his first Sales Operations title at Ingram Micro in 2009. And at Ingram, when he proposed dedicating a group of reps to nothing but outbound calls—what he named Outbound Campaign Specialists, or OCS—every leader in the room thought he had “grown a second head.” That function is now called a BDR team and is standard practice across the industry.

His credibility on this topic is not theoretical. It is built from being the person who invented the motion, watched it scale, and is now one of the loudest voices saying it needs to fundamentally change.


Key Takeaways

The central lesson from Merlin’s framework is that sales metrics must be tested against a single question: does changing this number actually move a business outcome? Most metrics tracked in B2B sales—call volume, email sequences, sales cycle length—fail that test. The frameworks that survive it (MEDIC, MEDPIC) are designed to surface the real buying process, not just document activity. RevOps, in this model, is not a CRM admin function—it is the strategic advisor whispering insight into the CRO’s ear before problems surface in quarterly reviews.


Deep Dive: The Frameworks and Decisions That Actually Drive Revenue

Why Most Sales Metrics Are “Interesting” But Not Actionable

The difference between metrics that drive revenue and metrics that just fill a dashboard is causality. An actionable metric is one where improving it demonstrably moves a business outcome—pipeline created, ARR closed, retention improved. An interesting metric is one that is trackable, reportable, and ultimately meaningless.

Merlin’s Actionable vs. Interesting Data Framework forces sales leaders to run every metric through five tests: What business outcome are you trying to influence? Which metrics causally relate to that outcome? Is this a leading indicator (controllable) or a lagging indicator (forecasting only)? Does changing this metric actually move the outcome? And finally—reject anything that is tenacious but not driving results.

“I have sat in so many L10 style meetings or company meetings where you dig into stats and the stats don’t tell the story of the business. Generally metrics should be telling the story of the health and direction and progress of the business.” — Merlin, VP of Sales and Marketing

The failure mode is common: leadership spends the first 40 minutes of a weekly review discussing call volume, sequence response rates, and average sales cycle length—none of which connect to why a specific enterprise deal slipped or why a segment of pipeline is converting at half the expected rate. The meeting ends with action items that optimize the metric, not the outcome.

The discipline required here is subtractive. Sales leaders need to ask what to stop measuring, not just what to add to the dashboard.

Sales Cycle Length: A Forecasting Tool, Not a Performance Goal

Sales cycle optimization is one of the most commonly cited goals in B2B SaaS RevOps. It is also, by Merlin’s analysis, one of the most misapplied.

Sales cycle length is a lagging indicator. It tells you what happened, not what will happen or what you can do to influence the next deal. Its legitimate use is narrow but real: it gives you forecast timing. If your average sales cycle is 60 days and it is July 14th, any deal that does not close within 15 days is a Q4 deal on average. That is actionable for capacity planning and board reporting.

“Sales cycle doesn’t matter only in so much as it’s required for forecasting and understanding where the business is going…it helps with forecasting but driving the metrics towards like I’d rather have a 50-day sales cycle or a 45-day sales cycle versus a 60-day sales cycle. Does that actually have any meaningful impact? I don’t know that it does other than forecasting and getting the business faster.” — Merlin, VP of Sales and Marketing

What Merlin is rejecting is the practice of setting a goal to reduce average sales cycle from 60 days to 45 days and then managing reps against that number. The problem: the actions reps take to shorten a sales cycle (pushing harder, discounting, skipping discovery stages) often reduce win rate and average contract value—outcomes that are far more important than cycle length. Optimizing a lagging indicator can actively damage the leading indicators that matter.

The BDR/SDR Metrics Problem Is Structural, Not Tactical

The BDR motion Merlin invented at Ingram Micro—dedicated outbound reps doing nothing but prospecting calls—was genuinely innovative in its time. He hit $1 million per year in individual sales productivity as one of 200 reps, earning President’s Club by focusing obsessively on the right activities before anyone had a framework for what those were.

That same motion, applied in 2025 and measured by call volume and email sequences, is producing diminishing returns that the industry has not yet fully admitted.

“I think BDR metrics and I’ve got a real bone to pick with the whole BDR SDR ecosystem in and of itself. I don’t think it’s working anymore and everybody needs to change…how many phone calls did you make? How many emails did you send? All of this data can be accumulated and reported on, but if it doesn’t actually mean anything, it doesn’t mean anything.” — Merlin, VP of Sales and Marketing

The mechanism behind this decline is twofold. First, buyers have become desensitized to high-volume outbound sequences—the same templates are deployed at scale across the industry, and response rates have collapsed. Second, the measurement system itself creates perverse incentives: BDRs optimize for the metric (calls made, emails sent) rather than the outcome (qualified pipeline generated). A rep can hit 100% of their activity quota while generating zero pipeline, and the standard metrics will not surface that failure until it shows up in a missed revenue target two quarters later.

“Wildly less effective. The metrics bear that out, but also vibes, man. The vibe checks are off.” — Merlin, VP of Sales and Marketing

The more important implication: marketing’s role in pipeline generation has increased in direct proportion to outbound’s decline. Teams that continue to staff and fund BDR functions at the same ratio as five years ago—without reweighting toward content, demand generation, and inbound—are misallocating resources in a way that compounds over time.

BANT vs. MEDIC vs. MEDPIC: Choosing the Right Qualification Framework

The qualification framework a sales team uses is not a philosophical preference—it directly determines which deals get pursued, which get disqualified, and how sales leaders forecast. Using the wrong framework for your deal complexity is a structural mistake that no amount of coaching or compensation redesign can fix.

FrameworkBest FitKey Addition vs. PreviousLimitation
BANTTransactional or single-buyer B2B dealsBaseline: Budget, Authority, Need, TimelineMisses multi-stakeholder dynamics and procurement process
MEDICComplex B2B SaaS, multiple stakeholdersAdds Champion and Economic Buyer distinctionDoes not map competitive landscape or formal decision process
MEDPICEnterprise SaaS with formal procurementAdds Decision Process and CompetitionRequires more discovery time; can slow early-stage pipeline

BANT was designed for a selling environment where one person has the budget, makes the decision, and has a defined timeline. That describes very few B2B SaaS enterprise deals today. A founder or VP-level champion may love your product, but if you have not identified the Economic Buyer, mapped the Decision Process, or understood how their accounting system codes the purchase—whether as SaaS ARR, a project-based engagement, or capex—you will lose deals you should have won, or win deals structured in ways that destroy your unit economics.

“Enterprise sales 101 is understanding that you don’t know how they buy. You don’t understand how they want to buy and how they purchase and how their accounting system is and how they code things in NetSuite or QuickBooks or whatever it is that they’re using and where that budget is going to come out of.” — Merlin, VP of Sales and Marketing

The MEDPIC extension adds two dimensions MEDIC misses: the formal Decision Process (what steps does procurement require, who has sign-off authority at each stage, what legal or security reviews are mandatory?) and Competition (who else are they evaluating, and on what criteria?). For enterprise deals with six-to-twelve month cycles and multiple stakeholders, skipping these dimensions is not a minor oversight—it is why deals stall in late stages without a clear reason.

Selling ARR vs. Selling Projects: A Fundamentally Different Motion

One of the most underappreciated strategic errors in B2B sales is applying a transactional or project-based sales motion to recurring revenue products—or vice versa.

The way a company evaluates and justifies a one-time professional services engagement is structurally different from how it evaluates a multi-year SaaS subscription. The pain identification process differs (project pain is acute and bounded; SaaS pain must justify ongoing spend). The ROI framing differs (project ROI is one-time; SaaS ROI must compound over the contract term). The Economic Buyer often differs (project budgets frequently live in department operating budgets; SaaS ARR may require IT, Finance, and Legal involvement). And the champion’s internal pitch to their executive team differs entirely.

“How a company picks up a contracted amount of ARR over the course of one or two years versus making a one-time purchase of or an investment in and how you present those products in a selling environment, how you position those products as defining ROI for the customer or the prospect in there. Completely different approaches front to back.” — Merlin, VP of Sales and Marketing

Sales teams that sell both recurring and project-based offerings—common in companies with both SaaS products and implementation or consulting services—need separate playbooks, separate qualification criteria, and separate success metrics for each motion. Conflating them in a single pipeline view with unified metrics is a data integrity problem that corrupts forecasting and misleads leadership about where revenue is actually coming from.

RevOps as Strategic Advisor, Not CRM Administrator

The RevOps function that Merlin describes is not the role most B2B companies have built. The standard RevOps hire is, in practice, a CRM administrator who builds reports, manages integrations, and keeps data clean. That is necessary but insufficient.

The RevOps function Merlin argues is essential—and that most CROs and VPs of Sales do not have—is a strategic advisor role: someone who surfaces insights about product gaps, pricing misalignment, process failures, and market shifts that do not appear in standard pipeline reports. Someone who is, as he puts it, “the consigliere whispering in the ear of the CRO.”

“I don’t, in today’s climate, understand how CROs, VPs of Sales don’t do this job without a reliable robust RevOps section—either a human or a division, or they themselves understand it…being that proactive, process-based strategic leader who kind of is the consigliere, whisper in the ear of the CRO at the time.” — Merlin, VP of Sales and Marketing

This version of RevOps requires a person who understands the business model, can read pipeline data with commercial judgment, and can connect CRM signals to strategic decisions about where to invest, what to price differently, and which sales motions are working versus which are producing activity metrics that mask underlying problems.

The first Sales Operations title Merlin received was at Ingram Micro in 2009. The role has evolved substantially since then—but most companies are still hiring for the 2009 version of the job.

The Familiarity Bias as a Repeatable Sales Technique

One of the more tactically specific frameworks Merlin introduces is using familiarity bias deliberately to create the conditions for high-trust sales conversations. The mechanic: establish social connection and genuine rapport before pivoting to commercial intent. This is not manipulation—it is an acknowledgment that buyers make decisions based on trust, and trust requires familiarity.

The discipline required is a clear line between being friendly with customers and being friends. Merlin is explicit: you can be friendly during the selling relationship, but friendship—the kind that creates social obligations and blurs commercial judgment—belongs after the deal is done.

“You can be friendly with your customers, but you can’t be friends while you’re in a selling relationship. And then once that selling relationship ends, you can be friends all day long.” — Merlin, VP of Sales and Marketing

The practical application: invest real time in understanding what matters to the buyer as a person and as a professional before presenting your product. This creates a familiarity baseline that makes the eventual commercial conversation feel like advice from a trusted peer rather than a pitch from a vendor. In a market where cold outbound is “wildly less effective,” this relationship-first motion is one of the few high-conversion alternatives that does not require a massive inbound engine.


Who This Is NOT For

Merlin’s frameworks are grounded in complex B2B sales environments. There are specific conditions under which this approach does not apply and contexts where following it without adaptation will produce poor results.


About Merlin

Merlin is a VP of Sales and Marketing with a career built at the intersection of sales operations, enterprise GTM, and go-to-market architecture. He held VP-level roles at 3DR and Cubix, built a custom CRM (LLO) that was rolled out company-wide, and received his first Sales Operations title at Ingram Micro in 2009—before the field had a canonical name. Most notably, he created the first dedicated BDR function (OCS—Outbound Campaign Specialists) at Ingram roughly 15 years before BDR teams became standard industry practice. His individual sales productivity at Ingram—$1 million per year as one of 200 reps, earning President’s Club—was the direct result of the methodological thinking he now applies to advising sales organizations. His perspective on metrics, BDR teams, and RevOps is shaped by having built the systems from scratch, watched them become industry standard, and then watched them calcify into practices that no longer serve the businesses using them.


Ready to Replace Activity Metrics With Revenue Metrics?

If your sales reviews feel like reporting for reporting’s sake—call counts up, pipeline coverage unclear, RevOps producing dashboards no one acts on—the problem Merlin describes is structural, not motivational. The shift from tracking interesting data to tracking actionable data requires rethinking which metrics are on your dashboard, which qualification framework matches your deal complexity, and whether your RevOps function is built to advise or just to administer. Founders and GTM leaders at B2B SaaS companies making that transition consistently find the same thing: the metrics that drive revenue are fewer, simpler, and more uncomfortable to look at than the ones being reported today.

Talk to a Growth Strategist →


Frequently Asked Questions

How do you distinguish between actionable data and interesting data in sales metrics?

Actionable data is a metric where changing it demonstrably moves a business outcome—closed ARR, qualified pipeline, net retention. Interesting data is trackable and reportable but has no causal link to outcomes. The test: if your team improves this metric by 20%, does revenue go up? If you cannot trace that connection, the metric is interesting, not actionable. Call volume and email sequence counts are the most common examples of interesting data masquerading as performance indicators in B2B sales organizations.

What should RevOps leaders focus on instead of standard activity metrics?

RevOps leaders should focus on metrics that reveal the health and direction of the business—pipeline conversion rates by stage, ARR mix between new and expansion, deal velocity tied to specific qualification criteria, and win/loss patterns segmented by deal size and buyer type. Beyond metrics, the highest-value RevOps work is surfacing strategic insights: where pricing is misaligned with how buyers want to purchase, where the sales process breaks down relative to the buyer’s procurement process, and which segments are generating disproportionate pipeline relative to investment.

How do you identify which budget owner to talk to for SaaS vs. project-based deals?

For SaaS ARR deals, the Economic Buyer is typically someone with authority over multi-year operating budget commitments—often a CTO, CFO, or VP-level executive whose budget carries recurring line items. For project-based engagements, the budget often lives in a departmental operating budget and the decision can be made lower in the org. The critical step, per MEDPIC, is asking directly how the prospect’s accounting system categorizes the purchase—whether it codes as OpEx (recurring SaaS), project spend, or capex determines which budget owner you need and how the approval process is structured.

Why does selling recurring ARR require a different sales approach than selling a project?

Recurring ARR requires the buyer to justify ongoing spend, not a one-time investment. That changes the ROI framing (value must compound over the contract term), the pain identification (the problem must be persistent, not acute), the champion’s internal pitch (they are committing to a vendor relationship, not a project), and the Economic Buyer (multi-year SaaS contracts typically require more stakeholders and formal procurement than a bounded project). Applying a project-based motion to an ARR product undervalues the product, attracts the wrong buyer, and produces churn when the buyer treats the subscription like a one-time engagement.

How do you structure BDR team goals when call volume and email sequences are no longer reliable metrics?

Replace activity quotas with outcome-based quotas tied to qualified pipeline generated—specifically, meetings held that progress to a second conversation, or opportunities created that meet defined MEDIC/MEDPIC qualification criteria. This forces BDRs to focus on quality of outreach rather than volume, and it surfaces the real question: which channels and messages are generating pipeline? That answer, in 2025, increasingly points toward warmer outbound (referrals, event follow-up, social-first sequencing) and away from cold volume plays. The metric change also forces a conversation about whether the BDR motion is the right investment relative to marketing-driven inbound.


Frequently Asked Questions

What is the difference between BANT and MEDIC sales frameworks?

BANT (Budget, Authority, Need, Timeline) is designed for simpler, single-buyer or transactional sales cycles. MEDIC (Metrics, Economic Buyer, Decision Criteria, Identify Pain, Champion) is built for complex B2B SaaS deals with multiple stakeholders, longer cycles, and formal procurement processes. MEDPIC extends MEDIC further by adding Decision Process and Competition, giving sales teams a complete map of how an enterprise buyer actually evaluates and approves a purchase—information BANT simply does not surface.

Why are traditional BDR metrics like call volume and email sequences no longer effective?

Call volume and email sequence counts measure activity, not outcomes. As Merlin puts it, all of this data can be accumulated and reported on, but if it doesn't actually mean anything, it doesn't mean anything. Cold outbound effectiveness has declined significantly—confirmed both by metrics and by what Merlin calls 'vibe checks.' Tracking activity gives sales leaders the illusion of management while masking whether the BDR motion is generating qualified pipeline or real revenue.

Is shortening the sales cycle actually a good goal for B2B SaaS companies?

Not necessarily. Sales cycle length is a lagging indicator, useful for forecasting but not for operational improvement. Merlin argues that chasing a 45-day cycle versus a 60-day cycle has no proven impact on business outcomes beyond forecast timing. The practical use: if your average sales cycle is 60 days and it's July 14th, any deal not closing within 15 days is a Q4 deal. Use it for pipeline timing—not as a performance lever your team tries to optimize.

Ready to accelerate your B2B SaaS growth?