CRM architecture / Field note
One sales process.
Too many pipelines.
A different region or product does not automatically mean a different sales process. That distinction matters when you design HubSpot.
Based on my published HubSpot advice. The configuration below is illustrative, not a client case study.
The problem
Teams can end up with several pipelines that have the same stages but different labels for products, regions, or owners. Every change then needs to be maintained in multiple places, and reporting has more places to disagree.
The decision I start with
Are the stages and the criteria for moving between them meaningfully different? If they are, a separate pipeline may be appropriate. If the difference is how you want to group or view the same process, consider properties and filtered views first.
| Difference | Start by considering |
|---|---|
| Region | A region property and team views |
| Product | A product property and reporting filters |
| Owner or team | Ownership rules, access requirements, and views |
| Different stages and exit criteria | A separate pipeline with explicit definitions |
What I would check before changing it
- Map stages, exit criteria, and the people responsible for each handoff.
- Identify workflows, integrations, permissions, and reports that depend on the existing pipelines.
- Test a small sample and compare reporting before moving more records.
- Document the new structure and how the team should use it.
The goal is a process people can operate and reports they can explain. The number of pipelines follows from that.
Working through something similar?
Tell me about the process, the tools, and the part that keeps getting in the way.
Talk Through Your Setup