You are very surprised, however, when they continue to pour! The wine overflows onto the table and then splashes onto the floor. The entire bottle has been emptied, but the only portion you can consume is contained in the glass.

What would you say if the waiter charged you for the full bottle?

– Henry Ford

I was the prospect listening to a vendor present their offering. The salesperson was working his way through their product presentation and entered a section on “Competitive Differentiation.”

One slide listed several competitors, and the salesperson began to discuss how his product was superior to the others. I perked up and made a quick note.

Seeing this, the salesperson asked me what I thought about the various competitors.

I responded, “Well, I didn’t know that [Vendor C] had an offering in this space. Many thanks for letting me know – I’ll check them out!”

And [Vendor C] did have an excellent product that, for our needs, was the best fit – which we purchased and enjoyed for years!

Moral? Beware of Premature Elaboration!

Resources:

Stunningly Awful vs Truly Terrific Competitive Differentiation – What, When, and How?

https://greatdemo.com/truly-terrific-competitive-differentiation/

And for more Sales Prevention Team stories, see:

“Stunningly Awful Sales Prevention Demos: Real-Life Examples of What Not to Do!”

https://greatdemo.com/stunningly-awful-sales-prevention-demos-real-life-examples-of-what-not-to-do/

– The sound of crickets in an empty room

Because he’d heard prospects ask certain questions repeatedly, he chose to incorporate the answers into his demo “script.”

The result was not what he expected! The more questions that he addressed in advance, the less successful his demos were.

Before making this change, his audiences were engaged as they asked their questions. But now prospects were quiet and seemed uninterested. By pre-answering questions, he had turned his demos into monologues, removing the possibility for a two-way, bidirectional conversation.

Moral: Encourage a real conversation by letting your prospect ask their questions!

Resources:

The Elegant Art of Managing Questions and Time

And see the stories in “Suspending Disbelief” for more engaging lessons learned!

https://tinyurl.com/yc7rsrmy

– SaaS Founder in year two

“When you first released your MVP [Minimum Viable Product], how much time did you schedule for your demos to prospects?” I asked this of a founder who told me her demos weren’t getting the job done.

“An hour,” she replied, “and we generally used all of that time.”

“And how long are your demo meetings now?” I enquired.

“Still an hour…” she noted, “and I’m rushing through the software, but I can’t show everything I want to show!”

I pursued this with, “How often do your development folks release new features?”

“Every few weeks,” she responded.

“And do you incorporate these new capabilities in your demos?”

“Oh yes! I try to show everything!” she confirmed.

“I believe we’ve found the problem,” I told her. “It’s like you’re trying to pack two weeks of clothes for a trip into a bag that only holds one week’s worth.”

I continued, “You’re going to have to prioritize what you show based on your prospects’ needs and wants. Show the most important capabilities first and confirm that they solve the problems. Then show the next sets of relevant features in accord with your prospects’ interests and the meeting time constraints.”

“Just like that too-small travel bag,” I explained, “you’re going to have to leave some things out of your demo!”

Resources:

Why Structure Demos Like a News Article?

https://greatdemo.com/why-structure-demos-like-a-news-article/

Great Demo! Chapters 5-9

https://www.amazon.com/dp/B0C9SNKC2Y/

And see the stories in “Suspending Disbelief” for more engaging lessons learned!

https://tinyurl.com/yc7rsrmy

– Ayn Rand

The prospect had invested in several hours of discovery with the vendor, but the vendor’s demo didn’t reflect any of what had been learned…

I was preparing to coach this vendor’s sales and presales teams and had been reviewing a number of discovery conversations and associated demos. In this particular case, I felt the discovery calls (there were two) were quite good. They had uncovered and confirmed several important use cases.

Unfortunately, it appeared that either this information wasn’t communicated to the demo presenter, or the presenter chose to ignore discovery and present their standard demo.

Fascinatingly, about forty minutes into the demo meeting the prospect lead player said, “So, we spent hours with your team outlining our needs and situation. You appear to be ignoring everything we said!”

He paused, looked annoyed, and observed, “You’re showing use cases that are irrelevant and referencing scenarios that we don’t need. You’re like a doctor who did a terrific job diagnosing a specific illness, but your prescription is for diseases that we don’t have!”

He then terminated the demo meeting, ending the sales process for that vendor.

Moral: Map your demos to your discovery information!

Resources:

Situation Slides: A Swiss Army Knife for Sales and Presales

https://greatdemo.com/situation-slides-sales-and-presales-swiss-army-knife/

Doing Discovery

https://www.amazon.com/Doing-Discovery-Important-Enablement-Processes/dp/B0B8RJK4C2/

And see the stories in “Suspending Disbelief” for more engaging lessons learned!

https://tinyurl.com/yc7rsrmy

– Vendor rep watching people leave the room…

It was an important opportunity, and the vendor organized a two-hour face-to-face demo with the prospect’s team of twenty to make sure there was sufficient time to cover everything. Sadly, discovery had been limited to the confirmation of the prospect’s general “pain,” some demographics about the number of users, and tech stack requirements.

With this limited information, the vendor began the meeting with fifteen minutes of corporate overview presentation, followed by their standard demo, starting with system configuration, then general navigation, followed by function after function in a long, linear flow.

It was a perfect example of a stunningly awful Harbor Tour!

A few minutes into the demo portion, one person excused themself and left the room. And since the vendor never asked for introductions of the prospect’s team, the vendor had no clue that they’d just seen the key executive leave the room!

Ten minutes later two more prospect players quietly headed for the door. As the meeting reached one hour, several additional people mumbled something about “having another meeting…” and slipped away.

It was at this point that the presenter begged, “Wait! Don’t go away, we haven’t gotten to the best stuff yet!”

Now only eight of the original twenty remained, one of whom commented to their neighbor, “I’ll stay as long as the donuts hold out!”

Important opportunity squandered, with no sale resulting.

Additionally, because it was an important opportunity, the vendor had sent a team of four folks to the meeting (including a salesperson, solution consultant, product specialist, and professional services rep) incurring the costs of airfare, lodging, rental car, and food to the tune of ~$5,000, not to mention the associated opportunity cost (pun intended)!

Moral: Do the Last Thing First!

Resources:

Illustrations: Doing the Last Thing First!

https://greatdemo.com/illustrations-doing-the-last-thing-first/

Why Structure Demos Like a News Article?

https://greatdemo.com/why-structure-demos-like-a-news-article/

The Menu Approach – A Truly Terrific Demo Self-Rescue Technique

https://greatdemo.com/the-menu-approach-a-truly-terrific-demo-self-rescue-technique-3/

And see the stories in “Suspending Disbelief” for more engaging lessons learned!

https://tinyurl.com/yc7rsrmy

– Gandalf to Saruman

Software wizards are intended to make a complex workflow simple to use, but only if a reasonable path is followed! Here’s another true story:

The presenter started a wizard to execute an analysis of business data and was still walking me through the options sixty minutes later!

Once he’d finally completed that portion of the demo, I asked him to show me how to execute that same workflow using the wizard the way someone would typically use it on a day-to-day basis.

How long do you think it took?

Two-and-a-half minutes start to finish.

Moral: Execute all demo pathways with the fewest number of clicks!

Resources:

Page 157 in Great Demo!

https://www.amazon.com/dp/B0C9SNKC2Y/

And see the stories in “Suspending Disbelief” for more gems!

https://tinyurl.com/yc7rsrmy

– Alexandra Stoddard

I watched a ninety-minute demo recording and noted two rather astonishing things…

Astonishing Thing Number One:

Approximately half of the demo was consumed by setup and configuration items, including setting up the environment, configuring the application, creating and editing templates, forms, reports, dashboards, etc.

This wasn’t astonishing on its own, perhaps, until…

Astonishing Thing Number Two:

At the end of all this setup activity the vendor said proudly, “Of course, you won’t have to do any of this. We take care of it during implementation. It’s all done by our Professional Services team…”

Wait. What did you say?

You just spent forty-five minutes showing stuff your prospect will never need to use? (Enter your choice of an appropriate exclamation of surprise and astonishment here ______.)

But wait, there’s more: A bonus Astonishing Thing!

I called the presales manager who had sent me the recording and asked, “Why did half of the demo present capabilities that your prospect will never use?”

They responded, “Oh! We’ve been told that these are key differentiators and that we must include them in every demo!”

Moral: Don’t take guidance from the Sales Prevention Team!

Resources:

Stunningly Awful Demos – The Painful Irrelevance of Setup Mode

https://greatdemo.com/stunningly-awful-demos-the-painful-irrelevance-of-setup-mode/

Page 244 in Great Demo!

https://www.amazon.com/dp/B0C9SNKC2Y/

And see the stories in “Suspending Disbelief” for more gems!

https://tinyurl.com/yc7rsrmy