Closed lost reasons list: 15 common ones and what to do about each

A good closed lost reasons list has about 15 options, each specific enough to tell you what would reopen the deal. The 15 most common closed lost reasons are: no budget, price too high, lost to a competitor, no decision, timing, champion left, lost the executive sponsor, missing feature, building in house, stayed with current vendor, security or procurement, technical fit, went dark, priorities changed, and not a fit. Below is what each one really means, what to log, the trigger that reopens it, and picklist values you can paste into HubSpot or Salesforce today.

Most CRMs are full of loss reasons like “other”, “price”, and “lost”. Those labels end the conversation. A reason like “Lost to a competitor, renews in March” starts the next one. The difference is a few minutes of setup and one required field.

The closed lost reasons list: all 15 at a glance

Reason	What it usually means	What to log	What reopens it
1. No budget	They could not fund it this year, or the money went elsewhere.	Ask when the fiscal year ends and whether it was cut or never allocated.	New fiscal year, headcount growth, a new leader with a mandate.
2. Price too high	The value you showed did not beat the price. Often a value problem, not a price problem.	Log the gap: what they would pay versus what you quoted.	Growth that raises the cost of the problem; a new leader; packaging you can now offer.
3. Lost to a competitor	They bought someone else.	Log which competitor, the contract term and the renewal month.	90 to 120 days before renewal; a new leader; the competitor’s champion leaving.
4. No decision	Nobody chose anyone. The status quo won.	Log what they were afraid of getting wrong.	A new leader, hiring for the initiative, or a public statement of the problem.
5. Timing, not now	They want it, later. The best reopen candidates you have.	Log the event they are waiting on and its expected date.	The named event happening (migration live, round closed, quarter ended).
6. Champion left	Your internal advocate changed jobs mid deal.	Log where they went and who replaced them.	Champion’s new company is a warm lead; the successor is a fresh start.
7. Lost the executive sponsor	The leader who backed it left, or a reorg moved budget.	Log who the new decision maker is, if known.	A new VP or C level leader settling in.
8. Missing feature	A specific capability was a must have and you lacked it.	Log the exact feature, not “product gap”.	You ship it. Keep a list per feature so product can see the revenue attached.
9. Building in house	They decided to build it themselves.	Log the team that would build it and their estimate.	Hiring stalls, the build slips, or the engineering leader changes.
10. Stayed with current vendor	They renewed what they have. Inertia plus switching cost.	Log the incumbent and the renewal month.	Renewal window, new leader, complaints about the incumbent in public posts.
11. Security, legal or procurement	A review blocked it: data residency, a missing certificate, terms.	Log the exact requirement that failed.	You meet the requirement; their policy changes.
12. Technical or integration fit	It did not work with their stack.	Log the system and the gap.	They migrate to a system you support; you ship the integration.
13. Went dark	They stopped answering. No position taken.	Log the last real conversation and who went quiet.	A quiet contact opening your email again; a new leader.
14. Priorities changed (reorg, merger, layoffs)	The company itself changed under the deal.	Log what changed and who survived it.	Headcount recovering, a new leader, or the merged company settling.
15. Not a fit (disqualified)	They were never a real opportunity.	Log why, so marketing can stop sourcing them.	None. Do not reopen; fix targeting instead.

Reason 4 deserves a note. Challenger Inc.’s research found that “40-60% of lost deals” can be attributed to indecision, and that medium to high indecision shows up in 87% of deals (Challenger Inc.). If your CRM has no “No decision” value, those losses get filed under price or timing, and your reporting tells you the wrong story about why you lose.

What to do about each closed lost reason

The reason is only useful if it changes what you do next. Here is the move for each, grouped by what kind of loss it is.

Money: no budget, price too high

Ask the budget question before you close the deal as lost: “Was this cut, or never in the plan?” A cut budget can come back with a new year or a new leader. A never planned budget needs a business case, which means you reopen with a number, not a check in. For price losses, log the gap. If it was 10%, packaging can fix it. If it was 3x, they were not your buyer.

Competition and status quo: lost to a competitor, stayed with current vendor, building in house

Always log the contract term. Most competitor losses are reopenable exactly once per contract, roughly 90 to 120 days before renewal, when switching is cheapest. Build in house losses reopen when the build slips: watch for the engineering roles they planned to hire staying open, or the engineering leader changing.

People: champion left, lost the executive sponsor

These are the most underrated losses, because each one is two leads. Your champion’s new company is a warm prospect who already believes in you, and the successor at the old account is a fresh start without the old objections. Our guide to champion tracking covers how to follow both.

Indecision and timing: no decision, timing not now, went dark

Separate these three carefully. “Timing” means they told you what they are waiting for. “No decision” means they could not choose. “Went dark” means they never took a position. Only timing comes with a date. The other two need a change at the account before you write, such as a new leader or new hiring. For digging real deferrals out of old threads, see no decision deals.

Product and process: missing feature, technical fit, security or procurement

Log the exact gap, not the category. “Missing feature: SSO with Okta” is something product can count and you can act on the day it ships. “Product gap” is neither. Keep a saved report of losses per missing feature; it is the cleanest revenue case your product team will ever see.

Company change and bad fit: priorities changed, not a fit

Reorgs and layoffs often look final and rarely are. Note who survived and check again when headcount recovers. Bad fit is the only reason with no reopen trigger: send those back to whoever sourced them, and fix the targeting.

Ready to paste: HubSpot closed lost reason values

HubSpot ships a default deal property called Closed lost reason, described as “the reason the deal was lost” (HubSpot default deal properties). Replace free text with a dropdown using the values below, then require it on the Closed Lost stage.

Label                              | Internal value
No budget                          | no_budget
Price too high                     | price_too_high
Lost to a competitor               | lost_to_competitor
No decision                        | no_decision
Timing, not now                    | timing_not_now
Champion left                      | champion_left
Lost the executive sponsor         | lost_exec_sponsor
Missing feature                    | missing_feature
Building in house                  | building_in_house
Stayed with current vendor         | stayed_with_vendor
Security, legal or procurement     | security_legal_procurement
Technical or integration fit       | technical_fit
Went dark                          | went_dark
Priorities changed                 | priorities_changed
Not a fit (disqualified)           | not_a_fit

1. In HubSpot, go to Settings, then Properties, and open the Deal properties. Either edit Closed lost reason or create a new dropdown select property (for example Loss reason) with the values above.
2. In Settings, under Data Management, open Objects, then Deals, then the Pipelines tab, and click your pipeline. In the Closed Lost row, hover over Conditional logic rules, click Add rule, and add your loss reason property as a dependent property.
3. Tick Required. HubSpot’s help explains that when a property is required, users cannot create or update the record until they set a value for it (HubSpot pipeline settings).
4. Add the companion fields below, and show Competitor and Contract renewal only for the competitor and incumbent reasons.

Ready to paste: Salesforce loss reason picklist

Salesforce has no single standard loss reason field on Opportunity in most setups, so create a custom picklist and make it depend on Stage. Salesforce’s own help uses this exact example: a Reason picklist whose valid values depend on the Stage picklist, shown when Stage is Closed Lost (Salesforce dependent picklists).

Field label: Loss Reason      API name: Loss_Reason__c      Type: Picklist
Controlling field: Stage (StageName). Values available only when Stage = Closed Lost.

No budget
Price too high
Lost to a competitor
No decision
Timing, not now
Champion left
Lost the executive sponsor
Missing feature
Building in house
Stayed with current vendor
Security, legal or procurement
Technical or integration fit
Went dark
Priorities changed
Not a fit (disqualified)

Then add a validation rule so nobody can close a deal as lost without a reason:

Validation rule: Loss_Reason_Required
Error condition formula:
AND(
  ISPICKVAL(StageName, "Closed Lost"),
  ISBLANK(TEXT(Loss_Reason__c))
)
Error message: Pick a loss reason before closing this deal as lost.

Fields that make the reason useful later

The dropdown is for reporting. These companion fields are for the person who reopens the deal in six months, who may not be you.

Companion fields (both CRMs)
Loss detail        Long text   One or two sentences in the buyer's words
Reopen trigger     Dropdown    New budget year / Renewal window / New leader /
                               Champion move / Hiring / Feature shipped /
                               Named event / None
Revisit date       Date        Only when the buyer gave you one
Competitor         Dropdown    Only when Loss Reason = Lost to a competitor
Contract renewal   Date        Only when Loss Reason = Lost to a competitor
                               or Stayed with current vendor

Keep Loss detail to the buyer’s own words. “Revisit after the ERP migration in Q2” is worth ten times “timing”.

How to run a monthly loss review

1. Pull last month’s closed lost deals with reason, detail and amount.
2. Fix any that landed in the wrong bucket, especially price versus no decision.
3. Group by reason and look at the top three by amount, not by count.
4. For each reopenable reason, confirm the trigger and revisit date are filled in.
5. Send the missing feature list to product with the amounts attached.
6. Move every reopenable deal’s account and contacts onto your watched lost deals list.

Watch your lost deals for the trigger in Salesgear

Salesgear does not sync closed lost deals from your CRM. The practical version is a list: export your reopenable losses from the review above, put the accounts on an account list and the contacts on a contact list, and point signals at those lists. Job changes catch champions and blockers moving (1 credit per contact per check). New leader and headcount growth watch the accounts (1 credit per company per check). Hiring intel shows what each lost account is hiring for and who owns it (2 credits per company per check). Came back fires, free, when a contact who has been quiet for 30 days opens or clicks your email again.

When one fires, an agent researches the change, finds the right person, checks they are still there, and drafts a note that starts from the change and your logged reason. Signals and agents find the moment and do the homework; nothing sends on its own, every draft waits for your OK. The full playbook is in closed lost win back: the trigger events that reopen a lost deal, and the emails by reason are in closed lost email templates.

Related reading

• Win back closed lost deals: the trigger events that reopen a lost deal
• Closed lost email templates by loss reason
• 12 buying signals examples that show a buyer is ready to talk
• MEDDIC: the sales qualification framework, explained

Frequently asked questions