In 2007, I attended IBM Global Sales School, a six-month international sales training program that combined remote learning with intensive classroom sessions in Austria.
We spent a lot of time practicing real customer situations, challenging assumptions, understanding business problems, and learning how to build a business case for change.
One lesson stayed with me throughout my career:
Customers need a compelling reason to move away from the status quo.
It sounds obvious. But even today, I see sales teams presenting impressive solutions without establishing why the customer should change anything at all.
At IBM, we learned to build that compelling reason around four elements.
1. Business pressure: What is making the current situation difficult?
A customer might struggle with rising operational costs, declining productivity, security exposure, or increasing competitive pressure.
But identifying a problem isn't enough.
Is it a problem the organization recognizes? Does it affect an important business priority? And is someone willing to take responsibility for solving it?
A salesperson can uncover a genuine problem that the customer still has no intention of addressing.
2. Economic impact: What does the problem cost the business?
This is where the conversation moves beyond product capabilities.
What does the current situation cost in money, time, lost opportunities, or operational risk?
What could improve if the organization made a change?
Understanding the financial impact helps buyers assess whether the investment deserves attention alongside all their other priorities.
But even a convincing ROI doesn't guarantee a decision.
3. Timeline: Why should something happen now?
A business pressure becomes more actionable when there is a meaningful reason to address it within a specific timeframe.
It could be a regulatory deadline, an upcoming investment cycle, a customer commitment, or a business objective that is becoming harder to achieve.
Without a genuine reason to act now, a project can remain interesting for months.
And artificial urgency created by the seller rarely survives the customer's internal discussions.
4. Significant outcomes: What would make the change worthwhile?
The expected business improvement must justify more than the purchase price.
Customers also need to consider the effort of implementation, the disruption to existing operations, and the resources required to make the solution work.
A solution might promise substantial savings or productivity improvements.
But are those outcomes important enough to justify the organizational effort?
That is the real question.
What I learned later, on the buyer's side of the table
For years, I used these principles in enterprise sales, sales leadership, and conversations with customers.
They worked. And I still use them today.
But my perspective changed when I became involved in enterprise buying decisions myself.
I experienced something that sales training doesn't always prepare you for.
A company can have a strong business case, a real problem, available budget, and a clear reason to act, and still not make a decision.
Why?
Because an enterprise decision is rarely made by one person.
Someone sees the business value. Someone else worries about implementation. IT questions integration or security. Finance challenges the assumptions. Operations worries about resources. Leadership has other priorities.
And the person who wants the solution may have to convince all these stakeholders without the salesperson in the room.
I began to understand that a compelling reason to act is only part of the buying decision.
The organization must also become confident that it can make the change successfully.
From a compelling reason to act to a confident decision
This experience has strongly influenced how I work with founders, sales teams, and sales leaders today.
I still ask the questions IBM taught me:
- What business pressure makes change necessary?
- What is the economic impact?
- Why does the timing matter?
- What significant outcomes could justify the investment?
But now I go further.
Who actually needs to agree?
The person who recognizes the problem may not be the person who controls the budget, approves the solution, or carries the implementation risk.
What happens when your contact discusses the proposal internally?
Can they explain the business case clearly enough to gain support? Do they understand what colleagues will challenge?
What could make the organization hesitate, even when the value is clear?
Sometimes the issue isn't the solution or its price. It's uncertainty about implementation, competing priorities, internal politics, or the consequences of making the wrong decision.
What evidence and conversations would help the buying group move forward?
A stronger presentation isn't always the answer.
Sometimes the buyer needs an internal discussion with Finance, a technical validation, a conversation with Operations, or agreement on what success should look like.
These questions have become central to my Buyer Sense Conversations approach.
The status quo isn't always the enemy
This is probably the biggest shift in my thinking since 2007.
In sales, we often treat the status quo as something we must overcome.
But from the buyer's perspective, maintaining the status quo can feel like the safest available option.
Changing systems, suppliers, processes, or operating models creates uncertainty. People may have to defend the decision, commit resources, and live with the consequences.
Even when the existing situation is far from ideal, doing nothing can appear less risky than making the wrong change.
That doesn't mean buyers don't want to improve.
It means they need enough confidence to commit.
And confidence doesn't come from repeatedly explaining why your solution is better.
It develops when people understand the problem, agree on the priorities, see credible evidence, address the risks, and know what needs to happen next.
Almost 20 years later, I still use what IBM taught me
IBM Global Sales School gave me a foundation that has served me throughout my career.
The four elements of a compelling reason to act remain highly relevant.
But enterprise selling, sales leadership, and eventually sitting on the buyer's side of the table taught me to look beyond the business case.
Today, when a deal stalls, I don't immediately assume the customer lacks urgency or the salesperson hasn't demonstrated enough value.
I want to understand what's happening inside the buying organization.
Who is aligned? Who isn't? What remains uncertain? What risks haven't been addressed? And what would help the people involved feel ready to commit?
Because helping a buyer understand why change makes sense is not the same as helping an organization become ready to make that change.
Both matter.
And that is how my thinking has evolved from IBM Global Sales School to Buyer Sense Conversations.
Petra Wagner
Author of Buyer Sense Conversations: How Founders Help Buyers Make Confident Decisions in Complex B2B Deals