Skip to main content

Improving Win Rates

Still here at the Gartner Local Briefing. In a session with Richard Fouts about customer win rates.


Sharing Win/Loss Data


Sales teams tend to advertise their wins, yet contain their losses. Why is this so?

Q: How many global IT companies conduct win/loss on an enterprise scale? Less than 5%? About 10%? About 20%?
A: Less than 5%

Why?
  • CEOs and Sales people say "I know why we win/lose". 
  • Some politics are touchy; people don't want you to expose what they did well/not (especially in competitive environments). 
  • "I clicked the won/loss checkbox in Salesforce.com"
One company evaluated their win/loss data. They looked at 140 wins, and 55 losses. Looking at this data, they noticed a correlation between the wins and the fact that they beat their competition to market with compelling announcements in over a third of the scenarios.

An IT services firm attempted to sell a more sophisticated solution. Upon evaluation of the win/loss data, they found that more deals were being lost. That data point led the company to discover that their sales force wasn't prepared to sell the more complex solution and thus they were unable to close those deals. The company had two choices: revert to less-complex deals, or retool their sales team. They opted for the latter.



Getting Buyer Feedback


True/False: Buyers are more willing to share why they bought from us...then why they didn't. (Trick Question!)
  • Buyers don't want to tell you why they did select you because they don't want you to become complacent with them as a customer. They want to keep you on your toes!
  • Buyers don't want to tell you why they didn't want to buy from you because they don't want you to come back and try to re-pitch them and create an uncomfortable scenario.
  • Third party interviews, however, enjoy the benefits of being a "safe" resource.

One interesting tactic is to ask a Buyer to spend 20 minutes to answer 5 questions. This is a disarming quantity of time that people are willing to afford you. What questions should you ask?
  • Competitors: Which vendors were considered?
  • Evaluation: What were top priorities?
  • Sales Cycle: How did requirements change?
  • Lessons: Anything you would have done differently?
  • Conclude: What did I forget to ask you?
Avoid closed-ended questions (yes/no).
Think about the follow-up question you'll ask if you get a certain response.
Know when to let the interview go off-script (let the buyer take you somewhere interesting).

Some other good questions:
  • What went well?
  • What could have gone better?
  • Would you buy again?
  • If asked about us, would you recommend buying from us?

Conclusion


If you don't know why you're winning (or losing), you are ill-equipped to to sustain your success or correct your approach. If you don't have the human resources to invest in win/loss, you can retain third-parties to do this for you. Most companies that contract win-loss work spend $50-$75K/year on it. If this swings one to two deals in your favor, it pays for itself.

Once you have the data, present the big picture and spotlight on key wins/losses from which valuable advice/lessons can be derived and shared.

Comments

  1. AnonymousMay 8, 2012 at 11:20 AM

    Addendum: An Informatica rep here at the briefing shared how they used both internal (sales) win/loss data collection and third-party contractors to collect the information. They discovered that the information they got from the contractors was *dramatically* different than that which came from the internal sales team. It turns out that the internal sales team was just clicking the most convenient button in their CRM system rather than providing accurate, thoughtful analysis. This helped Informatica get better data, train their sales team, and reconfigure their CRM to prompt for better information.

    ReplyDelete

Post a Comment

Popular posts from this blog

Social CRM: Putting Customers First

Last night I attended Social CRM: Putting Customers First , hosted by the San Francisco chapter of the Social Media Club .  It was a great event, and I'll briefly recap some of the discussion and my observations. The panelists were first asked why Social CRM (SCRM) was relevant.  Their answers were as follows: Vendors need to know who their customers are out there on the social web. Vendors need to be able to identify customer pain points from conversations on the social web.  Vendors need to know what to do with these conversations on the social web.  These discussions are the center of business today; their importance cannot be understated. The social web grows too fast for vendor solutions to keep up.  Therefore, vendor solutions must embrace the social web, and learn how to crowdsource.  There is no way that you can scale communities and community managers that fast. Customers don't care about your organization structure, they just want answers a...
1 comment
Read more

Product Parenthood

It has been a long time since I've been able to sit down and write a lucid blog post.  This one will not be one of them. I've come to realize that my full-time job as a Product Manager, my other full-time job as a husband, and my newest (and most demanding) full-time job as a parent (to a delightful son) consume roughly 100% of my time; leaving precious few moments in the day in which to gather and synthesize my thoughts.  Thus, I've been using Twitter more often and blogging less. " Blogging less?  What?  You only have 3 prior entries! " I used to blog quite a bit under a different moniker.  However, as a parent, I have come to the realization that composing longer, thoughtful essays are a luxury that I generally cannot afford. With that, I've added my Twitter feed to the left, and will make an effort to write "larger-than-micro" blogs here on at least a weekly basis, if not more frequently. And now it's back to full-time job #1, follo...
1 comment
Read more