A lost deal is not merely an adviser's failed result. It provides data about price, range, lead time, qualification quality, response speed and competitive position. The data becomes useful only when reasons are recorded consistently and supported by evidence.
Free-text comments such as “too expensive”, “not relevant” or “disappeared” do not create a comparable report. Use a short controlled reason list, an explanatory note and the deal context.
Separate the outcome from the reason
The outcome says how the deal ended: won, lost, removed as a duplicate or disqualified. The reason explains why.
| Level | Example | Purpose |
|---|---|---|
| Outcome | Deal lost | Complete the pipeline correctly |
| Primary reason | Product unavailable by required date | Create comparable statistics |
| Detail | Customer chose next-day dispatch elsewhere | Understand the specific situation |
| Evidence source | Customer reply or recorded system event | Separate knowledge from assumption |
Build a controlled reason list
Reasons should be specific enough to support a decision without becoming hundreds of variants. Begin with 8–12 primary reasons and use a note for detail.
| Group | Primary reason | Possible management response |
|---|---|---|
| Need | Request does not fit the offer | Improve positioning and qualification |
| Price | Customer did not accept the price | Check segment, value, margin and competitors |
| Product | Required item or configuration unavailable | Review range and substitutes |
| Timing | Delivery or completion would be too late | Change stock, planning or promised lead time |
| Terms | Payment, delivery or warranty unsuitable | Review policy for the target segment |
| Competitor | Another confirmed offer selected | Record the specific difference |
| Sales process | Late response or missed action | Correct service targets and control |
| Customer | Project postponed or cancelled | Set a genuine return date without false activity |
Do not create “10% too expensive”, “20% too expensive” and “far too expensive” as separate reasons. Store the difference in a note or numerical field.
Fact, customer statement and assumption are different
- Confirmed fact: stock cannot arrive by the required date; a rejection was received; the order was placed with a competitor.
- Customer statement: “too expensive”, “we will return later”, “management did not approve”. Useful, but potentially incomplete.
- Sales assumption: “probably changed their mind” when the customer stops replying. It must not be stored as proved fact.
Add an evidence level: confirmed, stated by customer, or assumed after required contact attempts. This prevents false certainty.
Use one primary reason and optional contributing factors
Price, lead time and a slow response may all affect one deal. For consistent statistics, choose the primary reason — the factor whose absence would most likely have changed the outcome. Keep the others as contributing factors.
If five equal reasons are allowed, report totals exceed the number of deals and no clear priority emerges.
“Customer disappeared” is not a final explanation
No reply is a communication state, not a proven rejection reason. Define minimum contact attempts across suitable channels and intervals, followed by a final message. The deal can then close as “contact lost after required attempts”, while retaining the stage and last meaningful event.
Analyse context with the reason
| Dimension | Question answered |
|---|---|
| Loss stage | Where the problem appears in the process |
| Product or direction | Which part of the offer fails most often |
| Channel and campaign | Whether the source brings relevant demand |
| Customer segment | For whom the product, price or terms do not fit |
| Sales adviser | Whether qualification or execution differs systematically |
| First-response time | Whether loss relates to response speed |
| Amount and margin | Where the business impact is greatest |
| Competitor | Which specific advantage the market chooses |
Count value as well as deals
Reason share = Lost deals with the reason / All lost deals × 100%.
Also measure potential revenue and contribution margin. Ten small price-related losses may matter less than two major deals lost because a critical configuration was unavailable.
Potential value is not guaranteed loss. Consider the deal stage and the realism of the opportunity.
Example management conclusion
During a month, a company loses 120 deals. Required stock was unavailable in 38, price was rejected in 27, 18 followed an overdue response, 15 did not fit the target profile and the remainder involved terms or cancelled projects.
The report must not end with a chart. Create a check for every material group:
- stock losses — affected items, demand, missed margin and substitutes;
- price losses — segment, competitor, term difference and minimum margin;
- response losses — channel, workload, response time and service breach;
- poor-fit enquiries — advertising source and offer wording.
Do not turn reasons into punishment
If the list is used only against staff, advisers select safe answers such as “customer changed their mind”. The purpose is to identify a changeable cause, not assign blame.
Process failures must still remain visible. An overdue action should be recorded automatically from its date rather than an adviser's self-assessment.
Common mistakes
- One reason: “did not buy”. The report supports no decision.
- The reason is entered a month later. Detail has been lost.
- Every factor is equal. No priority can be chosen.
- An assumption is stored as fact. Price or product changes are made without evidence.
- Lost deals are deleted. Conversion rises artificially.
- Only deal count is analysed. Value, margin and stage are ignored.
- The report creates no action. Reasons accumulate while the process stays unchanged.
Loss analysis in Business Reactor
Business Reactor connects a loss reason with the actual stage, product, customer, proposal, activities and deadlines. Recorded events such as an overdue action, unavailable stock or a price change reduce dependence on an adviser's memory.
Managers can move from a reason to the underlying deals and determine which change addresses the largest verified loss.
Conclusion
Reliable loss analysis separates outcome, primary reason, contributing factors and evidence level. Analyse the reason with stage, product, channel, segment, response speed and potential margin.
The goal is not to explain the past with an attractive chart, but to identify a specific change in product, inventory, terms or the sales process. Business Reactor Core.
