Kea Insight / Analyst Relations
Your Competitor Is Winning. Do You Actually Know Why?
A lost deal is an outcome. The explanation in your CRM is a starting point. Competitive intelligence earns its value when it helps your team understand the buyer’s choice—and change something that matters.
1. First establish what ‘winning’ actually means
Your competitor announces another customer. Sales says they are discounting. Product says their technology is weaker. Leadership concludes that the market has not understood your advantage. Every explanation may contain some truth. None, on its own, explains the buying decision.
Before commissioning more intelligence, define the result you are trying to understand. Is the competitor entering more shortlists, winning a larger share of head-to-head decisions, expanding inside existing accounts or gaining attention in a segment you want to enter? Those are different problems. A company can be highly visible and commercially weak; it can also win quietly through an established channel you barely monitor.
Do not infer market share from press releases or a handful of painful losses. State what you can observe: “We lost four qualified opportunities in this segment to this provider during the quarter.” Then state what you cannot yet establish: whether the pattern extends beyond those opportunities, whether the accounts were comparable and whether the reported reasons came from buyers or your own account teams.
The purpose of competitive intelligence is to improve a decision. Start with one: which accounts to pursue, which claim to change, which capability to prioritise or which commercial obstacle to remove. A broad request to “tell us everything about the competitor” usually produces a large document and an unclear next step.
2. Map the alternatives in the buyer’s world
Your competitor slide is a statement about how you see the market. The buyer’s alternatives are revealed by what they can actually fund, deploy and defend internally. That list may include a specialist vendor, a broader platform, a managed service, internal development or an extension of the incumbent contract. It also includes postponing the decision.
A specialist may outperform a platform on a specific capability and still lose because the buyer values one procurement process, existing skills and fewer integrations. A technically inferior workaround may survive because changing it consumes time the team does not have. Neither outcome proves that the buyer failed to understand the product.
Record the starting point as well as the final shortlist. What was the organisation doing before the project? Which event made change worth considering? Who proposed the alternatives? What would happen if no purchase were made? If the project was cancelled, record that separately from losing to a named vendor.
Be equally careful with internal development. A team may initially frame the decision as build versus buy, then choose a platform that helps it build. Your neat categories can obscure the actual choice. Map the work, the budget and the constraints before drawing the competitive boundary.
3. Reconstruct the decision, not just the final objection
The last objection voiced is not necessarily the reason you lost. Price may be the easiest explanation to give a vendor after the decision. A missing feature may have removed you early, leaving the final negotiation to providers that already passed the real test.
Trace the sequence. How did the buyer discover the options? What determined initial eligibility? Which requirements were mandatory? What changed after the demonstration, technical assessment, reference call or procurement review? When did confidence in your offer weaken? Separate reasons for exclusion from reasons for preferring the eventual winner.
A useful buyer conversation might ask:
- What made this project worth doing now?
- Which alternatives did you seriously consider, including keeping the current approach?
- What did a provider have to demonstrate to remain in consideration?
- Where did the options differ in ways that mattered to your team?
- Which concern was still unresolved when you made the decision?
- What would have had to be different for you to choose another option?
Invite the explanation before suggesting a cause. Asking “Was our price the problem?” encourages a narrower answer than asking how cost entered the decision. Speak to more than one role where practical: the sponsor, practitioner and procurement lead may describe different parts of the same choice. Preserve those differences rather than forcing a single tidy story.
4. Give each source a job—and a limit
Competitive intelligence becomes more useful when the team knows what each source can establish. Public product documentation can substantiate a capability claim within its stated scope. It does not prove how well that capability works in a specific production environment. A customer interview can explain that customer’s experience. It does not establish how every buyer behaves.
Use buyer interviews to understand decisions. Capture the role, segment, circumstances and timing. Compare wins, losses and no-decisions rather than asking only disappointed account teams to explain the quarter.
Use current documentation and authorised product access to check capabilities. Record the edition, release, deployment model and any conditions. Distinguish announced, preview, generally available and demonstrated in the relevant use case.
Use analyst research to understand market framing and assessment criteria. Check publication date, scope and methodology. A research evaluation can help structure questions; it cannot substitute for the buyer’s requirements.
Use reviews and delivery experience to investigate operational friction. Look for recurring themes, then test their relevance. A review describes a particular experience and may concern an older release or a different customer type.
Use commercial records to establish your own pattern. Check opportunity stage, qualification, discount, partner involvement and outcome. CRM completeness is itself a research question, not an assumption.
Keep observation and interpretation separate. “The buyer asked for a migration plan twice” is an observation. “Migration confidence influenced the decision” is a hypothesis worth checking. “All enterprise buyers favour this competitor because of migration” goes far beyond the evidence.
5. Ask analysts questions they can usefully answer
The most productive analyst question is rarely “Why are they beating us?” It combines several markets, decisions and possible causes. Give the analyst a specific segment, use case and uncertainty. Ask about the criteria buyers apply, the trade-offs they accept and the evidence they need.
For example: “For regulated mid-market organisations replacing an incumbent, which implementation risks tend to shape vendor selection, and what should a provider be able to demonstrate?” That creates a useful discussion without asking the analyst to disclose a competitor’s private information or identify confidential buyer conversations.
Ask where the view applies and where it does not. Is it based on recent buyer discussions, published research, technical assessment or broader judgement? Which other explanation should you investigate? What would change the analyst’s assessment? Do not turn a qualified answer into a universal statement in the board pack.
The format matters. Gartner’s published briefing guidance treats vendor briefings as a way for vendors to inform analysts, with feedback not their purpose. If you need advice, check the inquiry or advisory access your agreement actually provides. Other firms have their own arrangements. A quiet briefing does not establish that your competitive claims were endorsed.
Bring the person who can use the answer, subject to the agreement’s access rules. AR can frame the question and preserve its context; a product or commercial owner should hear consequential reasoning directly when possible.
6. Count decisions, not repeated stories
Imagine ten salespeople mention the same competitor weakness. That sounds like a pattern until you discover they all copied it from one battlecard. Or three analysts discuss an emerging requirement after reading the same public announcement. Multiple mentions may still have one underlying source.
Track the origin. Count separate buying decisions separately from the number of people discussing them. Four interviews from one account provide richer understanding of that account; they are not four independent wins or losses. Repeated references to one report increase its visibility, not the number of independent observations.
Use denominators that answer the stated question. A head-to-head win rate can be calculated as your wins divided by your wins plus losses against that competitor among a clearly defined set of decided opportunities. Keep no-decisions and unknown outcomes visible outside that denominator. Also report how many opportunities lacked a reliable competitor record.
In an illustrative cohort, six wins and four losses give a 60% observed head-to-head win rate. That says nothing by itself about the whole market, accounts you never reached or buyers that excluded you before entering CRM. With such a small, selected set, the narrative behind the decisions is at least as important as the percentage.
Segment before concluding. Deal size, geography, use case, incumbent position and partner involvement can change the comparison. An overall improvement can result from selling into easier accounts rather than becoming more competitive within any segment. Avoid declaring progress until you have examined that mix.
7. Decide how much evidence the decision requires
There is no universal number of analyst calls or lost deals that turns an observation into a strategy. The required confidence depends on the consequence, reversibility and cost of being wrong. Correcting a demonstrably stale sentence in a battlecard is a different decision from committing a year of engineering capacity.
Use three practical responses. Act when the fact is well established and the remedy is proportionate, such as withdrawing an unsupported comparison. Investigate when a plausible explanation could change a material decision, such as whether implementation risk is suppressing wins. Monitor when the signal is weak, the relevance uncertain and no immediate decision depends on it.
Monitoring still needs a trigger. Specify what would cause a review: a repeated objection in the target segment, a verified competitor release or a change in an important procurement requirement. Otherwise “monitor” becomes another word for forgetting.
Write confidence as an explanation. “Moderate confidence: three separate buyers raised the issue, but we have not interviewed wins and the accounts all used the same implementation partner” is more useful than a green dot. Keep the counter-evidence beside the conclusion. Someone should be able to challenge the recommendation without reconstructing the entire investigation.
8. Look beyond the feature comparison
A feature matrix can help verify functionality. It becomes misleading when the team treats it as a complete explanation of buyer value. The competitor may be winning because the overall purchase feels easier to complete and safer to operate.
Implementation: who carries migration risk, supplies the integration work and supports the first production deployment? An attractive product can look expensive when the buyer must assemble the delivery capability.
Commercial fit: does pricing match the buyer’s budget structure and expected usage? A lower unit price can coexist with a higher or less predictable total cost. Compare equivalent scope, services, commitments and operating assumptions.
Trust: can the buyer inspect evidence from a comparable organisation? A recognisable logo does not establish that the reference used the relevant capability at the required scale.
Distribution: does an existing partner, framework or platform relationship make one provider easier to buy? Sometimes the competitor reaches the decision before your team knows a project exists.
Organisational effort: how much change must the customer absorb? Training, workflow redesign, ownership disputes and approvals can outweigh a technical advantage.
These explanations point to different interventions. A migration objection might require a delivery plan. A budget mismatch might require different packaging. A missing capability might require product work. Rewriting the pitch should follow the diagnosis, not replace it.
9. A worked example: the feature gap that was not the whole problem
Consider a fictional enterprise software vendor. Its leadership believes a competitor is winning because of a reporting feature. Over one quarter, the company records twelve losses involving that competitor. This is an illustrative case, not a Kea client result.
A review finds that three opportunities had never met the company’s qualification criteria and two had actually ended without a purchase. That leaves seven recorded competitive decisions worth investigating. Buyers from four agree to interviews. Their accounts suggest that the reporting feature mattered, but three also describe uncertainty about migration effort and who would support deployment.
The team checks current documentation and finds that its own reporting claim was out of date: the relevant capability is now available through an integration, with limitations. Two reference customers confirm that the integration works for their use cases. Neither establishes that it will satisfy every prospect.
An advisory conversation helps the team formulate better questions about implementation accountability. It does not prove why the seven buyers decided as they did. The team now has a working explanation involving both proof and delivery confidence, plus substantial gaps because only four buyers participated.
The response is deliberately bounded. Product verifies the supported reporting scope. Marketing corrects the comparison. Services produces a migration responsibility plan. Sales tests both in the next comparable qualified opportunities and records what objections remain. Leadership postpones a broad reporting rebuild until the evidence distinguishes missing functionality from missing confidence.
A later improvement in outcomes would be encouraging, but not automatic proof of causation. Account quality, competitive offers and sales execution may also change. The test should reveal whether the intervention addresses the observed concern, alongside the commercial result.
10. Replace ammunition with useful sales guidance
A good battlecard helps an account team understand a decision. It should not teach them to repeat the least flattering interpretation of a competitor. Unsupported claims are especially costly when a buyer already knows the alternative well.
Start with the situations where your offer fits and where it may not. Give sales a small number of discovery questions, current evidence for specific differences, conditions that affect the comparison and a route to help when the answer is uncertain. Put the review date and owner somewhere visible.
Replace “They cannot support enterprise scale” with a question the team can substantiate: “What throughput, availability and operating model does this buyer require, and what evidence can each provider show?” Replace “They are expensive” with a comparison of relevant total costs under explicit assumptions.
Include the strongest reason a sensible buyer might choose the alternative. This forces the team to understand the trade-off and prepares sales to respond with respect. Dismissing the competitor can make the buyer feel that you are dismissing their judgement.
When the evidence changes, withdraw the old version from the systems people actually use. Updating a central document will not help if the field continues presenting a downloaded slide from last year. Give the change a practical explanation and make uncertain questions easy to escalate.
11. Keep intelligence credible at the source
Use information you are entitled to obtain and use. Public materials, appropriately licensed research, authorised product access and candid buyer conversations can support a strong programme. Misrepresenting who you are, encouraging disclosure of confidential material or treating a former competitor employee as a source of proprietary documents undermines that credibility.
Competitive intelligence only remains useful when the methods behind it are credible. Apply the same discipline to third parties collecting information for you. Make the scope and boundaries explicit rather than assuming a supplier’s methods are acceptable.
Analysts should not be asked to disclose a competitor’s confidential roadmap, pricing or named buyer advice. Ask about relevant market requirements and publicly supportable comparisons. If restricted information arrives unexpectedly, stop its circulation and involve the appropriate internal owner before using it.
AI can help organise permitted material, identify contradictory claims and draft questions. It cannot establish that an unsupported comparison is true. Preserve original sources, dates and scope, and check the actual material behind any generated summary. A plausible answer without provenance belongs in the question list, not the sales deck.
12. Make competitive learning somebody’s responsibility
AR should not become the department that knows the problem while everyone else owns the right to ignore it. Agree how evidence moves into a decision. Product marketing can maintain the comparison and sales guidance; sales operations can improve opportunity records; product can assess capability gaps; services can address implementation concerns. Leadership resolves trade-offs that cross those boundaries.
Give each material finding a named decision owner, a next action and a review date. “Sales should be aware” is not an action. “The sales enablement lead will replace the unsupported scale claim before the next training session” can be checked.
Keep a short decision record: the question, the relevant segment, the evidence and its limitations, competing explanations, the selected response and what would cause the decision to change. Link to the underlying notes so that later reviewers can distinguish learning from repetition.
A monthly review can work for an active competitive issue; urgent factual corrections should not wait for it. Choose the cadence around the decision, not a reporting ritual. Escalate when a claim is wrong, a significant customer commitment is exposed or the evidence materially challenges a funded plan.
13. A practical first month
Choose one competitor, one segment and one commercial decision. In the first week, define the comparison and audit what you already know. Check the most frequently used competitive claims, identify missing opportunity data and decide which buyer conversations would reduce uncertainty.
In the second week, gather a balanced set of accessible evidence. Include wins and no-decisions as well as losses. Where participation is uneven, record it. Review current product information and relevant research, and prepare a focused advisory question if you have suitable access.
In the third week, compare explanations with the people who could act on them. Resist the urge to solve every weakness at once. Select a limited intervention that addresses a supported concern and state what you expect to observe if the explanation is useful.
In the fourth week, put the change into use and establish the review. Thirty days may be enough to improve a claim, a discovery question or a delivery explanation. It is not necessarily enough to observe enterprise buying outcomes. Judge early progress by evidence quality and implementation, then revisit commercial results over an appropriate period.
The output should be a better decision and a maintained body of evidence. If the only result is a more elaborate competitor presentation, the programme has not yet done its job.
14. Where Kea adds value
Kea helps connect analyst understanding with the questions commercial and product teams need to answer. That includes selecting relevant expertise, preparing focused conversations, examining the limits of what was heard and translating supported findings into briefing evidence, positioning and practical follow-through.
For an established AR team, this is work we can support alongside the existing programme. The company retains responsibility for its product, pricing and investment decisions. Our role is to help it reach those decisions with clearer market context and fewer unsupported assumptions.
This also requires leadership to tolerate an inconvenient conclusion. Sometimes the competitor has a real advantage. Sometimes you are pursuing an unsuitable account. Sometimes you have the capability but have failed to demonstrate it. Each deserves a different response.
The question is not whether you can produce a persuasive explanation for losing. It is whether you can establish enough about the buyer’s choice to compete more intelligently next time.
For the wider context, read Your analyst subscription is not a strategy. It is a stepping stone. and The analyst disagrees with you. That does not make them wrong.
Put this into practice
Understand why buyers choose the alternative
Kea helps your team test competitive assumptions, ask sharper analyst questions and turn market evidence into practical decisions for sales and product.
Explore AR SupportNot sure where to start? Take the eight-question AR Readiness Check.