The Legend of the Purple Squirrel

Part III

You are a sales team in an enterprise deal and here's the situation:

You're up against a behemoth of a competitor

The evaluation is poorly managed and you have been forbidden access to the decision makers

You have one last shot to win

What do you do?

To recap the previous installment, my team was working on an opportunity with a DC non-profit organization. We were hastily called in and provided a straightforward, sincere, presentation on our capabilities, followed by an awesome lunch at the Capital Grille, and we made the final list of two. It was down to us and Microsoft.

To win, we had to win. A "tie" and my competitor wins. And lets not forget the whole "No one gets fired for buying Microsoft factor". We were the riskier purchase. To top it all off, every bit of technology in that shop was Microsoft and we were written in Java.

All things being equal we really were a better fit. The prospect had over 20 sites that they wanted in multiple languages, with pdf download, and xml syndication requirements. This was our sweet spot. However, because we had limited communications with the prospect, we needed a hook, an easily-consumed message that would resonate with the audience and strengthen our claim as a better fit for their requirements.

"The Purple Squirrel" idea actually came about as a result of a conversation with a seasoned consultant who claimed that given enough time, money, and resources, you could build (in software) anything, even a purple squirrel.

Now, before you go nuts and try something in your sale pitch that has only been successful in the cartoons, it is important to know that there are three criteria for anything included in your sales presentation:

Relevancy

Uniqueness

Timeliness

In short, you want to be talking about the right things, to the right people, at the right time. Miss one of these criteria and you lower your chances of moving forward in the deal.

Cahill and I surmised that our most valuable advantage was that we had functionality relevant to the project that was part of our standard software install that would otherwise have to be custom built in the Microsoft software. The challenge was that the last scheduled meeting would be timed and scripted. When your meeting is scripted you can't veer too far off topic without looking like a real schmuck.

So we devised a way to draw a great deal of attention to our advantages, without veering off script.

We arranged our presentation accordingly with only the following modifications:

Early in the presentation we had a graphic of our purple friend with the words "Purple Squirrels = Time and Money" emblazoned across the screen.

Secondly we placed two types of small graphics throughout the presentation. The first was our friend, sized about .75" x .75", on those slides that discussed features that would have to be custom built in the Microsoft solution, underscoring the message that there was expenses involved with our competitor that where not applicable to our solution. For example in our solution you could have an unlimited number of stages in a document's work flow approval process. At that time, Microsoft's could only support five stages before custom code had to be used.

The second graphic was the squirrel with a red circle and line superimposed on it, in a manner that you see "No Smoking" signs. We placed those on the slides where we offered a feature out of the box that they would normally have to build. For example our solution would automatically manage embedded hyperlinks within content. So if a press release had a link to product information that had been updated or removed from the site, the link would automatically be removed or updated.

We pack up and fly to DC. We were a bit nervous, because if our audience didn't really "get" what we are doing, we are going to look real stupid, real fast.

We arrived for our meeting, exchanged introductions, and started on the first exercise in the script, using PowerPoint to explain what we were about to accomplish in the software and to highlight any relevant advantages of our approach, followed by a software demonstration. At the beginning, we explained that the squirrel logo was simply there to highlight those areas where we offer more value than our competitor. We proceed through each section of the script, without drawing any additional attention to the squirrel, but it was obvious the audience had conditioned themselves to look for the graphic as we progressed along, because every time the squirrel appeared the number of questions increased vs those slides without the squirrel.

After a meeting like this, you can feel good about it, but you really do not know how well you did. I have been in meetings where I thought we hit a home run, only to find out we were practically eliminated in the first 15 minutes. Conversely, we've all had those client experiences where you would rather have gone through a severe IRS audit, only to find out that you were the best presentation they had seen. After this stunt, I didn't have the courage to fathom a guess on how well we ranked.

"Sasser, what in the hell is a purple squirrel?" This is how my VP of North American Sales greeted me on our Monday Morning conference call the following week. A quick lesson, if you are going to try a Purple Squirrel Maneuver, and you have the experience and seniority to suffer the consequences if you fall flat on your ass, tell as few people as possible. It is usually those with the least amount of field experience that will try and stop you.

Anywho, my inside team had followed up with the prospect while I was on the plane ride back home. The prospect responded that they really enjoyed the "rodent" in our presentation, and went on to share that during the meeting with the other vendor, the phrase "Oh we can do that with a little extra code" by the vendor was answered with an almost group wide cry of "PURPLE SQUIRREL!!!!".

Yeah we won. My team looked like heroes and the Purple Squirrel became a legend.

Mainly because the circumstances never aligned where we deemed it necessary, we never used the squirrel again.

The Legend of the Purple Squirrel

Part II

Being a virtual team we had people stationed all over the country. I lived in Georgia, my primary Sales Engineer lived in Providence, and our corporate office was in Boston.

A few years ago, in the middle of summer, our inside team finds an opportunity at a DC non-profit organization. This was a common event that was made special by the first phone call "Yeah, we meant to call you guys, but we forgot, but we have you scheduled for an onsite presentation this Wednesday".

"Whoa" was my initial response. Without giving us any written requirements, 36 hours notice, and no real contact to any of the decision makers, we were supposed to assemble our team and come into their organization and be relevant to their project based on one phone call. A project whose requirements where not going to be documented until after our first presentation. Lovely.

Frankly I wanted to take a pass, but unfortunately, it would have taken more effort to get out of going, than actually doing the meeting.

So Cahill and I meet up in DC, in July, wearing suits, looking suave, and with the lowest G.A.D. (Give A Damn) factor imaginable.

Its interesting, when your G.A.D. factor is that low, you come across as extremely confident. So confident in fact that when we met the project lead, who happened to be French, we corrected his English on our way into the board room.

We enter the board room and the consultant leading the evaluation(the one who was late on documenting the requirements) politely introduces herself and gives us the instructions. There was to be two segments to the presentation; "business requirements" and "technical requirements". She would monitor the questions during the demonstration and only the appropriate questions should be answered in each section. To clarify, if a technical question was asked during the business portion of the presentation, we were not to answer, but she would right down the question and we answer during the technical portion.

We had made reservations and announced to the consultant that we had a lunch meeting down the street from the Capital and would be finishing fifteen minutes earlier than the allotted time. She nodded her head in approval.

So the team for the Business portion of the requirements files in. Very nice people. After a brief conversation I realized it was the consultant's lack of performance that has caused the mad rush. But the G.A.D. factor still remained in the cellar.

We gave one of the most sincere, straight-forward presentations of our lives that afternoon. "No, our software doesn't do that", "I wouldn't try that if I were you, it will be expensive", and ,my favorite, "Our competitor does a better job in that area". I don't know if you ever had the Porterhouse at the Capital Grille in DC, but yeah, its worth it and I didn't want to be late.

During our meeting, no less than 20 times, our responses were interrupted by a shrill "Don't Answer!, Please save that for the technical portion!!!!". In fact the consultant stopped our presentation to scold the evaluation team (the people that were paying her) that they should limit their questions to only the topics listed on the requirements document (the one they told us that didn't exist 36 hours earlier).

So fine, we power through the business requirement, being polite, professional, and very succinct.

Finally, the consultant announces that we have reached the end of the business requirements. We were to take a 5 minute break and allow the technical team enough time to file in, and the business team to file out.

So we grab a coke, check our watches, and expect a mad rush of people.

One person gets up to leave.

And that's it.

No other people come in.

The exact same people are on both teams. The one who left was a secretary who was curious to what a content management system could do.

An group eye roll commenced in the direction of the consultant as we continued on.

We thanked everyone for their time. I had my steak, and we left DC.

Two days later we learn the evaluation was down to us and Microsoft. Microsoft hadn't actually shown up for their presentation, they barely returned phone calls, and no one at the client actually had seen the product. But they did know that it was doing the site for the XBox, so it had that going for them. (Disclaimer: My Microsoft stock is underwater right now, please buy as much Microsoft as you can).

So it was my team, who had jumped through hoops, paid prime travel dollar, and had 3 days invested in this, vs. Microsoft who was almost too busy to talk to the client in the final round.

It was time for the Purple Squirrel.

Continued......

Whats in a Name?

The post below was forwarded to me in response to a question posted on linkedin.com. After initially reading and laughing, a horrible thought struck me "Uh, oh I might be one of the guys he's talking about".

Thank you Gerald for sharing

"I've had business development people greet me in public places in a highly enthusiastic manner, which diminished not one iota after I advised them that I did not actually go by the name by which they addressed me.

In fact, I am an entirely different person and have an actual acquaintance with the real people they thought I was.

The five times this has happened, I was pressed to accept a business card and a luncheon invitation, both of which I have not further pursued."

-Gerald L.
www.linkedin.com

Purple Squirrel's Performance Anxiety

Sales meetings come in many forms - educational overviews, service level negotiations, real estate tours. For those of us in technology sales, "Proof of Concept" meeting brings the sort of peril that can take three seasoned professionals and strip them of all their confidence.

Government agencies, unlike private industry, need to justify each step of a purchase process, documenting the many ways that their requirements, which often strain reality require a 50% discount for the pleasure of doing business with them.

Back in the early 00's, Sasser, "Steve," and I presented to the agency developing the project scope and specification for a website spanning all Federal agencies, and bringing information resources together in one spot. The agency compiled a panel of two outside consultants and internal technology specialists to compare and evaluate the companies bidding for the work.

Our instructions were to arrive at the appointed date and time with a virgin laptop (If you knew our company, there was no such thing. "bada bing, I'll be here all week, don't forget to tip your waitress") and await further instructions.

Upon arrival, we had a schedule timed to the minute, with sections charmingly titled -

"install software"
"receive materials"
"build site from scratch"

During the break, the three of us happened to be using the men's room at the same time, and luckily, all had brought all of our bags, jackets, whatever.

"Whaddya think? They're all inside, we could leave now, and just pretend the whole thing never happened."

"That's an option - they don't know our hotels?"

"You leave anything behind in there?"

"No, we're good - let's jet."

Of course, being wusses, we didn't.

Point being, even given a structured evaluation process and intelligent people running that process, the temptation to ask a company to create a Purple Squirrel out of thin air, on a moment's notice, keeps smart people and good products from getting to the market.