Skip to main content
Loading...
sales

Map the Buying Process on a MEDDIC Discovery Call

Practice a MEDDIC discovery call with a guarded director who will share real buying-process details if you ask the right questions. Use it to map stakeholders, decision criteria, and the final approver without breaking rapport.

Every employee gets a seat — priced per employee in Performance & Learning, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Software · Saas · Business services · Operations

Overview

This roleplay template is a MEDDIC discovery call scenario built to help a seller map the buying process with a guarded director of operations. The learner is not trying to close the deal in one call; the goal is to uncover the current pain, the business impact, the decision criteria, the people involved, and who will actually approve the purchase.

Use it when a prospect has already shown interest and is evaluating workflow software, but the path to a decision is still fuzzy. The persona is professional and busy, so the learner has to earn detail through focused, consultative questions rather than pushing for a demo or talking features. That makes it a strong fit for reps who need practice with MEDDIC qualification, stakeholder mapping, and next-step control.

Do not use this template when the objective is cold outreach, product pitching, or handling a simple pricing objection. It is also not the right fit if your team needs a broad objection-handling scenario, because the core skill here is discovery discipline: asking for specifics, confirming assumptions, and leaving the call with a clear view of the buying path. The best attempts will sound natural, stay grounded in the director's context, and end with a concrete follow-up tied to what was learned.

How to use this template

  1. Read the situation first so you understand the prospect's context, the current pain, and the qualification goal before starting the roleplay.
  2. Start the conversation by asking about the workflow problem, the impact on the team, and what prompted the evaluation now.
  3. Probe for decision criteria, stakeholders, and the buying process by asking who else is involved, what matters most, and how the final decision will be made.
  4. Complete the roleplay against the scored rubric, making sure you have mapped the pain, the process, the people, and the likely economic buyer or approver.
  5. Review the feedback, note where you lost specificity or rapport, and retry with sharper follow-up questions and a clearer close.

Best practices

  • Lead with the prospect's operational pain before asking about vendors, timelines, or budget.
  • Use follow-up questions that force specificity, such as asking who owns each step of the decision and what each stakeholder cares about.
  • Mirror the director's language about manual handoffs, missed follow-ups, and reporting gaps so the conversation feels grounded in their reality.
  • Confirm the buying process in sequence, from evaluation to shortlist to approval, instead of collecting stakeholder names in random order.
  • Treat guarded answers as a cue to narrow the question, not to switch into a product pitch.
  • Close by summarizing what you learned and proposing a next step that matches the discovery gaps, such as a stakeholder review or tailored demo.
  • Avoid asking five questions in a row without acknowledging the answer, because that makes the director more defensive.

What this template typically catches

Issues teams running this template most often surface in practice:

Jumps into product features before mapping the prospect's current pain and business impact.
Asks vague stakeholder questions and accepts broad answers like "a few people will weigh in" without drilling deeper.
Fails to identify who the economic buyer or final approver is.
Does not clarify the evaluation process, leaving the buying path ambiguous.
Lets the conversation drift without confirming decision criteria or next steps.
Overtalks and loses rapport with a busy, guarded director.
Ends the call with a weak follow-up that is not tied to the discovery findings.

Common use cases

Mid-market SaaS rep qualifying a workflow automation deal
A rep is preparing for a live discovery call with an operations director who has been comparing workflow tools for several weeks. The rep needs practice uncovering how the team will evaluate options, who will weigh in, and who can say yes.
Sales manager coaching a rep on stakeholder mapping
A manager uses the scenario in a 1:1 coaching session after noticing the rep gets vague answers about decision makers. The roleplay helps the rep practice asking for names, roles, and approval flow without sounding interrogative.
Enablement workshop on MEDDIC qualification
A sales enablement lead uses the template in a group exercise to reinforce the difference between surface-level discovery and true qualification. The team compares attempts against the rubric to see whether they actually mapped the buying process.
Late-stage deal review before forecast submission
A rep uses the scenario to rehearse a call before a deal review meeting, where leadership expects clarity on decision criteria and the final approver. The practice helps the rep avoid bringing an unqualified opportunity into forecast.

Frequently asked questions

What does this roleplay help me practice?

This template is built for MEDDIC discovery, with a focus on mapping the buying process rather than pitching product features. You practice uncovering pain, decision criteria, stakeholders, and the likely economic buyer or final approver. It is especially useful when the prospect is willing to talk, but only if you stay consultative and precise.

Is this for early discovery or later-stage qualification?

It fits late discovery or qualification calls where the prospect has already shown interest and is evaluating options. The scenario assumes the director has been looking at workflow software for several weeks, so the goal is to clarify how the deal will actually move forward. It is not a cold-call opener or a generic needs-analysis exercise.

Who should run this roleplay?

Sales reps, sales managers, and enablement leads can all run it. Reps can use it for solo practice, while managers can use it for coaching on question quality, control of the conversation, and next-step clarity. It also works well in team practice sessions where one person plays the rep and another plays the director persona.

What makes this different from an ad-hoc discovery conversation?

The template gives you a realistic persona, a specific situation, and scored rubric criteria so the practice is repeatable. Ad-hoc roleplay often drifts into vague objections or feature talk, which does not train the learner to map the buying process. Here, the learner is pushed to ask for concrete names, roles, criteria, and decision flow.

How often should I use this template?

Use it whenever a rep struggles to move from interest to qualification, or before a pipeline review, forecast call, or discovery skills workshop. It is also useful after a lost deal when the team suspects the buying process was never fully mapped. Repeating the scenario helps reps build the habit of asking for specifics early.

What should I customize before using it with my team?

Customize the workflow software context, the company size, and the director's priorities so the scenario matches your sales motion. You can also adjust the persona's temperament, the level of resistance, and the rubric weights if your team cares more about stakeholder mapping or economic buyer identification. If your product sells into a different function, swap the title and pain points while keeping the buying-process structure.

What are the most common mistakes this scenario surfaces?

The most common misses are jumping to product fit too early, asking vague questions about stakeholders, and failing to confirm who owns the decision. Reps also often accept broad answers like "a committee will review it" without drilling into the actual path. Another frequent issue is ending the call without a clear next step tied to what was learned.

Can this be used with CRM or coaching workflows?

Yes. The notes from the roleplay can feed coaching plans, call reviews, and CRM fields for stakeholders, decision criteria, and next steps. It is also a good fit for onboarding because managers can compare the learner's attempt against the rubric and coach specific gaps. If your team uses call scorecards, this template maps cleanly to those fields.

Go deeper on the topic

Related concepts
  • A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
  • A frontline employee app is a phone-first application that gives hourly, field, and deskless workers access to their schedule, pay, announcements, training,...
  • A frontline worker is any employee whose job happens away from a desk — on a production floor, in a patient room, behind a store counter, in a customer's...

Ready to use this template?

Every employee gets a seat. Request pricing for Performance & Learning and we quote into a workspace with Map the Buying Process on a MEDDIC Discovery Call ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.