60-Min Sales Training: Mapping the Decision Process

The outcome you should expect from one hour

The measurable output of this training is not knowledge — it is artifacts. At minute 60, every rep should be holding a completed Decision Map on their top three open opportunities with a real human name in each of the five boxes, at least one flagged blocker per deal, and one new committee meeting on the calendar. If reps leave with notes instead of names, the hour failed regardless of how good the discussion felt.

Set the bar explicitly at minute 0 so nobody treats the session as a lecture. The manager script that works is blunt: *"Pull up your single biggest open deal. I want one name in each of the five boxes. If a box is empty in five minutes, we are going to assume that role is working against us until we prove otherwise."* That framing does two things — it converts an abstract exercise into a live deal review, and it makes the absence of a name a finding rather than a shrug.

The behavioral outcome you are buying is multi-threading. Reps who single-thread — one contact, one relationship, one point of failure — get ambushed at procurement, at security review, or at the leadership meeting they were never invited to. Reps who multi-thread arrive at those checkpoints already known to the people running them. Gartner's B2B buying research has consistently found that enterprise software purchases now involve roughly six to ten active stakeholders, and that any individual buyer spends only a small fraction of their total buying time with any one vendor. If your rep is talking to one person out of eight, the math on how much of the buying process they actually see is grim.

The secondary outcome is forecast honesty. A deal where the rep cannot name the Economic Buyer is not a Commit deal, no matter what the rep says on the call. Once the five-box map becomes the standard artifact, forecast conversations stop being about gut feel and start being about verifiable coverage. That shift is worth more to a sales leader than the training itself.

Do not promise pipeline lift from a single hour. What one hour buys is a shared vocabulary, a completed artifact on three deals per rep, and a leading indicator you can inspect every Monday. Everything beyond that comes from the reinforcement cadence, not the session.

What drives the outcome: the five-box map and the blocker overlay

The framework teach is fifteen minutes and it covers exactly five roles. Each role gets one definition, one verification test, and one named risk. Definitions without verification tests are what produce fake maps — reps write "CFO" in the Economic Buyer box because that is what a CFO sounds like, and nobody ever checks.

Economic Buyer. The person who can say yes when everyone else says no, and no when everyone else says yes. Verification test: the rep has had a live meeting — not an email thread, not a forwarded message — where the Economic Buyer confirmed budget authority and discussed a dollar figure. The diagnostic question for the manager is *"what did the Economic Buyer say about price?"* If the rep cannot answer with something close to a quote, the box is unverified. MEDDPICC practitioners have long argued that early Economic Buyer engagement is the single largest swing factor on win rate; whatever the exact number in your own data, run the correlation on your last two quarters before you argue with it.

Champion. An internal advocate with power, influence, and a personal win tied to the project. The distinction that matters is Champion versus Coach. A Coach gives you information. A Champion spends political capital. Three-part verification test: (a) they have introduced you to the Economic Buyer, (b) they have shared an internal artifact — a budget memo, an internal deck, a screenshot of a Slack thread, and (c) they have used your name unprompted in a meeting you were not in. Two out of three is a Coach. Three out of three is a Champion. Teach reps to say the word "Coach" out loud when that is what they have; the self-deception is the expensive part.

Technical Validator. Usually a VP of RevOps, a Head of Data, or a Solutions Architect. They write the technical approval memo that procurement and legal wait on. Verification test: they have asked you for a SOC 2 report, the data model, or an integration spec. If they have not asked, they have not started, and your close date is fiction. This is the most commonly skipped box because the validator rarely shows enthusiasm — silence from a Technical Validator reads as "no objections" when it usually means "have not looked."

User Buyer. The two to four frontline managers whose teams will actually use the product. Verification test: at least one user manager has run a pilot, a hands-on demo, or a sandbox session. Procurement's first question in most intake processes is some version of "did the team evaluate it?" — a User Buyer who can answer yes shortens the security and legal path materially. Reps skip this box because the User Buyer "is not the decision maker," and then the deal dies in week nine when someone says the team never got to test it.

Procurement gatekeeper. Almost always a specific analyst or category manager, never "procurement" as a department. They own the MSA, the security review, and price negotiation. Verification test: the rep knows the analyst's name, their typical cycle time, and the company's standard payment terms — Net 30, Net 60, or Net 90. A rep who does not know whether the account pays Net 60 is going to be surprised by a two-week delay they could have planned around.

On top of the five boxes, apply the blocker overlay from the Challenger Customer taxonomy: tag every contact as a Mobilizer, a Skeptic, or a Talker. Mobilizers drive internal change and are worth disproportionate time. Skeptics can be converted with proof and are often your most durable advocates once flipped. Talkers are pleasant, responsive, and consume calendar time without moving anything. Coach reps to spend the large majority of committee time on Mobilizers and Skeptics.

The verbatim scripts reps rehearse in the room

Fifteen minutes of the hour goes to scripts, because the gap between "map the committee" and "actually get the Economic Buyer on a call" is language. Hand out a printed script card. Read each one aloud. Have every rep repeat the first three back before moving on — reading silently produces nothing under pressure.

Asking the Champion for the Economic Buyer introduction. *"You have been incredible at moving this forward. Before we get to a final proposal, we typically lose six weeks at procurement if I have not had a twenty-minute conversation with whoever signs the contract. Who is that person, and would you be willing to send a three-sentence intro this week?"* The mechanism is that it frames the introduction as protecting the Champion's timeline, not the rep's quota.

First call with the Economic Buyer. *"Thanks for the twenty minutes. I am not here to re-pitch — you have been briefed on the why. I have three questions. What would have to be true for this to be a yes by quarter end? What is the dollar amount above which this needs a different approval path? Who else in your leadership needs to sign off, and what do they need from me?"* The second question is the one reps skip and the one that most often reveals a board or committee threshold nobody mentioned.

Surfacing a hidden blocker. *"If I were a fly on the wall when you walk out of Thursday's leadership meeting, who would be the one person who pushed back hardest? What did they say? What would change their mind?"* Naming a specific meeting beats a generic "any concerns?" every time.

Pre-empting procurement. *"Before we send the redlined MSA over, can you put me in touch with whoever runs your procurement intake? I want to give them our SOC 2, the vendor questionnaire, and the price sheet now so we are not waiting two weeks later."*

Activating the User Buyer. *"You mentioned Marcus runs the team that will use this daily. Can we set up a thirty-minute hands-on session with Marcus and one or two of his managers? I want them to break the product before your CFO sees the contract."*

When the Champion goes dark. *"I have not heard back in eight days and I want to respect your time. Has something shifted internally I should know about? If this is no longer a priority I would rather hear that now than guess. If it is still a priority, what is the one thing I can do to make your life easier this week?"*

Getting the org chart onto the call. *"Can we spend the first five minutes next time drawing a box-and-arrow chart of who needs to bless this? I will share my screen and we build it together."* This is the highest-leverage script on the card, because it converts a guessing exercise into a collaborative one and the buyer almost always says yes.

Mobilizing a Skeptic. *"I heard you have concerns about the rollout timeline. That is fair. Can we get fifteen minutes — not so I can convince you, but so you can tell me directly what would have to change in our plan for you to be a yes."*

Then run three role-plays, five minutes each, pairing the most-tenured rep with the least-tenured, with a third rep observing. Round A: the Champion deflects the Economic Buyer introduction with "our CFO doesn't meet vendors until contract stage — just send me the proposal." Disqualifier: the seller agrees to just send it. Round B: a Head of RevOps is publicly silent but privately telling the Champion this overlaps with tooling they already pay for. Disqualifier: the seller never asks who would push back. Round C: a procurement analyst calls at week eleven demanding three redlines, a refreshed SOC 2, and a double-digit discount to move this quarter. Disqualifier: the seller offers a discount on the call. Score each seller one to five on named roles, verbatim script use, blocker surfacing, and whether a next step got booked with an actual date.

Benchmarks and realistic ranges to hold the team to

The leading indicator worth tracking is the percentage of open opportunities with all five boxes verified — verified meaning the test was passed, not that a name was typed. A reasonable ramp for a team starting near zero is roughly 60-70 percent coverage within 30 days and 80-85 percent within 60 days. Teams that hit 100 percent in week one are almost always self-reporting; audit five deals at random and check the Economic Buyer test specifically.

Expect coverage to vary by deal size. On deals under roughly $50K annual contract value, a full five-box map is often overkill — the Economic Buyer and the User Buyer may be the same person, and procurement may be a credit card. Set the rule at a deal-size threshold: full map required above your median ACV, three boxes (Economic Buyer, Champion, User Buyer) below it. Forcing a five-box map onto a transactional segment is how you get reps quietly fabricating names.

Cycle-length expectations should also be explicit. On a 60-to-90 day cycle, all five boxes should be verified by the end of week three or the deal slips a quarter. On a 6-to-12 month enterprise cycle, the Economic Buyer often is not reachable until after a technical evaluation, so the realistic sequence is Champion by week two, Technical Validator by week four, User Buyer pilot by week six, Economic Buyer by week eight, procurement pre-brief by week ten. Publish the sequence for your own median cycle rather than importing someone else's.

On multi-threading depth, a useful floor is three engaged contacts on any deal you intend to Commit, and five on anything above your enterprise threshold. "Engaged" means a two-way interaction in the last 21 days, not an email address in the CRM. Build the report so it counts inbound replies, not outbound sends — otherwise reps will hit the number by blasting.

For reinforcement, assume decay. Skills taught in a single session and never inspected regress substantially within a quarter. Budget a ten-minute map review in the weekly pipeline meeting and one full re-run of the role-plays at the 90-day mark. The re-run costs another hour and is cheaper than re-teaching from zero.

Finally, watch discount rate as a downstream signal. Panic discounting at the procurement stage is the classic symptom of a deal that was single-threaded — the rep has no Economic Buyer relationship to escalate to, so price is the only lever left. If average discount on late-stage deals drops after this training lands, the mapping is working even before win rate moves.

Risks, edge cases, and failure modes to name out loud

Coach mislabeled as Champion. The most common failure. The rep has a friendly, responsive contact who will not put the rep's name in writing to their leadership. Coach the rep to either elevate that person — ask directly for the introduction and see what happens — or find a real Champion elsewhere in the account. A Coach who is treated as a Champion produces a Commit forecast on a deal with no internal sponsor.

Procurement treated as an adversary. Procurement is a buyer with their own scorecard: cycle time, savings captured, risk avoided. Vendors who volunteer the security packet, the MSA, and the price sheet before being asked tend to move through intake noticeably faster, because they reduce the analyst's work. Coach reps to be procurement's easiest vendor of the quarter.

Skipping the User Buyer. Reps deprioritize the User Buyer because they cannot sign. Then in week nine someone in a leadership meeting asks whether the team tested it, the answer is no, and the deal moves to next quarter for a pilot that could have happened in week three.

Confusing title with power. The CFO is not automatically the Economic Buyer. On mid-market RevOps purchases it is frequently the CRO; on data infrastructure it is frequently the CTO; in founder-led companies it is frequently the founder regardless of the org chart. Verify by asking *"who has to sign off, and at what dollar threshold?"* rather than inferring from LinkedIn titles.

Outsourcing the mapping to tooling. Conversation intelligence and account intelligence platforms can surface stakeholder names from call recordings, email metadata, and community signals. That is genuinely useful for discovery. It is not verification. The rep still has to run the test for each role. A practical rule: if a rep cannot name the Economic Buyer without opening a tool, they do not know the Economic Buyer.

Fabricated maps under inspection pressure. The moment you report five-box coverage in a stand-up, you have created an incentive to type names into boxes. Counter it with spot audits — pick two deals per rep per month and ask for the evidence behind one box. Ask what the Economic Buyer said about price, or ask to see the internal artifact the Champion shared. Two audits a month is enough to keep the number honest.

Champion departure. In a long cycle, there is a real chance your Champion changes roles or leaves. A single-Champion deal has a single point of failure. On any deal above your enterprise threshold, require a second relationship at peer level or above, and note in the map who the backup would be.

Committee sprawl at the top end. Above a certain size, the committee stops being five roles and becomes five roles plus a steering group, a security team, a legal team, and possibly an external consultant. Do not try to map twenty people in a five-box worksheet. Add an overflow section listing everyone else with a single tag each — Mobilizer, Skeptic, or Talker — and focus the five boxes on the people who own the decision.

A practical rollout plan for the week after

The hour ends at 10:00 on Monday. What happens between then and Friday determines whether anything sticks. Give every rep four assignments with a named artifact and a deadline, and inspect all four.

By Tuesday EOD — complete the five-box Decision Map on the top three open opportunities. Named humans only. "The finance team" is not a name and does not count toward coverage. This is deliberately the day after training, while the language is fresh.

By Wednesday EOD — book at least one new committee meeting per deal. Acceptable forms are an Economic Buyer introduction call, a User Buyer pilot session, or a procurement pre-brief. One booked meeting per deal, three deals, is a realistic target for a full-time rep in one day of outreach using the scripts from the card.

By Thursday EOD — run the first User Buyer session on whichever deal is furthest along, and update the CRM so every mapped contact carries a Mobilizer, Skeptic, or Talker tag. Tagging in the CRM rather than a worksheet is what makes the data survivable past this week.

By Friday 4 PM — send the manager a one-screenshot recap showing the map and the booked meetings. One screenshot, not a document. The constraint keeps the artifact honest and takes the rep under five minutes.

The following Monday stand-up — report percentage of open opportunities with all five boxes verified, by rep, on a shared screen. Do not editorialize on the low numbers in week one; just show them. Public, unemotional inspection is what converts a one-hour session into a durable habit, and the number itself becomes the coaching agenda for the next several weeks of one-on-ones.

Related questions

How is this different from teaching MEDDPICC?

MEDDPICC is a full qualification framework covering metrics, pain, decision criteria, and competition. This hour isolates one slice — the human map — and drills it to a completed artifact. Teach MEDDPICC over a quarter; teach the Decision Map in an hour.

What if a rep insists there is genuinely only one decision maker?

Ask who signs the MSA, who runs security review, and who owns the budget line. If all three answers are the same person, the rep is right and it is a small or founder-led deal. If any answer differs, the map has more boxes than the rep thought.

Does this work for renewals and expansions?

Yes, and coverage tends to be worse there. Existing accounts have quiet committee turnover — the original Champion moves teams, a new Technical Validator arrives with opinions. Re-run the map at 90 days before renewal rather than assuming last year's contacts still hold.

Should the manager map their own deals during the session?

Yes. Managers who work a live deal alongside the team surface the same blank boxes reps do, which removes the pretense that mapping is easy. It also gives the room a worked example to argue with.

How do you keep the map current after week one?

Attach it to the opportunity record, not a worksheet. Make the five role fields required before a deal can move to a late stage, and review coverage in the weekly pipeline meeting for ten minutes. Anything living outside the CRM is dead within a month.

FAQ

What exactly does mapping the decision process mean in a 60-minute training?

It means identifying the six to ten people who influence, approve, or block a purchase rather than the single title the rep assumed was in charge. The session gives reps a repeatable method to name each role — Economic Buyer, Champion, Technical Validator, User Buyer, Procurement — on their actual live opportunities, with a verification test attached to each box so the names mean something.

Do reps need to bring their own deal data?

Yes. The hour is built around the top three open opportunities per rep, so reps should arrive with CRM access and their pipeline sorted by value. Reps without live deals — new hires, or someone who just closed everything — should work a recently stalled or lost deal instead, which often produces the most useful discussion in the room.

How fast can reps act on the scripts after the session?

Most reps can send the first multi-threading outreach within 24 to 48 hours, because the scripts are short and only require personalization with a name and one piece of account context. The rollout plan above assumes the first committee meeting is booked by Wednesday, which is achievable for three deals if the rep blocks two hours.

Is this only useful for SaaS sales?

The framework applies to any complex purchase with a buying committee of four or more people. SaaS is the most common context, but the same five roles show up in professional services, medical devices, industrial equipment, and enterprise hardware. What changes across industries is the sequence and the relative weight of the Technical Validator, not the existence of the roles.

If a rep already has a strong Champion, is the full map still necessary?

Yes. A Champion rarely closes a deal alone — they still need the Economic Buyer for budget, the Technical Validator for security sign-off, and Procurement for terms. A strong Champion accelerates access to those people; they do not substitute for them. Single-Champion deals also carry real risk if that person changes roles mid-cycle.

Does the training still apply to sales cycles longer than a quarter?

It applies, with adjusted timing. On long cycles the five boxes get verified over weeks or months rather than days, and the Economic Buyer typically comes late, after a technical evaluation. Publish a sequence keyed to your own median cycle length and use the coverage percentage as an inspection metric at each stage gate.

Sources

• https://www.gartner.com/en/sales/topics/b2b-buying-journey
• https://www.gartner.com/en/sales/insights/b2b-buying-journey
• https://www.meddicc.com/meddpicc
• https://hbr.org/2017/03/the-new-sales-imperative
• https://www.challengerinc.com/
• https://www.saastr.com/
• https://www.salesforce.com/resources/research-reports/state-of-sales/
• https://www.forrester.com/blogs/category/b2b-buying/
• https://www.linkedin.com/business/sales/blog
• https://blog.hubspot.com/sales

Related on PULSE

• [Empathy Mapping Exercise: Walking in the Buyer's Shoes Template](/knowledge/st0738)
• [Territory Mapping Workshop: Using Data to Prioritize Leads](/knowledge/st0732)
• [The Sales Process Audit Reboot — 60-Min Training](/knowledge/st211)
• [The Sales Process Documentation Reboot — 60-Min Training](/knowledge/st197)
• [Deal Desk Simulation: Cross-Functional Approval Process Roleplay](/knowledge/st0710)
• [Prospecting on LinkedIn: Interactive Template for a 20-Minute Sales Session](/knowledge/st0795)