Vocabulary
8 key words for this lesson
NARRATIVE
A structured account that moves through a beginning, middle, and end. In sales, a narrative is more persuasive than presenting facts in isolation — because it gives the listener a way to locate themselves in the story and imagine the outcome for their own situation.
Riley did not list the product features. She built a narrative: a specific company, a real problem, a moment of change, and a measurable result. By the end, Marcus had not been sold to — he had been shown what was possible.
TENSION
The sense of risk, urgency, or unresolved conflict that makes a story worth hearing. Without tension, there is no reason for the listener to care about the outcome. Tension in a sales story comes from showing what was at stake if the problem was not solved.
Riley did not rush past the problem. She held the tension: the team was losing two hours per rep per day, the quarter-end was approaching, and the VP of Sales was asking for answers. That pressure made the solution feel necessary, not optional.
STAKES
What was at risk if the problem remained unresolved — the cost of inaction in human, financial, or strategic terms. High stakes are what make tension feel real. A story without visible stakes is a description of a problem, not a story about one.
The stakes in Riley's story were specific: the company was about to lose its third enterprise client in a row to a competitor with faster response times. That detail made the problem impossible to ignore — because Marcus recognised the same pressure in his own business.
TURNING POINT
The moment in a story where something changes — the decision, discovery, or intervention that shifts the trajectory from problem toward resolution. In a sales story, the turning point is usually when the solution enters, but it should feel like a story moment, not a product pitch.
Riley described the turning point not as 'they implemented our software' but as 'the week their ops lead stopped spending Fridays building manual reports and started spending them coaching the team.' That shift — from describing a feature to naming a moment — made Marcus lean forward.
RESOLUTION
The point in a story where the tension is released and the outcome becomes clear. A strong resolution is specific and measurable — it shows what changed in terms the listener can evaluate. A vague resolution ('things got better') is almost as ineffective as having no resolution at all.
Riley's resolution was precise: twelve weeks after implementation, the team's average response time dropped from four hours to forty minutes, and the client retention rate recovered by 18 percentage points. The resolution gave Marcus something concrete to take to his CFO.
PROTAGONIST
The central character in a story — in sales, usually a customer or user whose experience the prospect can identify with. For a sales story to land, the prospect must be able to see themselves in the protagonist. A protagonist who is too different from your audience makes the story feel irrelevant.
Riley chose her protagonist carefully: a VP of Sales at a B2B software company with 25 reps, a fast-growth mandate, and a workflow problem that was invisible to the C-suite. Marcus had 22 reps. The similarity was not an accident.
VIVID
Producing strong, clear mental images through specific details — names, numbers, moments, and sensory descriptions — rather than generalisations. Vivid storytelling makes abstract value concrete. The more specific a detail, the more real the story feels, even to someone who was not there.
Riley did not say 'the team was overwhelmed.' She said 'by Thursday afternoon, the support queue had 340 open tickets and the team lead had stopped answering Slack messages.' The specific number and the specific behaviour made the scene visible — which made it believable.
RESONANCE
The quality of connecting deeply with someone's own experience — the feeling that a story is describing something the listener recognises, not just something that happened to someone else. A story has resonance when the prospect says — out loud or internally — 'that is exactly what is happening to us.'
Halfway through Riley's story, Marcus stopped taking notes. He was no longer evaluating the story — he was inside it. That moment of resonance — where the protagonist's situation became his situation — was worth more than any slide in the deck.
Phrases
6 phrases and their meanings
LET ME TELL YOU ABOUT A CUSTOMER WHO
The opening line that signals a story is coming. It shifts the register from pitch to conversation, invites the prospect to listen rather than evaluate, and positions what follows as evidence rather than assertion.
'Let me tell you about a customer who had almost exactly the situation you are describing — because I think the way it resolved is relevant to the conversation we are having today.'
THE PROBLEM WAS
The line that sets up the problem clearly and specifically — not as a category ('they had an efficiency issue') but as a concrete, named situation. The more specific the problem, the more the prospect recognises it.
'The problem was that every time a new enterprise client onboarded, the same three people had to drop everything for two weeks. It was not a capacity problem — it was a process problem that looked like a capacity problem, and no one had separated the two.'
WHAT MADE IT WORSE WAS
The tension escalator — a second detail that deepens the urgency of the problem before the solution arrives. Used to hold the tension longer, which makes the turning point feel more earned when it comes.
'What made it worse was that the board had just approved headcount for three new enterprise sales reps — which meant the onboarding problem was about to get significantly larger before anyone had fixed it.'
THE TURNING POINT WAS WHEN
The phrase that introduces the solution or intervention — but as a story moment, not a product feature. The turning point should describe a change in what someone was able to do, not a change in what software they were using.
'The turning point was when the ops lead ran the first automated onboarding sequence and realised she had been doing manually in two weeks what the system did in four hours. That was the moment the conversation with leadership changed.'
THREE MONTHS LATER
A time marker that creates narrative distance between the problem and the outcome, making the resolution feel earned rather than immediate. Can be adapted — 'six weeks later', 'by the end of Q3' — but always puts the outcome at a credible remove from the intervention.
'Three months later, the average onboarding time had dropped from fourteen days to three. The three new sales reps the board had approved were fully supported. And the ops lead was spending her Fridays on process improvement instead of manual configuration.'
WHAT THAT MEANT FOR THEM WAS
The translation layer — converts the outcome from a metric into a business impact the prospect can evaluate. Not 'the product worked' but 'what that meant in practice was that they stopped losing enterprise clients to a competitor with a faster response time.'
'What that meant for them was that they closed Q4 as their best quarter in three years — not because the market changed, but because the team finally had the headroom to do the work they had been hired to do.'
Videos
Watch these terms used in context
Dialogue
Read the dialogue and hover the blue words for definitions
Marcus
RileyI understand the product — but honestly, I am still not sure it solves our specific situation. We have tried workflow tools before and they never quite fit.
I hear that. Let me tell you about a customer who said almost exactly the same thing in our first meeting — because I think what happened next is more relevant to you than anything in our product deck.
Go ahead.
Her name was Sofia — VP of Sales at a B2B software company, 22 reps, fast-growth mandate. The problem was that every new enterprise client required the same three people to drop everything for two weeks. It looked like a capacity issue. It was actually a process issue — but no one had separated the two.
That sounds familiar. We have the same three people on every new account.
Exactly. And what made it worse was that the board had just approved three new enterprise reps — which meant the problem was about to get larger before anyone fixed it. The stakes were real: if the onboarding time did not come down, the new hires would be generating pipeline the team could not support.
That is our situation right now. We hired two new reps in January and the same three people are already stretched.
So Sofia was at the same point. The tension was building — Q2 pipeline was strong, but delivery capacity was not. The turning point was when her ops lead ran the first automated onboarding sequence and realised what she had been doing manually in two weeks, the system completed in four hours.
Was the transition difficult? That is always where these things break down for us.
The first two weeks were uncomfortable — I will not pretend otherwise. That is the honest part of the narrative. But the discomfort was in learning the system, not in the system itself. By week three, the ops lead had rebuilt one process on her own without our help.
And the outcome? What actually changed?
Three months later, average onboarding time dropped from fourteen days to three. What that meant for Sofia was that the two new reps she had hired were fully supported, Q3 became their strongest quarter in two years, and the ops lead — for the first time — had time to build the process documentation the team had needed for eighteen months.
The ops lead part is the one that gets me. Ours has been saying the same thing for a year.
That resonance — when you hear the same words your own team has been saying — is usually the signal. Not that the product is right. That the problem is real and resolved. The question is just whether the resolution is the right shape for your team.
Exercises
Complete all three exercises to see your final score
Pitch Corner
Read the pitch — click or drag words from the bank to fill the gaps.
Customer Story Email
Riley is following up after a meeting where Marcus expressed doubt about whether the product fits his situation. Instead of sending more product information, she sends a customer story — structured to map directly onto what Marcus described
Dear Marcus, Thank you for being direct in our meeting about your concerns — it helped me understand what you actually need to hear, which is not more product information. I want to share a customer story instead, because I think the— — —maps closely enough to your situation that it is worth two minutes of your time. I have kept it short.Sofia was VP of Sales at a B2B software company — 22 reps, fast-growth mandate, and a broken enterprise onboarding process. The— — —were real: the board had just approved three new sales hires, and the existing onboarding process could not support the current volume, let alone the incoming one. The team was already stretched. Adding headcount without fixing the process would make things significantly worse.The— — —was in week two of the pilot, when Sofia's ops lead ran the first automated onboarding sequence and realised that what she had been doing manually over fourteen days, the system completed in four hours. That was not a product discovery — it was the moment the internal conversation changed.Three months later, average onboarding time had dropped from fourteen days to three. The— — —was not dramatic — the team did not double in size or close a transformational deal. What changed was simpler and more significant: the ops lead had her Fridays back, the two new reps were fully supported from day one, and the VP of Sales stopped spending Monday mornings in firefighting meetings.I chose this story because the— — —— the person at the centre of it — is close enough to your situation that I think you will recognise the moments that matter. Same team size, same pressure, same concern about whether a new system would actually fit rather than add complexity.The reason I am sending this rather than a case study PDF is that I think the— — —— the feeling that this is describing something you already know — is more useful than a metrics slide. Does any of it sound familiar? If so, I think it is worth a thirty-minute call to talk about what the resolution would look like for your team specifically. Riley
Tip: Read the whole passage first to understand the context, then fill in the blanks.
Matching
Click a word, then click its correct definition.
Click a word on the left, then its definition on the right.
Words
Definitions
Fill in the Blank
Drag the correct words from the word bank to complete each sentence.
Sentence 1
Riley built a— — —rather than listing features: a specific company, a named problem, a moment of change, and a measurable result. By the end, Marcus had not been sold to — he had been shown what was possible.
Sentence 2
Riley held the— — —longer than felt comfortable. The team was losing two hours per rep per day, the quarter-end was approaching, and the VP of Sales was asking for answers. That pressure made the solution feel necessary, not optional.
Sentence 3
The— — —were specific: the company was about to lose its third enterprise client in a row. That detail made the problem impossible to ignore — because Marcus recognised the same pressure in his own business.
Sentence 4
The— — —was when the ops lead ran the first automated sequence and realised that what she had been doing manually in two weeks, the system completed in four hours. Riley described it as a human moment — not a software implementation.
Sentence 5
Riley's— — —was precise: twelve weeks later, average response time dropped from four hours to forty minutes. She gave Marcus something concrete to take to his CFO — not a projection, but a result.
Sentence 6
Riley chose her— — —carefully: a VP of Sales with 22 reps and a fast-growth mandate. Marcus had 22 reps. The similarity was not an accident — it was the detail that made the story feel relevant rather than generic.
Sentence 7
Riley did not say 'the team was overwhelmed.' She said 'by Thursday afternoon, the support queue had 340 open tickets and the team lead had stopped answering Slack messages.' That— — —detail made the scene visible — and visible made it believable.
Sentence 8
Halfway through the story, Marcus stopped taking notes. That moment of— — —— where the protagonist's situation became his situation — was worth more than any slide in the deck.
Tip: Think about the meaning of each word and what makes sense in the sentence.
Multiple Choice
Choose the best answer for each question about the dialogue.
1.Why does Riley begin with a customer story rather than responding directly to Marcus's concern about the product?
2.Riley says 'what made it worse was that the board had just approved three new enterprise reps.' What function does this detail serve in the story?
3.Why does Riley describe the turning point as 'the moment the ops lead realised what she had done manually in two weeks, the system completed in four hours' rather than saying 'they implemented our software'?
4.Marcus says 'the ops lead part is the one that gets me — ours has been saying the same thing for a year.' What has happened at this point in the story?
5.What does Riley mean when she says 'the question is just whether the resolution is the right shape for your team'?
6.According to the lesson, why is it a mistake to skip the tension in a sales story?
7.Riley says Sofia had '22 reps' and Marcus has '22 reps.' Why is this specific detail in the story?
8.What is the purpose of the phrase 'what that meant for them was' in a sales story?
Deal Clinic
Read the conversation — judge each highlighted move: Good or Weak?
Evaluate each highlighted move — is it effective or not?
✓ 0 of 4 evaluatedContext
Marcus has expressed scepticism: 'I understand what you are saying, but I've heard similar pitches before.' Watch how two salespeople respond.
Marcus
Look, I understand the value proposition — but honestly, every vendor we have spoken to says something similar. I'm not sure how this is different.
Salesperson A
I completely understand that concern. What makes us different is that our platform is specifically built for B2B sales teams — we have deep integrations with the tools you already use, our onboarding is managed end-to-end by our team, and our average customer sees a 40% improvement in process efficiency within 90 days. We also have a dedicated customer success team that is with you for the entire contract period.
Verdict
Salesperson A — Response to scepticism
Salesperson B
I hear that — and I am not going to try to argue my way out of it with a list of differentiators, because that is exactly what every other vendor has done. Let me tell you about a customer who said the same thing in our first meeting. Her name was Sofia. She had 22 reps, a broken onboarding process, and she had been through two workflow tools in eighteen months that had not delivered.
Verdict
Salesperson B — Response to scepticism
Salesperson B
What made Sofia's situation worse was that the board had just approved three new hires — which meant the broken process was about to handle significantly more volume before anyone had fixed it. The turning point was not the implementation. It was the moment her ops lead realised she had been spending fourteen days doing something the system did in four hours. That was the week the internal conversation changed.
Marcus
The ops lead detail — that's the part that sounds familiar. Our ops lead has been saying the same thing for about a year.
Salesperson A
That's really common — it's one of the things we hear most often. Our onboarding process is specifically designed to reduce that burden from day one, so your ops lead would be in a much better position very quickly. Can I show you what the onboarding timeline looks like?
Verdict
Salesperson A — Follow-up move
Salesperson B
Three months after the turning point, Sofia's average onboarding time was three days instead of fourteen. What that meant for her was that the three new hires were fully supported, and her ops lead — for the first time in two years — had time to do the process work the team actually needed. The reason I told you that story is that you have said three things today that Sofia said in our first meeting. Where does your situation feel closest to hers?
How to read it: The blue dot marks a move you need to evaluate. Prospect lines are context only.
Group Activities
Role-play scenarios and discussion questions for group classes
🎯 Choose the Best Response
Work in pairs. For each situation, choose the response that best uses sales storytelling technique. Discuss your reasoning before clicking.
Customer says
“A prospect says: 'Can you give me some examples of results other customers have seen?'”
Salesperson responds…
Customer says
“You are mid-story and the prospect says: 'Okay, I get the picture — what was the solution?'”
Salesperson responds…
Customer says
“A prospect has just heard your customer story and says: 'That's interesting. I can see the similarity.'”
Salesperson responds…
Customer says
“A CFO joins the meeting unexpectedly and asks: 'Can you summarise what you do and why we should care?'”
Salesperson responds…
🔗 Customer Profile Match
Match each sales story challenge to the technique that resolves it. Discuss before clicking.
Plans / Options
Ask the connecting question
End the story with 'where does your situation feel closest to theirs?' — this forces the prospect to do the mapping themselves and surfaces the specific detail they recognised. Without this question, the story is an anecdote. With it, it becomes a mirror.
Add the stakes
The problem feels abstract because the cost of not solving it is not visible. Add a specific consequence: what happened — or nearly happened — because the problem went unresolved. Stakes make tension real. Without them, the problem is just a situation.
Compress to the four-part structure
One sentence each: the problem ('they had X'), the stakes ('the risk was Y'), the turning point ('everything changed when Z'), the resolution ('three months later, A'). Four sentences, the full arc. Then the connecting question.
Customers — which plan fits each one?
Challenge 1
You have told a strong customer story, but the prospect seems interested in the story rather than connecting it to their own situation. They are listening but not saying 'that sounds like us.'
Challenge 2
You are telling a story and you notice the prospect seems unmoved by the problem section. The problem feels abstract — they are not leaning in.
Challenge 3
The prospect asks for the story to be shortened. You have two minutes to deliver the essential structure.
✏️ Finish the Salesperson's Line
The salesperson has started a story — finish the line using language from this lesson. Compare your completions before clicking for the suggested answer.
Customer
“A prospect says: 'I'm not sure this applies to our situation.'”
Salesperson
“Let me tell you about a customer who said exactly the same thing — …”
Customer
“You are building the tension in a story and want to add a second layer of urgency.”
Salesperson
“And what made it worse was …”
Customer
“You have just described the turning point in a story and want to move to the resolution.”
Salesperson
“Three months later, …”
Customer
“You have finished a customer story and the prospect says 'interesting.' You want to create the connecting moment.”
Salesperson
“The reason I told you that story is that you have said three things today that Sofia said in our first meeting. …”