If you're a founder, engineer or solutions engineer, the sales demo is where your instinct to show everything quietly kills deals. These sales tips turn a product tour into a demo that moves a buyer forward: shorter, built on discovery questions, and closed with a clear next step.
The pattern is familiar. You built the thing, you know every screen, and the buyer said "can you show me how it works?" So you share your screen and walk through it, feature by feature, for 40 minutes. The buyer nods, says "this looks great, let me take it to the team", and then nothing happens.
The product was fine. The demo answered questions the buyer never asked.
Sales tip 1: no discovery, no demo
A demo without discovery is a guess. Before you share your screen, you need answers to three discovery questions:
- "What made you take this call now?" You're looking for the trigger: a new hire, a missed target, a painful process that broke last week.
- "How do you handle this today, and what's annoying about it?" This gives you the current workflow, in their words.
- "If this worked, what would be different in three months?" This gives you the outcome you'll demo toward.
If the buyer wants to jump straight to the screen, say so honestly:
"Happy to show you. So I don't waste 30 minutes on screens you don't care about, can I ask two quick questions first?"
Almost nobody says no to that. And if the first call has to be a demo, keep it to ten minutes and spend the rest on discovery.
Sales tip 2: demo the "after", not the menu
Engineers organise demos the way the product is organised: settings, then dashboard, then reports. Buyers think in their own day.
Build the demo as a story with three beats:
- Their pain, in their words. "You said onboarding a new rep takes about two months of shadowing calls."
- The one workflow that fixes it. Show only the path that solves that pain, start to finish.
- The result. End on the screen that shows the "after": the report, the finished output, the thing they would send their boss.
Everything else stays hidden unless they ask. A feature the buyer didn't ask about is a new question you just created, and new questions slow deals down.
Sales tip 3: the 3-to-1 rule
For every three minutes you click, give the buyer one minute to talk. Build check-ins into the script:
- "Is this close to how your team would actually do it?"
- "What would break if you rolled this out tomorrow?"
- "Who else would need to see this before it goes anywhere?"
That last one is the most important discovery question of the whole demo. If the answer is "my CFO and our security lead", you just learned your real buying process, and you have a reason for the next meeting.
Sales tip 4: handle objections live, don't defend features
Objections in a demo usually sound technical: "Does it integrate with X?" "What about edge case Y?" Engineers love these questions because they have answers. The trap is answering the literal question and missing the real one.
Use a simple objection handling loop:
- Acknowledge. "Good question, a lot of teams ask that."
- Ask why. "What happens on your side if it doesn't?"
- Answer the real concern. Often "does it integrate with X" really means "I don't want another tool my team ignores."
Example:
Buyer: "Does it export to our CRM?"
You: "Not today, honestly. What would you want in the CRM, the scores or the call notes?"
Buyer: "Mostly so managers see who practised."
You: "Got it. Managers get that in a weekly summary. Would that cover it, or does it have to live in the CRM?"
You didn't oversell, you didn't lose the thread, and you learned what actually matters.
Sales tip 5: close the demo, not the deal
Founders often end a demo with "So, any questions?" and then wait. That hands control back to the buyer, and the deal drifts.
You don't need a hard close. You need a clear next step, booked before you hang up:
"Based on what you said, the next step would be a 30-minute session with you and your sales manager, where we run this on one of your real scenarios. Does Tuesday or Thursday work better?"
Concrete, small, dated. If they can't commit to a next step, that's information too: ask what's in the way.
A sales demo checklist you can copy
Before the call:
- [ ] I know why they took the call now (trigger)
- [ ] I know their current workflow and its pain
- [ ] I picked one workflow to show, max two
- [ ] I prepared demo data that looks like their world, not "Test Company 1"
During the call:
- [ ] Recap their pain in their words before sharing my screen
- [ ] Check in at least every three minutes
- [ ] Ask "who else needs to see this?"
- [ ] Answer objections by asking why first
At the end:
- [ ] Propose one specific next step with a date
- [ ] Send a three-line recap the same day: their pain, what they saw, the next step
Why demos feel hard for technical people
The hard part of a demo isn't the product knowledge. It's staying calm when the buyer interrupts, asks the question you didn't prepare for, or says "we tried something like this and it didn't work." That's a sales skill, and like cold calling or discovery, it gets better with sales practice, not with reading about it.
The fastest way to improve is to rehearse the uncomfortable parts out loud: the skeptical buyer, the "can you just show me pricing" interruption, the silence after your close. Run it with a colleague, record yourself, or use sales role play with virtual customers who push back like real ones.
That's what we're building at Kulissa: a sales coach where you practise these conversations before the real call. If demos are the part of selling you dread, take a look at kulissa.com.
Top comments (1)
The 3-to-1 rule stood out for me, three minutes of clicking to one minute of listening. Asking who else needs to see this before it goes anywhere is a smart way to find the real decision maker early.