A well-configured CRM is, above all, a tool built to drive sales performance. Yet over time, HubSpot pipelines tend to become cluttered : statuses, intermediate stages, and edge cases pile up until the pipeline no longer reflects where opportunities actually stand, but rather a log of everything that has ever happened.
This was exactly the situation facing this B2B company: pipelines that were full, but had lost their original purpose. Our goal was straightforward: make the CRM more readable, more reliable, and more actionable for both sales and operations teams.
During the audit, two main pipelines were reviewed:
The existing pipeline structure was trying to cover too many use cases at once, mixing several distinct processes within the same pipelines:
The result: the CRM held a lot of data, but visibility was suffering. The sales pipeline could no longer clearly separate:
Beyond mixing business verticals, several structural issues were also undermining the quality of sales reporting 👇🏼
The pipeline extended all the way to a very advanced stage, but without a final step clearly configured as "Won" or "Closed Won" at 100%. This made it harder to track revenue that had actually been booked.
Stages like "Nurturing" or "To Reactivate" were treated as lost statuses but a prospect that needs reactivating isn't necessarily lost. They may simply not be ready yet.
Several stages were more about targeting and outreach than actual sales opportunities. This created an overloaded pipeline with poorly qualified deals, leading to a lack of visibility and difficulty prioritizing next steps.
The Customer Success pipeline included steps such as:
While these steps are relevant for tracking project progress, they have no place in a sales pipeline. They belong to the execution phase of a client engagement, not the sales process.
Rather than adding more layers of information, which would only make the CRM harder to use, the priority was to clarify the role of each element.
A sales pipeline should answer one question: Where does this opportunity stand in the sales process?
Prospecting, nurturing, and reactivation can all be tracked through dedicated properties, views, or statuses, without cluttering the main pipeline.
A final "Won" / "Contract Signed" / "Closed Won" stage makes it possible to reliably track:
Rather than creating multiple lost stages, the recommendation is to maintain one "Lost / Closed Lost" stage and use properties to capture the nuance:
Not everything important needs to be a pipeline stage. Processes like RFIs, RFPs, or competitive bids can be tracked as deal properties, keeping the pipeline clean while still making the data available for filtering and reporting.
A simple rule for pipeline design: before adding a stage, ask yourself: "Will more than 75% of my opportunities go through this step?" If yes, it belongs in the pipeline. If not, it belongs in a property.
Post-signing follow-up should live outside the sales pipeline, following a clear separation of concerns:
Once a deal is marked as won, a project is created and linked to the deal, the company, and the relevant contacts, keeping everything connected without mixing the two workflows.
The optimized BizDev pipeline features stages that are clearer and better aligned with the actual sales process:
Once a deal is closed, client follow-up moves to a dedicated space: the Projects module. Each project is linked to the deal, the company, and the relevant contacts, ensuring information continuity without cluttering the sales pipeline.
Project stages reflect the actual delivery process:
The new structure delivers three concrete outcomes:
1 - More reliable sales reporting: the pipeline focuses on real opportunities, closed revenue is properly tracked, and key metrics like closing rate and cycle length become measurable.
2 - Greater clarity for teams: prospecting, active sales, and delivery are cleanly separated, making it easier to prioritize and reducing the risk of misinterpretation.
3 - A seamless sales-to-project handoff: once a deal is closed, the transition to the Projects module is straightforward and can be fully automated, with no loss of information.
With a cleaner structure, HubSpot stops being a status repository and becomes a real operational tool. Sales reps know where to focus, managers get a reliable view of the business, and operations teams pick up the baton without friction.
That's what a well-structured CRM looks like: not more information but the right information, in the right place.
Does this sound familiar? Let's talk about your HubSpot pipeline structure.