Pull your closed-lost report for last quarter and read the reason column from the top. “Other.” “Price.” A blank. “Other” again. A one-word note that made sense to the rep who typed it on a Thursday afternoon.
The report was supposed to tell you why you lose. It tells you how fast your reps want to get out of the Mark as lost screen.
That’s a design choice, and you can make a different one in an afternoon. This paper gives you a picklist you can copy, the exact setting to change in HubSpot, Salesforce and Pipedrive, and a quarterly review that keeps the list honest.
Why are most closed-lost reports useless?
Because the field was built to be easy to fill, not easy to report on. Free-text reasons can’t be grouped, since different reps describe the same loss in different words. A catch-all “Other” or a vague “Price” absorbs whatever a rep didn’t want to explain. A field that isn’t required at the moment of loss stays blank. And reasons picked during an end-of-quarter cleanup are guesses about deals the rep barely remembers.
None of that is a rep problem. A rep closing out a dead deal has one goal, which is to stop looking at it. If the fastest path through the screen is a blank, a shrug word or “Other,” that’s the path the data shows you. We wrote about the same drag in why good reps enter bad data.
Your reps aren’t hiding why deals die. The field makes the vague answer the fastest one.
The opposite failure exists too. A loss-reason list that grew one “can we add one for...” request at a time is a field a rep can’t pick from in under a minute, which is how it ends up back on “Other.” If that sounds like more than one field in your CRM, start with CRM field bloat.
A closed-lost picklist you can use
Use 8 to 10 reasons that don’t overlap, with “No decision or status quo” as one of them, and define each one tightly enough that two reps looking at the same lost deal would pick the same value. The table below is our recommendation, not a vendor default. The third column is the test: if a rep can’t say that sentence about the deal, they pick a different reason.
| Reason | What it means | What the rep must be able to say |
|---|---|---|
| No decision or status quo | The buyer didn’t buy from anyone and kept doing what they do today | “They didn’t pick a vendor. They kept their current process.” |
| Lost to competitor | The buyer chose another vendor. Pair it with a required Competitor field | “They signed with a named competitor, and I recorded which one.” |
| Price or budget | The buyer said price was the reason | “They told me our price was the problem and named the number they could pay.” |
| Missing capability | The product lacked something the buyer needed. Pair it with a short note | “They needed a specific capability we don’t offer, and I wrote down which one.” |
| Timing or priority changed | The project still exists but moved out or down their list | “The project moved to a later quarter or lost its spot to something else.” |
| Champion or sponsor left | The person driving the deal inside the account left or changed roles | “The person pushing this internally is gone, and no replacement took the deal on.” |
| Lost access to decision maker | The deal stalled below the person who signs | “We couldn’t get in front of the person who signs.” |
| Went dark after proposal | The buyer had pricing and stopped responding | “They had the proposal and stopped replying to my follow-ups.” |
| Disqualified: not a fit | The deal didn’t meet your qualification criteria | “This deal shouldn’t have been in the pipeline.” |
| Duplicate or created in error | The record isn’t a real deal | “This record shouldn’t exist.” |
Three rows need a rule your team agrees on before launch.
Price or budget only counts when the buyer said it. A rep’s sense that the deal felt expensive is a guess, and guesses on this value are how “Price” ends up covering losses that had little to do with price. If the buyer named a number, the rep writes it in the notes.
Lost to competitor needs a name. Without a Competitor field next to it, you know you lose to someone, which you knew already.
The last two rows aren’t losses. Decide whether disqualified and duplicate deals belong in closed-lost at all. If they stay, filter them out of your loss reports, or they’ll dilute the reasons that point at something you can change. “Went dark after proposal” is worth a second look as well, since a pile of those often started as stalled deals that sat open too long.
Trim the list to what your team sells. Eight sharp values beat twelve fuzzy ones.
What should “Other” and free text be allowed to do?
Free text belongs in a notes field next to the picklist, where it adds detail to a reason the rep already chose. It shouldn’t be a reason value of its own, because a free-text escape hatch is the fastest option on the screen and tends to become the most-picked one. Pipedrive’s default is the free-text side, so in Pipedrive this is a setting you change.
Pipedrive’s knowledge base says that by default Pipedrive is set to use freeform lost reasons, that a user with the Deals admin permission can set up a list of predefined lost reasons instead, and that a company account can have up to 100 lost reasons (Pipedrive, Lost reasons, September 23, 2026).
The 100 is a ceiling. Treat it as one.
When you enable predefined reasons, the “Mark as lost” prompt shows a dropdown instead of the fillable text form, and Pipedrive presents an option to allow freeform lost reasons alongside your predefined ones (Pipedrive, How can I enable predefined lost reasons?, September 3, 2026). Leave that option off. Turning it on puts the escape hatch right back next to the list you built to replace it.
How do you set this up in HubSpot?
HubSpot already ships the field. Its default deal properties include Closed lost reason, “the reason the deal was lost,” alongside Closed won reason, and HubSpot links that entry to instructions for customizing the Closed lost reason options (HubSpot Knowledge Base, HubSpot’s default deal properties, September 29, 2026). Your work is setting its options to your picklist and requiring it on the Closed lost stage.
- Check what you have. Open the Closed lost reason property in your property settings and look at its field type and any existing options. HubSpot’s default properties page doesn’t state the field type, and whoever set up your portal may have changed it, so look at yours rather than assuming.
- Turn it into your picklist. HubSpot says editing a property lets you update its field type and edit display options for certain field types, such as the options of a dropdown select (HubSpot Knowledge Base, Create and edit properties, October 26, 2026). Set the values from the table above.
- Require it when the deal is lost. In your pipeline settings, add Closed lost reason as a property on the Closed lost stage and select the Required checkbox. Per HubSpot, “If a property is required, users cannot create or update the record until they set a value for it” (HubSpot Knowledge Base, Set up and manage object pipelines, October 22, 2026).
- Add the companions. Create a Competitor property for “Lost to competitor” and a text property for loss notes, and add both to the same stage so the detail lands next to the reason.
Once the reason is required and the values are fixed, your loss report groups cleanly. If other HubSpot reports still disagree with what your team sees, the causes are usually upstream of the report, which we covered in why HubSpot reports aren’t accurate.
How do you require a closed-lost reason in Salesforce and Pipedrive?
In Salesforce, Salesforce’s own Trailhead exercise has admins create a custom Close Reason field and an opportunity validation rule that blocks saving a Closed Lost opportunity without one. In Pipedrive, a Deals admin switches lost reasons from freeform to a predefined list. Both get you to the same place as the HubSpot setup: a reason picked from your list at the moment the deal closes.
Salesforce. The Trailhead project Customize a Salesforce Object walks through creating an opportunity validation rule “to force users to enter a Close Reason when the opportunity Stage is Closed Lost,” with this error condition formula (Salesforce Trailhead, Create Validation Rules):
``` ISPICKVAL( StageName ,”Closed Lost”) && ISBLANK(Close_Reason__c)
```
The rule fires when the stage is Closed Lost and the Close Reason field is empty, so the save fails until the rep picks a reason. The __c suffix marks Close Reason as a custom field in that exercise. Match the field name in the formula to the API name of your own field, set the field’s values from the picklist above, and test the rule in a sandbox before you turn it on.
Pipedrive. Have a Deals admin switch from freeform to predefined lost reasons, enter your values and leave the freeform-alongside option off, per the two Pipedrive articles above.
| HubSpot | Salesforce | Pipedrive | |
|---|---|---|---|
| Where the reason lives | Default Closed lost reason deal property | A custom Close Reason field in Salesforce’s Trailhead exercise | The lost reason entered in the “Mark as lost” prompt |
| Out of the box | Property ships with options you can customize | Trailhead has you build the field and the rule | Freeform lost reasons by default |
| How you get a fixed list | Edit the property’s field type and dropdown options | Set your custom field’s values | A Deals admin sets predefined lost reasons, up to 100 per account |
| How free text stays out | Keep notes in a separate property | Keep notes in a separate field | Leave “allow freeform alongside predefined” off |
| How it’s required at loss | Required property on the Closed lost stage; the record can’t be updated until it has a value | Validation rule ISPICKVAL( StageName ,”Closed Lost”) && ISBLANK(Close_Reason__c) blocks the save | The cited articles don’t cover a requirement; the dropdown replaces the text form |
How to review lost reasons every quarter
Once a quarter, block 30 minutes and count closed-lost deals by reason, then cut those counts by segment, by rep and by competitor. Look for two things: reasons so broad you can’t act on them, which you split, and reasons reps rarely pick, which you merge or retire. Retire a loss reason only with a mapping to the reason that replaces it, so last year’s losses still report.
Where to pull the counts:
- Pipedrive. Pipedrive documents two ways: add the lost reason column to the deals list view filtered to lost deals, or build an Insights report (Report > Deal > Performance) with a filter for lost reasons (Pipedrive, Lost reasons, September 23, 2026).
- HubSpot and Salesforce. Build a deals or opportunities report filtered to closed-lost and grouped by the reason field, then add segment, owner and competitor as the second grouping.
Four questions to answer in the 30 minutes:
- Which reason grew since last quarter, and in which segment did it grow?
- Does one rep pick one reason far more often than their peers? That’s either a coaching conversation or a definition that two people read differently. Your pipeline review is the place to sort out which.
- Which competitors show up by name, and at which stage did you lose to them?
- Which values went unused, and which one is absorbing losses that belong somewhere else?
When you retire or merge a value, move the deals that carry it to the replacement before you remove it, and write the mapping down. A list you change without a mapping gives you a clean quarter and an unreadable trend line.
Retire a loss reason only with a mapping, so last year’s losses still report.
Illustrative process · no data
| Step | Description |
|---|---|
| Count by reason | Closed-lost deals this quarter, one count per reason. |
| Cut the counts | By segment, by rep and by competitor. |
| Split the broad ones | Reasons so broad you can’t act on them. |
| Merge or retire the rare ones | Reasons reps rarely pick. |
| Map before you remove | Move the deals to the replacement reason and write the mapping down. |
Keep the column, or make it count
You can keep collecting loss reasons you can’t use, and keep guessing in forecast calls about why the quarter slipped. Or you can spend an afternoon on a picklist and a required rule, and walk into next quarter’s review with a column you can count.
Start this week: export last quarter’s closed-lost deals with their loss reason, count how many say Other or are blank, and read twenty of the notes on those deals. The reasons you find in the notes are the first values for the new picklist.
If you want to see what else your CRM collects that you can’t report on, the free CRM Diagnostic runs 40+ automated checks on your HubSpot, Salesforce or Pipedrive data, read-only. Book your free diagnostic.