What 3 systems store on a lost deal: 6 fields

• HubSpot’s default deal properties include a field defined as "Closed lost reason: the reason the deal was lost" HubSpot.
• HubSpot’s default deal properties also include "Is closed lost: true if the deal is in the closed lost state, false otherwise" HubSpot.
• Pipedrive’s Lost reasons documentation states that comments are saved as a note on the deal so you can refer back to details later Pipedrive.
• Pipedrive’s Lost reasons documentation states that you can have up to 100 lost reasons in your company account Pipedrive.
• Microsoft’s opportunity lifecycle training notes that the Lost status includes three default status reasons: Lost, Canceled, and Out-sold Microsoft.

This specific field is the primary mechanism for creating a readable record that the next review can actually read. The action is not about adding new data structures; it is about using the existing storage location that the system already provides for this exact moment.

The core action is to locate the specific field designated for the loss reason before you close the record. This field is distinct from the status change itself. Writing the reason is a separate data entry that captures the specific circumstance behind that status change. Without this entry, the history only shows that the deal died, not why it died.

This distinction matters for the next forecast meeting. A revenue leader needs to know if a deal was lost to a competitor, lost to budget, or lost to timing. These are different circumstances that require different responses in the next quarter. The field is already there. You do not need to create a custom field or a new note to capture this information if you use the provided reason field.

When you mark a deal as lost, providing a reason helps you understand trends and circumstances when you look back at your deal history, according to Pipedrive. This stored entry functions as a specific record for the next review, capturing the context of why the deal died at that moment. Without this data, the next review becomes a guess about the cause, relying on memory rather than documented facts. The reason field turns a single lost transaction into a data point that can be examined for patterns over time. It allows the revenue leader to see if specific circumstances repeat across different deals or sales periods. This is not about predicting the future or guaranteeing that writing a reason will win the next deal. It is about creating a readable history that explains the current state of the pipeline. The record supports the forecast meeting by providing concrete evidence of what happened, rather than vague assumptions. This approach aligns with the broader need for clarity in software sales numbers, where the reason for a loss is as important as the amount of the deal. To check the amount on the deal, read weighted deal amount. The stored reason serves as the primary artifact for this analysis, making the history of the deal accessible and reviewable.

The following table lists the specific fields and mechanisms each publisher documents for recording why a deal was lost.

Use this table to identify which specific field in your system captures the reason for the next lost deal.

When a deal moves to the closed lost state, the system records specific data points to distinguish the outcome from the cause. In HubSpot's default deal properties, the "Closed lost reason" field is defined as the reason the deal was lost. This is a distinct property from the status indicator itself. The "Is closed lost" property is a boolean value that is true if the deal is in the closed lost state, false otherwise. It does not contain text explaining why the deal failed; it only confirms the status change occurred.

The system also tracks successful outcomes with a parallel field. The "Closed won reason" property is defined as the reason the deal was won.

Do not conflate the boolean flag with the reason field. The flag tells you the deal is lost; the reason field tells you why. If the "Closed lost reason" field is left empty, the record only contains the boolean truth value that the deal is closed lost, without the explanatory text needed for the next review.

• Action: When marking a deal as lost, enter the specific cause into the "Closed lost reason" field. Do not rely on the "Is closed lost" flag to provide this information, as it only records the state change.

According to Pipedrive, you can have up to 100 lost reasons in your company account.

According to Pipedrive, these comments are saved as a note on the deal, so you can always refer back to the details later. This note field is separate from the reason field itself. It allows a sales representative to capture specific circumstances, such as a competitor's action or a budget change, that might not fit neatly into a standard reason category. The note remains attached to the deal record, providing a persistent log of the details surrounding the loss.

For the next review, this structure offers two layers of information. The note field provides the narrative context. When reviewing lost deals, a revenue leader can look at the reason to identify patterns across multiple deals and read the note to understand the specific circumstances of a particular loss. This separation ensures that the high-level reason is consistent enough for analysis, while the detailed note preserves the unique context of each deal.

When a deal is marked lost in the system described on the page titled "Close opportunities as won or lost," the close screen prompts you to verify and update specific details. These include actual revenue, competitor, close date, and description, as stated in the documentation Microsoft. The close date is one field on that screen; it is not a change log. For context on how dates move, see the close date change log.

The underlying data structure supports this record. According to the page titled "Opportunity tables," you can use the table to store information about the revenue, why you closed the opportunity, close date, and the competitor Microsoft. This confirms the reason is a stored attribute, not just a transient state.

The system provides three default status reasons for the Lost status: Lost, Canceled, and Out-sold, from the training module titled "Manage the opportunity lifecycle" Microsoft. These are the published defaults, not a recommended policy for every team.

After you close an opportunity record, the forecast category of the opportunity is automatically updated to Won or Lost depending on your selection for the opportunity closure Microsoft. This automatic update links the closed record directly to your forecast view. If you are tracking how these categories affect your numbers, review the forecast categories explained.

The system stores the competitor and actual revenue alongside the close date, so the record contains the full context of the loss. Do not rely solely on the status reason; use the description field to add the nuance that the next review needs.

This is a mechanical step, not a manual task. Your job is to fill the fields before you leave the record. The system handles the category change; you handle the reason.

Mark one deal lost and set the amount to 100. Write the reason as timing. Add a note that the buyer delayed the work by 30 days. On the close screen, record the competitor, the close date, and a description. The flag can read true and still leave the reason blank. Read the reason before the note at the next review. Use the same check on the next lost deal. Do not read the flag as the cause. The figures 100 and 30 are illustrative only.

Fill the specific reason field in your chosen system before closing the record.

Where does HubSpot store why a deal was lost?

HubSpot's default deal properties include a specific field called "Closed lost reason," which is defined as the reason the deal was lost. This property is distinct from the deal's stage or status and is designed to hold the explanatory text for the loss. According to HubSpot, this is the designated location for that specific detail.

Is the closed-lost flag the same as the reason?

No, the flag and the reason are separate fields within HubSpot's default deal properties. The "Is closed lost" property is a boolean value that is true if the deal is in the closed lost state and false otherwise.

How does Pipedrive save extra comments?

When a user adds comments to a lost reason in Pipedrive, those comments are saved as a note on the deal. This mechanism allows users to refer back to the details later. According to Pipedrive, the system links these additional comments directly to the deal record as a note.

How many lost reasons can a Pipedrive account hold?

A Pipedrive company account can hold up to 100 lost reasons. According to Pipedrive, this is the maximum number of distinct lost reason entries permitted in the account.

What does Microsoft ask for on the close screen?

Verify and update the details such as actual revenue, competitor, close date, and description. That is what Microsoft asks you to check on the close screen.