Deal stages come up all. the. time. in my work. Nine times out of ten, something’s been customized. Often the customization makes total sense. I look at the deal stages, they follow a clear journey, they’re well defined. When customization happens within a rigorous framework, it’s almost always successful.
It’s not always this clean, though. Sometimes customization is not the answer. Companies that have a mature sales team with a lot of data and plenty of experience managing deal flow? Trust yourself and have the debate. Companies that are launching a sales team for the first time? Companies that just closed a round and need to purchase their first CRM? Keep it so, so simple.
The defaults exist for a reason
Most CRMs ship with deal stages that look something like this: New, Appointment Scheduled, Qualified to Buy, Proposal Sent, Negotiation, Closed Won, Closed Lost. The specific names vary by platform, but the concept is the same. They represent a progression from “there’s an opportunity here worth tracking” to “this customer is paying us money.”
These stages are far from arbitrary. They’re based on how the vast majority of B2B sales processes work. The terminology is widely understood, which means your team, your future hires, and anyone who’s worked in B2B before will immediately understand what they mean.
When you customize, you risk losing that shared understanding. “Stage 3: Engaged Prospect” might make perfect sense to the person who created it, but six months from now, your new sales hire has no idea what it means or how it’s different from “Stage 2: Active Lead.”
Whether you’re using the defaults or customizing, make sure the definitions are comprehensive, clear, and well communicated. The latter is key! Does everyone on the team know the rules? If not, figure out why and fix it promptly.
Where to start
Before you customize your deal stages, spend time defining what each default stage means for your specific business. This step is sometimes skipped but it’s a valuable one. If anything, it gets the team talking about your buyers’ journeys, and understanding that is critical to deciding “Do we customize or not?”
For each default stage, write down three things:
The definition. What does it mean for a deal to be in this stage? Be specific. “Qualified” is not a meaningful definition. “The buyer has confirmed budget, timeline, and who signs the contract” is clear and precise.
The entry criteria. What has to happen for a deal to move into this stage? This should be concrete and observable. “Sales rep has had a discovery call and confirmed budget” or “Proposal has been sent and the buyer has acknowledged receipt.”
The exit criteria. What moves a deal out of this stage and into the next one? And what moves it backward? Yes, deals should be able to move backward. If a deal has sat in Qualified to Buy for 60 days with no activity, it probably isn’t qualified anymore.
This conversation should reveal a lot. Do we know our buyers? Are we all on the same page about what our sales process looks like? If the answers to these questions feel nebulous, start with the default stages. Capture some data and revisit with the team in 6 months.
Set up the rules
Once you’ve defined each stage, build automation to keep the burden off your team. Most CRMs let you create workflows that automatically advance deals when they meet certain criteria. Instead of relying on your team to manually update deal stages, let the system do it or send explicit owner prompts based on the rules you defined.
A few things to think about:
Days in stage. How long should a deal sit in a stage before something happens? If a deal has been in Appointment Scheduled for 30 days and the meeting still hasn’t happened, that points to a process problem. Set up rep alerts or manager reports that flag stale deals. Establish internal SLAs and use automation to flag overdue tasks.
Gates. Some transitions should require a human decision. Moving from Appointment Scheduled to Qualified to Buy might need a sales rep to confirm they’ve actually qualified the buyer. That’s important. Build it as a task or an approval step, not a fully automated workflow. And critically: Not everything has to be completely automatic. Sometimes using automation to flag items for human review is all you need.
Backward movement. If a deal falls apart, it shouldn’t sit in Negotiation forever. Define what triggers a backward move and automate it. “No activity in 30 days” is a reasonable starting point. What specifically does “stalled” mean for your organization? Set up rules so the system notifies you when deals need attention.
When customization makes sense
There are plenty of cases where the defaults just won’t work. If your sales process has a genuinely unique step, add the custom stage. Some companies have a “pilot” or “trial” stage between Proposal Sent and Closed Won. If you’re selling to government entities, your procurement process may be rigorous enough that “legal review” and/or “reference check” are their own distinct stages. Or perhaps you have a channel partner and need a custom stage to reflect external involvement. These are all legitimate business cases that deserve consideration.
But “I don’t like the name Qualified to Buy” is never a good reason to customize. “Our team doesn’t use that terminology” is also not a good reason. If you can, try to adopt the terminology. It’s industry standard for a reason!
Platform-specific resources
If you want to dig into the specifics of how deal stages work in your CRM, here are official docs from some of the big players:
- HubSpot: Set up and manage object pipelines
- Salesforce: Lead and Opportunity stages
- Pipedrive: Deal stages
The bottom line
Strong definitions and clear rules matter more than custom stage names. Write internal documentation that explains exactly what each stage means for your business. Set up automation to move deals through the stages based on observable criteria. Revisit every quarter to make sure the definitions still match how your team actually works.
If you’ve done all that and there’s still a gap that the defaults can’t cover, then customize. But some teams may never get there, and that’s a good thing.