Why RevOps Metrics Are Broken – And How to Fix Them

Here’s the number that should stop you mid-scroll: public go-to-market software companies are trading at just 3.7x trailing revenue on average – a multiple so low that Salesforce’s $5.66 billion acquisition of Braze represented a 58% premium to where the stock was sitting on Monday. The market has essentially decided that GTM software is worth less than almost any other category in B2B. That’s a sharp signal. And for RevOps professionals, it raises an uncomfortable question: if the tools that power our revenue motion are being priced like commodities, are we actually proving they work?

The answer, for most teams, is no. Not because the tools don’t deliver value, but because the measurement layer sitting on top of them is fundamentally broken.

What Low GTM Multiples Actually Tell RevOps Teams

Market multiples aren’t just a finance story. They reflect investor confidence in whether a category can sustain durable, measurable growth. When GTM software trades at depressed valuations, it signals that buyers – not just investors – are struggling to tie spend in this category to outcomes they can defend.

Think about what RevOps teams are routinely asked to justify: headcount for SDR tools, spend on intent data platforms, licensing costs for engagement software. The standard response is a dashboard showing activity metrics. Emails sent. Sequences enrolled. Meetings booked. Almost none of that connects cleanly to Annual Recurring Revenue (ARR) in a way that holds up to a CFO’s scrutiny.

That gap – between activity measurement and revenue measurement – is where RevOps credibility lives or dies. And right now, most teams are living in the activity half.

Data point: GTM software companies are trading at an average of 3.7x trailing revenue as of late October 2026, compared to a 6.8x multiple implied by Salesforce’s acquisition of Braze – a 58% premium to the public market price. (Source: SaaStr)

The Pipeline Attribution Problem Hasn’t Been Solved – It’s Been Avoided

Pipeline credit fights are legendary in B2B. Marketing claims the lead. Sales claims the relationship. RevOps is stuck in the middle trying to produce a number everyone will agree to – which means producing a number nobody really trusts.

The sourced vs. influenced debate has been running for years, and most teams still haven’t resolved it cleanly. The honest reason is that clean resolution requires political will, not just technical infrastructure. Your CRM can track first touch, last touch, and multi-touch attribution. What it can’t do is make your CMO and VP of Sales agree on what “credit” actually means.

A practical model gaining traction with smaller B2B teams works like this:

• Sourced credit goes to the channel or team that originated the opportunity – the first meaningful touchpoint that created a sales pipeline record.
• Influenced credit is tracked separately and applies to any touchpoint that demonstrably accelerated or supported a deal already in motion.
• The two buckets are reported side by side and never collapsed into a single “pipeline generated” number.

This approach doesn’t eliminate disagreement. It does something more useful: it makes the disagreement visible and structured, so leadership can make deliberate trade-off calls rather than pretending consensus exists when it doesn’t.

How Agentic Commerce Is About to Complicate RevOps Measurement Further

Just when pipeline attribution was starting to feel like a solved problem for mature teams, Salesforce’s Winter ’27 Release introduced something that changes the measurement surface entirely. Their Agentic Commerce Search capability – part of the broader push toward agent-native product discovery – has published conversion numbers for merchant-side performance.

This matters for RevOps for a reason that isn’t obvious yet: if AI agents start initiating and completing purchase decisions on behalf of buyers, the traditional touchpoint model breaks. There’s no email open. No demo attended. No SDR sequence. The agent queries, the agent evaluates, the agent converts – and none of that lives anywhere in your attribution model.

Not yet, anyway. Teams that aren’t thinking about this now will spend 2027 retrofitting their measurement frameworks to catch up. As we covered in Why AI Agent Governance Is Now a GTM Strategy Problem, the governance questions around AI-initiated actions aren’t hypothetical anymore – they’re arriving in production environments ahead of the measurement infrastructure designed to track them.

For RevOps specifically, the immediate action is to map your current attribution model and flag every step that assumes a human buyer is making a decision. That assumption is eroding fast.

Which RevOps Metrics Actually Predict Revenue – Not Just Reflect It

Most RevOps dashboards are lagging. They show what happened: churn rate last quarter, win rate year to date, ARR attainment this period. These are important numbers, but they don’t tell you what’s going to happen – and they arrive too late to change the outcome.

The metrics with genuine predictive weight are less popular in board decks because they’re harder to explain and harder to game. Here are the ones worth prioritising:

• Pipeline coverage ratio by segment – not blended across the whole book, but broken out by your Ideal Customer Profile (ICP) tiers. A 3x coverage ratio in your core ICP is worth far more than 5x coverage in accounts that rarely close.
• Time-to-qualification – how long it takes a new opportunity to reach a qualified stage. Compression here usually predicts better win rates six to eight weeks later.
• Net Revenue Retention (NRR) by cohort and by acquisition channel – because the channel that produces the fastest-closing deals isn’t always the one that produces customers who stay.
• Multi-threaded deal percentage – the share of open opportunities where you have documented relationships with more than one stakeholder. Single-threaded deals fail at a disproportionate rate, and this metric surfaces that risk early.
• Sales cycle length by deal source – to identify which pipeline sources actually accelerate velocity versus which ones just inflate your pipeline count.

None of these are exotic. Most CRM platforms can surface them today. The problem is that teams default to reporting what’s easy to pull rather than what’s useful to act on.

Data Security Is a RevOps Risk Category – Start Treating It That Way

AU Small Finance Bank is currently investigating a potential data leak involving a Salesforce-managed platform affecting vehicle loan data. The bank confirmed its core systems are unaffected, but the investigation itself is the story for RevOps leaders.

CRM and GTM platforms now sit at the center of extraordinarily sensitive commercial data: pipeline values, deal terms, customer financial profiles, competitive intelligence. That’s not hyperbole – it’s a description of what lives in a standard enterprise CRM deployment. Yet data security rarely appears as a line item in RevOps planning conversations.

It should. RevOps teams need clear answers to three questions before something goes wrong:

• Which fields in your CRM contain data that would trigger regulatory notification if exposed?
• Who has export access to those fields, and is that access audited on a regular basis?
• If a third-party integration were the source of a leak, how quickly could your team identify which records were affected?

If you don’t have fast, documented answers to those questions, the AU SFB situation is a useful prompt to go find them. Check your CRM Tools Directory for platforms with built-in data governance features, and cross-reference against what your current stack actually enforces versus what it promises.

What the Salesforce-Braze Deal Means for Your Tech Stack Decisions

When a major platform acquires a customer engagement tool at a significant premium to market, the practical implication for RevOps teams isn’t about the deal itself. It’s about integration timelines and consolidation pressure.

Braze users who are also Salesforce customers will face the familiar post-acquisition question: do you wait for native integration and accept the roadmap risk, or build connectors now and accept the technical debt? Neither answer is universally correct. It depends on how tightly Braze is embedded in your go-to-market motion and whether your team has the internal capacity to maintain custom middleware.

The broader pattern is worth watching. Salesforce is assembling a stack that spans CRM, customer engagement, commerce, and AI agents – which creates real consolidation opportunities for RevOps teams. Fewer vendors, fewer integration points, less data fragmentation across the pipeline. But it also creates concentration risk. Putting more of your revenue infrastructure inside a single vendor’s ecosystem means that vendor’s platform decisions become your operational constraints.

There’s no clean answer here. What matters is the framing: don’t evaluate the Braze acquisition as a market event. Evaluate it as a vendor strategy signal and ask what it means for your specific stack over an 18-month horizon. For deeper thinking on how to manage this kind of instability, the framework in How to Build a GTM Strategy When the Tech Stack Shifts Under You is worth revisiting.

The RevOps Team That Wins in 2027 Looks Different From Today’s

Public markets pricing GTM software at commodity multiples is a symptom. The underlying condition is that too many GTM tools have been sold on potential and priced on activity, while the people operating them – RevOps teams – haven’t had the measurement infrastructure to prove otherwise.

That’s changing, and agentic capabilities are forcing the issue. When AI handles parts of the revenue motion autonomously, you can’t measure success in clicks and opens anymore. You have to measure it in Customer Lifetime Value (LTV), Customer Acquisition Cost (CAC) by channel, and cohort-level retention. Those are harder numbers to produce. They’re also the ones that actually answer the question every CFO is asking: is this spend producing durable revenue, or just durable activity?

RevOps teams that build toward those harder metrics now – that clean up their attribution models, instrument their pipelines for predictive signals, and treat data governance as a strategic concern rather than an IT ticket – will be in a fundamentally different position when the measurement conversation becomes unavoidable.

The teams that don’t? They’ll still be fighting about pipeline credit when the quarter closes.

Measure what moves revenue. Everything else is decoration.