Sales Discovery Roleplay Interview: A Complete Practice Session

A sales roleplay can feel awkward even when you have handled real customers for years. You have limited product knowledge, a short clock, and an interviewer who may expect a different stage of the sales process from the one you prepared.

For an account executive discovery exercise, prepare a conversation that can change direction. This guide supplies a complete 12-minute simulation, a buyer brief for a practice partner, response branches, and an evidence-based review. It complements short cold-call drills by making you manage an entire scheduled discovery meeting.

Before you write a script

1. Confirm the exercise: cold introduction, scheduled discovery, demonstration, or negotiation.
2. Ask who the buyer is, what they already know, the allotted time, and the desired next step.
3. List approved product facts separately from capabilities you still need to verify.
4. Prepare a short opening, several follow-up questions, and a concise recap.
5. Rehearse at least one outcome where the buyer should not move forward.

Recent candidates describe inconsistent roleplay feedback and uncertainty about discovery versus pitching. A September 7, 2026 discussion from an experienced AE raised the first problem; an August 3 discussion about an SMB sales interview asked how to balance discovery, a competitor objection, and price. These accounts support practicing the format, but do not establish what every hiring manager scores.

Agree the rules before going into character

Ask: “Is this our first scheduled discovery after an introductory conversation, and are you playing the operations manager? Should I use only the product facts in the brief? What outcome would make this a useful meeting?” If the exercise instructions already answer these questions, acknowledge them rather than asking again.

Clarify whether interruptions are buyer objections or coaching from the interviewer. If feedback arrives mid-call, a quick “Would you like me to respond in the scenario or pause and discuss my approach?” prevents an unnecessary mismatch.

Research the company's public product information before the interview, but distinguish confirmed capabilities from marketing examples or assumptions. Never invent a customer story, integration, price, or financial result to make the roleplay sound polished. If the brief is intentionally incomplete, show how you would find the answer.

Use this complete practice scenario

Everything in this simulation is fictional. You sell a scheduling platform to multi-site retail teams. The approved brief includes an open-shift board, manager approval, and a weekly CSV export. It does not confirm payroll integrations, pricing, implementation time, or savings. You are meeting Morgan, an operations manager, after Morgan agreed to discuss shift coverage.

Your objective is to determine whether a more specific evaluation would be useful. A meeting booking alone is not proof of fit. The buyer may reasonably decline or reveal a requirement the platform cannot meet.

Buyer card: give this section to your practice partner. Morgan oversees four stores. Store managers fill gaps through separate group chats. The difficult part is knowing which requests remain unresolved. The existing payroll product works adequately, and Morgan does not want to replace it. Two last-minute gaps occurred last week, but their financial impact has not been measured. Morgan can evaluate operations workflows; finance approves spend, and an IT colleague reviews data handling. Those stakeholders have not joined the evaluation yet.

For the first run, Morgan is willing to explore a weekly export if it avoids retyping. For a second run, change exactly one constraint: automatic payroll synchronization is mandatory. The seller does not know whether it is supported. Reveal the facts in response to relevant questions rather than reciting the whole card at the start. Do not add new product capabilities to rescue the seller.

Run the 12-minute discovery meeting

The timing is a rehearsal constraint, not a mandatory sales formula. If the buyer identifies a decisive mismatch at minute four, investigate it instead of continuing through six more prepared questions.

For example, Morgan says, “We already have a scheduling system.” A weak response lists your features. A useful follow-up is, “Which part works well today, and what led you to agree to discuss coverage?” If Morgan explains the separate group chats, ask how a manager knows a request has been filled. Then explore what happens when that status is unclear.

When Morgan mentions two gaps last week, do not manufacture an annual loss. Ask whether that week was typical and what the team actually experienced. “Two gaps last week; frequency and financial effect unmeasured” is an accurate note. “Chronic understaffing costing thousands” is not supported.

Practice four branches instead of four canned rebuttals

“We are happy with our current vendor.” Acknowledge the constraint: “Keeping payroll in place makes sense. Is the coverage issue something you want to address within that setup, or is the current process working well enough?” If there is no meaningful problem or interest, close courteously. Do not create a problem for the buyer.

“Just tell me the price.” Be direct about what you know: “The brief does not give me an approved price, so I cannot quote one. I can arrange an accurate commercial answer. Are you checking against a fixed budget or comparing options?” If the buyer needs a price before further discussion, respect that condition and agree on the information needed to obtain it. Do not use discovery as an excuse to evade the question.

“Will this automatically update payroll?” Answer the capability boundary: “I can confirm the weekly CSV export; I cannot confirm automatic synchronization. Which payroll product and workflow must it support?” If automation is mandatory, make the next step a technical fit check before a broader demonstration. If the check later confirms incompatibility, say so and close the evaluation on that basis.

“Can you guarantee we will never have an uncovered shift?” Decline the unsupported guarantee: “I cannot promise that. We can evaluate whether managers can see unresolved requests and approve coverage more clearly. Staffing availability would still affect the outcome. Would that narrower evaluation help?” If the guarantee is essential, do not book a meeting under a false expectation.

Close on the decision the evidence supports

In the first run, suppose Morgan confirms that a weekly export may work and wants to investigate status visibility. A useful close is: “You want managers to see which coverage requests remain open while keeping payroll. We could use a fictional shift example to examine the board, approvals, and export. Would a 20-minute session with you and the person who handles that export be useful?” Confirm a specific time only after agreement; check who else needs to participate.

Your recap should distinguish agreement from pending work: “Morgan agreed to evaluate the coverage workflow. Payroll stays. Export suitability, commercial terms, and finance approval remain open.” Do not label the opportunity approved because an operations manager accepted another conversation.

In the second run, automatic synchronization is mandatory. Your close changes: “Before asking you to spend time on a demo, I will verify that requirement with our technical team. We can agree when and how I return with the answer.” That is progress toward an accurate decision even if it does not produce a booking.

Review what happened, then repeat one section

Ask your partner to mark five behaviors as observed, partly observed, or absent: confirming the scenario; following an answer with a relevant question; separating facts from assumptions; changing course when fit changes; and closing with accurate commitments. Have them identify the exact moment behind each judgment.

Then run a three-minute retry. If feedback says you pitched early, restate the specific correction: “I connected the platform before understanding how unresolved shifts are tracked. I will ask about that step first.” Repeat the exchange and visibly apply the change. You can discuss the broader tradeoff afterward.

For focused practice, use the SDR and BDR collection, especially listening when the buyer changes the problem and coaching with a specific before and after. These shorter exercises train components of the full meeting. Some answers require account or subscription access; this simulation is complete without them.

A hiring decision includes factors you cannot observe. After a real roleplay, request one concrete example of a strength and one behavior to improve. Keep the useful evidence, rehearse the change, and avoid turning either a booking or a rejection into a complete verdict on your selling ability.