What Is a Sales Process? And How to Build One Reps Follow

Nearly every sales team has a sales process. Almost none of them runs it. We asked 198 sales leaders, and 89 percent said they have a defined process while only 36 percent said their reps follow it. A 53-point gap means that, on a typical team, the thing called the sales process is a document, and the document and the behavior have almost nothing to do with each other.

The same gap swallows every famous sales methodology. Matthew Dixon and Brent Adamson wrote The Challenger Sale on the back of thousands of reps studied, and their finding was stark: “How you sell has become more important than what you sell” (Dixon & Adamson, 2011). They are right. A Challenger rep, a MEDDIC rep, a SPIN rep all sell better than a rep with no method at all. But a methodology is a set of moves a rep is supposed to make, and a move only counts if the rep makes it, on this deal, today. Challenger, MEDDIC, and SPIN do not fail in their design. They fail in execution, the same place a sales process fails, which is why the humbler question, what is a sales process, decides more revenue than which clever methodology you pick.

The gap between the version on paper and the version reps run is the most expensive number in a revenue business, and it starts with how the process gets defined. (If you came for the seven steps one at a time, with the buyer commitment behind each, they have their own walkthrough in the sales process steps.) A sales process is a behavior before it is a document, and treating it as a document is how a team ends up with one that a third of its reps run.

It helps to start with a plain picture. A sales process is the closest thing a revenue team has to a map: it does not make the journey for you, but it keeps you from wandering and lets the next person take the same road without learning it the hard way. In our survey, 89 percent of teams have drawn the map. 36 percent have a team that walks it.

What is a sales process, underneath the diagram?

Strip away the diagrams and the sales process definition is a simple promise: every deal will move through the same stages, in the same order, and will not skip ahead until it has earned the right to. The stages are the few moments that genuinely decide whether a deal lives or dies. The rules are what separate a stage from a feeling.

It helps to say what a process is not, because the confusion is where most of them go soft:

• Stages, not tasks. A process names the handful of moments that decide a deal, not the fifty small actions a rep takes in a week. A to-do list is not a process.
• Criteria, not vibes. Each stage has an entry and an exit you can check. “It feels close” is not a stage, and a forecast built on it inherits the same fog.
• Shared, not personal. The point is that two reps run the same play, so a deal does not depend on who happens to own it. A process that lives only in your best rep’s head is a single point of failure, not an asset.

A process is also not the same thing as a sales methodology. The sales methodologies reps run, MEDDIC, SPIN, and Challenger, are ways of working inside the stages, mostly how a rep qualifies and runs a conversation. The process tells you where the deal is. The methodology tells you what to do once you are there. You want both, and you should not confuse one for the other. The next section is about why that distinction is worth more than it looks.

Is a sales methodology more important than a sales process?

It is the natural question, and the best-known voices in the field have a clear answer: pick the right methodology and the rest follows. The most influential of them is Challenger.

We should grant Challenger its full case, because the case is strong and the evidence is real. Dixon and Adamson studied thousands of reps and sorted them into five profiles: the Relationship Builder, the Hard Worker, the Problem Solver, the Lone Wolf, and the Challenger. Among average performers the profiles barely differed. Among top performers, the picture broke open: roughly 39 percent of star sellers were Challengers, and in complex sales that share rose past 50 percent, while the Relationship Builder, the profile most sales managers were busy hiring for, produced only 7 percent of the stars (Dixon & Adamson, 2011). The mechanism is insight. As the authors put it, “what sets the best suppliers apart is not the quality of their products, but the value of their insight, new ideas to help customers either make money or save money in ways they didn’t even know were possible.” Neil Rackham, who wrote SPIN Selling and largely invented evidence-based sales research, called the book “the most important advance in selling for many years.” This is not a fad. Insight-led selling earns its reputation.

We part ways with what teams do next, and we keep the thesis. A leader reads Challenger, agrees, and rolls out training: a two-day workshop, a deck, a certification. The reasoning seems sound, because the book is about how reps behave. The trouble is that knowing how a Challenger sells and selling like one in a live call are different things, separated by exactly the gap we opened with. Dixon and Adamson saw this themselves. Buried in their own implementation chapter is the warning that the training must not read as another top-down mandate, and the instruction to “equip reps to challenge customers,” not merely tell them to. They knew the idea was the easy part.

A methodology is a recipe. A brilliant one, in Challenger’s case. But a recipe pinned to the wall feeds no one. What gets a dish cooked the same way on every ticket is the kitchen: the stations, the order of operations, the expediter calling the line, the standard no cook is allowed to skip when the rush hits. A sales process is that kitchen. It is the operational machinery that makes a methodology happen on deal after deal instead of living on a wall. Challenger, MEDDIC, and SPIN all fail the same way and in the same place: the kitchen never cooks the recipe.

So the unglamorous question wins. Argue methodology all year and you are arguing about the recipe. Build a process reps run and you have built the kitchen, and the kitchen is what turns any recipe into revenue. Pick the methodology that fits your motion, by all means. Then spend the real effort making it run, every deal, the same way.

What are the stages of a sales process?

Five to seven sales process stages is the common range. The names vary; the shape rarely does. A deal is found, qualified, understood, shown a solution, given a proposal, negotiated, and closed. People use “stages” and “steps” loosely, and the difference is worth a sentence: the stages are where a deal is, and the steps are the moves a rep makes to carry it from one stage to the next. A stage is a place; a step is a move. Each of the seven, with what it is for and the buyer commitment that ends it, gets its own section in the seven sales process steps.

The number of stages matters less than the rules around each one. A stage with no entry criterion is a stage every hopeful deal wanders into. A stage with no exit criterion is a stage where dead deals linger on while the forecast keeps counting them. Give each stage two plain answers, what gets a deal in and what it must prove to move on, and you have a process. Leave those blank and you have a set of folder names.

What does a sales process look like? An example

Written down, a sales process is a one-page table: a row for each stage, and in each row the rule that lets a deal in, the buyer commitment that lets it out, the person who owns it, and the evidence in the CRM that proves the exit happened. That table holds the five elements a working process carries. A process missing any one of them is still a draft.

• Stages. The five to seven moments that decide a deal, named for what the buyer is doing, since the buyer is the one deciding.
• Exit criteria. The buyer commitment a deal must show before it moves on, written so a skeptic could check it from the record.
• Owners and handoffs. Who holds the deal in each stage, and what travels with it when it changes hands. The SDR-to-AE handoff is where context most often gets dropped.
• Evidence. The field, contact, or note in the CRM that proves the exit criterion was met, so a manager can inspect the stage without calling a meeting.
• An inspection rhythm. When someone checks that open deals meet the stage they sit in. Without this one, the other four decay back into a document.

A sales process example makes those five concrete. The table below writes one out for a mid-market software team running an AE-led motion. Treat it as an illustration of the shape, not a template to copy: your stage names and evidence fields will differ.

Read across the Discover row and the whole idea is in one line. The deal enters on something the seller controls, the AE accepting it. It leaves only on something the buyer did, telling you how they will decide and who will decide it. And a manager can check that exit at a glance, by looking at whether the buying group sits on the record. A stage written that way is hard to fake and cheap to inspect, and those two properties are the reason to write it down.

A fill-in-the-blanks version of this table, with exit criteria drafted for each stage, lives in our sales process template.

Does a sales process move revenue?

The evidence says yes, with a condition attached.

The correlation is real. Harvard Business Review, studying high- and low-performing sales organizations, found the strong performers were far more likely to run a closely monitored, formally enforced sales process, while the laggards tended to run informal ones or none at all (Harvard Business Review, 2015). CSO Insights, the research group now inside Korn Ferry, found the same shape in its sales enablement studies: teams with a dynamic process, one actively monitored and adjusted, posted materially higher win rates and quota attainment than teams without (Korn Ferry).

But the more useful finding is the condition. When CSO Insights sorted teams by how widely the process was adopted, the win rate climbed steadily, from roughly 40 percent where the process was barely used to nearly 58 percent where adoption ran above 90 percent.

Read that carefully, because it reframes the whole subject. The document on the shelf and the document the team runs at 90 percent are the same document. The eighteen points of win rate between them are not a property of the process. They are a property of how much of it happens. Which means the interesting problem was never writing the process. It is getting it adopted.

Why don’t reps follow the sales process?

Here the field data is blunt, and it is the gap we opened with. We put the question to 198 sales leaders in our 2026 research: a defined process almost everywhere, reps running it in barely a third of teams.

The reflex is to read that as a discipline problem, reps who need more training or more accountability. The behavioral science says that reflex is usually wrong, and it is worth understanding why, because the wrong diagnosis leads to the wrong fix.

Following a process is a behavior. And behavior, in the model the Stanford researcher BJ Fogg spent two decades validating, happens only when three things arrive at the same instant: motivation, ability, and a prompt. Fogg writes it as B = MAP (Fogg Behavior Model). The piece rollouts tend to ignore is ability, which Fogg defines not as skill but as simplicity, how little time, effort, and mental load the action costs in the moment. The harder a behavior is, the more motivation it demands to fire. Make it hard enough and no realistic amount of motivation will carry it.

Now look at where a typical process lives. The playbook sits in a doc, a wiki, or an LMS. The work is happening somewhere else. Following the process means stopping the actual work, going to find the instructions, holding them in your head, and coming back, and doing all of that precisely when a rep is busiest and most loaded. That is a large ability cost landing at the worst possible moment. The behavior drops below Fogg’s action line, and a motivated, well-trained rep skips the step anyway. Not because they do not care. Because the system asked for more effort than the moment had to give.

It is the difference between a co-pilot in the seat beside you and the same instructions locked in a manual in the cargo hold. Identical words. Only one of them can speak while the plane is moving. Plenty of companies write a brilliant manual and bolt it in the hold, then wonder why the crew flies some other way.

The ability cost is the mechanism underneath the 53-point gap, and it explains why the usual remedies underdeliver. More training raises motivation, which is the axis that was not broken. Tighter enforcement raises the cost of skipping, which is friction pointed the other way. Neither touches the ability problem, so the behavior stays below the line.

Two independent sources now point at the same spot. Our field data shows the gap is enormous. Fogg’s model says it is an ability problem, not a motivation problem. And the CSO Insights adoption curve shows that the teams who close that gap are the ones who win more deals. When practitioner data, a validated behavioral model, and an industry study converge, that is about as much confidence as this kind of question allows.

How do you build a sales process?

You build a sales process in five moves: write down what your best reps already do, cut it to the five to seven moments that decide a deal, define each stage’s exit as a buyer commitment, put CRM evidence behind each exit, and decide before launch how the process will reach reps and how adherence will be inspected. The first four are design, and a small team can draft them in an afternoon. The fifth decides whether the design ever runs, so it belongs in the build, not in a rollout plan bolted on afterwards.

1. Your best reps’ motion, written down. Sit with the two or three reps who win most often and record what they do between first call and signature. Their motion is already a process; it is unwritten, and it already works on your buyers.
2. Five to seven stages. Keep the moments that decide deals and cut the rest. A stage is an ability cost for every rep who has to honor it.
3. Exits defined by the buyer. For each stage, name the commitment the buyer must make to leave it, the way the Discover row above does.
4. Evidence behind every exit. Decide which field, contact, or record proves the exit, so a manager can inspect it without a meeting.
5. Delivery and inspection, designed in. Decide where the rep meets the stage criteria while working the deal, and when someone checks open deals against them.

The full walkthrough, with the questions to ask your top reps and the order to roll it out in, is in how to build a sales process your reps will run. The fifth move is the one teams skip, and the Fogg model says why it matters most. You are trying to lower the cost of doing the right thing until it falls below the cost of skipping it, and four design rules follow from that.

• Few stages, hard edges. A stage or field is an ability cost. Write a real entry and exit rule for each stage you keep, and cut the rest. A leaner process is cheaper to follow.
• The expectation reaches the rep in the moment. The single highest-impact move, and a direct application of Fogg: surface the required fields, the stage criteria, and the next step the instant the rep hits the decision, in whatever they are working in, so following the process costs almost nothing extra. Removing that trip to the doc is what Fogg calls a facilitator, raising ability instead of nagging motivation.
• Measured in the moments that decide deals. You want to see who is on the process and who has drifted today, while you can still act, rather than discovering it at the quarterly review when the deals are already cold.
• Coached early, not policed late. Seeing drift the week it happens lets a manager make one small correction. Chasing field updates at quarter close raises friction for the whole team and changes little.

A tool belongs at this point and not before. Reducing the ability cost of an entire team’s process, across the open pipeline, in real time, is hard to do with a doc and good intentions.

The recommendation follows straight from the evidence above. A team facing a soft number has two roads. One is to reach for a better methodology, a Challenger rollout, a MEDDIC certification, on the theory that the moves are wrong. The other is to assume the moves are roughly right and the problem is that reps are not making them on enough deals, and to fix the kitchen instead of the recipe. The data points hard at the second road. The 53-point gap is an execution gap, not a knowledge gap. Fogg says the missing axis is ability, not motivation. The CSO Insights curve says the win-rate lift comes from adoption, not from the document. Three independent sources, one verdict: choose the methodology that fits your motion, then put almost all of your energy into making the process run, every deal, the same way. Writing the process is an afternoon. Getting it to live in how reps sell is the job, and the job is making the right move the cheapest one in the moment and seeing drift the week it starts. Spend the energy on the afternoon and the workshop instead, and the year looks like the last one.

Two threads run on from here. The drift itself, why reps leave a process they helped write, is its own subject, and we take it apart in why reps drift from a process you already documented. And the specific ways teams sabotage their own process, too many stages, unverifiable exit criteria, stages that advance on your activity instead of the buyer’s commitment, get named one by one in five common sales process mistakes.