Resources > Articles

Win/Loss Analysis Checklist for Product Managers

Post Author
marketing analytics, analysis

We have all seen it written that product managers should get out of the office and visit customers, or, at the very least, telephone one customer a week. This is important not only for customer retention reasons, but also for competitive analysis and product performance reasons as well. With the state of the economy, and everything product managers have on their plates these days, that is a task easier said than done. What if product managers started participating in the back-end of a sales win or loss? If a win, the product manager would be helping to develop the new relationship, resulting in retention and obtaining valuable customer feedback or, in the event of a loss, finding out the reasons for the loss, be it a product issue, sales issue or support issue, possibly resulting in the prospect using the company as a backup vendor or placing the company on the ‘short list’ for future proposals.

Regardless, the product manager becomes the objective third party who helps the company and customers/prospects have better success in converting sales. Product Management can easily sell the Sales team on performing this task by stating the benefits of doing so:

  • Product Management can perform the function, thus saving the sales team valuable time.
  • Product Management acts as an objective third party, which will result in a prospect or customer’s ability to be more open about the sales win or loss.
  • Product Management obtains feedback on how to make products more robust, thus resulting in more sales down the road.

So, now that you are conducting win/loss analysis, what is the next step? Use the following handy checklist and you will be on your way to performing effective win/loss analyses.

Before the Win/Loss Analysis Interview

  • Sit down with the sales team involved in the win or loss. Be sure to include the highest-ranking Salesperson in the discussion. Get the Sales team’s input as to the background such as how the company got involved in the proposal, the type of relationship they had/have with the customer/prospect, sales processes involved, products or solutions used to close the sale, the result, and whether they anticipated this result.
  • Schedule the interview with the customer/prospect. Let them know in advance the topics you plan to discuss.

During the Win/Loss Analysis Interview

  • Introduce yourself and thank the prospect/customer for their time.
  • Explain upfront that the purpose of the interview is to learn as much as possible about the customer or prospect’s perceptions and experience during the recent sales process so your organization can continually improve.
  • Discuss confidentiality. State that you want to communicate feedback throughout your organization, but if the customer/prospect feels there are certain aspects that are too sensitive, they should be identified during the conversation.

Ascertain the Following

  • Confirm the opportunity, product/solutions, and get customer/prospect to expound on it. What did/didn’t we solve and what are customer/prospect’s expectations in our ability to solve that pain?
  • Find out the other firms that were competing for the business. Why was your firm included in the mix? How and why did the customer/prospect make it a competitive process?
  • Overall, why did/didn’t your company win the business?
  • Explain the decision-making process. Who was involved in the decision? What were the key selection criteria?
  • What was the customer/prospect’s perception of the quality of the Sales team’s management of the relationship? Did the customer/prospect meet other personnel from your organization? What was the customer/prospect’s perception of them?
  • What were the customer/prospect’s thoughts about your proposal and presentation?
  • Was the customer/prospect comfortable with your capabilities? Which capabilities were most important to them?
  • What were the customer/prospect’s thoughts about your pricing? Was the customer/prospect able to determine true value from your pricing?
  • How did you stack up against the competition? What did the customer/prospect view as your strengths and weaknesses? What did the customer/prospect view as your competitors? strengths and weaknesses?
  • Did the customer/prospect call your references? If so, were they helpful?
  • What was the customer/prospect’s perception of your organization before entering the buying cycle? Did the perception change? If so, how did it change?
  • What advice would the customer/prospect give you for working with them in the future?
  • Would the customer/prospect feel comfortable in recommending your solutions to others?
  • If a win, would customer feel comfortable in participating in a case study, testimonial, joint press release, or beta test (for a future solution)?
  • Does customer/prospect have any additional comments or suggestions?

Post- Win/Loss Analysis Interview

  • Send a thank you note to the customer/prospect.
  • Summarize in writing the notes from the interview and distribute them to appropriate internal personnel.
  • Conduct the debriefing meeting and list any action items that came out of the meeting.

Win/Loss Analysis should be conducted regardless of whether business was won or lost. Consistently implementing the process of win/loss analysis will make your solutions and your company more valuable, and build more credibility in the eyes of your customers and prospects.

Related Links

Author

Author:

Other Resources in this Series

Most Recent

Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.
Article

Use Scenarios are Stories That Provide Context

The problem with today’s user stories is that they aren’t interesting. And they aren’t stories. The solution is use scenarios. It’s a narrative. It explains the problem in the form of a real-life story.
Article

Benefits of Bundle Pricing

Bundle pricing is simply a strategy where services or products are packaged together for one (often reduced) price rather than priced separately. This article covers some benefits of bundle pricing followed by a system for getting started.
Article

A Quick Guide to Value-Based Pricing

Value-based pricing begins with knowing the customer’s willingness to pay based on the perceived value of your product. You can charge less than a customer’s willingness to pay, and they feel like they’ve received an
Article

What Is Captive Product Pricing 

If you’re looking for a simple answer, it’s this: captive product pricing is when consumers make a one-time purchase (usually a lower-priced core product) but are required to purchase accessories for the main product to

OTHER ArticleS

Article

[Comprehensive Guide] Product Owner vs Product Manager

Learn how to separate the roles of product owner and product manager on Agile teams and uncover some common challenges with confusing these roles. Including a short primer on the Agile revolution.
Article

Use Scenarios are Stories That Provide Context

The problem with today’s user stories is that they aren’t interesting. And they aren’t stories. The solution is use scenarios. It’s a narrative. It explains the problem in the form of a real-life story.

Sign up to stay up to date on the latest industry best practices.

Sign up to received invites to upcoming webinars, updates on our recent podcast episodes and the latest on industry best practices.

Subscribe

Subscribe

Training on Your Schedule

Fill out the form today and our sales team will help you schedule your private Pragmatic training today.

First Name*
Last Name*
Email Address*
Phone
Company
Job Title
Location
How can we help you?
Preferred method of contact
Privacy Policy*
Map Your Message to Its Audience with the Communication Compass
Map Your Message to Its Audience with the Communication Compass
Ensure your message hits the mark. This eBook helps you visually map communication styles so you can tailor your design story to a stakeholder or business partner.

Download Ebook

Demystifying Data Projects: A Guide for Business Leaders
While data science is a competitive advantage, data isn’t magic. Learn how to make magic happen by partnering more effectively with data professionals. This eBook delves into types of data projects, sample questions, tools and methods, key points and cautions—so stakeholders like you can initiate data projects with real business impact.

Download Ebook

Define Ebook Thumbnail
What’s the difference between a successful data analysis project and one that falls flat? 

Before you begin working with the data, you need to understand what you’re solving for. Gathering context and aligning around goals with your stakeholders from the outset will help you avoid disconnects and deliver actionable insights. Discover the most vital questions to ask before embarking on a data analysis project in our in-depth guide, “Define: Laying the Foundation for Successful Data Analysis.”

Download Ebook

Download Now