How to Build a Sales Process Your Reps Will Run

Most teams do not need to be told to have a sales process. They have one. What they are missing is how to build a sales process their reps will run on a real deal, on a Tuesday, when the buyer goes dark and the number is due. That is a harder thing than drawing seven boxes in your CRM, and almost everything written about building a sales process stops at the boxes.

Here is the surprising part, and it sets up the whole post. The industry has already solved the hard intellectual question of how to design good stages. The pages that own this query say the right things. HubSpot’s mapping guide, written by Kyle Jepson, tells you a deal stage must be three things at once (HubSpot, “How to Design Your Sales Process in HubSpot CRM,” updated December 2021):

Factual: A step is factual if it’s based on actual actions that have been taken rather than a feeling or intuition you or the buyer might have. Inspectable: A step is inspectable if there’s some sort of record that can be used to prove that the action has been taken. Buyer-centric: in the end, it’s the buyer’s actions that will close the sale.

Read that twice, because it is correct, and it is the exact opposite of the lazy strawman that the template-first world ships activity-named junk. Jepson is right. He even adds, in the same guide, that “less is more” on stage count and that you should base each stage on an action the buyer takes. Jacco van der Kooij and Winning by Design go further still, rebuilding the entire stage map around customer impact in the SaaS Sales Method and the Bow Tie model (Winning by Design, The SaaS Sales Method). Grant both their case in full. On paper, the design problem is a solved problem.

So why do most built processes still go unrun? Because designing the stages and getting reps to run them are two different jobs, and the industry pours its ink into the first one, which was the easy one. A perfect, buyer-centric, inspectable stage map is still only a drawing until it reaches a rep at the moment of the work and someone checks whether the buyer commitment is real. That second job, delivery and inspection in the flow of the work, is the part the template and the methodology leave you to figure out alone. It is also where almost all of the number is won or lost. This post is about that part.

When a university lays out a new quad, it faces a small and revealing choice. It can pour concrete walkways from an architect’s drawing, neat diagonals that look right on paper, and then watch students cut across the grass anyway, wearing a muddy line straight to the library that no planner ever drew. Or it can plant the grass, wait a year, watch where the feet go, and pave those routes. Planners have a name for the muddy line. They call it a desire path: the route people take when no one is choreographing them. The wise campus paves the desire path. The proud one pours the diagram and spends a decade at war with the lawn.

Building a sales process is the same fork in the path. You can import a seven-stage diagram from a template, pour it into the CRM, and announce it at the sales kickoff, then watch your best reps keep selling the way they always have while the strugglers follow a map to nowhere. Or you can find the route your winners have already worn into the grass, the moves they make that the others skip, and pave that. One of these your team will walk. The other you will spend a year enforcing.

What does it mean to build a sales process?

Building a sales process is two jobs that get confused for one. The first is drawing the stages, the sales process framework: the shape a deal passes through from stranger to signature. The second is making that shape something a whole team runs the same way and a manager can inspect. The first job is an afternoon’s work. The second is the one that decides whether you have a process or a poster.

This matters because the search results, and most advice, treat building as the first job only. Draw seven stages, name them, drop them in the CRM, done. If that worked, every team with a documented process would be a high-performing one, and they are not. We surveyed 198 sales leaders for The State of Sales Enablement and found that 89 percent had a defined sales process while only 36 percent saw their reps reliably follow it. The diagram is everywhere. The running of it is rare. So if you are going to build a sales process, build it for the second job from the first day, because that is the part that was ever hard.

Think of it like a cookbook in a restaurant. The recipe can be flawless. A three-star chef can write it, every quantity tested, every step in order, the dish perfect when followed. None of that puts dinner on the table at seven o’clock on a Friday, when forty orders are in and the line cook has both hands full. What feeds the room is not the quality of the recipe but whether the right card is at the station, at the burner, at the second the cook reaches for it. HubSpot and Winning by Design wrote you an excellent recipe. The build is everything between the recipe and the plate.

Designing the stages well is necessary. It is not sufficient. A buyer-centric, inspectable stage map, taught in a workshop and drawn on a blueprint, still has to survive a rep on a Tuesday with the buyer gone dark. The recipe does not stand at the cook’s shoulder; the process has to. That gap, between a well-designed process and a run one, is the one neither the template nor the methodology closes, and it is where most of the number is lost.

The shift that makes the difference is small to describe and large in effect. A stage is not a thing your rep does. It is a thing the buyer commits to. Hold that, and the rest of the build follows.

How do you build a sales process, step by step?

Six steps. The first and last are the ones teams skip, and they are exactly the two that decide whether the process gets adopted or dies forgotten in the CRM. Whether you call this how to build or how to create a sales process, the work is the same: not drawing the stages, but making them run.

1. Capture the motion your best reps already run

Do not start from a blank diagram or a borrowed one. Start from your winners. Pull your last ten won deals and sit with the two or three reps who close at a rate the others envy, and trace the moves they make that the strugglers skip. There is almost always a pattern: the winners qualify harder and earlier, they reach more of the buying group, they get a real next meeting booked before they hang up. Your working process already lives in your best people. The job is to find it and write it down, not to import a consultant’s template nobody believes in.

This is the desire path again, made practical. The route is already worn; you are only paving it. It is also the cheapest way to win the room, because a process drawn from your own top reps arrives with built-in credibility. The team is not being asked to follow a stranger’s idea. They are being asked to sell like the person at the top of the leaderboard.

2. Define each stage by a buyer commitment, not a seller activity

Here is the move that separates a process that forecasts from one that flatters. Write the exit criterion for each stage as something the buyer did, never as something the rep did.

“Demo delivered” is a seller activity. It happens whether or not the buyer moved an inch. It is a captain’s log that faithfully records how hard the crew rowed and says nothing about which way the ship is pointed. “Buyer confirmed the product solves a problem they named, and agreed to a defined next step” is a commitment. You can check it. It only happens if the deal genuinely advanced.

This is not a reason to stop tracking activity. Capturing what the rep did is good and necessary; it is how you verify the process is being followed at all, and the activity shapes the buyer’s experience. The point is that a stage should reflect the buyer’s real position, not the bare fact that a box got checked. A deal advances on the commitment. The activity is how it gets there. We walk every stage and its matching buyer commitment in detail in the seven sales process steps; for the build, the rule is enough: every exit criterion names something the buyer did.

3. Cut to five to seven stages

The instinct, once you start, is to add stages. More stages feel like more rigor. They are the opposite.

Sheena Iyengar and Mark Lepper ran a now-famous experiment with a grocery tasting table, some days laid with 24 jams and some with 6. The big display drew a bigger crowd and far fewer buyers, 3 percent against 30 percent, because a wall of options raises the cost of choosing until people walk away (Iyengar & Lepper, 2000). An eleven-stage pipeline does that to a rep at every gate. Worse, long pipelines almost always map your own internal handoffs, SDR to AE, AE to solutions engineer, deal desk, legal, dressed up as buyer progress. The buyer could not care less about your org chart and is certainly not walking through it. Cut until every stage is a moment the buyer would recognize in their own decision.

4. Write exit criteria a manager can inspect

A buyer commitment that cannot be checked is a wish. For every stage, write down the one piece of evidence that proves the commitment is real: a recap email where the buyer states the problem in their own words, a confirmed meeting with the economic buyer, a mutual plan with a date on it.

The principle underneath is older than sales. You can only expect what you inspect. A stage with no inspectable exit becomes a holding pen where deals get waved through on a rep’s good feeling, and the pipeline inflates one optimistic judgment at a time. The exit criterion is the thing that lets a manager ask “show me” instead of “how’s it feeling,” and “show me” is the only question that keeps a forecast honest. This is the same discipline that separates a defensible sales process from a decorative one.

5. Put each stage’s next action in the flow of work

You have now built a process that is correct. Correct is not adopted. The gap between the two is the single largest performance variable on most teams, and it is bridged by one thing: delivery.

Reach for the mechanism, because it tells you exactly what to do. BJ Fogg’s behavior model holds that a behavior happens only when three things meet in the same instant: motivation, ability, and a prompt (Fogg, B=MAP). A rep who has to stop work, open a different tab, and hunt through a 40-page playbook to find the next step has low ability at the moment of action, and the behavior does not fire, no matter how motivated they were at kickoff. Make the right action easy and present in the moment, and the same rep follows the process without thinking about it.

There is a second, converging finding worth knowing, because it has been tested on tens of thousands of people. Peter Gollwitzer and Paschal Sheeran reviewed 94 studies covering implementation intentions, the simple act of deciding in advance “when situation X arises, I will do Y,” and found a medium-to-large effect on whether people follow through (Gollwitzer & Sheeran, 2006, meta-analysis of 94 studies). A sales process delivered in the flow of work is an implementation intention made operational: at this stage, on this deal, the next action is already named and waiting where you are. The buyer-research giant agrees from the other side; Gartner finds B2B buyers spend only about 17 percent of the buying journey with any supplier, so the few moments you do have with a rep in the work are the ones that have to count (Gartner). Where the process should live, and why a CRM field alone is not enough, is its own subject in where your sales process should live.

6. Measure adherence, then change one thing

A process is not a document you finish. It is a loop you tune. Once it is running, measure whether reps run the stages on real deals, find the single stage where deals stall or skip ahead, and fix that one thing. Then watch again.

This is what turns a static diagram into a living standard, and it is the prerequisite for every other improvement. You cannot ask “what should we change about our process” until you can answer “is the process being followed,” because a stage that nobody runs cannot be said to work or fail. It was never tried. Measurement first, then change, in a loop. The deeper mechanics of getting that loop to stick are in sales process adoption.

Why do most sales processes fail after you build them?

Because the build was never the hard part, and teams pour all their effort into the part that was easy. Drawing the stages is maybe a tenth of the work. Getting reps to run them on live deals is the other nine-tenths, and it gets almost none of the attention.

The size of the gap is not a matter of opinion. Across our 198 leaders, teams whose process lived only in a document hit quota 15 percent of the time, while teams that delivered the process in the moment of work and measured whether it was followed hit quota 49 percent of the time. Same stages on paper. A threefold difference in the field, decided entirely by whether the process got run.

There is a name for this in behavioral science: the intention-action gap. People intend to do the thing, decide to do the thing, and then, at the moment of action, do not. A documented process is an intention. Reps fully intend, at kickoff, to run it. The gap opens on the Tuesday, under quota pressure, when the next right step is buried in a doc and the easy thing is to wing it. When reps go off-process, the cause is almost never laziness. It is friction, late delivery, and missing inspection. The fix is to the system, not to the rep.

That is why “build for adoption from day one” is not a slogan. It is the instruction that follows directly from the data. If you build the diagram and bolt on adoption later, you have built the concrete walkway and left the lawn for someone else to fight.

Where should the process live so reps use it?

Not in a slide deck, and not buried in a CRM field nobody reads. It should live in the flow of work: surfaced to the rep in the tool where the deal is being worked, at the instant the question arises, guiding them to the next best action without making them leave the task to go find it.

This is the principle behind what we build at Supered, and it is worth naming as one concrete instance of the mechanism, not the point of the piece. We call it the Behavior Layer: continuous, in-the-moment enablement that meets the rep in HubSpot, Salesforce, Salesloft, Gong, Gmail, wherever the work is happening, and measures whether the buyer commitment for each stage landed. It enhances the CRM rather than replacing it, and it never asks a rep to open a new tab to do their job. The mechanism is general, though. Any team that delivers the next step in the moment and measures adherence is building for the second job, the one that decides whether the process runs.

How is building a sales process different from a methodology or a template?

Three words get used as one, and keeping them apart saves a lot of confusion at build time.

• A sales process is the sequence of stages a deal moves through, shared across the team. It is the road. This is what you are building.
• A methodology like MEDDIC, SPIN, or Challenger is how a rep works inside the stages, mostly how they qualify and run a conversation. It sharpens a rep within a stage; it does not tell you where the deal is. Build the process first, then choose a methodology that fits how your winners already sell.
• A template is a scaffold for the shape, useful for remembering the stages a deal usually passes through and useless as a source of content. Use it to recall the skeleton, then replace every generic stage with the buyer commitment your own winners earn. Our sales process template is built around commitments rather than activity for exactly this reason.

The short version: the template reminds you of the shape, the process defines your stages, the methodology sharpens the rep inside them. You want all three, built in that order.

What to build, and what we would build

There are two honest ways to build a sales process, and they lead to different places.

The first is design-first and stop: take a stage map, even a good one built the way HubSpot and Winning by Design teach, with buyer-centric, inspectable stages, load it into the CRM, and announce it. It is fast, it looks finished by Friday, and on its own it produces the 36 percent, a well-drawn process most of your reps will route around. Designing it correctly is not the failure. Stopping there is.

The second is capture-first and built for adoption: trace the path your best reps already walk, define every stage by a buyer commitment you can inspect, cut the list to the few that matter, deliver each next step in the flow of work, and measure whether the stages get run so you can tune the one that leaks. It is slower to look finished, and it is the version that produces the 49 percent.

We would build the second every time, and the reason is in the data rather than in taste. The design is a tenth of the work and gets you the same outcome as everyone else, because the best stage maps are nearly identical across teams; the buyer’s path does not change much, and HubSpot already gave it away for free. The edge is the other nine-tenths, in whether your team runs the process on a real deal when no one is watching. So borrow the recipe, then build the part the recipe cannot do for you. Pave the desire path, write your stages as commitments you can check, pin the next step at the rep’s burner where they are already working, and measure whether the dish gets made.

Then go deeper on the pieces this build rests on: the full sales playbook guide that ties the stages, methodology, and coaching together; the seven steps and the buyer commitment behind each; why a built process still goes unrun in the sales execution gap; and how to make adoption stick in sales process adoption. The stages are the easy part. Building one your reps run is the work, and it is the only part that was ever worth doing.