You're twenty minutes into a call with someone who runs a small consulting firm. She has told you her team is stretched across too many projects, that new enquiries sit unanswered for days, and that she has already tried two systems that didn't stick. You know exactly how you would help, so you explain it: the approach, the stages, what usually changes in the first three months. She listens carefully, and at the end she says it all sounds very sensible.
"Sensible" is a polite word. It usually means the explanation made sense in theory, and she still can't picture it working for her.
What often moves a conversation like that forward is a client story, told at the right moment. Client stories in sales conversations do something an explanation struggles to do: they show the prospect someone who started where they are now and ended up somewhere they want to be.
Why an explanation only goes so far
An explanation asks the prospect to do the imagining. They have to take your process, apply it to their own business and decide whether they believe it would work, all while you're still talking. Even experienced buyers find that hard, and many don't try, because saying it sounds sensible is much easier.
That's usually where things start to stall. She asks you to send something over, so you put together a thorough proposal, which is more explanation, and a week later she's still thinking about it. You follow up, she's positive but busy, and the conversation that felt so promising slowly loses its pace. The fit was obvious and the call went well, but she never had a picture she could hold on to. Some of those prospects eventually go with someone else, often someone who simply made the result feel more real.
A story does that imagining for them. When you describe a client who had the same stretched team and the same unanswered enquiries, the prospect doesn't need to translate anything. They hear their own situation, and then they hear what happened next.
In an earlier post, I wrote about what changes when prospects stop comparing options and start picturing the result. Good questions are what get them there. When a prospect needs a little more to feel sure, a well-chosen story can add to that.
What makes a client story work
The stories that help a prospect decide tend to have a few things in common, and none of them require you to be a gifted storyteller.
The starting point matches theirs. The prospect needs to recognise the client at the beginning of the story, so spend most of your time there: the situation, the frustration and, ideally, the doubt they had before starting. A line like "she wasn't convinced another system would make any difference" is often the one that makes a hesitant prospect lean in.
The change is specific. "Things improved a lot" gives them nothing to hold on to. "Enquiries are answered the same day now, and she stopped working Saturdays" gives them something they can picture in their own week.
It's short. A story in a client conversation takes a minute or two. If it needs slides or a long run-up, it has turned into a case study, and the prospect's attention will drift back to their own problems.
When to tell it
Timing matters as much as the story itself. The same story told in the first five minutes sounds like a pitch, because neither of you knows yet whether it's relevant. When you tell it straight after the prospect has described their situation, it shows you've been listening, and that you've seen this before.
The moment to listen for is when they tell you what they've already tried, or what they're worried about. That's usually when "I worked with someone in almost exactly that position" feels like a natural reply, and the story that follows feels like part of the conversation.
Where client stories tend to go wrong
The most common mistake is turning the story into a highlight reel. A run of impressive results, well-known clients or glowing feedback makes it all about you, and prospects notice that. The stories that work are about the client, with you as a supporting character.
The second is finishing the story and moving straight on to your offer. After a good story, the prospect is usually thinking about their own situation, so give them room to say so. A simple "Does that sound close to where you are?" hands the conversation back to them, and what they say next often tells you more than anything else in the call.
Keeping a few stories ready
You don't need a library of case studies. A few short stories linked to the situations you hear most often are enough: the client who had already tried everything, the one who was unsure about the investment, or the one who felt too busy to start. If you haven't worked with many clients yet, these can all come from one or two of them, because a single client journey usually holds more than one useful moment. You'll add variety as your business grows.
Knowing your stories well before the call means you can tell them when the moment comes, instead of searching your memory for an example halfway through a sentence.
Which client story do you find yourself telling most often, and does it start where your prospects usually are?
If you'd like help building stories like these into your own client conversations, it's one of the things we work on in BOOST. Reach out, you can contact me here.
