Map the Buying Process on a MEDDIC Discovery Call
Practice a second discovery call where you qualify a deal with MEDDIC, map the buying process, and identify the real decision makers before the opportunity goes stale.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Software · Saas · Technology
Overview
This roleplay template is a second discovery call for a mid-market software deal where the buyer has acknowledged a real operational problem but has not yet shared the full buying process. The learner practices qualifying the opportunity with MEDDIC: uncovering pain, quantifying impact, identifying decision criteria, mapping the decision process, and determining the economic buyer and likely signer.
Use it when a prospect is interested enough to keep talking, but the deal still feels fuzzy. The guarded director persona gives enough context to make the conversation realistic, but only reveals buying details when the learner asks the right questions in the right order. That makes it a strong fit for reps who need to move from product curiosity to real qualification.
Do not use this template for a first-call intro, a product demo, or a generic objection-handling exercise. It is also not the right fit if the buyer has already clearly shared budget, process, and stakeholders. The value of this scenario is in the gap: the learner must earn the information needed to decide whether the opportunity is real, who is involved, and what next step makes sense. By the end of the attempt, the rep should be able to summarize the buying process clearly and say whether the deal has a credible path to close.
How to use this template
- Read the situation carefully so you understand the buyer stage, the partial signals already on the table, and the specific qualification gap you need to close.
- Start the roleplay by asking the persona about the operational problem, the impact on the business, and what prompted the second conversation.
- Use a structured MEDDIC discovery flow to uncover metrics, decision criteria, decision process, economic buyer, and likely signer without sounding like a checklist.
- Complete the attempt and review the scored rubric to see whether you actually mapped the buying process or only collected surface-level interest.
- Retry the scenario with tighter questions and a clearer summary until you can state the pain, stakeholders, and next steps in a way the buyer would accept.
Best practices
- Lead with the buyer's operational pain before asking about budget or authority, because guarded directors usually open up only after they feel understood.
- Quantify the impact in the buyer's language by asking what the problem costs in time, rework, missed deadlines, or team capacity.
- Ask for the decision criteria as a real comparison process, not as a generic list of features, so you can learn what the buyer will actually use to choose.
- Map the decision process step by step by asking who reviews, who approves, who signs, and what happens after internal consensus is reached.
- Name the economic buyer explicitly and test your assumption, because the person you are speaking with is often not the final approver.
- Summarize the buying process back to the persona before ending the call so you can confirm whether your understanding is accurate.
- Avoid pitching features too early, since this scenario rewards qualification discipline more than product knowledge.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this MEDDIC discovery call template help me practice?
It helps you run a second discovery call that goes beyond surface-level interest and into real qualification. You practice uncovering pain, quantifying impact, mapping decision criteria, identifying the economic buyer, and learning the decision process. The goal is to determine whether the deal has a credible path to close, not just whether the prospect sounds interested.
When should I use this roleplay instead of a first-call discovery scenario?
Use it after an initial demo or early discovery call has already created interest. This scenario is built for the point where the buyer says there is a real operational problem, but budget, criteria, and decision path are still vague. It is not meant for cold outreach, product pitching, or a first-touch qualification conversation.
Who should run this practice scenario?
This is best run by sales reps, account executives, sales managers, and enablement leaders coaching discovery skills. It also works well for new hires who need structured practice with MEDDIC and for experienced reps who want to tighten qualification discipline. A manager or coach can score the attempt using the rubric and give targeted feedback on missed questions.
How often should a team use a template like this?
Use it during onboarding, before live discovery calls, and anytime a team is seeing weak qualification or stalled opportunities. It also works well as a recurring coaching exercise because MEDDIC skills improve through repeated reps with immediate feedback. Reps can retry the same scenario until they can clearly map the buying process in one conversation.
What is the main pitfall this scenario is designed to expose?
The most common failure is jumping from interest to solution mode before understanding how the deal will actually be bought. Reps often stop after hearing a pain statement and fail to identify the economic buyer, signer, decision criteria, or approval sequence. This template surfaces whether the rep can stay structured while still sounding natural.
Can I customize the persona or company context?
Yes. You can change the industry, company size, persona temperament, product context, or level of resistance while keeping the MEDDIC structure intact. Many teams customize the scenario to match their own sales motion, such as enterprise buying groups, mid-market operations leaders, or technical evaluators. The key is to preserve a guarded persona who only reveals information when the learner earns it.
How does this compare with an ad-hoc mock discovery call?
An ad-hoc mock call often turns into a loose conversation with no clear scoring or repeatable learning outcome. This template gives the learner a specific situation, a realistic persona, a defined objective, and rubric criteria tied to observable behaviors. That makes it easier to coach, compare attempts, and see whether the rep can actually map the buying process.
Does this template integrate with CRM or sales training workflows?
It can be used alongside CRM notes, call review, and sales coaching workflows, even if the roleplay itself is separate from your systems. Reps can practice the call, then translate the outcome into opportunity notes, MEDDIC fields, or next-step planning. It is especially useful when paired with call scoring, manager feedback, and follow-up action items.
Related templates
Ready to use this template?
Get started with MangoApps and use Map the Buying Process on a MEDDIC Discovery Call with your team — pricing built for small business.
