Enterprise sales
One of the weirdest things about sales is how often you can do almost everything right and still lose to absolutely nothing.
The buyer agrees there’s a problem.
They understand what it’s costing them.
They like the solution.
The ROI makes sense.
You’ve handled the objections.
You’re probably the preferred vendor.
And then the deal just stops moving.
No competitor swoops in.
Nobody dramatically undercuts your price.
There is no shocking procurement scandal.
The buyer simply does nothing.
The opportunity sits in Salesforce for another six weeks while everyone involved pretends it is still “active.”
Eventually somebody changes the close date.
Again.
And again.
At some point, the deal stops being a sales opportunity and becomes a historical artifact.
I’ve sold through very different environments over the years, from short-cycle transactional sales to larger enterprise deals, and one thing has become increasingly clear:
In a lot of complex sales, your biggest competitor is nothing.
The buyer’s default option is to leave everything exactly the way it is.
And nothing has some very unfair advantages.
Think about what a buyer has to do to purchase something new.
They may have to get budget approved.
They may need legal.
Procurement.
IT.
Finance.
A security review.
An executive sponsor.
A stakeholder who mysteriously appears three months into the deal and apparently has veto power over everything.
Then somebody has to implement the solution.
Employees may need training.
Processes may need to change.
Data may need to move.
Someone may eventually have to explain whether the investment actually worked.
Doing nothing has none of these requirements.
The status quo is already implemented.
Everyone has been trained on it.
Legal has approved it by virtue of nobody asking legal anything.
Procurement has no questions.
Finance has no paperwork.
And if the current process continues producing mediocre results, there usually isn’t one person in the organization who gets blamed for selecting it.
That matters more than most salespeople realize.
Let’s say you’re a VP responsible for evaluating a $150,000 purchase.
If you approve it and everything works perfectly, the company gets the benefit.
Maybe you get some credit.
Maybe somebody says “great job” in a leadership meeting before immediately moving on to the next slide.
If you approve it and the implementation becomes a six-month disaster, suddenly everyone remembers exactly whose idea it was.
There’s an asymmetry there.
The upside belongs mostly to the business.
The downside can feel very personal.
That’s one of the reasons I think salespeople sometimes misread hesitation late in the process.
We assume the customer needs more proof that the problem is painful.
They may already understand the problem perfectly well.
What they’re struggling with is the decision.
This is one of the ideas from The JOLT Effect that changed how I think about complex sales.
A buyer can understand why they should change and STILL be afraid to make the change.
Those are different problems.
Earlier in a sales process, you’re often trying to establish why anything needs to change in the first place.
What’s broken?
What is it costing?
What happens if the current situation continues?
This is where a lot of Challenger and SPIN-style thinking becomes useful.
Help the buyer understand the problem.
Help them quantify the impact.
Maybe challenge the way they currently think about it.
At some point, though, the buyer may fully agree with you.
“Yes, this is a problem.”
“Yes, we should fix it.”
“Yes, your solution makes sense.”
And still hesitate.
Now they’re asking a different question.
“What if we make the wrong decision?”
That transition is incredibly important.
If the buyer is worried about choosing incorrectly and the salesperson keeps pounding on the pain, the conversation starts getting strange.
“Yes, I understand your concern about implementation. But remember, your current process is costing you $300,000 a year.”
They know.
That’s why you’ve all been meeting for two months.
You’re essentially shouting the fire alarm at someone who is already standing outside the building.
At that point, the job changes.
Salespeople are taught to find pain for good reason.
If the problem is vague, the deal usually becomes vague too.
You need to understand what is happening, why it matters, and what the customer stands to lose by leaving it alone.
But pain has limits.
There comes a point where piling more pain onto the conversation can actually increase the perceived risk of making the decision.
Now the customer isn’t thinking:
“This is a $300,000 problem.”
They’re thinking:
“This is a $300,000 problem and apparently I’m responsible for choosing the thing that fixes it.”
Fantastic.
No pressure at all.
This is where I think a lot of reps confuse urgency with anxiety.
You want urgency.
You want the buyer to understand that delaying the decision has consequences.
But if the buyer becomes so anxious about the decision that doing nothing feels safer, you’ve created movement in the wrong direction.
One of the most useful things a salesperson can do is help the buyer stop thinking of “do nothing” as the neutral option.
Doing nothing is still a decision.
If the current problem costs $20,000 per month, waiting another six months has a cost.
If the sales team is losing hundreds of hours to bad data, keeping the same process has a cost.
If change orders are consuming days of manual work, continuing to process them manually has a cost.
If a bad customer experience is suppressing conversion, keeping the exact same experience has a cost.
The status quo feels free because nobody sends an invoice for it.
That doesn’t make it free.
Sometimes the most important part of the business case is making that visible.
Not dramatically.
Not with some ridiculous “Can you afford NOT to do this?” line delivered like you’re selling timeshares in Orlando.
Just clearly.
“If nothing changes over the next 12 months, what does that look like?”
That can be enough.
There is a point late in a complex deal where more selling can make things worse.
The customer already understands the problem.
They already understand the product.
They already believe there is value.
The rep senses that the deal is close and becomes increasingly enthusiastic.
The buyer senses that the decision is close and becomes increasingly nervous.
These two emotional trajectories often collide in a proposal meeting.
The rep is thinking:
WE CAN GET THIS IN THIS QUARTER.
The customer is thinking:
If this goes badly, Karen from Finance is going to bring it up until one of us retires.
This is where clarity becomes more persuasive than excitement.
What happens after they sign?
Who owns implementation?
How long does it take?
What does the customer need to provide?
Where do implementations typically get delayed?
What happens if adoption is slower than expected?
What are the real risks?
What can be done to reduce them?
What does success look like 30, 60 or 90 days later?
The closer you get to a decision, the more concrete the path forward should become.
Another place I see deals get stuck is when salespeople give the customer too many choices.
This usually comes from a good place.
The rep wants to be consultative.
So the customer gets six packages, four implementation options, eleven add-ons and a pricing document that looks like they’re configuring a new Porsche.
Then we tell them:
“Take a look and let me know what you think.”
That’s not always helpful.
If I’ve spent weeks learning someone’s business, understanding their problem, mapping stakeholders and figuring out what matters, I should have an opinion.
“Based on everything you’ve told me, this is the option I would recommend.”
And then explain why.
That doesn’t mean hiding choices.
It means reducing unnecessary cognitive load.
The buyer hired you, at least temporarily, to help them evaluate a solution.
Act like an advisor.
If your answer to every decision is “whatever you guys want,” eventually you’re just a very expensive menu.
This is also why credibility matters so much throughout the entire sales process.
Credibility is not something you establish once during the first five minutes of discovery and then keep forever.
It accumulates.
You said you’d send something Tuesday.
You sent it Tuesday.
You told them you’d get an answer.
You got the answer.
You admitted when you didn’t know something.
You told them one feature probably wasn’t necessary.
You didn’t try to cram another $20,000 into the deal because it was technically possible.
You remembered what they told you three meetings ago.
You understood their concern before responding to it.
By the time the customer has to make the decision, all of those little moments matter.
Because now you may need to say:
“If I were in your position, based on everything we’ve discussed, this is what I would do.”
That sentence only has value if you’ve earned the right to say it.
When a deal stalls, I don’t think the answer is always “follow up more.”
Sometimes sales teams treat stalled deals like vending machines.
Insert another email.
Press B7.
Maybe a purchase order falls out.
Instead, I want to understand why the decision stopped moving.
Is there still disagreement internally?
Did a stakeholder appear late?
Did the business case weaken?
Did priorities change?
Is implementation making them nervous?
Are there too many options?
Is the decision-maker worried about personal risk?
Is there simply no deadline forcing action?
Or did we fail earlier in the process to establish why this problem matters enough to solve?
Those are very different situations.
The response should be different too.
Sometimes a stalled deal needs more urgency.
Sometimes it needs reassurance.
Sometimes it needs simplification.
Sometimes it needs another stakeholder.
And sometimes the correct answer is that the deal was never as real as we wanted it to be.
Salespeople are not always famous for enjoying that last possibility.
One of the ways I think about enterprise selling is that the buyer often has to sell the decision internally after you leave the room.
So help them.
Give them the numbers.
Give them the business case.
Give them a clear explanation of the problem.
Give them a simple explanation of why this solution makes sense.
Give them proof.
Give them an implementation plan.
Give them something they can forward to someone without needing a 45-minute phone call to explain what you meant.
The easier the decision is to defend internally, the easier it becomes to make.
That’s part of reducing perceived risk.
A buyer does not just need to believe the decision is right.
Sometimes they need to believe they can explain WHY it is right to five other people who were not on your discovery calls.
The more complex the sale gets, the less I think closing is about one magical closing technique.
It’s the accumulation of everything that came before it.
Do they trust you?
Do they understand the problem?
Do they understand the cost of leaving it alone?
Do they believe the solution fits?
Can they defend the investment?
Do they understand what happens next?
Do they feel confident enough to make the decision?
That last part matters.
Because customers usually don’t need 100 percent certainty.
Nobody has that.
They need enough confidence that making the decision feels more reasonable than avoiding it.
And that’s where the status quo finally starts losing its advantage.
The biggest competitor in a complex deal may never appear on a competitive matrix.
It doesn’t have a website.
It doesn’t have a sales team.
It won’t undercut your price.
It won’t send a proposal.
It just sits there.
Quietly.
Already implemented.
Already approved.
Requiring no signatures.
That’s what makes it so difficult to beat.
So when a customer understands the problem and likes the solution but still isn’t moving, I try not to assume they need to be sold harder.
Sometimes they need the decision made clearer.
Sometimes they need fewer options.
Sometimes they need more confidence in implementation.
Sometimes they need to understand that staying exactly where they are carries its own risk.
And sometimes they simply need someone credible enough to say:
“Based on everything you’ve told me, this is the path I would take.”
Because at the end of the day, doing nothing isn’t the absence of a decision.
It is a decision.
And it should have to defend itself just like every other option.