How do you coach reps to qualify the decision-making process?

What decision-process qualification actually is, and why RevOps cares

Decision-process qualification is the discipline of documenting *how* a buying organization converts intent into a signed contract. It is not the same as decision criteria. Criteria answer "what do they want" — the feature set, the integration list, the security posture, the price ceiling. Process answers "what physically has to happen, in what order, owned by whom, and by when." A rep can know a buyer's criteria perfectly and still have zero idea that procurement requires three competitive bids above a spend threshold, that InfoSec runs a four-week vendor review, or that the signer is a CFO who only reviews contracts in the first week of the month. Those are process facts, and they are what actually determine close date.

The distinction matters because sales stages are usually written around criteria and sentiment ("demo complete," "value confirmed," "verbal") while slipped deals almost always die on process. A deal does not slip because the buyer stopped liking the product. It slips because a step nobody mapped — a security questionnaire, a legal redline cycle, a board meeting that only happens quarterly, a fiscal-year budget freeze — took time nobody budgeted for. Every one of those is knowable in advance if a rep asks.

The named framework most teams anchor on is MEDDIC and its extended form MEDDPICC, where the second "D" — Decision Process — sits alongside Decision Criteria, Paper Process, and Identify Pain. The framework's value is not that it is magic; it's that it gives you and the rep a shared vocabulary so coaching feedback is specific. "Your Decision Process is thin, you have steps but no owners" is coachable. "This deal feels soft" is not. Other frames work too — the Challenger buying-process map, mutual action plans from Winning by Design, or a simple homegrown checklist. Pick one, name it, and never rotate it mid-quarter, because half the coaching value comes from the team sharing one mental model.

For RevOps, this is a data-quality problem as much as a skill problem. If your CRM has one close-date field and a free-text notes box, you have structurally guaranteed that decision-process knowledge lives in reps' heads and evaporates on attrition. The RevOps contribution is to build the fields, the required-at-stage gates, and the reporting that make process qualification visible — then hand managers a report they can coach from. Without that, coaching is anecdote-driven and doesn't compound.

The commercial argument is straightforward. B2B buying committees routinely span six to ten people across functions with input from many more, and research from Gartner on the B2B buying journey has consistently found that buyers spend the majority of their buying cycle *not* talking to any vendor — doing internal work you can only see if you ask about it. A rep who cannot describe that internal work is forecasting on the visible 20% of an iceberg. That is the entire case for making decision-process qualification a non-negotiable, coached skill rather than an optional discovery nicety.

Diagnosing the gap before you coach anything

The single most common coaching failure is applying the wrong intervention. A manager sees "rep doesn't qualify the decision process," reflexively runs a training session on MEDDIC, and nothing changes — because the rep already knew the questions and simply wasn't asking them. Diagnose first. There are four distinct root causes and each has a different fix.

Knowledge gap. The rep genuinely does not know what an enterprise buying process looks like. This is normal for an AE promoted from SMB or from an SDR seat, where deals closed on a credit card and "the decision maker" was one person. They cannot ask about procurement thresholds because they don't know procurement thresholds exist. Fix: teach the map. Walk them through three of your own closed-won enterprise deals end to end — every step, every function, every duration — until they can draw it from memory. Budget two to three sessions.

Skill gap. The rep asks, but the questions are weak or they accept the first vague answer. "So what's the process from here?" gets "we'll take it to the team," and the rep writes "taking to team" in the CRM and moves on. This is the most coachable gap and responds fastest to rehearsal: they need better phrasing and, critically, the ability to sit in silence and ask a second-level follow-up.

Will gap. The rep knows and can ask, but avoids it. The usual driver is fear that the honest answer will reveal the deal is not real, and they'd rather keep a soft deal on the forecast than kill it. Sometimes it's a fear of "slowing the momentum" or seeming presumptuous with a senior stakeholder. Pep talks don't fix this; changing the incentive does. Make forecast accuracy visible, praise fast disqualification publicly, and reframe the ask as buyer-service ("I don't want to be the reason your go-live slips") rather than sales pressure.

System gap. Nobody ever required it. There is no field, no stage exit criterion, no deal-review template that asks. If your pipeline review consists of "where are we on this one," you are structurally teaching reps that process detail doesn't matter. This is the RevOps fix and it is often the highest-leverage one, because it changes behavior for the whole team at once rather than one rep at a time.

The diagnostic move is cheap: pull one call recording and one CRM record per rep. If the questions never appear on the call, it's knowledge, skill, or will — listen to *how* they approached it to tell which. If the questions appear on the call but the detail never lands in the CRM, it's a system or hygiene problem. Ten minutes of evidence beats an hour of speculation.

The coaching sequence, step by step

Run the loop weekly, keep it to 30 minutes, and cap it at two deals. Coaching sessions fail when they become pipeline reviews; the distinction is that a pipeline review asks "what's the status" and a coaching session asks "what will you say, and let's practice it."

Step 1 — Observe with evidence, not memory. Pull an actual recording from Gong, Chorus, or whatever your team uses. Coaching from the rep's recollection of the call is coaching from a rewritten transcript; every rep remembers asking better questions than they asked. Pick a specific two-minute window where the process question should have appeared.

Step 2 — Let the rep grade themselves first. Open with "walk me through, step by step, what has to happen between today and a signed contract." Say nothing else. The length and specificity of the answer *is* the diagnostic. If they can name six steps with owners and durations, the deal is qualified and you should move to the second deal. If they say "they're aligned internally and want to move fast," you've found your session.

Step 3 — Pressure-test against a fixed checklist. Use the same five questions every week so the rep internalizes them:

• What is the paper process — purchase requisition, security review, legal, signature — and in what order?
• At what dollar threshold does procurement get pulled in, and do they require competitive bids?
• What does legal need to see, and has our MSA been sent ahead of redlines?
• Who approves budget, and is that the same person who signs?
• What is the compelling event, and what happens to the buyer if the date slips?

When you get a soft answer — "they said it's pretty quick" — do not fill the gap yourself. Ask "quick according to whom: your champion, or the person who controls procurement?" The gap surfaces on its own, and the rep owns discovering it.

Step 4 — Make the rep generate options before you offer one. "Given you don't know the procurement timeline, what are two ways you could ask without sounding pushy?" Only after they propose do you add a script they can steal verbatim: *"To make sure we hit your go-live date, can you and I build a simple plan working backward from signature? I'll bring what I've seen work at similar companies; you tell me where legal and procurement usually add time."*

Step 5 — Rehearse out loud. This is the step managers skip and it is the one that changes behavior. You play the champion; the rep asks. Run it twice. The first attempt is always stiff. The second is usable. Ninety seconds of role-play beats twenty minutes of advice.

Step 6 — Commit to a specific, dated action. "What's the one question you'll ask, who will you ask, and by when?" Vague commitments produce vague follow-through.

Step 7 — Verify next week. Open the following session by checking the CRM record and the call. If the commitment was not kept, that is the topic — not the deal.

Timelines, effort, and what good looks like on a calendar

Treat this as a 30/60/90 build, because it is a habit, not a fact to be transmitted.

Days 1–30 — language and map. The rep learns what a paper process looks like, memorizes the five-question checklist, and role-plays it until it sounds like conversation rather than recitation. Expect two 30-minute sessions per week plus one longer 60-minute walkthrough of past closed-won deals. Realistically that's about three hours of manager time per rep in month one. The output you're grading is not deal progress; it's whether they can recite the checklist cold and deliver it naturally.

Days 31–60 — live application under review. The rep applies it on two real deals per week and you review the recordings together. This is where most of the skill actually forms, and where the failure mode is manager drop-off. Keep the cadence at one 30-minute session per week per rep. Across a team of eight, that's four hours a week of manager time — a real number, and the reason coaching quietly dies when a manager also carries an individual number.

Days 61–90 — self-correction. The rep arrives at deal reviews already mapped. Your job shifts from teaching to spot-checking and stretching into harder situations: multi-vendor bake-offs, a champion who loses their job mid-cycle, a procurement lead who opens with a demand for three bids.

On the buyer side, the ranges reps should learn to expect vary enormously by deal size and industry, so teach them to *ask* rather than to assume a number. That said, the shape is consistent: small transactional deals often have almost no formal process; mid-market adds a manager approval and a light security review; enterprise adds procurement, InfoSec, legal redlines, and sometimes a formal RFP. Legal redline cycles are frequently the single most underestimated step, because each round trip depends on the buyer's counsel's queue, not on your urgency. Security reviews in regulated industries — financial services, healthcare, government — routinely add weeks and can require documentation your team must assemble. Fiscal-year boundaries and budget freezes are hard walls that no amount of champion enthusiasm moves.

The practical coaching instruction is: for every step the rep identifies, they must capture three things — owner, expected duration, and what triggers the *next* step. A step with no duration is a wish. A step with no trigger is where deals go to stall, because everyone assumes someone else moves it forward.

Cost of getting it wrong is easiest to make concrete with the rep's own numbers. Take their average deal size, multiply by the deals that slipped a quarter last year, and compute the carried cost in quota attainment and commission timing. Reps respond to that arithmetic far more than to an abstract argument about rigor. The inverse framing works too: a rep who disqualifies a bad deal in week two reclaims six to eight weeks of selling capacity, which is usually worth more than the small chance the bad deal would have closed.

Where teams get this wrong

Rescuing the rep. The manager joins a call and asks the buyer-process questions themselves. The deal advances, the rep learns nothing, and the manager has just created a dependency. If you must ask on a live call, debrief immediately: "I asked that one — here's exactly why I phrased it that way. You take the next one."

Coaching the deal instead of the skill. Fixing this quarter's process map for one deal is a transaction. Building the rep's ability to map every deal is an asset. The tell is whether your session ends with an updated CRM field (deal coaching) or with a rehearsed script and a committed behavior (skill coaching). Do both, but never only the first.

No follow-through. A great session with no verification is entertainment. Reps quickly learn which commitments get checked. If you check every one for four weeks, follow-through becomes the norm; if you check none, the coaching cadence becomes theater within a month.

Uniform coaching across a mixed team. A green AE needs the map; a ten-year veteran needs a will nudge and maybe a conversation about why they're protecting a soft deal. Running the same session for both wastes the veteran's time and overwhelms the newcomer.

Confusing criteria with process. The technical error. Reps declare a deal qualified because they know what the buyer wants. Force the distinction verbally in every review: "That's criteria. Now tell me the process."

Mistaking a friendly champion for a route to signature. Champions are frequently sincere and frequently wrong about their own organization's process, especially about procurement thresholds and legal timelines they have never personally navigated. Coach reps to ask the champion "who else has bought software at this size here recently, and how did that go?" — it surfaces the real process without challenging the champion's credibility.

Turning it into an interrogation. Six blunt process questions in a row reads as a compliance audit. The fix is the mutual action plan framing: you're building a shared plan backward from the buyer's own deadline, and you need their input on where their internal steps add time. Same information, opposite emotional register.

Capturing it nowhere. If it lives in the rep's head or in call notes, it is not organizational knowledge. RevOps should provide structured fields — step, owner, duration, status — not a text area, because you cannot report on a text area, and what you cannot report on you cannot coach systematically.

Choosing the right intervention, and what to measure

Not every gap deserves a coaching session. Match the intervention to the diagnosis and to how widespread the problem is. If one rep is missing it, coach the rep. If the whole team is missing it, the problem is the system — the stage definitions, the required fields, the review ritual — and coaching individuals is treating symptoms. If a rep has been coached on the same gap three or four times with no change, you have crossed from coaching into a performance conversation, and continuing to coach is a kindness to no one.

On measurement, coach to leading indicators and let the lagging ones confirm.

Percentage of pipeline with a complete decision process. Define "complete" strictly — every step has an owner and a date — and report it weekly by rep. This is the single best proxy for whether coaching is landing, and it moves within two to three weeks of real coaching.

Process questions asked per call. Conversation-intelligence platforms can track keyword and topic coverage; behavior change appears here before it appears anywhere else. Watch it per rep, not just as a team average, because a team average hides the two reps who never ask.

Late-stage slip rate. The percentage of deals that were forecast to close in a period and moved out. Better process qualification should compress this specifically in the stages after "value confirmed," where legal and procurement surprises live.

Forecast accuracy at the rep level. Reps who genuinely map the process commit deals that close on the dates they name. Track commit-to-close variance in days, not just a percentage, because the direction and size of the miss tells you which step is being underestimated.

Disqualification velocity. Days from first meeting to closed-lost for deals that were never real. Well-coached reps kill weak deals faster. This number going *up* is a success signal, and you must say so out loud or reps will read it as punishment and stop disqualifying.

If the leading indicators climb but win rate and cycle time don't follow within a quarter or two, the problem is not qualification — it's more likely fit, pricing, territory, or comp design. Name that honestly rather than coaching harder against a wall.

Related questions

Should decision-process detail be required to advance a stage?

Yes, for stages after discovery. Make specific fields — steps, owners, dates — exit criteria rather than optional. Requiring them from the first stage creates fabricated data; requiring them before the proposal stage creates real conversations. Enforce it in the CRM, not just in policy.

How do you coach this without turning discovery into an interrogation?

Reframe it as a mutual action plan. The rep and buyer build a shared timeline backward from the buyer's own go-live date, and the rep asks where internal steps typically add time. It gathers identical information while positioning the rep as an ally in hitting the buyer's deadline.

What if the buyer genuinely doesn't know their own process?

Common in companies making their first purchase in a category. Coach the rep to offer a template — "here's how similar companies handled it" — and to identify who inside the buyer's org has bought comparable software recently. That person, not the champion, holds the real process knowledge.

How often should the process map be refreshed?

At every stage gate and after any significant event: a new stakeholder appears, a reorg, a budget shift, a legal requirement surfaces. Stale maps are more dangerous than missing ones because they create false confidence in a forecast that no longer reflects reality.

Does this apply to transactional SMB deals?

Proportionally. A one-signer, credit-card deal needs two facts: who signs and what triggers signature. Forcing an enterprise-grade map onto a two-week cycle wastes time and teaches reps the framework is bureaucratic. Scale the depth of the map to the size and complexity of the deal.

FAQ

What is the difference between decision criteria and decision process?

Criteria are what the buyer wants — features, integrations, security posture, price. Process is how they buy: the sequence of internal steps, the people who own each one, the approvals and gates, and the dates. Reps commonly learn the criteria, declare the deal qualified, and leave the actual buying workflow completely unexamined. Both must be documented; only the process determines the close date.

How do I get a rep comfortable asking about the decision process?

Rehearse it in a 1:1 until they've heard themselves say it naturally at least twice. Discomfort usually comes from unfamiliarity with the phrasing, not from the question itself. Pair the rehearsal with the buyer-service framing — "I don't want our paperwork to be the reason your go-live slips" — which changes the question from a sales demand into help the buyer wants.

What should a mapped decision process look like in the CRM?

Structured, not free text: each step as its own row with an owner, an expected duration, a status, and the trigger that starts the next step. A single close-date field is insufficient. If your CRM only offers a notes box, that is a RevOps problem to fix, because unstructured process notes can't be reported on and therefore can't be coached systematically across a team.

What if the buyer won't share their decision process?

Treat it as a qualification red flag rather than a personality quirk. Coach the rep to explain plainly that they need the internal steps to avoid delays, and to try once more through a different contact. Persistent refusal usually means either the deal isn't real or the champion lacks access to the process — both change how you should forecast it.

Should managers use call recordings for this, or is that heavy-handed?

Use recordings, and be transparent about why. Coaching from a rep's memory means coaching a rewritten version of the call. Frame it as reviewing evidence together rather than surveillance, pick one short window rather than the whole call, and always start by asking the rep what they'd change. Reps accept it quickly when the feedback is specific and useful.

How long before coaching this shows up in results?

Behavior changes fastest: questions asked per call can move within two weeks. CRM completeness follows in three to four. Late-stage slip rate and forecast accuracy need a full sales cycle to register, so on a 90-day cycle expect the lagging proof roughly one to two quarters out. Judge the program on the leading indicators before then.

Sources

• MEDDPICC explained — MEDDICC
• Gartner: The B2B Buying Journey
• Harvard Business Review: The New Sales Imperative
• Gong Labs — sales research blog
• Winning by Design resources
• RAIN Group sales research and blog
• Salesforce sales blog
• HubSpot sales blog

Related on PULSE

• [How do you validate that the person you are talking to actually has decision-making authority?](/knowledge/cg0953)
• [What single question helps you identify whether a gatekeeper has real decision-making power?](/knowledge/cg0924)
• [How do you coach a solutions consultant to qualify deals earlier?](/knowledge/cg0220)
• [How do you coach a rep to qualify out bad-fit deals early?](/knowledge/cg0055)
• [How do you qualify whether a lead is ready to buy or just gathering information?](/knowledge/cg0943)
• [What is your process for handling a prospect who brings up a competitor?](/knowledge/cg0944)