The Uncomfortable Truth About Presales Metrics: Most of Them Measure Busyness, Not Impact

After analysing deal outcomes across enough quarters to spot the pattern, the finding is boringly consistent: the metrics most presales teams report to leadership - demos delivered, POC completion rate, average response time - have weak or no correlation with win rate. The metrics that actually predict wins are rarely on any dashboard. They’re not even in most CRMs. They live in the heads of experienced SEs who can feel a deal working but have never been asked to articulate why in structured terms.

This matters because when you optimise for the wrong metrics, you get exactly what you’d expect: a team that’s very busy, very measurable, and no more likely to win.

The three signals that actually correlate with wins

Three leading indicators show up disproportionately in won deals versus lost ones. They’re not magic, and I want to be careful about the word “predict” - this is correlation, not causation. But they’re the closest thing presales has to reliable forward-looking signals.

Discovery depth, measured by the number of distinct business outcomes documented before a demo gets built. Champion engagement post-demo, tracked as stakeholder-initiated follow-up within 48 hours. And technical win confirmation - the discrete moment a technical stakeholder explicitly says “this solves our problem” - logged before commercial close begins.

None of these are standard dashboard metrics. They require deliberate tracking, which is probably why most teams don’t bother. But they share a quality that separates them from the usual presales reporting: they measure what happened in the buyer’s world, not what the SE did.

Consider two deals. SE A delivers a polished 45-minute product tour. Good energy, clean transitions, solid feature coverage. SE B runs a 30-minute demo that directly maps to three outcomes surfaced in discovery, then stops talking so the prospect’s architect can ask follow-up questions. SE B’s deal closes in six weeks. SE A’s goes dark after the second follow-up email.

The difference isn’t demo quality. It’s the upstream work that shaped the demo and the downstream signal it generated. SE B had documented outcomes. SE B’s champion came back with questions within a day. SE B’s architect said, unprompted, “this would actually fix the thing we’ve been struggling with.” Three signals, all trackable, none of which appear in a standard activity report.

The practical version of this is almost disappointingly simple: create a deal scorecard with three fields per opportunity. Outcomes documented pre-demo (count them). Stakeholder follow-up within 48 hours (yes or no). Technical win confirmed (yes, no, or pending). Run a 90-day retrospective against your closed/won and closed/lost. The pattern will be visible. You don’t need a new tool. A shared spreadsheet works. A custom field in Salesforce works. The barrier isn’t technology - it’s the habit.

Demo completion rate measures whether the SE showed up and finished. POC velocity measures how fast the SE moved. Neither captures whether the buyer was convinced. And yet these are the numbers that end up in quarterly business reviews, because they’re easy to pull from CRM and calendar data.

They’re effort proxies, not outcome proxies. There’s a meaningful difference.

Demo completion rate conflates “we ran the meeting” with “we advanced the deal.” A completed demo in front of the wrong stakeholders - say, three mid-level engineers who were told to attend but have no influence on the decision - contributes nothing to win probability. It does, however, look great on a slide.

POC velocity is especially treacherous. A fast POC that the champion never presented internally is worse than a slower one where the SE coached the champion through an internal review. Speed feels like progress. Sometimes it’s just speed.

Most presales leaders have a version of what I’d call the POC graveyard: proof-of-concept engagements that completed on time, got a thumbs-up from the technical evaluator, and then died somewhere between legal and procurement because no business case was ever built. The POC completion metric looked pristine. The deal was never real. It was a tyre-kick with a deadline.

Response time metrics - how quickly SEs respond to RFP questions, for instance - measure service level, not strategic value. They’re useful for capacity planning. They tell you nothing about whether the SE’s response actually moved the deal forward or just ticked a box on someone’s evaluation spreadsheet that seventeen vendors were also ticking.

The deeper risk is behavioural. When leadership optimises for activity metrics, SEs optimise for them too. More demos. Faster POCs. Quicker turnaround on RFP responses. The team gets more efficient at doing things that may not matter, and nobody notices because the dashboard is all green.

What discovery depth actually looks like in a won deal

In won deals, discovery depth means the SE can name - before building a single slide - the specific business outcome the champion is accountable for, the technical constraint that makes the status quo painful, and who else in the organisation has a stake in the decision.

Most SEs do some discovery. The output is often something like “they want to improve efficiency” or “they’re unhappy with their current tool.” This is discovery in the same way that “food” is a recipe. It’s too vague to build a targeted demo, so the SE builds a generic one, and generic demos produce polite feedback and then silence.

Contrast with: “The VP of Engineering is accountable for reducing deployment failures by Q3. Their current bottleneck is that environment configuration is done manually and takes four hours per release. The team has tried scripting it but the scripts break when infrastructure changes. Two other teams are affected and have escalated independently.”

That level of specificity changes everything. It changes how the demo is built, who should be in the room, what the POC success criteria look like, and what language the champion uses when they’re selling internally on your behalf. Which they will need to do, because you won’t be in most of the rooms where the decision actually gets made.

There’s a test I find useful, though it’s not mine originally. Read your discovery notes back to the champion. If they say “yes, exactly,” you have depth. If they say “sort of” or “broadly, yes,” you don’t. The gap between “sort of” and “exactly” is where deals go to die quietly.

The measurable proxy here is simple enough: count the named business outcomes and named stakeholders documented in the opportunity record before the demo is scheduled. It’s not a perfect measure. But it’s a better one than “demo completed: yes.”

One more thing worth noting, because it connects to career trajectory: SEs who can articulate deal context in business terms rather than feature terms are the ones who get pulled into strategic deals. They’re the ones sales leadership asks for by name. The skill that makes discovery depth possible - translating technical capability into business consequence - is the same skill that eventually opens doors to advisory roles, leadership, or whatever flavour of “senior” your organisation uses.

How to report presales metrics without lying to everyone

Report two tiers. Activity metrics - demos completed, POCs active, RFPs in flight, average SE utilisation - for capacity and resource planning. And leading indicators - discovery depth score, technical win confirmation rate, champion engagement rate - for deal quality assessment.

Conflating the two gives leadership a false picture of presales impact. It’s like reporting a restaurant’s success by how many plates left the kitchen, without mentioning whether anyone ate the food.

Sales leadership often asks for presales metrics without a clear framework for what they’re trying to learn. Are they asking about capacity? Deal health? SE effectiveness? The answer changes what you should report, and if nobody specifies, you’ll default to activity metrics because they’re easy. Easy is not the same as useful.

The risk of reporting only activity data is positioning. It frames presales as a support function - high volume, reactive, measured by throughput. A two-tier model makes deal influence visible, which matters when budget conversations happen, when headcount requests go in, and when someone needs to justify why presales should have a seat in deal strategy rather than just being dispatched to “do the demo.”

Here’s what the shift sounds like in practice. Instead of “our team ran 47 demos last quarter,” the presales leader says: “Of the 31 deals where we confirmed a technical win before commercial close, we closed 24 - a 77% win rate. Of the 16 where we couldn’t confirm a technical win, we won 3.” That’s a different conversation. That’s a conversation about deal qualification, about where presales effort should be concentrated, about which deals deserve a POC and which ones deserve a polite decline.

The second tier requires manual input or a lightweight tracking habit. It’s not free. But it’s the section that demonstrates strategic value, and strategic value is what keeps presales teams funded, staffed, and involved early enough in deals to actually make a difference.

Nobody’s going to build this for you. Your CRM vendor isn’t going to add a “champion engagement within 48 hours” field to the default layout. It’s a small amount of deliberate work that most teams never quite get around to, which is precisely why the teams that do it stand out.

The spreadsheet isn’t the hard part. The hard part is accepting that the metrics you’ve been reporting might have been measuring how hard your team works rather than how much they influence. Those aren’t the same thing. They never were.