# Lost reasons in Pipedrive: from a dropdown nobody trusts to a monthly loss review https://salesbond.app/blog/pipedrive-lost-reasons/ Published: 2026-09-29 · Updated: 2026-10-26 Lost reasons are the answer a rep picks when marking a deal lost in Pipedrive. You can collect them as free text or from a fixed list; a short predefined list is what makes the data countable, and a monthly review is what makes it useful. If you change one thing this week, switch from free text to a predefined list of six to eight reasons. This piece starts after the rep has already clicked “Lost”. Whether a deal should be closed in the first place is a different question, and we covered it in [when to close a deal as lost](https://salesbond.app/blog/when-to-close-a-deal-lost/). Here we care about what gets written in that little box, and what you do with it a month later. ## Freeform or predefined lost reasons, and why you probably have both Out of the box, Pipedrive uses freeform lost reasons: the rep types whatever they like ( [Pipedrive Knowledge Base](https://support.pipedrive.com/en/article/lost-reasons)). That sounds flexible. In practice it produces “price”, “Price”, “too expensive”, “pricing – see email”, “ghosted” and a lot of single dots typed by someone who wanted the modal to go away at 6 pm. A predefined list fixes the counting problem. According to the Pipedrive Knowledge Base, you can have up to 100 lost reasons per company account, and only users with the Deals admin permission can configure the predefined list. So on a small team this is usually a job for the founder or the sales lead, not something each rep sets up. Here is the part the setup guides skip. Almost every team that switches ends up with two kinds of data in the same field: a year or two of free text from before the switch, and clean picks from after it. Nobody decides to have both. It just happens on the day the list goes live, and from then on every report that spans that date mixes the two. You can live with that, as long as you know where the line is and you don’t compare the “before” pile with the “after” pile as if they meant the same thing. The setup itself is short. Go to Company settings > Lost reasons, click “+ Lost reason”, type the name and save; repeat for each reason on your list ( [Pipedrive help: enabling predefined lost reasons](https://support.pipedrive.com/en/article/how-can-i-enable-predefined-lost-reasons)). The same page lets you keep freeform reasons alongside the predefined ones. We’d switch that off. If you keep it, keep it only with a team rule that free text is for explaining a pick, never a way around the list. ## A reason list that holds up The test for every reason on the list: does it describe what happened in the deal, or who is to blame? “Rep didn’t follow up” is blame. “Buyer stopped responding after the proposal” is an event. Reps will pick events honestly; they will avoid blame options, and then your data fills up with whatever sounds most neutral. Here is a starting list. It’s hypothetical, built for a small B2B team selling a subscription product, and you should rename things to match how your team talks. - Chose a competitor: only when the buyer said so or you know who they picked. Put the competitor’s name in the note field if you have it. - Chose to do nothing. They kept the spreadsheet, the old tool, the status quo. Often the biggest real category, and the one reps under-report because it feels like a sales failure. - Price after a proposal, and narrow on purpose: the buyer saw a number and said it was the problem. Without a proposal on the table, “price” is a guess, and a guess shouldn’t get its own bucket. - No budget this cycle, which is different from price. They liked the offer and couldn’t fund anything. - Missing capability, with the [capability named in the note](https://salesbond.app/blog/feature-requests-pipedrive-deals/). This one goes straight to whoever owns the product roadmap. - Timing moved: project postponed, champion left, reorg. [The deal may come back](https://salesbond.app/blog/reopen-lost-deal-or-new-deal-pipedrive/), which is useful to know when you look at re-engagement later. - Went quiet: no reply after repeated attempts. Keep it, because pretending every silence has a known cause is worse. - Not a fit. Wrong size, wrong use case, should never have been in the pipeline. If this one grows, the problem is upstream of sales. Once price has its own reason, it is easier to decide [when discounts are the answer to price objections, and when they aren’t](https://salesbond.app/blog/discount-policy-sales-teams/). That’s eight. You could merge “no budget” into “timing” and get to seven; that’s fine. Once the same competitor name shows up three times in the notes, it earns [a one-page battlecard per competitor](https://salesbond.app/blog/sales-battlecards-small-teams-pipedrive/), built from exactly these lost deals. Two rules make the list work. First, the options must not overlap: if two could apply, the rep picks whichever happened first in the deal. Second “Other” is not a default. If you keep it at all, it goes last, and anyone who picks it writes one sentence explaining why none of the others fit. We also ask for one sentence on every lost deal above a value threshold you choose, whatever the reason. Treat this as a team rule enforced in the pipeline meeting, not as a Pipedrive setting. Pipedrive’s help pages don’t describe a setting that makes the note mandatory, so don’t count on the software to do it. ## Cleaning up what you already have You don’t need to rewrite history deal by deal. You need to know what the old data says, roughly, and where the clean data starts. 1. Filter your deals to lost ones and add the lost reason column to the list view (the Pipedrive Knowledge Base describes this column). 2. Read through the free text and map each entry to one of your new reasons in a spreadsheet. Anything you can’t map honestly goes to “unknown”, not to the nearest guess. 3. Write down the date the predefined list went live. Every future report starts from that date, or labels the old period clearly. 4. Delete nothing from the CRM. Step 2 sounds tedious. On a small team it is usually an afternoon, and it tells you whether the the new list covers what actually happens. If a third of the old entries don’t fit any reason, fix the list before you roll it out. If you are doing a wider cleanup, our [Pipedrive audit](https://salesbond.app/blog/pipedrive-audit/) walk-through covers the other fields that drift the same way. ## The monthly loss review, 30 minutes Pick a fixed slot, say the first Tuesday of the month, and keep the same three people in the room: whoever runs sales, one rep, and whoever owns product or pricing. More than that and it turns into a debate about individual deals. This is win-loss analysis at the size a small team can actually keep up. Start with the export, prepared before the meeting: last month’s lost deals, with reason, the stage the deal was in when it was lost, and its value. The Pipedrive Knowledge Base says you can filter Deal Performance reports in Insights by lost reason; the list view with the lost reason column also works if you’d rather count by hand in a sheet. The lost-reason report is also one of the [five pipeline health reports we suggest keeping on a Monday dashboard](https://salesbond.app/blog/pipedrive-reports-pipeline-health/). ![Monthly sales loss review meeting with team members.](https://salesbond.app/wp-content/uploads/2026/09/lost-reasons-in-pipedrive-2.png) The first ten minutes go to losses by reason. You are looking for change, not size: which reason grew compared with last month or last quarter. A big “chose to do nothing” bucket every single month tells you little. A sudden jump in “missing capability” tells you a lot, especially if the notes name the same feature. Better to catch it earlier: [four signs of a no-decision deal](https://salesbond.app/blog/no-decision-deals-pipedrive/) are visible while the deal is still open. The next ten minutes go to losses by stage. A deal lost at qualification and a deal lost after a proposal are different problems even with the same reason. Price objections after a proposal point at packaging or at who you’re quoting. “Not a fit” deals lost late mean qualification let them through, and that is worth a look at how long those deals sat in the pipeline; our piece on [rotting deals in Pipedrive](https://salesbond.app/blog/pipedrive-rotting-deals/) covers the aging side. To see them before the deal is lost, you can [log objections in Pipedrive](https://salesbond.app/blog/objection-handling-pipedrive-log-coach/) as they come up. When the Not a fit share keeps growing, [define your ideal customer profile](https://salesbond.app/blog/ideal-customer-profile-won-deals/) from the deals you already won, so fit means something specific. The last ten minutes go to losses by amount. Read the notes on the largest few lost deals out loud. This is where the one required sentence earns its keep, because a reason code on a big deal is a headline and the sentence is the story. Those sentences are also raw material when you [write the pitch in the words buyers use](https://salesbond.app/blog/sales-pitch-small-team-pipedrive/). Then close with one decision, one owner. Change a price page, add a qualification question, ask product about a feature, retrain on a stage. One. If you leave with five action items, next month you’ll review the same numbers and remember none of them. ## What lost reasons can’t tell you A lost reason is the rep’s account of the deal. It is not the buyer’s. That sounds obvious, but it changes how much weight the data can carry. Reps pick the reason that is easiest to say and hardest to argue with. Price and timing are comfortable; “I didn’t find the real decision maker” is not on the list and wouldn’t get picked if it were. Buyers, for their part, often give a polite reason on the way out, because telling a salesperson the demo was confusing is awkward. So the field records a negotiated story between two people who both had reasons to smooth things over. None of this makes the data useless. It makes it a trend line, not a verdict. When a reason moves month to month, something probably changed. When a reason is simply large you don’t yet know whether it’s true or just comfortable. The way to test it is outside the CRM: call a few lost buyers a month or two after the decision, when there’s no sale at stake, and ask what happened. If what they say keeps disagreeing with the dropdown, trust the calls and change the list. It also can’t tell you about deals that never got marked lost. If your pipeline is full of [deals nobody closes](https://salesbond.app/blog/pipedrive-archive-old-deals-leads/), your loss data is describing only the ones someone bothered to clean up. The [CRM data quality metrics](https://salesbond.app/blog/crm-data-quality-metrics/) we track include this kind of gap, and it’s worth checking before you read too much into a single month. Start with the list. Run the first review with whatever data you have, messy or not, and let the second one be better.