Guides
12 Sales Role Play Scripts and Scenarios for Rep Training
Use 12 sales role play scripts for discovery, objections, proof, implementation risk, stakeholder alignment, and next-step practice.
Guides
Use 12 sales role play scripts for discovery, objections, proof, implementation risk, stakeholder alignment, and next-step practice.
Published
Sales role play scripts are most useful when they define a believable buyer, a specific sales moment, a skill to practice, and a clear standard for success. They should give the rep enough structure to begin without supplying every line. The point is to practice judgment, not rehearse a tiny play.
The 12 scenarios below cover discovery, competitive pressure, price, internal approval, implementation risk, missing features, proof, expansion, and next-step control. Each one includes a buyer opening, a rep objective, a curveball, and pass criteria so a manager can run it with a partner or turn it into repeatable practice in Lira.
Turn your sales scenarios into practice with Lira
Treat each script as a controlled practice environment. The buyer role needs motives, constraints, and information it will reveal only if the rep asks useful questions. The rep needs an outcome to pursue and boundaries that prevent invented claims. Managers need a rubric that separates fluent talking from good selling.
Our recommendation is to run one skill at a time. A scenario that asks a rep to discover pain, position three products, handle procurement, negotiate price, and close the deal is not realistic training. It is six exercises wearing one trench coat.
| Script element | What to define | Why it matters |
|---|---|---|
| Buyer and context | Role, company situation, priorities, and current approach | Gives the conversation a credible point of view |
| Call stage | First discovery, evaluation, negotiation, expansion, or follow-up | Prevents the rep from using the wrong move at the wrong time |
| Rep objective | One observable outcome for the attempt | Keeps coaching focused |
| Facts and boundaries | Approved product facts, proof, limits, and prohibited claims | Tests accuracy as well as fluency |
| Curveball | One new fact, objection, or stakeholder constraint | Forces listening and adaptation |
| Pass criteria | Three to five behaviors the rep must demonstrate | Makes feedback specific and repeatable |
Use the buyer opening exactly once, then let the conversation move. The facilitator can use the curveball if the rep reaches the obvious path too easily. Pass criteria should be scored on what the rep actually does, not whether the fictional buyer agrees to buy.
Scenario: A revenue operations director requested a demo after comparing several products. The buyer has a real problem but has not agreed that this category is the answer.
Buyer opening: "We are looking at a few options. I can give you 25 minutes, but I do not want a generic pitch."
Rep objective: Establish why the buyer is evaluating now, how the current process works, and what a useful next step would need to prove. Curveball: the buyer names a feature before explaining the problem.
Pass criteria: The rep sets an agenda, asks a focused follow-up, connects the feature request to a workflowWorkflowA workflow is a defined sequence of steps, decisions, actions, delays, and outcomes used to complete a business process., and earns a buyer-owned next step. A feature tour before discovery is a miss.
Scenario: A sales leader says the team needs to improve conversion, but cannot yet identify where deals are breaking.
Buyer opening: "Our win rate is not where it should be. We probably need better training."
Rep objective: Turn a broad complaint into a specific behavior, segment, or stage that can be investigated. Curveball: the buyer offers a favorite theory without evidence.
Pass criteria: The rep tests the theory without insulting it, asks for a recent example, separates symptoms from causes, and avoids promising that one tool will fix an undefined problem.
Scenario: The buyer likes its incumbent and is exploring alternatives only because a new team has different requirements.
Buyer opening: "Our current vendor is fine. The issue is that our new region works differently."
Rep objective: Understand what must change while respecting what already works. Curveball: the buyer asks the rep to criticize the incumbent.
Pass criteria: The rep asks about the new requirement, distinguishes switching value from general dissatisfaction, and compares verified capabilities without inventing weaknesses.
Scenario: The buyer accepts the use case but says the proposal costs more than expected.
Buyer opening: "This is higher than the other option. I am not sure the difference is justified."
Rep objective: Clarify the comparison and revisit the buyer's evaluation criteria before discussing concessions. Curveball: the buyer asks for an immediate discount.
Pass criteria: The rep diagnoses the gap, ties the answer to stated value, stays inside approved commercial terms, and does not manufacture an expiring offer.
Scenario: The buyer believes the problem matters but says the budget is already committed.
Buyer opening: "I like the idea, but there is no budget until next year."
Rep objective: Separate true timing from weak priority and identify whether planning work is useful now. Curveball: the buyer is willing to continue only if the rep promises a future price.
Pass criteria: The rep confirms the budget reality, avoids false urgency, agrees on a sensible planning step, and makes no unsupported pricing commitment.
Scenario: The contact sees value but cannot make the decision alone. Finance and a senior sales leader will need different evidence.
Buyer opening: "I can see this helping, but I am not the person who signs off."
Rep objective: Map the decision, help the contact prepare, and propose a collaborative next step. Curveball: the contact wants the rep to send a generic deck.
Pass criteria: The rep asks what each stakeholder needs to believe, offers relevant material, and does not treat the contact as a courier or a blocker.
Build repeatable sales role plays with Lira
Scenario: The buyer asks for a capability that is not currently available and may be important to the first use case.
Buyer opening: "We need that integration at launch. Can you commit to it?"
Rep objective: Understand the requirement, state current capability accurately, and decide whether another path is genuinely viable. Curveball: the buyer asks for a roadmap date.
Pass criteria: The rep does not invent availability, distinguishes must-have from later-phase value, and is willing to identify a bad fit.
Scenario: The buyer has heard several confident vendor claims and wants evidence that applies to its situation.
Buyer opening: "Everyone says the same thing. Why should I believe your results?"
Rep objective: Clarify the evidence threshold, provide only support the company can stand behind, and narrow claims when needed. Curveball: the buyer asks for a guaranteed outcome.
Pass criteria: The rep names what is known, what depends on implementation, and what a pilot should prove. A guarantee or invented customer story is a critical failure.
Scenario: The buyer previously purchased software that was technically sound but poorly adopted.
Buyer opening: "The last platform created more work and nobody used it."
Rep objective: Understand what failed, surface ownership and adoption requirements, and propose a smaller proof. Curveball: the buyer wants a zero-effort implementation promise.
Pass criteria: The rep acknowledges the history, identifies the risky work, defines buyer and vendor ownership, and refuses to describe change as effortless.
Scenario: An executive joins late, has one minute, and wants the point without a replay of the whole discovery call.
Buyer opening: "Give me the short version. Why are we still talking about this?"
Rep objective: Summarize the business problem, decision, and evidence needed in the buyer's language. Curveball: the executive challenges one premise.
Pass criteria: The rep is concise, uses facts already established, answers the challenge directly, and hands the conversation back to a useful decision.
Scenario: A current customer is getting value in one team. The rep believes another team may have a related use case.
Buyer opening: "The first rollout is going well. I am not sure the other group has the same need."
Rep objective: Discover whether a distinct problem exists before proposing expansion. Curveball: the buyer offers access to the other leader but no clear reason for the meeting.
Pass criteria: The rep avoids assuming fit, asks for relevant differences, and earns an introduction around a specific hypothesis rather than a quota-shaped favor.
Scenario: A well-qualified evaluation has gone quiet after a productive meeting. The contact replies but avoids a decision.
Buyer opening: "We are still discussing internally. I will let you know when we have an update."
Rep objective: Clarify what remains unresolved and agree on a respectful next action or close the loop. Curveball: the buyer will not name a timeline.
Pass criteria: The rep makes the uncertainty specific, avoids pressure, offers a low-friction next step, and accepts that the correct outcome may be a later date or no active opportunity.
These scripts complement the sales objection examples, which focus on response structures, and the AI sales roleplay guide, which explains how dynamic practice and scoring should work. The sales training operating-model guide covers the separate decision about in-house, outsourced, and AI practice.
Lira turns a scenario brief into a spoken practice loop. Teams can start with the conversations that matter, let a rep talk naturally with an AI counterpart in the browser, review specific feedback, and try again. The current product page also describes shared scenarios, rubrics, passing requirements, scores, and certificates for a consistent readiness standard.
Lira should be the practice layer, not the owner of sales judgment. Enablement and sales leaders still decide which scenarios matter, what claims are approved, what good looks like, and when a person is ready for live calls.
Score observable behavior, not charisma. A rep can sound polished while missing the buyer's question, inventing a claim, or forcing the next step. Use this rubric as a starting point, then adjust the weights and passing requirements to the risk of the conversation.
| Criterion | 0 points | 1 point | 2 points |
|---|---|---|---|
| Opening and agenda | Starts pitching without context | States a generic purpose | Confirms time, purpose, and a buyer-relevant agenda |
| Question quality | Asks leading or irrelevant questions | Asks broad questions | Uses focused follow-ups that change understanding |
| Listening and adaptation | Ignores the buyer's answer | Acknowledges it but follows the script | Changes the next move based on what the buyer said |
| Relevance | Feature dumps | Connects some points to context | Explains only what matters to the buyer's decision |
| Accuracy and boundaries | Invents or overstates | Stays accurate but vague | Uses precise facts and names limits clearly |
| Next step | Pushes for commitment | Suggests an action | Agrees on a clear buyer-owned next step |
Twelve points is a convenient scale, not an industry standard. Set the passing threshold around the job and the consequence of error. Regardless of total score, treat fabricated claims, ignored opt-outs, disrespect, or unsafe advice as critical failures.
The best library is small enough to maintain. Ten current scenarios tied to real conversations are more useful than 100 generic prompts nobody owns.
Include the buyer and business context, call stage, rep objective, approved facts, boundaries, a realistic curveball, and observable pass criteria. Do not write the rep's full answer. The exercise should require listening and judgment.
Make it long enough to expose the target skill and short enough to repeat. A focused five-to-fifteen-minute practice can be more useful than simulating an entire sales cycle. Debrief one or two behaviors, then run another attempt.
No. Reps can memorize product facts, compliance boundaries, and useful question structures, but complete dialogue encourages cue matching instead of listening. Vary the buyer response while keeping the target skill and rubric consistent.
Yes. The current Lira product page says teams can turn their materials into scenarios, practice conversations around their products and objections, set a shared rubric and passing requirements, and review results. Lira is an AI sales roleplayAI sales role-playAI sales role-play is sales practice in which an AI counterpart plays a buyer and responds during a simulated conversation. and practice product, not an autonomous cold dialer or an all-in-one enablement suite.
See Lira in action with your sales scenarios
Lira product page for current positioning, browser-based conversation practice, feedback, repeat attempts, shared scenarios, rubrics, passing requirements, scores, and certificates.
Thoughtly AI sales roleplay guide for the related scenario-design, repetition, and readiness framework.
Thoughtly sales objection guide for response structures and objection-specific practice.
Vitaly Gariev photo 36733316, Ivan S photo 8117714, and Mikhail Nilov photo 9301305, used under the Pexels License. Pexels permits blog and website use and does not require attribution; credits are included for transparency.
Matheus Bertelli photo 18999481 for the business training discussion image, also used under the Pexels License.
A useful sales role play script creates a decision, not a performance. Give the rep a credible buyer, a narrow skill, accurate boundaries, and another attempt. The lines will change. The standard should not.
