.webp)
Why are some technical demos absolutely captivating, while others have you doomscrolling by the third slide? Why do some Sales Engineers command a room start to finish, while others quickly lose the audience one camera at a time?
I came to presales after six years in pure sales roles, most of them phone-based. No slides, no demo environment, no screen share. Just a voice, doing all the work. In that world, tonality wasn't a nice-to-have; it was drilled and coached the way SEs rehearse demo flow. So when I moved into presales, something stood out immediately. The craft here runs deep on what to say and what to show: discovery questions, demo flows, objection responses, value framing. And reasonably so: that's the part you can write down, review, and improve. How it sounds is harder to put into words, so it tends to go undiscussed. Not because it doesn't matter. Because we often don't have a shared language for it.
Many of my colleagues naturally and skillfully use the right tonalities without ever thinking about them. But instinct has a ceiling: it shows up on your good days and vanishes when you're tired, rushed, or thrown off by a hostile question. What's unconscious can't be practiced, and what can't be named can't be coached. That's the point of naming these tones: turning something a few people do naturally into something anyone can do deliberately. Because the same sentence, in a different tone, becomes a different sentence.
"What if I told you an AI agent built this CMS in under 30 minutes?" can sound like a genuine question, a smug “gotcha,” or the moment every listener leans forward in their seat — and the words never change.
Selling in person gives you a whole body to work with. The room, the whiteboard, the eye contact, the handshake. Over Zoom, most of that bandwidth disappears — and the moment you share your screen it gets worse: your face shrinks to a thumbnail and retreats into the grid. Every channel you'd normally persuade with collapses into exactly one: your voice. It's the last channel left, and it's the one that rarely makes it into a demo review.
Tonality can feel like a small thing to sweat in a complex technical sale. It isn't. Everything in a technical sale sits downstream of the demo: the deep-dive sessions, the technical evaluation, the POC, the case your champion makes internally when you're not in the room. Nobody grants a POC to a team whose demo they tuned out of. Nobody escalates a deal because the presentation was forgettable. If you can't hold a room's attention for thirty minutes, you never get the chance to prove the rest.
Below, I'll break down the six tones that do the heavy lifting in a technical demo, and when to use each one. Then I'll show a few sequences (of many) where they combine — including the one pattern that can turn an objection into the strongest sixty seconds of your call. These aren't the only tones a voice can make. They're the six I've found do serious heavy lifting in a demo, and the ones I can actually coach someone through. None of this is about performing. It's about making sure the certainty you actually have is the certainty they hear.
The Six Tones
There's an obvious problem with teaching tonality in writing: you can't hear me. So I'm going to lean on one device throughout, and it's worth explaining before we start.
Every tone carries an unspoken sentence. The words you say are only half of what lands. Underneath them, your voice delivers a second message the listener receives without noticing. Say "how's it going?" to a friend you haven't seen in years and the additional words they hear are "I'm actually glad to see you." Say the identical three words to a coworker in a hallway and they hear "I'm acknowledging you exist." Same words. Different sentence.
So for each tone below, I'll give you the unspoken sentence it delivers, a phrase you've already heard said that way, what your body is physically doing to produce it, and what it sounds like when it goes wrong. The failure modes matter as much as the targets. They're the fastest way to hear the boundaries of a tone you can't listen to.
Six tones, in roughly the order you'll use them on a call.
1. Genuine Curiosity
The additional words they hear: "I want your answer more than I want to keep talking."
A phrase you've heard said this way: "Wait — what happened?" when a friend starts telling you actual gossip. Nobody has to be taught that one.
What your body does: You lean toward the camera. Tempo picks up slightly, the ends of your phrases lift instead of falling, and you take a quicker breath before speaking. Energy up, but only a notch. Eyebrows scrunched, head slightly tilted: the face you make when someone says "wait, it gets worse." You can't fake the face without the voice following.
When it goes wrong: Two directions. Too bright and it becomes customer-service cheer — "and how ARE we today!" — which technical buyers hear as a script. Too flat and the question turns into a form field; you sound like you're collecting intake answers, and people answer form fields in six words or less. The tell either way is short replies.
Where it lives in a demo: Every question you ask after the demo has started. "Help me understand your setup — when your team launches a new site today, who's touching the code?" Also the recovery when a room goes quiet: "Let me stop — setting implementation aside, does this approach fit how you'd actually want to work?"
2. Candor
The additional words they hear: "I have nothing to gain by telling you this."
A phrase you've heard said this way: A good mechanic telling you the repair isn't worth it on a car that old. He's talking himself out of the job, and you can hear that he is.
What your body does: You sit back instead of leaning in. The voice drops slightly in pitch, slows, and the push goes out of it. Nothing is stressed. It's the least effortful you'll sound all call.
When it goes wrong: Delivered with any energy behind it, an admission sounds like a rushed disclaimer, you skating past the bad part. Delivered too low and slow, it turns funereal, like you're breaking terrible news. Candor isn't grave; it's just unhurried and unsold.
Where it lives in a demo: Every tradeoff, every limitation, every validation of a concern. "You're right — there's no native sync yet. It's an API integration, and it takes a little work." This is the tone that turns a weakness into a trust-builder. It's also the one most of us skip, because admitting something in your presenting voice feels safer. It isn't.
3. Conviction
The additional words they hear: "I would stake my reputation on this."
A phrase you've heard said this way: A pilot coming over the intercom mid-turbulence: "Folks, we've got some weather ahead — nothing unusual for this route." You've never seen the pilot's face, and you've never doubted the pilot's calm. That's Conviction surviving on voice alone.
What your body does: The sound comes from your chest rather than your throat. You slow down instead of getting louder. This is the part most people get backward. Every word gets fully pronounced: no swallowed endings, no words running together, nothing mumbled through on the way to the next thought. You go still, and there's often a half-beat pause before the sentence starts.
When it goes wrong: You get louder instead of heavier, and land in infomercial territory. But the more common failure is overuse. Deliver everything in Conviction and it flattens into a monotone of intensity, one the room stops hearing. Worst of all, Conviction on an ask reads as pressure — the same tone that makes your rationale credible makes your request pushy.
Where it lives in a demo: The design-rationale moments. "We built it that way on purpose. It's more setup on day one, and it's why you won't be rebuilding this in eighteen months." Use it on the two or three claims you'd defend in front of your own CTO, and nowhere else.
4. The Given
The additional words they hear: "Obviously that's true — and that's not even the best part."
A phrase you've heard said this way: Someone walking you through a house: "The kitchen’s incredible (obviously) — but wait till you see the backyard." Nobody stops to prove the kitchen is nice. They're already moving.
What your body does: Say the word "obviously" out loud right now. Notice what happened: your head dipped and slightly shook left to right. Maybe your eyebrows lifted. Your eyes widened slightly, and your pitch rose and fell across the whole word instead of punching any part of it. That's the shape. The parenthetical isn't spoken; it's what the tone supplies for you. Now put that same shape on the benefit: "you’ll save money with this (obviously)," delivered with the dip, the left to right shake, the widened eyes. Then no pause, straight into the second benefit — but more importantly… You're giving two benefits and taking the first one for granted. The forward motion is what sells it: you're clearly not stopping to argue, because in your mind there's nothing to argue.
When it goes wrong: Pause after the first benefit and you've asked the room to react, which is an invitation to disagree. Add a because and you've turned a fact into a claim you're now defending. Leave out the second benefit and the first one has nowhere to hide — it stands there alone, waiting to be evaluated. The worst version is using it on something the room genuinely doubts. A contested benefit, delivered as obvious, sounds either arrogant or oblivious.
Where it lives in a demo: Benefits you don't want to argue about, delivered on the way to ones you do. "You'll save dev hours every week (obviously) — but more importantly, marketing stops filing a ticket every time they want to change a headline."
5. The Insider
The additional words they hear: "This is between us."
A phrase you've heard said this way: "Okay — don't repeat this, but..." at a dinner table. Everyone recognizes it instantly, including over a phone.
What your body does: Volume drops to just above a whisper, tempo slows, and you lean in toward the mic. A short pause before you start does most of the work.
When it goes wrong: If everything is a secret, nothing is. Overuse turns theatrical fast. It also curdles when the information isn't genuinely secret. Whisper a fact that's on your pricing page and you sound like you're manufacturing intrigue. And a practical Zoom hazard: drop too far and noise suppression will cut you out entirely. Just above a whisper means just above.
Where it lives in a demo: The setup before something the room hasn't seen coming. "Now — here's the part (micro-pause) that teams don't find out about (micro-pause) until month three..." It's the replacement for enthusiasm, which is what most of us reach for at that moment, and which reads — from a technical person — as marketing.
6. The Easy Ask
The additional words they hear: "No big deal either way."
A phrase you've heard said this way: "Want me to grab you a coffee?" Nobody has ever said that sentence with weight on it.
What your body does: Your voice rises at the end of the sentence and stays warm. Keep it short. Then stop talking.
When it goes wrong: Three ways. Too much push — "WANT ME TO SHOW YOU?" — and it's a demand. Too much lift and it turns pleading, like you need the yes. And if every sentence in your demo already ends on a rise, this one has nowhere to go: you've spent the tool. The rise only works when it isn't your default.
Where it lives in a demo: All the micro-asks that pace a call. "Want me to show you that?" "Should I go deeper on auth?" "Worth a look, or should I keep moving?"
Three Sequences That Do Real Work
Individual tones are useful. Sequences are where this gets powerful. The shift between two tones carries meaning that neither one carries alone. Here are the three worth learning first.
1. The Objection Arc
Genuine Curiosity → Candor → Conviction → The Easy Ask
This is what handling a technical objection sounds like when it's done well. A developer interrupts your demo: "Hold on — you're telling me we don't have full control of the codebase?"
[Genuine Curiosity] "Fair question — when your team launches a new site today, who's touching the code, and what are they changing?"
[Candor] "Got it. So full control is how you've always guaranteed quality. And you're right: on this product, you don't get direct codebase access."
[Conviction] "But actually, that's deliberate. The platform manages the core, the modules, the security patches — and that's exactly what makes site number twenty launch as fast as site number one."
[The Easy Ask] "Want me to show you what that looks like in practice?"
Four tones, four jobs: open them up, level with them, stand behind the design, make the next step frictionless. Watch where Conviction sits: on the rationale, never on the ask. End an objection response in Conviction and you'll accidentally sound like you're pressuring someone. Ending on the rise is how you sound like it's no big deal, which it should be.
2. The Reveal
The Insider → Conviction → The Given
For the moment you show the thing the room hasn't seen coming. Different demo this time — a developer platform — because this moment exists in every product.
[The Insider] "Now — here's the part (micro-pause) that teams don't find out about (micro-pause) until month three..."
[Conviction] "Every pull request spins up a full preview environment on its own. Your reviewers click a link and test the change live — before it ever merges."
[The Given] "You'll catch issues before they ship (obviously) — but more importantly, code review stops being guesswork and starts being a test drive."
The whisper earns attention. Conviction lands the fact. The Given slides the obvious benefit past without stopping to argue for it, while pointing at a bigger one. That last move is the confidence transfer: nobody debates whether it catches issues, because you never presented it as debatable.
3. The Executive Drive-By
Conviction → The Given → The Easy Ask
A third demo for this one — an analytics platform — because this moment finds every SE eventually. Forty minutes into the technical deep dive, a VP joins the call: "Apologies — I've got ten minutes between meetings. What am I looking at?"
This is the only moment in a demo where you should open at Conviction. No warm-up, no probing question. They asked for certainty on a clock — and making a ten-minute executive answer discovery questions is how you spend your window impressing nobody.
[Conviction] "We've been walking through how your team would consolidate reporting across all five brands. The short version is that the monthly board report takes your analysts two weeks today. On this, it's live — the numbers here update themselves."
[The Given] "You'll save your analysts two weeks a month (obviously) — but more importantly, you'll see a bad month in week one instead of week six."
[The Easy Ask] "Want the two-minute version of what they just saw?"
Three tones, three jobs. Conviction answers the question they actually asked — is this real? — with the stillness of someone who isn't auditioning. The Given hands over the business outcome as settled fact, already moving toward the sharper point — the one a VP repeats to their own boss. And The Easy Ask gives them back control of their ten minutes, which executives notice more than anything you demo.
The wrong version of this moment is the common one: the SE gets flustered, restarts the pitch at full enthusiasm, and burns eight minutes proving they know the product. In contrast, the tones above take forty seconds, and they leave the impression that matters: this person can compress.
Building Your Own
Three sequences won't cover every moment in a demo. But a few rules hold across all of them, and they're enough to assemble your own:
Lead with Genuine Curiosity when you don't know what the real concern is — and skip it when you do. Probing a straightforward question makes you sound evasive about an answer you should just give.
Candor before Conviction, never after. The admission is what earns you the right to explain.
The Insider before Conviction. The whisper buys attention, and the fact needs attention to land on.
Conviction before The Given. The weight of the first is what lets you be casual in the second.
End on The Easy Ask whenever you want the conversation to keep moving — and never end on Conviction when you're asking for something.
Where To Start
Don't try to run six tones in your next demo. You'll think about your voice instead of your prospect, which is worse than doing nothing.
Pick one pair and use it once. The easiest place to start is Conviction → The Given. You've already seen it twice above, and it works on any feature you genuinely believe in — nothing uncomfortable to practice on.
Take the one design decision you'd defend in front of your own CTO. Say it in Conviction: slower rather than louder, from the chest, still. Then, without pausing to check the room, hand over the benefit as already settled, with the obviously shape on it, and keep moving into the bigger one.
[Conviction] "We manage the codebase. The core, the modules, the security patches — that's a deliberate design choice."
[The Given] "You’ll never worry about updates and patches (obviously) — but more importantly, it'll cut your launch time from months to days."
Two moves, about eight seconds. The weight of the first is what earns the casualness of the second: you just showed them you're not guessing, so they have no reason to audit the payoff. That's the whole article in one pair, and it's the one I'd practice before anything else.
Then record yourself. Not a role play — a real demo. Play it back with the video off and the screen share gone, so you hear what your prospect actually receives once your face has shrunk to a thumbnail. Listen for one thing: how many different tones you used. If the answer is one, you now know exactly what to work on, and you have five more to try.
Because the goal was never to sound like a salesperson. It's the opposite. You already have the technical certainty — you built the demo, you know the product, you know the tradeoffs cold. The only question is whether any of that certainty survives the trip through the microphone.
About the Guest
Dimitriy Kaplan is a Solutions Engineer in the enterprise DXP space, where he leads discovery, demos, and PoCs for AI-driven CMS solutions. With nearly a decade of experience across presales, engineering, and sales, Dimitriy brings a unique perspective shaped by three years as a client-facing software engineer, three years as a top-producing Account Executive, and three years building and leading sales teams from the ground up.
For Dimitriy, presales is the one seat that brings together his experience as a builder, seller, and coach. He’s passionate about demo craft, sales craft, and the evolving role of agentic AI in presales.
