This is for B2B SaaS account executives, sales managers, and CROs who trust their CRM's "impact" or "value" field more than they should, and for customer success managers who have ever asked a client "what's your objective for next year?" and watched them stare back blankly.
Pain Feels Like Priority. It Isn't.
Every sales methodology since SPIN Selling has told reps to find pain. So they do. A prospect admits their current process is slow, their tool is clunky, or their team is drowning in manual work, and the rep writes "pain confirmed" in the CRM and moves the deal forward. The assumption baked into that step is that pain, once found, will eventually turn into budget.
That assumption is where most B2B SaaS pipelines quietly go wrong. A pain is real the moment someone describes it. A priority only exists once someone with budget authority feels that same pain and decides it deserves resources before every other problem on their desk. Those are two different events, often separated by months, several organizational layers, and at least one person who was never in your discovery call.
Pain doesn't equal priority. A pain becomes a priority the moment someone with budget authority feels it too, and decides it beats every other item competing for the same budget.
I wanted to know how big that gap actually is inside a real pipeline, not as a theory but as a number. So I built one.
Introducing the Impact Ladder
I went back into a client's CRM and scored a full year of closed deals against a scale I call the Impact Ladder. It is a five-level model for scoring how far the pain a rep uncovers actually reaches inside a prospect's organization, from a single user's inconvenience at level one to an executive-level priority at level five, and it is designed to separate a real, budgeted problem from a polite conversation.
I want to be precise about what this scale is not. It is not a proxy for deal size, and it is not the same as the Altitude dimension I've written about before, which asks whether a rep translated a user-level pain into business language during a single conversation. The Impact Ladder asks a longitudinal question: across the entire deal, including every conversation with every stakeholder, how high did the confirmed pain actually climb, and did anyone with the authority to fund it confirm it applied to them.
What the Data Actually Showed
I scored a full year of closed-won and closed-lost deals against the ladder using the CRM's own impact field, tracked per rep. The pattern held across the majority of the group: closed-won deals scored a higher average impact level than closed-lost deals.
Closed Won consistently scores higher than Closed Lost on impact across the group. Rep D is the one rep who bucks the trend, and that's exactly the kind of outlier worth a closer look.
Averaged across the group, closed-won deals landed at 3.67 on the ladder, closed-lost deals at 3.57. That is the difference between "departmental problem" and "departmental problem, slightly more department-wide." It is not the difference between a user complaint and an executive priority. Every rep in the group, won or lost, sat somewhere in a narrow 3.1 to 3.9 band. Nobody was reliably reaching level four or five.
A CRM dropdown field is only as good as the rep filling it in, so I ran a second pass to pressure-test it. I pulled AI-generated call transcript scoring (Modjo) for a wider group of twelve reps across three regional teams, unfiltered and unedited by the rep, and scored those against the same ladder.
The pattern holds across the majority of the group. Rep D repeats as the outlier here too, the same reversal showing up in two independent scoring methods.
The pattern held again: closed-won averaged 3.36, closed-lost (or lost to status quo, where no competitor won but the prospect simply didn't act) averaged 3.25, confirmed across the majority of the group.
The average deal doesn't stall because nobody found a pain. It stalls because nobody ever proved the pain was worth more than the fourth item on someone's priority list.
One result stood out. A single rep's CRM data ran backward, closed-lost scoring higher than closed-won, and the independent call transcript data showed the exact same reversal for that rep. Two unrelated measurement methods agreeing on the same anomaly is a real signal. That's the kind of thing a coaching conversation should chase down, not a training deck.
There's also a regional pattern worth flagging: one team, scored only through call transcripts, ran backward as a group, closed-lost averaging higher than closed-won. That's the kind of split a single company-wide average buries completely. It only shows up once you break the data down by team.
Here is the part that should worry any sales leader more than the raw numbers: in the underlying CRM, executives were visibly involved in a meaningful share of these deals later in the cycle. The information gap wasn't access. It was that once an executive joined a call, nobody went back and re-tested whether the pain, first surfaced weeks earlier with a mid-level champion, actually registered as a priority for them. The altitude score from the first conversation just carried forward, untouched, as if it were still accurate.
The One-and-Done Discovery Trap
Most sales training treats discovery as a stage: you complete it, you tick the box, you move the deal to the next phase. That framing is the root cause of what the data shows.
Discovery information is not canned goods. It doesn't sit on a shelf indefinitely and stay usable. It behaves more like fresh produce: accurate for a while, then quietly past its best. A budget cycle closes. A reorg happens. A competing initiative gets funded instead. The pain a mid-level champion described in month one might still be technically true in month four, and completely irrelevant to what the business is now prioritizing. Most reps never check the expiration date. They keep selling against information that went stale two stakeholder conversations ago.
This connects directly to a distinction worth naming explicitly: the difference between a champion and a fan. According to Nate Nasralla in Selling With, a real champion has three things: incentive, influence, and deal intelligence, meaning they can actually show you the map of how their organization decides. A person with only the first of those three will happily confirm your pain is real. They cannot tell you whether it is a priority, because that answer sits above their own line of sight.
Nasralla also describes what he calls the twenty-second death conversation: the moment your champion mentions your deal to their boss in a hallway, gets a "not a priority right now, let's revisit," and the deal is over before you ever hear about it. If the only altitude score you have came from the champion, you have no way of knowing that conversation is coming. Challenger's research on buying groups tells a similar story from a different angle: buying committees have grown from an average of 5.4 to 11.1 stakeholders, and buyers leave vendors out of their own internal problem identification roughly 90% of the time. Whatever gets decided about priority inside that group happens largely without you in the room, which is exactly why re-testing altitude every time a new stakeholder appears is not optional.
Reps don't skip this because they're lazy. They skip it because nobody scored them on it. A discovery call that reaches level three on the Impact Ladder still looks like a completed discovery call in most CRMs. Nothing in the pipeline flags that the altitude was never verified with the person who eventually has to sign off on the spend.
This Isn't Only a Sales Problem
I run upsell and expansion training for customer success teams, and I see the exact same gap show up in a different room.
In my upsell and expansion training, one of the first exercises I run is asking CSMs to ask their client directly: "What is your objective for the next year?" Most CSMs, when they actually try this in a live account, get a look back that says the client thinks they're speaking a language they don't understand. Not because the question is unclear, but because nobody at that account has ever expected their CSM to operate at that altitude. The CSM's own line of sight, as far as their client is concerned, stops at renewal and support tickets. They were never positioned to be asked strategic questions, so naturally, they're never given strategic answers.
A champion's line of sight stops wherever their own job title stops. Yours can't.
That's the actual argument for building executive relationships early in the customer lifecycle, not just at renewal risk, and maintaining them with a half-yearly or yearly executive business review. It's not a courtesy touchpoint. It's the only mechanism that keeps your altitude score current instead of frozen at whatever level your original champion happened to occupy.
This is the same underlying failure showing up in prospecting, in discovery, and in expansion: information about priority gets captured once, from whoever happens to be in the room, and then treated as permanent. It isn't. It touches every part of commercial life where one person's authority is mistaken for the organization's.
How to Actually Climb the Ladder
Talking to executives well is a different skill from talking to champions well, and it comes with real constraints.
Do the groundwork with your champion first. You still need someone inside the account to tell you what a mid-level manager is dealing with day to day. That conversation earns you the vocabulary and the specifics you'll need later. Skipping straight to the executive without that context wastes the one shot you'll get with them.
Prepare like it's a credibility test, because it is. Before an executive conversation, read what's public: press releases, the annual report if the company publishes one, recent funding or leadership news. Walk in with an informed hypothesis about what matters to them this year, not a blank slate. Executives can tell within a minute whether you did the reading.
Respect discovery fatigue. Executives get pitched constantly and have far less patience for open-ended questioning than a champion does. Plan for a maximum of around five sharp questions, then move to delivering value: a point of view, a relevant data point, something that earns the rest of the conversation instead of spending it on discovery alone.
Ask the altitude question directly. Something close to: "Here's what I heard from your team about [specific pain]. How does that show up for you, at your level?" That single question, repeated with every new stakeholder you meet, is what re-scores the deal on the Impact Ladder instead of letting the original score go stale.
Verify, don't assume. The goal of the executive conversation is not to re-sell them on the pain your champion already confirmed. It's to find out whether that pain, at their altitude, competes for budget against everything else they're funding this year. If it doesn't, you don't have a qualified deal. You have a well-documented level-three problem that nobody with authority has agreed to fix.
| Champion's line of sight | Executive's line of sight | |
|---|---|---|
| What they see clearly | Day-to-day friction, team-level workarounds | Budget priorities, competing initiatives, P&L impact |
| What they can confirm | That a pain exists and is real | Whether that pain is worth funding over other options |
| Typical Impact Ladder level reached | 2 to 3 | 4 to 5, but only if directly asked |
| Risk if you rely on them alone | You mistake a real pain for a funded priority | You never learn what the pain is actually like on the ground |
Neither line of sight is sufficient on its own. The deal needs both, verified in sequence, not just accessed once.
Frequently Asked Questions
The Impact Ladder is a five-level scale, from user inconvenience to executive priority, used to score how far a confirmed pain reaches inside a prospect's organization. It helps separate a real but low-altitude pain from a fully budgeted business priority.
Pain is a negative experience someone describes during discovery. Priority exists only once a person with budget authority recognizes that same pain and chooses to fund a fix for it ahead of competing initiatives. A deal can have confirmed pain and still have no priority behind it.
Usually because the pain's altitude was scored once, early, with a mid-level champion, and never re-verified once an executive joined the process. The original discovery information gets treated as still accurate instead of re-tested with the new stakeholder.
According to Nate Nasralla's Selling With, a real champion has incentive, influence, and deal intelligence. A fan may have genuine enthusiasm and confirm your pain is real, but lacks the influence or intelligence to tell you whether that pain is an organizational priority.
Every time a new stakeholder enters the conversation, not just once at the start. Priority information is perishable: budget cycles, reorgs, and competing initiatives can make an accurate discovery from month one irrelevant by month three.
Where This Leaves You
Check your own pipeline against the Impact Ladder before you check anything else this week. Pull ten open deals and ask, honestly, what level the confirmed pain actually reaches, and who verified it at that level. If most of them sit at three, you don't have a pipeline problem. You have a discovery habit problem, and it's fixable faster than most people think.
Find out where your team's pain scoring actually lands
The Gap Analysis scores real calls from your team against the same dimensions used here: pain, impact, novelty, and altitude. No generic benchmark, just your pipeline.
