Use it for
- Transcripts of interviews with buyers from won and lost deals, held 2 to 8 weeks after the decision.
- CRM data for each deal: outcome, deal size, segment, competitor named and the loss reason the sales rep entered.
- The list of vendors in each evaluation, if the buyer named them.
Steps
- Balance the sample
Interview buyers from won and lost deals in similar numbers. Include deals lost to no decision. Without wins, you cannot tell a weakness that loses deals from one that every buyer accepts.
- Code each decision factor with a direction
Code each passage where the buyer explains the choice. Add a direction: strength for your product, weakness for your product, or neutral. The same code can be a strength in one deal and a weakness in another.
- Mark the deciding factor
For each deal, mark one factor as deciding. Ask which factor, if it changed, would have changed the outcome. Buyers often say this when you ask what the winner did best.
- Compare with the CRM reason
Put the deciding factor next to the loss reason that sales entered in the CRM. Record each mismatch. Sales often enters Price, while buyers name a factor that made the price feel too high.
- Compare wins and losses per code
For each code, count weakness mentions in lost deals and in won deals. A weakness that appears in wins too is real but did not decide the deal. Focus on weaknesses that appear mostly in losses.
- Split by competitor and segment
Repeat the comparison for each main competitor and for each deal size band. You often lose to one competitor on Integration fit and to another on Price.
Codebook
Copy the codebook as a table. It pastes into a spreadsheet with one row for each code.
Requirement fit
How well the product met the buyer's list of functional needs.
- Include
- The buyer talks about features, use cases or requirements that the product met or did not meet.
- Exclude
- The need is about connecting to other systems. Use Integration fit for that.
- Example
- “They were the only one that handled multi-currency the way our finance team needed.”
Integration fit
How well the product connected to the buyer's existing systems and data.
- Include
- The buyer names a system, an API, a data source or a single sign-on need and how the vendors compared.
- Exclude
- The question was a security or legal review. Use Security and compliance for that.
- Example
- “The Salesforce connector was native for them. For you it was a third-party tool, and IT said no.”
Price and terms
The cost and the commercial terms of the offer compared with the alternatives.
- Include
- The buyer mentions list price, discount, contract length, payment terms or the pricing unit.
- Exclude
- The buyer talks about the cost or time to set up the product. Use Implementation effort for that.
- Example
- “Your number was fine, but they gave us monthly billing and you wanted a two-year contract.”
Implementation effort
The time, people and risk the buyer expected to need to get the product live.
- Include
- The buyer talks about setup time, migration, training, services or the time to the first result.
- Exclude
- The effort was to evaluate the product before purchase. Use Evaluation experience for that.
- Example
- “Their plan had us live in three weeks. Your team said three months with a consultant.”
Evaluation experience
How easy it was to evaluate the product: demo, trial, proof of concept and answers to questions.
- Include
- The buyer describes the demo, the trial, the proof of concept or how fast they got answers before purchase.
- Exclude
- The passage is about the skill or behavior of the sales rep. Use Sales experience for that.
- Example
- “We could set up a trial ourselves in an afternoon. With you we waited a week for a sandbox.”
Sales experience
The behavior of the vendor's sales team during the deal.
- Include
- The buyer comments on how the rep listened, followed up, pushed, understood the business or handled questions.
- Exclude
- The buyer comments on the trial or demo environment. Use Evaluation experience for that.
- Example
- “Your rep sent us a slide deck three times. Their rep asked about our process and built the demo around it.”
Security and compliance
Whether the vendor passed the buyer's security, legal, privacy and procurement reviews.
- Include
- The buyer mentions questionnaires, certifications, data residency, legal terms or a procurement review.
- Exclude
- The buyer doubts the vendor's future or size. Use Vendor credibility for that.
- Example
- “Legal needed data hosted in the EU. That ended it before we even compared features.”
Vendor credibility
The buyer's trust in the vendor as a company: stability, references, reputation and roadmap.
- Include
- The buyer mentions company size, funding, customer references, analyst reports, reviews or confidence in the roadmap.
- Exclude
- The trust is about a formal security or legal review. Use Security and compliance for that.
- Example
- “Nobody gets fired for picking the market leader. Our CFO wanted the safe name.”
Internal champion
The role of a person inside the buyer's company who pushed for or against a vendor.
- Include
- The buyer describes a person who sold the vendor internally, blocked it or changed role during the deal.
- Exclude
- The person is from the vendor's side. Use Sales experience for that.
- Example
- “Our CTO had used them at his last company and he made the case to the board.”
Status quo
The buyer chose to keep the current tool or process, or to make no decision.
- Include
- The deal ended with no purchase, a delay, a renewal with the current vendor or an internal build.
- Exclude
- The buyer chose a new competitor. Code the factors that decided for that competitor.
- Example
- “In the end the switch felt like too much work this year, so we renewed our old contract.”
Existing relationship
A link between the buyer and a vendor that existed before this evaluation.
- Include
- The buyer already used another product of the vendor, had a bundled license or knew the vendor.
- Exclude
- The link is a person inside the buyer's company who pushed a vendor. Use Internal champion for that.
- Example
- “We already pay Microsoft for everything, so adding their tool cost us almost nothing.”
Report outline
- The sample: deals won, lost and lost to no decision, by segment and competitor.
- Deciding factors in losses and in wins, with the direction and 2 quotes each.
- Differences between buyer reasons and CRM loss reasons.
- Results per main competitor: where each one beats you and where you beat them.
- What wins deals today, so sales and product keep it.
- Actions for product, sales and marketing, each linked to a code.
Mistakes to avoid
- Do not interview only lost deals. Without wins you cannot tell which weaknesses decide deals and which ones every buyer accepts.
- Do not let the sales rep who owned the deal run the interview. Buyers will not criticize the rep to their face.
- Do not code Price as the deciding factor without a follow-up. Ask what the winner offered that made its price feel right.
- Do not wait more than 8 weeks after the decision. The buying team forgets which vendor said what.
Guides that use it