Why Decision-Makers Hesitate (Even When the Capability Is There)
She had the proposal open but wasn’t really looking at it anymore.
The cursor was sitting halfway down the page, blinking in the margin next to a paragraph no one had mentioned. Something about implementation support. It had clearly been written carefully. You could tell by the way the sentences held together.
She kept scrolling up and down, not reading so much as moving.
“Everything looks good,” she said.
Not to anyone in particular. More like she was checking how it sounded out loud.
Someone from her team asked if there were any concerns.
“No,” she said. “No, I think you guys covered it.”
Then she went back to the top again. Slower this time. She stopped on the headline for a second, then moved down a few lines and paused again, like she had lost her place and didn’t want to admit it.
It went quiet in that way calls do when everyone assumes the decision has already been made and is just waiting to hear it said.
I’ve seen people say yes faster to things that were worse.
That part never quite makes sense when you’re in it. The work is right there. You can feel it. And it still doesn’t move.
She asked one more question about timing. Not because she needed the answer—it was already in the document—but because the conversation hadn’t settled yet.
Someone answered anyway. Clean, direct, exactly what was already written a few lines below where her cursor had been a minute earlier.
She said “okay,” and you could hear the nod even though her camera was off.
Then she said, “Let me just run this by a couple people on my side.”
No one pushed back. It’s a reasonable thing to say.
But it’s not always about other people.
If you’ve been on enough of these calls, you start to recognize the difference between someone who actually needs to check internally and someone who is buying a little time because something hasn’t landed yet.
Nothing was wrong with the proposal.
The team was credible. The examples held up. The pricing wasn’t the issue. If anything, it was cleaner than most of what they were probably seeing.
But there wasn’t a moment in that conversation where you could feel her decide.
Not even a small one. Not a shift in tone, not a question that moved things forward instead of sideways.
It all stayed slightly provisional.
Like she was waiting for something to click and it never quite did.
And it’s not that she couldn’t understand what they did. She could repeat it back well enough. She had already done that earlier in the call, almost word for word from their site.
That’s usually what makes this hard to catch.
The information is there. The explanation is technically clear. If you asked her to summarize it, she probably could.
But nothing in the way it was expressed made the next step feel obvious.
There wasn’t a point where the decision felt like the natural continuation of what she had just heard.
So the decision stretched.
And that part is easy to miss if you’re not looking for it. It just feels like a normal buying process taking its course.
But you can feel when something should have moved and didn’t.
That gap is small when you try to point at it. Hard to explain without sounding like you’re overanalyzing something routine.
It usually shows up in small ways.
A cursor blinking next to a paragraph no one is talking about.
A question that gets asked twice.
Someone saying everything looks good and not moving.
Share:
Search our blog:
Follow us on: