A defined sales process is one clear path from first conversation to closed deal, with stages based on what the buyer does, specific criteria for moving between stages, required actions at each step, and numbers you can measure. A simple test: if it's written down, everyone follows it, and you can measure it, it's defined. If any of those is missing, what you have is a set of habits.
Most growing companies don't have one, even when they have a CRM. Of the 200 businesses we've worked with since 2025, more than 90% had no defined sales process. Many were already past $3M in revenue, with a sales team, HubSpot or Salesforce, and steady referrals.
This guide covers what a defined process includes, the mistake almost every company makes with their pipeline, and how to set up HubSpot so it follows your process instead of just storing data.
When we started working with an IT services firm, their sales lead told us their process lived in HubSpot. The pipeline had stages and deal values. It looked organized.
But he'd been on three sales calls the week before, and only one was in the CRM. Deals were only created once a client had essentially said yes. Their pipeline wasn't a forecast. It was a list of deals they'd already won.
A CRM stores whatever you put into it. It can enforce a process, but only once that process has been defined. Without one, you get a well-organized picture of guesswork.
1. Stages based on buyer progress. "Proposal Sent" describes what your rep did. Good stages describe what the buyer has done or committed to, such as confirming the problem or agreeing on scope.
2. Exit criteria for every stage. These are the conditions that must be true before a deal moves forward. They're the part most companies skip, and the part that makes a pipeline trustworthy.
3. Required actions. The steps every rep takes at each stage, every time. If one rep follows up twice and another follows up until they get an answer, they're doing two different jobs.
4. Stage metrics. Conversion rates between stages and time spent in each stage. These tell you where deals are dying and what to coach.
Here's a simplified version of the new business pipeline we built for the IT services firm. Your stages will differ, but the structure carries over.
| Stage | Exit criteria (must be true to move forward) | Required actions |
|---|---|---|
| Discovery scheduled | Meeting date set, contact and company linked, lead source recorded | Confirm meeting, research the company |
| Discovery completed | Problem confirmed, prospect qualified or disqualified, deal type set | Log notes, schedule next meeting |
| Solution defined | Scope confirmed, service type and estimated amount set, enough information to quote | Build the quote |
| Proposal sent | Proposal date recorded, decision-maker identified | Review the proposal live, set follow-up date |
| Decision / negotiation | Decision-maker engaged, terms in discussion | Address objections, confirm close date |
| Closed won / lost | Final amount recorded, or a closed-lost reason selected | Hand off to delivery, or schedule a future check-in |
Two rules from this pipeline made the biggest difference:
This is the single biggest gap we see. Our rule of thumb: create a deal when a discovery meeting is scheduled or a qualified sales conversation has happened.
Before that point, the contact is a lead. Track leads separately, with their own stages like new, attempting contact, connected, qualified, disqualified, and nurture. That keeps prospecting activity from inflating your pipeline, and it stops your conversion rate from being dragged down by opportunities that were never real.
Once the process is defined, HubSpot can enforce it. These are the pieces we configure most often.
Separate leads from deals. Track early prospecting separately and use the deal pipeline only for real opportunities. When a lead is marked qualified, a workflow can create the deal automatically, already linked to the right contact and company.
Required properties at each stage. HubSpot lets you require specific fields before a deal can enter a stage, such as a meeting date, amount, decision-maker, or closed-lost reason. This turns exit criteria into something the system checks for you.
Stage probabilities for forecasting. Each stage gets a likelihood of closing, so your forecast weighs a deal in discovery differently from one in negotiation. A $10K conversation from a networking event shouldn't count as $10K.
Separate pipelines when the process is different. The IT firm had one pipeline for new business and another for existing clients, because selling to a current client follows different steps.
Automated follow-up tasks. Workflows can create a task whenever a lead or deal has no next step, so nothing sits untouched.
Views for what needs attention. Saved views like "no activity in 7 days," "stalled 14+ days," and "closing this month" show reps and managers where to focus without digging.
Playbooks for key calls. Discovery and solution-definition questions live inside the record, so reps ask the same questions every time and answers stay with the deal.
Reports that answer real questions. Pipeline by stage, conversion between stages, deal velocity, win rate, closed-lost reasons, and revenue by lead source.
Audit the setup first. Before training anyone, review the pipelines, stages, required properties, automations, reports, and data quality. If the portal doesn't reflect a defined process, training the team on it will only make the current habits more consistent.
Train on the process, not just the clicks. Reps need to understand why each stage exists and what has to be true to move forward, not only where the buttons are.
Practice with a test record. Our trainings use a demo contact that the team walks through the entire process live: creating the lead, qualifying it, watching the deal get created, moving it through each stage, and seeing what HubSpot requires along the way. Gaps show up quickly when people use the system for real.
Check back a few weeks later. The first few weeks of real use always surface something to adjust. Plan a follow-up to fix what isn't sticking.
The founder of a tech-forward investment consulting firm came to us after two years of sales problems. Marketing was producing plenty of leads, but they were dying after they came in.
Follow-up emails were going out four weeks apart. A referral from a top partner sat for nearly a month because emails landed in spam and no one called. About 17 deals were stuck at "Materials Sent," with only 3 at contract, partly because the firm was emailing free custom analysis to prospects who then went quiet. The dashboards showed a close rate he knew was wrong.
Near the end of our first call, he said: "I don't trust anything anymore." He was talking about experienced salespeople who hadn't delivered, but it applied to his reports too.
We rebuilt the pipeline around buyer steps: intro, discovery, strategy and planning, proposal, and close. Discovery became the place to qualify and gather information, and the custom analysis moved into a live strategy session instead of an email. Every meeting books the next one, and reps ask prospects how soon they'd like a follow-up, then track the answers.
The results: deals started moving past "Materials Sent," the reports matched reality, and the sales cycle became predictable. The firm gained a fair way to grade rep performance and a process to train new reps. They hired a new rep, and the founder was able to handle more deals while freeing up time to train them.
Answer yes or no:
Six or seven yeses means you have a real process to refine. Three to five means gaps are costing you deals you can't see. Two or fewer means you have activity, not a process.
[Download the full scorecard] to see what each "no" usually means and what to fix first.
How long does it take to define a sales process?
In our experience, owners trust their numbers within about 8 weeks, usually 1 to 2 weeks after the CRM is set up to follow the defined process.
What's the difference between a sales pipeline and a sales process?
A pipeline shows where deals are. A process defines how deals move, what has to be true at each stage, and what reps do along the way. The pipeline is how the process shows up in your CRM.
When should I create a deal in HubSpot?
When a discovery meeting is scheduled or a qualified sales conversation has happened. Before that, track the contact as a lead.
Do small sales teams need a defined process?
Yes. It's easier to define before you hire. Every rep who joins without one builds their own version, and those versions have to be undone later.
Can HubSpot enforce our sales process?
Yes. Required properties at each stage, automated tasks, stage probabilities, playbooks, and reports all help the system enforce the process once it's defined.
If your business is stuck at the same revenue number, the problem is almost never effort or people. It's the system underneath them.
Eternal Works helps growing businesses find what's really slowing them down, fix what isn't working, and build the sales and marketing systems that make growth predictable and measurable. To see how we approach HubSpot implementation and sales process consulting, book a 30-minute discovery call with Tim: https://www.eternalworks.com/meetings/timjones/disocvery-30min-linkedin