The Why Change Pyramid

By Pete Sanidas · Updated October 2026

The Why Change Pyramid is a framework for building the case for change one level of the buying organization at a time. End users care about capabilities and time saved. Managers care about KPIs and functional objectives. Executives care about top-line growth and bottom-line impact. A why-change case only survives the buying process when it climbs from the bottom of that ladder to the top, using the buyer's own answers to connect each rung to the next.

TL;DR

Every level of the org buys a different kind of value. Pitch the wrong rung to the wrong person and they tune out, politely.
The ladder runs from capabilities, to administrative efficiency, to functional objectives, to business impact. Executives sign at the top rung. Vendors almost always pitch the bottom one.
You climb with four questions, asked at the right level. The buyer answers them, so the case at the top is built in their words, not your deck's.
Somebody inside has to carry it up, and it's rarely the decision maker. Authority figures in complex deals have influence and incentive but don't get into the weeds. The case has to arrive at their desk already built.
Cover every level and let the buyer build the case, and you get the highest-probability deals with the least friction.

Persona pyramid

Why-change ladder

Value conversations

What is the Why Change Pyramid?

Three pieces, read side by side:

Level of the buying org	Why-change rung (what changes)	Value conversation (how you talk about it)
C-suite (top: fewest people, the signature)	Business impact. Top-line growth, bottom-line impact.	ROI, the business case, revenue drivers.
Directors and managers (the middle)	Functional objectives. Plus administrative efficiency.	KPIs, oversight and reporting, capacity improvement.
End users (the base: the most people, closest to the work)	Capabilities. What the product actually does.	Process-based time savings. Removing frustration.

The left side is the persona pyramid: who's in the deal. The middle is the why-change ladder, drawn as an inverted triangle because value starts as one narrow capability and widens into impact on the whole business as it climbs. The right side is the value conversation: the language that lands at each level.

Why do most why-change cases fail?

They pitch the wrong rung to the wrong level. The vendor leads with capabilities, the bottom rung, in front of an executive who only signs at the top one. Or they hand a full ROI model to an end user who just wants her Friday afternoons back. Both conversations are polite. Neither moves anything.

Here's the ladder for a sales-engagement tool:

Rung	What it sounds like
Capabilities	AI personalization, better sequence automation
Administrative process	Better reporting, CRM integration that doesn't break
Functional outcome impact	More leads, higher-quality leads, better conversion rates
Business impact	Faster, larger revenue. Lower CAC.

"AI personalization" means something to an SDR. It means nothing to a head of sales until it turns into conversion rates, and nothing to a CEO until it turns into CAC. Same product, same feature, four different reasons to change. The rep who only knows how to say the first one is going to lose the meeting with the person who signs.

How do you climb the pyramid?

You don't climb it with slides. You climb it with questions, and the buyer does the climbing.

At the base, connect the capability to their goals.
"How would this capability help your team meet its goals?"
Ask the end user. Their answer turns a feature into something they'd actually defend.

Turn time saved into objectives.
"How would this efficiency help you reach your objectives?"
Saving time isn't the outcome. What the team does with that time is. This question makes the buyer say it.

Establish why now.
"Why does this need to be improved now?"
No answer means no urgency, and no urgency means the deal sits in your pipeline until it dies there. Better to find out on call two than in month seven.

Tie the KPIs to the company's strategy.
"How would improving your KPIs align with your top-level corporate objectives or strategic pillars?"
This is the question that gets a manager to write your business case for you, in language the C-suite already uses.

Let the buyer take it to the top.
By the time the case reaches the executive, it should be ROI, business case, and revenue drivers, built from answers their own team gave. You didn't argue for change. Their org did.

Who carries the case up?

The pyramid tells you what to say at each level. It doesn't tell you who will carry it upstairs for you. For that, map everyone on three traits: influence (can they move the decision?), incentive (do they personally win if it changes?), and information (do they know how the decision really gets made?).

Champion: all three. Rare. Protect them.
Coach: incentive and information, no influence. They'll tell you the truth. They can't move the deal.
Influencer: influence and information, no incentive. They can sway the room, but they won't push.
Decision maker: influence and incentive, light on information. In complex deals the person with authority rarely gets into the weeds. That's normal, and it's also why they can't build the case themselves.

Most deals that "had a champion" actually had a coach. Good intel, no power, and a case that never left the middle of the pyramid.

How do the pieces fit together? Highest-probability deals, least friction.

Two questions decide almost every complex deal. Will it happen? And how hard will it be to get there? The Why Change Pyramid answers both, and the deals that score well on both are the only ones worth building a quarter around.

Probability comes from coverage. A deal closes when every level that can say no has its own reason to say yes. The end user got time back and less frustration. The manager got a KPI they can defend. The executive got a business case priced in revenue and margin. Miss a level and there's a quiet no sitting somewhere in the org chart. You won't find it until the deal slips.

Friction comes from translation. Every time the case moves up a level and has to be rebuilt, you lose a week, a meeting, or the deal. Friction is the rep re-pitching to the boss. It's the champion explaining your product in their own words and getting it wrong. It's the CFO asking for a business case nobody wrote. The climbing questions remove most of it, because the buyer answers them at each level in their own language. By the time the case reaches the top, there's nothing left to translate.

The carrier connects the two. In a complex deal, the decision maker has the influence and the incentive but rarely the information. They don't live in the weeds, and they shouldn't. That gap is exactly what the pyramid fills. The people who do have the information (end users, managers, your coach) build the case on the way up. A champion with all three traits puts it in front of the person with authority, finished.

So the highest-probability, lowest-friction deal looks like this: every level has its own reason to change, the case climbed in the buyer's own words, and a champion handed it to a decision maker who never had to get into the weeds to say yes.

Score any deal in your pipeline with five questions:

Does every level in the deal have its own reason to change, in its own language?
Did the buyer answer the climbing questions, or did you answer them for them?
Is there a "why now" with a date attached?
Is the person carrying the case a champion, or a coach?
Does the decision maker have a finished business case they can approve without the details?

Five yeses is a deal worth your best hours. Two or three tells you exactly which conversation is missing.

What it shows up as. Four numbers move when deals look like this: likelihood of change (no quiet no in the org chart), value (a case priced at business impact supports a bigger deal than one priced at features), velocity (nobody rebuilds the case for the next meeting), and retention and expansion (end users were sold time back, not someone else's ROI, so they actually use it).

Even a perfect pyramid can stall. Here's why.

A buyer can climb the whole pyramid, agree change is needed, and still freeze. Matthew Dixon and Ted McKenna studied more than 2.5 million recorded sales conversations for The JOLT Effect (2022) and found that 40 to 60 percent of qualified deals end in no decision, mostly because buyers were afraid of getting the choice wrong, not because they preferred the status quo. The pyramid wins the argument for change. What comes next is taking the risk out of saying yes: a clear recommendation, a smaller first step, a way out if it fails.

Take it to the next level with HBX Lens

The pyramid tells you what each level needs to hear. It doesn't tell you how this particular person needs to hear it. Two VPs on the same rung can need completely different versions of the same case: one wants the number in the first sentence, the other won't trust a number until they've seen how you got it. That's what HBX Lens adds. Every buyer reads as one of eight Lens Types, and each one changes how you build and deliver the why-change case.

Same pyramid. Same rungs. Eight ways to present it:

Lens Type	How they hear "why change"	Lead the case with	How the climb changes
Visionary	End state first. One bold claim, no setup.	Where the business is in a year if it changes, and what waiting costs in missed upside.	Start at the top rung and work down only if asked. Three slides, max.
Finisher	Number first. Short. No warmup.	The cost of waiting, as one number they gave you.	Put a figure on every rung. If a rung can't be quantified, cut it.
Catalyst	Warm, with names and energy. Show, don't tell.	A team like theirs, with the people named, and what changed for them.	Climb through people: whose week gets better at each rung.
Relator	Together, low pressure, complexity acknowledged.	"Here's what we heard from your team."	Climb slowly and build the case with them, not at them. ROI comes last and soft.
Architect	Sequence, mechanism, one concrete proof.	How it works, step by step.	Climb every rung in order and show the logic connecting them. Keep the ROI assumptions visible.
Guardian	Precedent. Reassure before you provoke.	Who else like them has already done it.	Frame inaction as the riskier precedent. Take the risk off the table before you add urgency.
Specialist	Clinical. Mechanism, not benefit.	The mechanism, with the assumptions exposed.	Go deep on the capability rung and skip the hype at the top. Let them reach the business case themselves.
Skeptic	Shortest version. A fact and an ask. No enthusiasm.	One fact and one question.	Make the assumptions editable and include what didn't work. Never push urgency.

Two rules keep this honest. A lens tells you how to say it, not whether they'll buy, so it changes the register and the order, never the facts. And when you don't know someone's lens, default to the most common Lens Type for that persona. Individual Analysis in GTM Heroes shows you which one that is from your own data: every prospect and customer you've profiled, broken down by persona and Lens Type.

In HBX: "Why Change" is a named stage in the Sales Execution Blueprint. HBX reads each stakeholder's Lens Type, works out which rung of the pyramid they decide on, and drafts the why-change case in their register from your own calls and emails. One deal, six stakeholders, six versions of the same case.

Start free

FAQ

What is the Why Change Pyramid?
A sales framework that maps each level of a buying organization (end users, managers, executives) to the type of value it cares about (capabilities, functional objectives, business impact) and the conversation that lands at that level. A case for change is built by climbing from the base to the top with questions the buyer answers.

Who created the Why Change Pyramid?
Pete Sanidas, founder of GTM Heroes, built the Why Change Pyramid to map the case for change onto the way complex B2B buying groups actually decide.

How do you find the highest-probability deals in a pipeline?
Look for coverage and low friction. Every level of the buying org has its own reason to change, the buyer built the case in their own words, there's a why now with a date, and a champion (not a coach) is carrying it to a decision maker who can approve it without the details. Deals missing two or more of those are forecast risk, whatever stage the CRM says.

When do you use it in the sales cycle?
Between discovery and the first real demo. Discovery tells you who's at each level. The pyramid builds the case for change before you show any product. Demo first, and the buyer judges your product against doing nothing, and doing nothing is free.

How is the Why Change Pyramid different from an ROI calculator?
An ROI calculator only works at the top rung, and it's your math about your product. The pyramid builds to ROI using the buyer's answers at every level below it, so by the time the executive sees the number, their own team has already defended it.

What if I can only reach end users?
Then your job is to build the champion who climbs it for you. Arm the end user with the base-level answers and the question that ties them to their manager's KPIs. A case that only exists at the base will never reach the signature.

How is this different from "Why Change, Why Now, Why You"?
That model sequences the argument over time. The Why Change Pyramid maps the argument to the org chart, so each level gets the value it actually decides on. They stack. The pyramid tells you what "why change" has to sound like to each person in the deal.