Tuesday, September 27, 2011

Using Salesforce.com’s Chatter To Support Great Demo! Implementation

A number of Great Demo! Workshop customers report using Salesforce.com’s Chatter functionality to reinforce and support roll-out and ongoing implementation.  For example, they report:
 
- Posting success stories
- Using and editing Situation Slides and Illustrations
- Posting tips and advice
- Discussing new and challenging situations
- Asking where to find or use specific pieces of Demo Capital
 
It is nice, simple mechanism to keep team members engaged and to share ideas.

Monday, September 26, 2011

Public Great Demo! Workshop


[Warning: Shameless Self-Promotion Alert!]

Our next Public Great Demo! Workshop is scheduled for October 12, 2011 in San Jose, California, co-sponsored by SKMurphy (
www.SKMurphy.com). This is a terrific opportunity for individuals or small groups to learn how to put Great Demo! ideas into day-to-day practice.

An overview, agenda, location and pricing information are available here: www.skmurphy.com/blog/2011/06/08/great-demo-workshop-on-october-12-2011/ .

Tuesday, September 20, 2011

“Clearly You Weren’t Listening…”

I’ve come across an affliction that, untreated, can cause serious chronic trauma to sales teams and forecasts:  Ignoremucitis.  This terrible disease manifests with the following symptoms:

1.       Sales team does a great job in qualification and discovery, asking many excellent and thoughtful questions.

2.       Sales team then presents a demo that essentially ignores everything that was learned.

3.       Customer chooses to purchase from a competitor or does nothing.

Additional collateral damage can include loss of sales team credibility, negative buzz from customers to other customers, and an ever-increasing spiral of trying to increase the sales “funnel” with more leads and more unproductive demos…

This horrible disease is curable.  For individuals, a single application of the Great Demo! book (applied topically, not to be ingested) has shown remarkable efficacy in studies done by the FDA (Famous Demonstrators Association).  For team-sized epidemics, the FDA recommends an initial dose of Great Demo! Workshops, followed periodically by refreshers to maintain desired antibody levels against future outbreaks.

Friday, September 16, 2011

Demos - Measure What You Want to Impact

Too many organizations measure the number of demos delivered – without exploring whether these demos were needed or productive.  In fact, a number of sales organizations incent their teams based on the number of demos scheduled or delivered, under the belief that the more demos in the pipeline, the better the pipeline…  This generates a negative spiral of doing more unproductive and unnecessary demos, yielding forecasts that are increasingly inaccurate and consuming valuable resources that could otherwise be allocated to more profitable sales opportunities.

It is my experience that doing fewer, much more qualified demos results in higher close rates and more accurate forecasts.  Great Demo! practitioners report measuring:

-          Demos per $ of revenue
-          Close rates
-          Sales cycle length
-          Cost of sales (per revenue $)
-          Free vs. paid trials and evaluations (POCs, POVs)
-          Number of trials and evaluations required
-          Deal size and breadth
-          No decisions
-          % follow-up calls
-          Internally-circulated demo success stories

Other measurements to consider?

Tuesday, September 13, 2011

We Are All In…Support

Most of us have heard the phrase, “We are all in Sales”, but I recently heard an interesting twist on this:  “We are all in Support”.  This is a terrific flip from the traditional positioning that everyone in the organization is part of the sales team and selling process. 

The idea that everyone in the company is ready, able (willing), and proactively working to help customers implement, use and get the desired value from the offerings is huge…!  It can be a key competitive differentiator, particularly when the customer perceives that the functional capabilities of your offering  vs. a competitor’s are essentially equal.

Tuesday, September 6, 2011

Public Great Demo! Workshop

[Warning: Shameless Self-Promotion Alert!]

Our next Public Great Demo! Workshop is scheduled for October 12, 2011 in San Jose, California, co-sponsored by SKMurphy (www.SKMurphy.com). This is a terrific opportunity for individuals or small groups to learn how to put Great Demo! ideas into day-to-day practice. An overview, agenda, location and pricing information is available here: www.skmurphy.com/blog/2011/06/08/great-demo-workshop-on-october-12-2011/

Thursday, September 1, 2011

Demo Capital – Underutilized, Undervalued and Often Insufficient

[This is a rather long article for a post - send me an email at PCohan@SecondDerivative.com if you'd prefer a copy emailed to you]


Consider the sum of an organization's knowledge, know-how, tools, techniques, tips and success stories related to demonstrating one's offerings.  As with other types of capital, how can this best be captured, developed, and leveraged? How is it valued (how should it be valued)?  And is what you have today sufficient?

Use of your organization’s Demo Capital should yield competitive advantages and opportunities, ranging from sales successes, to productivity and efficiency gains, to attracting and retaining high-value employees. A first step is to identify what you have...

What is Demo Capital?

Interestingly, its existence is often assumed rather than truly recognized.  Demo Capital is the aggregate sum of your organization’s demo infrastructure and know-how, ranging from laptop configurations to demo success stories swapped at the bar during kick-off meetings. 

Here are some tangible elements of Demo Capital, as a starting point:

-          Demo databases, data, and accompanying application scenarios
-          Demo virtual machine images
-          Specific demo support software and tools
-          Demo scripts
-          Recordings of demos and demo segments
-          Qualification, discovery and analysis forms and documents
-          CRM system forms and fields
-          Meeting preparation sheets and forms
-          Situation Slides
-          Illustrations
-          Defined and practiced "Do It" pathways
-          Similarly defined "Peel Back the Layers" pathways
-          Documented answers to typical questions
-          Formal Success Stories and reference customers
-          Documented Informal Success Stories
-          Market-specific data, notes, and materials
-          Competitive strengths/weaknesses tables and pieces
-          RFP response boilerplate (including "Adding Rows"); won/lost RFP’s
-          Documented stories, props and other tools applied in successful demos

One could define Tangible Demo Capital as any demo-related entity that can be accessed and used by the team as a whole. 

There is likely an even larger collection of assets and know-how that can be classed as Intangible Demo Capital – these are any demo-related entities that cannot be accessed and used by the team as a whole.  In addition to anything above that is simply undocumented or unknown beyond any specific individual, other intangible elements might include:
 
-          General best practices generated or evolved by individuals
-          Tips, tricks and techniques for face-to-face demos
-          Face-to-face presentation skills and techniques
-          White-boarding tips, methods and use scenarios
-          Tips, tricks and techniques for Remote Demos
-          Menu Approach super-sets and sub-sets for specific customer scenarios
-          Lists of probable or likely customer Critical Dates or Events
-          Particularly successful props, stories, and related presentation "nuggets"
-          Methods for handling specific questions and hostile audience members
-          Tactics for dealing with typical customer objections
-          Tips and proven methods for outflanking specific competitors
-          Successful Transition Vision development with customers
-          POV, POC and Evaluation success strategies and methods
-          Training techniques for new sales people and channel partners
-          Post-demo debriefing methods and tools
-          Other team-related tactics and techniques
-          Testing/retesting demo environments (particularly those with frequent releases)
-          Methods for surviving a full day at a trade-show booth – (and an evening at the bar)
-          Undocumented Informal Success Stories and related anecdotal success stories
-          Improvements and changes made to documented materials (but not documented)

[This last arena can be huge!  Just consider the (likely) multiple versions of “standard” overview, corporate and product presentation decks that have been evolved by individual team members, for example…]

Clearly, these lists are not exhaustive – a brief brainstorming exercise should yield longer and more specific lists unique to your organization. The resulting lists should also alert you to strengths and weaknesses in the Demo Capital you have – and gaps associated with capture, cataloging and re-use of these resources.

What is the Value of Your Organization's Demo Capital?

Demo Capital only has value if it can be, well, capitalized upon.  Let’s briefly examine the cost of not leveraging existing capital. 

Could we have avoided losing opportunities to competitors or "no decision" if a team member had access to another’s experience or tools?  (“For the want of a nail the shoe was lost…”).  Similarly, could a specific tip or idea have eliminated the need for a second meeting or repeat demo for one customer? 

Nearly all sales, presales and marketing teams complain that they don’t have enough time to get everything done.  What is the opportunity cost associated with repeat work?

-          Recreating materials or tools (that individuals could not find or were unaware of)
-          Re-developing know-how (often through painful experience)
-          Re-discovering applications of these (e.g., an effective white-boarding method)

There are approximately 220 “selling” days per year – it is extraordinarily painful to find that one or more of these days have been wasted (particularly if the impact resulted in the difference between achieving one’s numbers versus missing them!).

Yield From Investment

Here’s the payoff - and the challenge! There are a series of strategic and tactical questions that can help extract the best yield from your existing investment in Demo Capital – and to determine what might be missing or need improvement:

Tactically:

-          What do we have? What's missing? Is it sufficient?
-          Where is it? How is it organized and accessed?  How do we use it today?
-          Are there tools available to help? Are there best practices that we can apply?

Strategically:

-          Can we shorten our sales cycles? Improve our sales processes? Increase revenue per opportunity?  Reduce the number of demos per dollar of revenue?
-          Can we increase efficiency and productivity in our sales, presales and marketing teams?  What would help the team achieve quota most consistently?
-          Can we improve our ability to attract, hire and retain top-performing staff?  How do we further develop existing staff?

Assessing, capturing and leveraging Demo Capital can clearly be a means to address some of the critical business challenges faced by sales, presales, and marketing leadership - and at mid-management and staff levels as well.

Is It Sufficient?

For a specific example of an addressable but often painful “gap” in Demo Capital, let’s revisit the “Is it sufficient?” item from the previous section, with respect to demo data.  For many products, generating demo data that is satisfactorily broad for a range of markets yet specific for any one arena can be a tough challenge – especially when your offerings span multiple job titles, disciplines and markets. 

Generating meaningful demo data (and corresponding application scenarios) to address customer situations that might range from commercial banking to manufacturing to retail typically require either an enormous effort or some very clever data design, or both!

The importance of relevant demo data can be exceptionally high.  The ability for customers to see meaningful and realistic data as part of “their” solutions can be the difference between winning and losing the business. Data that is perceived as fake or unbelievable hurts your cause; data that appear to be real and relevant support your efforts.

Asking a customer to “pretend” with data that is obviously from an alien arena is a recipe for disaster.  A few specific things to avoid include:

-          Data that includes the words “test”, “demo”, or similar.
-          Data that is obviously fake, for example that include famous actors or other people with well-known names.
-          Ancient data – imagine describing “real-time access to up-to-date information” with screens that show the most recent records are from August 2006!

Have you ever felt you lost an order because of the quality of your demo data?  If yes, then what might currently be perceived as “something we just have to live with” should be recognized as a real Critical Business Issue – and needs to be addressed with a tangible investment of resources (time, people, money).

What about your on-boarding process?  How long does it take for a new presales, sales or marketing person to come fully up-to-speed?  What if you were able to leverage existing (but currently unshared) success stories, demo strategies, tips and techniques that are already in use – but are locked in other team members’ heads? 

In this example, the information is sufficient but the access to that information is not.  One simple solution is to implement a series of “Demo Days”, where team members present demos they are particularly proud of or that were wonderfully successful.  These sessions yield stories, tips, and new ideas that can be shared and used immediately within the team.

Underutilized, Undervalued and Often Insufficient

Demo Capital is too frequently taken for granted – both the presence and absence – resulting in what can be rather fearsome lost opportunities and unmet challenges.  Review your existing investment and determine: are there major gaps that need to be closed; are there opportunities waiting to be harvested?

Copyright © 2011 The Second Derivative – All Rights Reserved.

Monday, August 29, 2011

Passion – And Demos

(This is a brief post – but a huge topic…)  How do you keep your demos fresh, even after doing 5, 10, 20 or more demos in a month (or week!)? 

The passion we feel for what we do serves both as a source of energy and as an engine to help us make every demo unique (as far as the customer is concerned), remarkable and engaging.  The excitement we feel about our offering and the desire and ability to change the world is what often propels us, even after the 6th hour of a scripted demo. 
 
Harnessing and using this passion can make enormous differences in audience perception – the difference between someone simply “clicking the mouse to get the next screen…” vs. building a strong tangible vision of a solution in a customer’s mind.

Tactically, what can we do to tap into this passion?

-       Avoid pre-answering questions (let the customer ask questions that we can respond to)
-       Look for opportunities to learn something new in each demo
-       View each demo as a performance (like a performance of music or play)

Other ideas?

Friday, August 26, 2011

Jobs Thoughts (Steve, that is…)

I heard three ideas over these past few days with respect to Steve Jobs’ resignation from Apple that are particularly worth sharing:

First, Steve drives an ethos that is all about the experience rather than the product.  This can be paraphrased, “Don’t sell me a product; sell me an experience!”

Next, and along those lines, one might say that Apple doesn’t have a VP of Products so much as it has a VP of Lust – that person’s objective is not to present a product to us but instead to make us lust after his or her offering! 

And finally, Charles Revlon was famously quoted as saying, “In our factories we make cosmetics, in our stores we sell hope!”  What is it that Steve Jobs has been selling these past 14 years?  He’s been selling Confidence.  The confidence of knowing that whatever you buy from apple it will be delightfully easy to use – truly intuitive – no risk, no worries about complexity, no concerns about being overwhelmed.  Now that’s a Great Demo!

Tuesday, August 23, 2011

Completing Situation Slides at the Demo Meeting


A number of Great Demo! Workshop participants report good success with the following tactic:  While reviewing the customer’s situation using a Situation Slide, the sales team asks the customer to fill in any gaps  before the demo itself begins.  Showing the line item with blank data has had the effect, in some cases, of the customer actually volunteering the missing information!  This has proven to be very useful when working to understand customer Critical Business Issues, the Delta, and/or Critical Dates, in particular. 

Friday, August 19, 2011

Public Great Demo! Workshop

[Warning: Shameless Self-Promotion Alert!]

Our next Public Great Demo! Workshop is scheduled for October 12, 2011 in San Jose, California, co-sponsored by SKMurphy (www.SKMurphy.com). This is a terrific opportunity for individuals or small groups to learn how to put Great Demo! ideas into day-to-day practice. An overview, agenda, location and pricing information is available here:
www.skmurphy.com/blog/2011/06/08/great-demo-workshop-on-october-12-2011/

Thursday, August 18, 2011

Don’t Let Perfection Be The Enemy of Great

Just heard this paraphrase of the classic Voltaire quote (“Don’t let perfection be the enemy of the good”) in a demo.  The customer was very interested in the offering, which clearly offered terrific value, and asked about capabilities net yet implemented.  The presenter responded, “Don’t let perfection be the enemy of great” as a way of telling the customer that the offering in its current form would make substantial improvements to the customer’s process and bottom line – and to move forward now rather than waiting (potentially forever!) for additional capabilities that might make it better…

Friday, August 12, 2011

“Stalker” Demos

Just heard this phrase in a recent Great Demo! Workshop:  “Stalker Demos”.  Loosely translated, it amounts to “If you don’t agree to purchase after this demo, we’ll come back again – and again – and again – and we’ll keep delivering demos until you cave in…!”

This is amusing at one level, but it is based on situations where an initial demo didn’t go well – often because the initial demo was a Harbor Tour or Show-Up-and-Throw-Up Demo – causing the vendor to request doing another, “better” demo for the customer.  Given that there are only about 220 “selling” days per year, repeating a demo meeting represents a large opportunity cost. 

I suspect that many of us have or had parents who offered the advice, “Measure twice, cut once”.  Insufficient preparation, especially with regards to performing adequate qualification and discovery, can yield these “Stalker Demo” results!

Tuesday, August 9, 2011

Story-telling and Demos: The Hero

As I’ve remarked previously, story-telling can be an extremely effective method to communicate key ideas – and stories can be particularly “sticky” with respect to audience memory and retention.  An additional story-telling concept is the use of a hero – someone (or something) that the audience can identify with.  Traditional stories (e.g., sagas) typically have a hero that encounters and overcomes trials and adversity before achieving success. 

For demos, heroes can take a number of forms:

- Customer (an individual):  the customer can be portrayed as the hero (very effective!), with the payoff being the timely and on-budget completion of a project, accolades from colleagues or a promotion.  In my own experiences, it was gratifying to see customers I’d worked with over a period of years move from staff members to middle managers to senior and C-level management.

- Team (a customer team or group):  The logical corollary to an individual, a team can be presented as the hero in a story.

- Product:  your software can be the hero, similarly, enabling a customer to achieve their objectives in spite of (apparently) overwhelming challenges.

- SaaS:  Interestingly, the “cloud” can be positioned and perceived as a hero – “when our  own servers went down, we were still able to complete the project thanks to the ability to access the vendor’s software from the cloud…”.  I’ve heard a number of examples where the cloud is the hero, in addition to the one above:  access to key information via collaboration tools or capabilities, disaster recovery (“and we were able to get back up and running just in time for the opening…”). 

Any other hero types or ideas to suggest?

Friday, July 29, 2011

“Demo Day” Sessions

Many Great Demo! Workshop principals and participants ask what they can do to keep the implementation process moving forward, after a Workshop completes.  One simple (and surprisingly effective) tactic is to do a “Demo Day”.  This is an extension of the role-play sessions practiced in the Workshop, where each person or team presents an 8-10 minute demo to the overall group, followed by feedback and discussion.  This reinforces the key concepts and surfaces new tips and best practices – and is a highly valuable exercise whether or not the team has had the pleasure of participating in a demo skills Workshop.

I typically suggest allocating about 30 minutes per role-play to give sufficient time for the demo, feedback, technical glitches and break time.  In a half-day session you present and review 8 demos easily.

A Demo Day is something that teams and principals can do on their own or  [warning:  shameless self-promotion alert!]  have someone who is highly skilled in teaching and coaching demo practices facilitate – me, for example! 

Wednesday, July 27, 2011

Having Your Champion Drive – Interesting Variant

I often suggest having your customer (or more specifically your Champion) drive for portions of a demo.  This changes the entire dynamic in comparison with traditional demo meetings, making things different and very engaging.  I also recommend reducing any risks by working with your Champion and practicing beforehand so that both you and your Champion are comfortable.

A wonderful  alternative to this is to have your Champion narrate while you drive – this may be the next best thing to having the customer drive, but with (substantially!) reduced risk.  Try it!

Tuesday, July 5, 2011

Introducing the Demo - Like the Evening TV News

A number of Great Demo! Workshop participants have enjoyed good success in positioning “Do the Last Thing First” by drawing an analogy with the evening TV news.  They tell their audience that “We are going to start, like TV newscasters do, by going you the headlines for each “story” so that you have an outline of the overall demo.  Then we’ll go into each “story” section in more detail.”

Customers apparently understand and appreciate this analogy – it resonates!

Tuesday, June 28, 2011

Testing Web Collaboration Tools – While Doing Discovery

Many sales teams find that their customers are (still) unfamiliar with web collaboration tools (e.g., WebEx, GoToMeeting) or have not tested the tool before a scheduled vendor demo – resulting in fumbling, lost time and (sometimes) having to reschedule demos.  In addition to the several other ideas already offered in this forum, here’s another (very clever) one:

One Great Demo! Workshop participant recently noted that he sets up a web session for his discovery calls.  In addition to having the session open and available for any discovery needs (e.g., Menu Approach, Workflow Analysis, etc.) this is a subtle way to test the technology before any demo is scheduled.  Very clever!

Monday, June 13, 2011

Remote Demos – Who’s There?

Consider typing the names of the audience members on the screen (use a white board, PPT, or Word document).  This confirms who is actually present, engages the audience and gives you an accurate list as well – audience members will often correct any spelling errors for you!

Friday, June 10, 2011

Product Overview Presentations - Like Having a Brochure Read to You

Many demos are preceded by 1) a corporate overview presentation and/or 2) a product overview presentation.  Leaving the horrors of typical corporate overviews aside for the moment, it just struck me that watching many product overview presentations feel a lot like having someone read a product brochure you…  A recent product presentation I watched took over 30 minutes (before the demo) and reviewed the company history and mission statement (again, even after it was introduced in a corporate overview presentation!), then walked through the history of the problem/shortcomings of the existing technology, technology Bottlenecks, the product technology itself (how it works) including details of architecture and environment, typical numeric results, security, integration options (SDK and API’s) and finally deployment. 

The customer was quiet throughout the entire 30 minutes – no interaction.  It struck me that this was like having the product brochure being read to us!

Monday, June 6, 2011

Stunningly Awful SaaS Demos – Lost in the Clouds

What are the challenges of presenting SaaS offerings vs. “traditional” or “on-premise” software products?  SaaS demos present specific opportunities for disaster – several of which are outlined in this installment of Stunningly Awful Demos…

It’s the Same, Only Better – Let Me Show You…

Many vendors work to differentiate SaaS from traditional offerings, in spite of often positioning SaaS offerings as providing the same functionality as their traditional behind-the-firewall counterparts. Many demos attempt to show these 1:1 comparisons in gory, boring, painful detail – with negative results (including but not limited to):

-          Way too long, way too boring, ran into bugs, made the simple look complicated, opened the opportunity for damaging questions, key players left early, and on and on.

It’s Slow Today Because…

How often have you heard this phrase?  Customers assume that whatever environment you use for your demos is better than their infrastructure (have you ever heard a customer say, “Our network is blisteringly fast?”).  What they see in a demo is the best they typically expect the offering will perform in their own hands.

To add to this, customers are already concerned about performance when operating SaaS products over the web. Demos need to take this rather strongly into account to minimize clicks and other performance-related challenges.

No Plan “B”

And, of course, don’t capture screen shots of your key screens so that if you have no internet connection you are unable to show anything…!  God forbid you’d have these stored in PowerPoint or Keynote as a backup plan…

iPhone, iPad, iCloud, iAndroid, iBlackberry, iSmart

Customers expect to see a broad range of devices supported by SaaS product vendors, including “traditional” PC’s and Macs, iPads and other tablets, and a range of smart phones. New practices need to adjust and reframe demos to address this.

Demos done solely on a laptop may lack sufficient depth of proof for many customers – and emulators are OK, but they miss opportunities to use iPhones and iPads (etc.) as props and to put the product in customers’ hands (changing, wonderfully, the whole demo dynamic).

Getting “Social”

“Social” is an additional challenge for some SaaS demos…  Customers may want SaaS offerings to integrate with and/or feed a range of “social” tools (e.g., Twitter, LinkedIn, Facebook, etc.).  This adds more complexity in demo preparation and delivery.  There is even an entire cadre of “social aggregator” tools designed to help address these efforts, including EventBox, twentyfeet, Flock, friendfeed, youmeo, ping and a pile of others.  

[Some of the names of these tools are really fascinating, for example: Twitter Tools, Twhirl, TweetBeep, TwitBin, Twidget, TwitterBerry, and Twittalator Pro. Gad!]

Vendors that offer these capabilities are often only too happy to show them in their standard demos – is this a good thing?  Perhaps – but only if the customer views them as Specific Capabilities they need to address their problems. 

Vendor Vocab

If you want to confuse your customers, try verbalizing a variety of vendor vocabulary terms.  Here is a set to draw from, as a start – be sure to add your own company-specific terms and acronyms to further increase the perceived complexity.

-  Cloud, cloud-based, in-the-cloud, cloud-burst
-  On-premise, traditional, installed, behind-the-firewall
-   On-demand, hosted, ASP, multiple-tenant
-   SaaS, PaaS, IaaS, AaaS

Ignore F11

Most SaaS software is accessed (and demonstrated) via web browsers.  In day-to-day use of browsers, many demonstrators use a range of toolbars (Google, Bing, Favorites, Command Bar, etc.) to provide them with quick access to a range of capabilities.  These toolbars, however, consume screen real estate and may confuse audiences.  Stunningly Awful SaaS Demos ignore this…

Tapping F11 (in many browsers) hides these toolbars, devoting the maximum possible screen real estate to your application and reducing apparent complexity. Simple and effective!

The Latest (And Greatest)?

One advantage of SaaS offerings is the ability to deliver releases nearly continuously, as opposed to traditional processes of large, comparatively infrequent releases (often followed by “X.01” releases that address problems found with the last large release!). 

The corresponding disadvantage for presales and sales teams is staying on top of this release flow.  SaaS demos often show the latest, greatest releases and functionality – which increase the risk of encountering bugs, surprise when the “old” workflow has been changed, and confusion when capabilities have changed. 

Stunningly Awful SaaS Demos ignore testing the latest release environments or doing a dry-run of the demo ahead of time.  Feeling lucky?

Wait – Don’t Buy This Yet!

A dangerous corollary of the above is the knowledge or expectation that capabilities not yet released will be available shortly.  How often have you seen a purchase delayed by a misspoken comment or promise along the lines of, “Oh, that capability will be in the March release…” – to which the customer responds, “Terrific, then I’ll hold off buying until March…!”

Mismanaged Migration

What about upgrading existing on-premise customers to SaaS versions? 

Many sales teams assume that customers will want to make those migrations right away (and pay for the “added value” of SaaS).  Stunningly Awful SaaS Demos occur when it turns out that the customer is perfectly happy with their current on-premise implementation and do not perceive a sufficient driving force to move to the SaaS offering – there is no compelling reason to change.

This is exacerbated when demos delivered after insufficient discovery show that key functionality, in heavy use today by the customer, is not available or is insufficiently implemented in the SaaS version.  Ick.

Interestingly (and especially sadly), some of the key capabilities lacking in the new SaaS versions are often amongst the most important for customers – reporting tools and other output capabilities, for example.  These are (sadly again) often the last capabilities to be implemented in SaaS release rollout.  Double ick.
 
“Configure, Not Customize”

Have you ever heard this mantra chanted by sales teams?  “Our offering is configurable and doesn’t require custom development to implement customer-specific needs”.  That’s great.

However, vendors often spend the first 10 minutes of Stunningly Awful SaaS Demos showing the broad range of configuration options – well before getting to the end deliverables desired by the customer.  Bear in mind that many (most?) customers configure the offering only once, when it is first implemented!

Hijacked By IT

The demo was going great… and then an IT person asked, “What browsers do you support?”  The answer to that question prompted the IT person to follow-up with, “And Java?  What level of Java is needed?  Flash?  CCS?  HTTPS?  SOAP?  REST?  Multiple tenant...?” 

Instead of “parking” the question for later, the presenter answered each question in detail, getting dragged deeper into a hole and moving farther from the main issues that the key customer players were interested in – and then they left the meeting room…!

Input – But No Outgo?

Many new SaaS offerings focus on the operations a customer can apply to their data or the associated workflows.  A typical weakness for newly released SaaS offerings is the lack of sufficient capabilities for reporting or exporting the results. 

To paraphrase a terrible old TV commercial, “You can check the data in, but it can’t get out…”

Login Logorrhea

Many customers have concerns about the security of their proprietary information in vendor SaaS applications.  Rather than address this as a part of Q&A (where it typically belongs), Stunningly Awful SaaS Demos consume the first few (key) minutes of a demo detailing the login process, security arrangements, and customer data protection provisions. 

This is a great approach if the team is presenting to IT (alone), but bores the heck out of business users – and consumes the few minutes that high-level executives are willing to invest in a demo meeting.  Unless it has been identified as a key issue by customer management, save it for later in the meeting…!