1. Sharp POV
6. Demo
How to win
Chris Orlob
CEO, Caliber
The demo: catalyzing a decision
By the time a buyer sits down for a demo, they have spent hours in discovery explaining what is broken and why it matters. They have probably seen demos from other vendors, and are trying to find out whether you truly understand their real problems.
In this chapter, we argue that a demo has one job: to move the buyer to their next decision by showing how your product solves the problem they described. Most of what feels natural to a seller in a demo works against that.
This chapter is built on Chris Orlob's demo philosophy. Chris is the founder and CEO of Caliber. At Gong, he ran product marketing and the company's #1 producing sales team, and he helped grow Gong from $200K to over $200M in ARR. He created Gong Labs, where he led an analysis of 67,149 recorded sales demos matched to their outcomes. His Win the Demo course has trained roughly 10,000 sellers.
How to win
The demo is where the buyer learns whether you listened. In Chris's view, a core purpose of discovery is to collect what the seller needs to deliver a short, tailored demo. A demo either uses what discovery uncovered or ignores it. That's why he thinks of it as "the turning point of your deal."
Chris estimates that about 95% of salespeople run a feature-and-function walkthrough of the entire product instead of a demo built around the buyer's problem. The outcome is that the buyer leaves knowing how the software works but is then left to work out which of those features apply to their problem. In a demo, it's the seller's job to connect those dots for them.
The seller's job is to catalyze a decision
Chris defines the purpose of a demo as catalyzing the buyer's decision: should they proceed to the next step in the sales cycle. This can be accomplished when the seller uses the demo to solve the customer's problem in front of them, in order of importance, without showing anything beyond what the discovery uncovered.
Three things the buyer needs from the demo
First and foremost, the buyer needs to leave the demo feeling understood. They need evidence that you understand their problem in detail, ideally better than they could describe it themselves. Without that evidence, nothing you show will seem relevant to them.
Second, the buyer needs to see the product in terms of their own problem. A great demo is a link between the buyer's problem and the outcome they want, explained in the buyer's language.
"Here's your problem, here's your desired outcome. The demo is now a bridge between those two, and I'm going to show you how. And I'm going to do it through your language and your point of view."
Third, the buyer needs to believe the problem can be solved. Chris says the most common reason people buy anything in business is pain relief. A good demo ends with the buyer believing a specific, painful problem will go away.
Prev
Next
Tactics
Prev
Next
Tactics
A demo has five parts: the preparation before you share your screen, the choice of what to show, the presentation of each capability, the conversation during the call, and the close. In this chapter, we break down each part.
1. Prepare before you share your screen
Most of a demo's outcome is decided before the product appears. Three things have to happen first.
Find the real problem in discovery
You cannot build a demo around a problem you never uncovered, which is why Chris treats discovery as a core part of the demo. Buyers usually open with a request, and the request is often a solution they have already picked. Keep asking what sits underneath it. Chris's example from a Gong discovery call went five levels deep.
Level | What the buyer said | What it means for the deal |
|---|---|---|
1 | "We need more visibility into our sales calls." | This describes a solution. A deal that stops here is "dying to go dark." |
2 | "We're not very good at selling to power." | A real problem with limited business impact. |
3 | "Our sales cycles are nine months and they should be six." | A likely deal, probably mid-size. |
4 | "With 60 days to collect payment, that's an 11-month gap from cycle start to cash in the bank." | The CRO joins, and the problem is now cash flow. |
5 | "If we don't fix it, we'll have to raise a bridge round or a down round." | "Price doesn't matter, at least as long as you differentiate." |
Each level raises what the buyer is willing to pay. When a buyer answers a pain question with a feature, recognize it and ask what is behind it:
As we discussed in the Discovery section with April Dunford, discovery is where you establish differentiation. Get the buyer to agree that part of their problem is one you solve better than anyone else, then address that part in the demo.
If a buyer wants to skip discovery and see the product, agree on one condition: the call becomes an exchange where you show a few things and ask questions as you go. With inbound buyers who already explained their needs to someone else, let them finish, then ask: "Can I go back in time with you for just a second? What was the original challenge that led you to prioritize a solution like this?"
Set the upfront contract
In the first minute of the demo, agree on how the call will end.
“By the end of this call, I’d like you to be in a position where either one, you see the value in this and we plan a concrete next step, or two, you don’t see the value, you’re upfront with me about that, and we go our separate ways. Is that fair?”
It takes fifteen seconds, and it gives you permission to ask for a next step at the end of the call.
Open with a What We've Heard slide
Chris says this change is the highest impact for effort. Before showing any product, spend about five minutes on one slide that lists the buyer's business problem, its root causes, and its consequences. Present it as a draft, and ask the buyer what you got wrong.
Here is an example for an illustrative buyer, a 400-rep sales organization evaluating a coaching platform.
Challenge | Root cause | Consequence |
|---|---|---|
New reps take nine months to hit quota | Onboarding means shadowing whoever has time that week | Two quarters of lost capacity per hire |
Win rates dropped five points against a new competitor | Reps have no shared playbook for competitive objections | The forecast misses on the largest deals |
Frontline managers cannot coach every rep | Each manager hears a small fraction of their team's calls | Coaching goes to reps who ask for it, and the reps who need it most get little |
The slide also keeps the seller on track. Once the buyer's problems are on screen, every feature you show has to connect back to them.
After the slide, spend less than two minutes on context: the market change or industry problem that makes the demo relevant. In Gong's analysis, industry problems were the most common topic in the first ten minutes of winning demos. Without this context, you give "the impression that you have a solution in search of a problem."
With the buyer's problems confirmed, you can decide what to show.
2. Choose what to show, and in what order
Show only what solves a stated problem
A feature earns its place in the demo only if it solves a problem the buyer explicitly described. If two of your ten features solve it, show two. Gong called this rule "Solve Exactly."
Every minute spent on a feature the buyer does not need lowers the value they assign to the features they do need.
Lead with the most valuable capability
Start with the topic the buyer spent the most time on in discovery, then the second most, and continue in that order. If a buyer spent seven minutes on coaching, five on pipeline management, and four on onboarding, start with coaching. Gong called this the upside-down demo, and Chris credits the principle to Peter Cohan's Great Demo!
The order matters for three reasons.
Buyers remember what they see first.
The first capability may be all they need to see.
Senior people leave early.
"If you've got 45 minutes and you've bored them for the first 30 minutes and they're busy, you've missed your opportunity. So if you've got high-value people in the room, solve their problem immediately."
Once you know what to show and in what order, the next question is how to present each capability.
3. Present each capability with FAVORITE
Most sellers present a feature by describing what it does. Chris's structure, FAVORITE, states the value before and after each capability, which he calls a "value sandwich." Run it once per capability, three to five times in a typical call.
Frame the pain
Ask a question
Visualize the outcome
Orient them to the screen
Reveal the workflow
Implant the value
Tell a story
Elicit a response
Frame the pain
Before every capability, restate the pain it solves in the buyer's words. Spend no more than ten seconds on it. If the buyer is wondering what problem a feature solves, this step was skipped.
When the buyer described a goal, such as higher win rates, name the obstacles that block that goal. Then show how the product removes each one.
"What we do is help increase your win rates. Now, what stops most companies from increasing their win rates? Well, you've got X, you've got Y, you've got Z. These are obstacles, like bowling pins you're setting up so your product can knock them right down."
Ask a question
Ask a question that adds detail to the pain, such as "How are you handling that issue today?"
Visualize the outcome
Describe the result before you click anything, so the buyer knows what to watch for.
Orient them to the screen
Spend twenty to thirty seconds explaining what is on the screen. Sellers skip this step most often, because they use the product every day and forget the buyer is seeing it for the first time.
Reveal the workflow
Show the capability working.
Implant the value
Restate the outcome after the workflow, so the buyer hears the value before and after seeing the capability.
Tell a story
Describe a customer who had the same problem. Choose one similar to the buyer in size, sector, and scope, and spend more of the story on the problem than on the result. In Gong's data, sellers who used social proof techniques had a 22% lower close rate, which Chris attributes to famous logos: buyers conclude the product was built for companies unlike theirs.
Elicit a response
End with a question that asks the buyer to compare what they saw with how they work today.
Here is FAVORITE assembled for one capability, using the illustrative coaching-platform buyer from the What We've Heard example:
Frame: "Earlier, you said new reps take nine months to hit quota because onboarding is mostly shadowing whoever has time that week."
Ask: "How many reps are you planning to hire this year?"
Visualize: "Imagine new reps studying your best reps' discovery calls in their first week. That's what I'm about to show you."
Orient: "This is the call library. On the left are your top reps' calls, filtered by deal stage. On the right is the playlist a manager assigns to a new hire. Are you with me?"
Reveal: The seller builds a playlist of three discovery calls and assigns it to a new rep.
Implant: "As a result, every new rep hears how your best people run discovery before their first live call."
Tell: "A 350-rep team in your market set this up last year and cut ramp time from eight months to five."
Elicit: "How does that compare to how your managers onboard reps today?"
A well-built capability still fails if you deliver it as a monologue, which is the subject of the next tactic.
4 Keep the buyer talking
A demo should begin as a presentation and become a conversation. In Gong's analysis, winning and losing demos had nearly the same talk-to-listen ratio. The difference was in how the talking was distributed.
Losing demos | Winning demos | |
|---|---|---|
Talk-to-listen ratio | 66:34 | 65:35 |
Longest uninterrupted pitch | Up to 106 seconds | Never above 76 seconds |
Speaker switches per minute | Fewer | 21% more, rising 36% in the second half |
Average call length | 36 minutes | 47 minutes |
Chris cautions against lengthening demos on purpose. Winning calls ran longer because a focused demo prompted more questions from the buyer.
Ask questions that require an answer
"Does that make sense?" and "What questions do you have?" are easy to answer with a nod. Replace them with questions that ask the buyer to compare what they saw to their own situation:
"How does that compare to how you solve this now?"
"To what extent do you envision this solving [the pain]?"
"Feels like that resonated. How come?"
"Feels like that didn't resonate. Where'd it miss the mark?"
Stop when the buyer reacts
When a buyer reacts strongly to a capability, stop and ask what is happening in their business that made it stand out. Moving on to the next feature at that point is, in Chris's words, "the stupidest thing you can do." If the buyer starts talking at length, stop sharing your screen and continue the conversation.
Show less product
In a recent 45-minute demo with a chief sales officer and a CEO, Chris showed about nine minutes of product. The rest of the call was the What We've Heard slide, context, and discussion of the one capability that mattered most.
5 Close with a recommendation
The last ten minutes decide whether the demo produces a decision. Close in three moves:
Summarize the key points, which brings the buyers' attention back to the call.
Ask each person, "Talk to me about what excited you the most about what we've covered today?" What excited each person usually connects to a personal pain.
Recommend the next step yourself, after giving the buyer a chance to share their view.
Chris introduces his recommendation with this script:
"I have a pretty strong point of view on what we should do next. Before I offer my point of view, you know your organization better than I do. Do you have any strong opinions?"
Most buyers ask for his view. Be ready to say what the next step is, why it is the right step, and who needs to be involved on both sides.
Much of this advice seems intuitive but it's easy for reps to fall into common failure modes. In the next section, we outline the most common mistakes that kill deals in the demo stage.
How to win
Prev
Next
Common mistakes
Prev
Next
Common mistakes
Chris's view is that what feels right in a demo usually causes failure. The mistakes below are common practices that feel like the right call, but often set sellers up for failure.
1 Showing every feature
Chris calls this "the full harbor tour." The seller shows the whole product on the assumption that the more the buyer sees, the more valuable the product will seem. Features that solve the buyer's problem appear alongside features built for other customers.
The result is lower perceived value. Each irrelevant feature reduces the weight of the relevant ones, and each extra minute of screen time adds a chance to raise a new objection.
"So many sales reps do a full harbor tour, thinking that if they show everything, it builds higher perceived value, and all it does is deteriorate and destroy value."
The correction is in tactic 2. If a feature does not solve something the buyer described, leave it out.
2 Saving the strongest capability for last
In the "ramp up" demo, the seller starts with the basics, adds capabilities one at a time, and ends with the most impressive one. This structure assumes the buyer stays attentive and present through thirty minutes of buildup. Busy buyers lose attention, and executives often leave early. Chris says the structure works only for a skilled storyteller.
"The only time you can pull that off, where you save the best for last, is if you are a world-class screenwriter. And most account executives do not have the skills to be able to do that, where they're creating open loops and coming back and closing them."
The correction is also in tactic 2. Show the most valuable capability first, and let the buyer decide how much detail to see.
3 Ending without a next step
The call runs long, and the seller tries to schedule a next step in the last three minutes while the buyer is trying to leave. In another version, the seller asks the buyer, "What do you think we should do?"
In both cases, the seller hands the decision to the person with the least experience making it. The buyer has likely never bought a product like this, and the seller has sold it dozens or hundreds of times. A strong demo with no agreed next step gives the buyer no way to act on their interest.
"Reps who consistently struggle with converting deals to the next stage simply run out of time at the end of the call."
The correction combines tactics 1 and 5. Set the upfront contract, reserve the last ten minutes, and arrive with a recommendation.
Tactics
Prev
Next
How to avoid AI slop
Prev
Next
How to avoid AI slop
AI can turn a discovery transcript into a talk track, a list of challenges, and a feature sequence in seconds. The output reads as tailored, and that is the risk. A seller can deliver a confident demo built on generic language that does not describe the actual buyer.
The difficult parts of Chris's method require judgment about one buyer: which problems matter most, which features to leave out, and which customer story fits. AI produces convincing imitations of that judgment, so sellers need to know where to use it and where to check it.
Make the What We've Heard slide specific
Chris recommends using AI to draft the What We've Heard slide from call notes, which takes minutes. The risk is that the model describes the problem in language that could apply to any company in the category.
Before the slide goes in front of a buyer, the seller should ask whether the problem statement could apply to any other company. If it could, the seller adds details only this buyer has shared, such as their numbers, their terms, and the people involved.
Set limits when the buyer controls the product
AI products tend to be easier to use, which lowers the risk of letting the buyer operate the product during the demo. Chris thinks sellers should do this more often, particularly with workflow products, where buyers benefit from finding the value themselves. He also says the right choice depends on the product, and he would not do it for Caliber.
Without limits, a buyer-led demo turns into a random sample of features. The seller still states the pain first, explains what the buyer is about to explore, and restates the outcome when they finish.
Choose the features yourself
A model asked which features to show will draw on everything it knows about your product, which favors breadth. Solve Exactly requires a different input: what this buyer said in discovery, weighted by how long they spent on each topic. A model can rank the topics from a transcript. The seller decides which features to leave out, including the ones the product team wants shown.
Use real proof
The customer story in each capability has to come from a real customer similar to the buyer. A composite story written by a model gives the buyer a claim nobody can verify. The same applies to ROI. A model-generated ROI calculation is a set of assumptions an executive will challenge, and Gong's data shows that pitching ROI lowers close rates.
Where AI helps
AI is useful for these parts of demo preparation:
Drafting the What We've Heard slide from call notes and transcripts, before the seller adds specifics.
Ranking discovery topics by time spent, to set the order of the demo.
Finding customer stories that match the buyer's size, sector, and problem.
Practicing the demo. Chris's central argument is that demoing is a skill most sellers were never trained in, and AI role play gives them repetitions before they face a real buyer.
The standard stays the same when the draft arrives faster. If another vendor with the same tools could have produced the same demo, the demo will not move this buyer to a decision.
Common mistakes
Prev
Next
7. Mutual Action Plan
Prev
Next
Chris Orlob
CEO, Caliber
1
1
Chapter overview:
6. Demo
How to win
Tactics
Common mistakes
How to avoid AI slop
1. Sharp POV
2. Outbound & cold call
3. Discovery
4. Champion Enablement
5. Business Case
6. Demo
7. Mutual Action Plan
9. Pilot
10. Procurement, Security, and Legal
5. Business Case
Chapter overview:
6. Demo
How to win
Tactics
Common mistakes
How to avoid AI slop