9 Sales Roleplay Scenarios & Exercises (With Hyperbound AI Bots)

Disclaimer: This article was created in collaboration with Hyperbound, who sponsored this content – an AI sales roleplay and upskilling platform I’ve used as a customer to enable realistic, impactful practice at scale. The article contains affiliate links, meaning I may earn a commission if you book a demo or make a purchase through these links, at no extra cost to you. These partnerships support the blog, allowing me to continue providing free, valuable content. Everything I write is driven by my commitment to provide the highest educational value to my readers.

Introduction 

When I first explored the possibilities of AI sales roleplays in my article AI Sales Roleplay: 31 Use Cases for Your Business, I wanted to show just how versatile these tools could be. 

Whether it’s objection handling, discovery practice, or even full-cycle deal simulation, AI-powered practice is proving to be a game changer – especially for mid-sized and enterprise sales teams looking to scale coaching and drive measurable sales training efficiency.

But while that article focused on use cases, I wanted this one to take things a step further, by making it practical.

In collaboration with Hyperbound, I’ve built AI bots for the most common sales roleplay scenarios that you can try out for yourself. 

These bots simulate lifelike buyer interactions, giving reps the chance to practice key skills in a controlled, risk-free environment. 

Whether it’s a cold call or a discovery meeting, these scenarios are designed to sharpen the reps’ approach and build confidence.

Before we dive into these practice bots, though, it’s important to revisit the basics. 

The foundations of effective sales roleplays – clear objectives, realistic personas, and structured feedback – remain the same whether you’re practising with a colleague or an AI bot. 

In this article, I’ll cover these essentials and show you how to build strong buyer profiles (you will get to know my fictional CIO, Morgan Fischer, very well) and structure your scenarios effectively.

By the end, you’ll not only have access to AI-powered roleplay exercises but also the tools and insights needed to make them as impactful as possible. 

Let’s get started!

(Note: if you’d prefer to skip straight to the practice scenarios, you can click here to jump ahead.)

How to run effective sales roleplays 

As we just mentioned, before we jump into specific AI scenarios, let’s take a moment to revisit the basics. 

It doesn’t matter if the salesperson is roleplaying with a colleague, their sales manager, an outside coach, or an AI bot; the essentials of effective sales roleplays stay the same. 

At its core, roleplay is about practising conversations, sharpening specific skills, and building overall confidence in a controlled, safe environment.

To get the most out of these sessions, it’s crucial to follow a few timeless principles – ones that have made sales roleplays a cornerstone of great training for decades.

Key guiding principles

From setting clear objectives to refining through repetition, these fundamentals ensure every roleplay session delivers real-world value. 

Let’s explore the key ingredients that make a sales roleplay truly effective.

1. Clear objectives

Every effective sales roleplay starts with a clear goal. In other words, what does success look like in this scenario? 

Is it booking a meeting, overcoming objections, or simply moving the deal forward with clear next steps? 

Without well-defined objectives, reps can struggle to focus their efforts, turning the roleplay into an aimless exercise rather than a purposeful learning experience.

Clear objectives act as a compass for both the participant and the observer, providing structure to the session and ensuring everyone knows what they’re working towards. 

For example, if the goal is handling pricing objections, the rep can focus on steering the conversation toward value rather than getting sidetracked by unrelated topics. Meanwhile, the observer or coach can evaluate how effectively the rep achieves this outcome.

Objectives also make feedback more actionable. 

When reps know exactly what they are supposed to achieve, it’s easier to pinpoint areas for improvement and celebrate successes. 

For instance, if the objective was booking a meeting but the rep didn’t ask for a firm commitment, feedback can zero in on closing techniques.

Whether you’re running traditional roleplays or using AI bots, defining objectives upfront is non-negotiable.

2. Realistic buyer personas

In order to truly prepare reps for real-world conversations, the buyer persona in the roleplay needs to feel authentic, complete with specific characteristics, goals, pain points, motivations, and opinions. 

(We will go into far more detail about building buyer personas later in the article.)

Realistic buyer personas are essential for reps to sharpen their ability to tailor their approach. 

For example, a persona might represent a procurement manager concerned about cost efficiency or a tech leader prioritising scalability. 

Depending on your product and the industry that you’re targeting, your sales team might be talking to a whole slew of personas. 

By practising with detailed, custom-tailored personas, reps learn to align their messaging with what matters most to the buyer, whether it’s solving operational challenges, achieving strategic goals, or anything else.

These personas also teach reps to uncover deeper insights during discovery calls. 

Imagine a roleplay where the buyer is facing inefficiencies due to outdated software. The rep can practice asking probing questions to uncover the root cause of the problem and position their solution effectively.

The more lifelike the persona, the better equipped your team will be to handle real-world conversation intricacies and build meaningful connections.

3. Situational realism

Once you’ve built a well-defined buyer persona, the next step is to place them in a realistic situation. After all, even the most detailed persona won’t feel authentic if the context surrounding them is vague or disconnected from real-world scenarios. 

The more specific and relatable the situation, the better prepared your reps will be to handle similar real world buyer interactions.

Situational realism entails providing a clear and realistic context for the interaction:

• How was the prospect contacted? 
• Are they responding to a cold email, following up after a demo, or engaging in a renewal discussion? 
• What’s their mindset: are they curious, sceptical, or under pressure to make a decision? 
• What recent event or change might have triggered this conversation? (e.g. budget cuts, leadership change, market shifts)
• Is the buyer evaluating multiple solutions, or are you the first one they’re speaking to?
• Are there any internal blockers or competing priorities they’re dealing with?
• How familiar are they with your solution or similar tools?
• What’s at stake for them personally or professionally if this decision goes wrong?

These details shape how reps approach the conversation and adapt their messaging.

Consider this: a roleplay scenario might involve a buyer who was referred by a mutual connection but is hesitant about switching from their current solution. 

This setup allows the rep to practise building rapport based on trust while addressing objections tied to loyalty or perceived switching costs. 

With this level of detail, the roleplay becomes far more realistic and impactful. 

Realistic situations also help reps develop empathy. 

By understanding not just who the buyer is but also what they’re experiencing in that moment, reps can practice responding in a way that feels thoughtful and personalised. 

This ability to connect authentically is often what separates great salespeople from good ones.

Situational realism is essential for bridging the gap between practice and performance. It’s what makes every interaction feel like a true test of skill rather than just another exercise.

4. Focus and brevity

One of the most common mistakes I’ve seen sales and enablement teams make when it comes to sales roleplays is making them too long and/or without a clear focus.

Trying to cover too much in a single session can overwhelm reps and dilute the learning experience. 

Instead, each roleplay should have a clear focus, targeting one or two specific skills or objectives at a time. 

Whether it’s objection handling, active listening, effective questioning, or closing techniques, keeping the scope narrow allows reps to dive deeper and refine their approach.

Of course, there are some exceptions to this rule, like, for instance, discovery call roleplays. This is simply due to the fact that discovery calls tend to be long themselves and because they are arguably the most unpredictable of scenarios that can be covered in roleplays. 

It should be pointed out, however, that even discovery call roleplays should not be analysed only as a whole. 

I’ve found that discovery calls can be divided into more or less distinct parts that can be individually assessed, analysed and then improved on in shorter, more focused roleplays.

But to get back to the original point. 

Roleplays that drag on can lose their impact, especially when attention spans wane. 

By focusing on critical moments of the sales process, such as the initial cold call, navigating gatekeepers, overcoming objections, or closing the deal, you can keep sessions short and engaging while maximising their value. 

For example, a five-minute roleplay centred on handling pricing concerns is far more effective than a sprawling 20-minute exercise that tries to cover seven different things.

This combination of focus and brevity also makes it easier to iterate. 

Reps can practice the same scenario multiple times in quick succession, refining their skills with each attempt. 

The goal is to create targeted opportunities for growth that build confidence over time.

5. Structured and actionable feedback 

One of the most overlooked elements of sales roleplays is valuable feedback, and too often, it’s delivered in a vague or unstructured way.

Some managers or coaches may assume that the occasional comment based on instinct or overall impression is enough.

But for feedback to truly drive growth, it needs to be specific, balanced, and grounded in structure.

Let’s start with structure. 

Using a scoring system or scorecards can help break down performance into specific elements like opening, questioning, objection handling, agenda setting, and closing. 

For example, you might rate how well a rep builds rapport or handles pricing objections.

This structure ensures feedback is clear and focused, giving reps tangible areas to work on rather than broad generalisations like “You need to be more confident” or “That was pretty good overall.”

Just as important as structure is starting with what went well.

Reps are far more open to feedback when they first hear what they did right.

Whether it’s their calm under pressure, their thoughtful questions, or their ability to stay composed, positive reinforcement builds confidence and trust, setting the tone for a more productive conversation.

From there, you can shift into constructive areas: what could be improved and how.

This transition is very important. It makes feedback feel less like criticism and more like guidance, especially when it’s paired with actionable suggestions.

Lastly, create space for immediate do-overs.

Giving reps the chance to re-run scenarios right after receiving feedback is one of the quickest ways to turn insights into progress. 

For instance, if a rep struggled with handling a specific objection in their first attempt, they can immediately apply the suggestions from the feedback in their second run, reinforcing the learning while it’s still fresh in their mind.

When feedback is structured, starts with strengths, and includes space to immediately practice the improvements, you create a learning environment where growth feels clear, safe, and genuinely motivating.

6. Repetition and iteration

Repetition is the secret weapon of any effective sales roleplay. 

Practising the same scenario over and over again allows reps to refine their approach, build confidence, and internalise key techniques until they become second nature. 

Rome wasn’t built in a day.

Traditional sales roleplays, while valuable, often fall short when it comes to repetition. 

They require another person, a colleague, manager, or coach, to play the buyer, which can be time-consuming and logistically challenging. 

Scheduling conflicts, limited availability (both of the seller and the person playing various customer types), and the need for preparation all make frequent practice difficult to achieve. 

As a result, reps might only get a handful of opportunities to rehearse critical scenarios before facing them in the real world.

This is where AI sales roleplay tools truly shine. 

With AI, reps have access to infinite repetitions without relying on another person’s availability. They can run through scenarios as many times as they need, whenever they feel like doing it. 

This allows them to experiment with different approaches and learning from their mistakes. 

For example, a rep struggling with objection handling can practice dozens of variations of the same scenario until they feel confident addressing even the toughest pushbacks.

By combining repetition with iteration, reps can turn every roleplay into a powerful learning experience. It’s this ability to practice endlessly and adaptively that makes AI roleplay tools an invaluable resource for modern sales teams.

That said, sales managers and enablers still play a vital role. 

They should regularly review how reps are using these tools and, where possible, build on the AI-generated objective feedback to deliver even more tailored and specific sales coaching. 

By doing so, they not only save time but also sharpen the precision and impact of their guidance, creating an effective blend of human and AI-enabled development.

Turn sales call insights into revenue-driving action

Hyperbound analyzes real sales calls in the context of live deals and surfaces exactly what reps need to fix — then reinforces it with realistic AI roleplays. The result: faster ramp, better deal execution, and more consistent performance.

TAKE ME THERE

Sponsored: I may earn a commission if you purchase through this link. I only partner with tools I’ve personally used or rigorously tested, and that I genuinely trust.

Essential components of a realistic roleplay: creating a strong buyer profile

As we have already touched upon, the foundation of any realistic sales roleplay lies in the strength of the buyer profile. 

A well-crafted persona makes the roleplay feel authentic and also equips reps with the context they need to practice tailoring their approach, asking better questions, and navigating complex conversations. 

This is especially critical when using AI bots, as the quality of the persona directly impacts the quality of the practice.

Key elements of the buyer profile

The following are the key elements that will help you build a buyer profile for any roleplay scenario. 

You can check out my full guide to building B2B buyer personas here if you want to go into more detail.

As you’ll see later, these are the same elements I used to build the buyer personas for the scenarios I created in Hyperbound.

1. Clear instructions for the rep

Before diving into the roleplay, reps need clarity on what they’re stepping into. This includes:

The aim of the roleplay: Is the goal to book a meeting, handle objections, or close a deal?

Scenario overview: Provide a high-level scenario overview (e.g., “The buyer is aware of their problem but unsure about available solutions” or “The buyer is using a competitor solution but dissatisfied with its performance”).

Call context: Set the stage by explaining how this interaction came about – was it a cold call, a follow-up after a demo, or an inbound inquiry?

These instructions give reps a clear starting point and help them stay focused during the roleplay.

2. Personal details of the buyer

Personal details add a human touch to the persona and help reps practise building rapport. These can include things like:

• Career path (e.g., rose through the ranks in their current company, recently hired)
• Years in their current role
• Previous work experience 
• Communication style (e.g., direct, collaborative)
• Hobbies and interests

While these details are optional, they can make the roleplay feel more lifelike and help reps connect more naturally in the conversation.

3. Company details

When building buyer personas, company details provide crucial context that creates the conditions for a more realistic interplay between the seller and the fictitious buyer. 

These details shouldn’t just paint a broad picture – they should go deep into the company’s operations, goals, and current state

Industry and specialisation: Defines the company’s niche within its industry. 

For example, in this article’s scenarios, the company is DanFran Production A/S, which specialises in custom wooden furniture and interior design solutions. 

This specificity enables reps to speak directly to industry pain points or trends, such as sustainability or supply chain optimisation.

Location and workforce: Includes the company’s headquarters and workforce size. 

In my scenarios, the company is based in Copenhagen with around 210 employees. 

This gives reps insight into the company’s scale, which can influence their approach, for example, tailoring solutions for mid-sized businesses versus large enterprises.

Annual revenue: Knowing the company’s revenue.

In my example, it is €50 million annually. This helps reps gauge their financial capacity and position solutions accordingly. 

Strategic focus areas: Highlights what the company is prioritising. 

DanFran Production A/S is currently modernising production processes and inventory management to become more agile, efficient, and sustainable. This focus gives reps a clear idea of how their product or service can align with the company’s goals.

Tech stack: Details the company’s existing technology infrastructure and software solutions. 

Since my buyer persona will be the CIO of DanFran Production A/S, I’ve included specific information on their IT infrastructure setup: 

• Hardware/infrastructure: Cisco networking, Hewlett-Packard Enterprise servers.
• Software tools: Microsoft 365 for collaboration, Microsoft Azure for cloud services.
• Operation model: Primarily on-premises IT hardware with in-house integration.

Information like this helps reps identify gaps or opportunities where their solution could enhance or complement the current setup.

Financial model: Includes insights into how the company approaches spending. 

For instance, DanFran Production A/S is shifting from CAPEX to OPEX and as-a-service models to become asset-light. 

This detail allows reps to frame their offering in a way that aligns with the buyer’s financial priorities as they learn about this during the conversation (reps won’t necessarily know this information ahead of time). 

By incorporating these elements into buyer personas, reps can practice crafting messaging that resonates deeply with the prospect’s organisational context.

4. Organisational structure

Understanding organisational structure is critical for preparing reps to navigate multi-threaded deals and engage effectively with stakeholders. 

Reporting lines: Identifies who the persona reports to and their level of influence within the organisation. 

In my scenarios, the persona reports directly to the CEO, highlighting their strategic importance.

They are responsible for leading IT planning to support business growth, making them a key decision-maker in digital transformation initiatives.

Team composition: Details who works under them and their specific roles:

My persona’s IT team includes a CISO named Michael Thompson, who focuses on security transformations and advanced IT initiatives.

It also includes Julia Strau, the IT Operations Manager, who ensures smooth day-to-day IT activities but relies on external help for complex tasks.

Cross-Functional influence: Highlights how this persona interacts with other departments or teams. 

In the case of DanFran, their team drives digital transformation projects that impact multiple areas of the business.

They collaborate closely with external vendors for advanced IT solutions.

Decision-making style: Include insights into how decisions are typically made within this structure.

Does this persona have autonomy in purchasing decisions?

Are approvals required from higher-ups or other departments?

Is the buying process formalised (e.g. through procurement or legal), or more informal and relationship-led?

By fleshing out organisational structure in this way, buyer personas become far more useful to practice with, enabling reps to practise engaging with multiple stakeholders effectively while addressing internal dynamics.

5. Buyer priorities and motivations

A strong persona should reflect what the prospect’s goals, motivations and priorities are:

Priorities and goals: What are they trying to achieve? For example, are they focused on reducing costs, increasing efficiency, or scaling operations?

Motivations: Why are these goals important to them? Is it tied to personal KPIs or broader company objectives?

By practising with personas that reflect real-world priorities, reps can hone their ability to align their pitch with what resonates most.

6. General opinions

Adding nuance to the persona’s perspective makes interactions more dynamic:

• Their opinions on the organisation, processes, leadership, colleagues, and more. 
• Industry-related frustrations or trends they’re navigating.
• Any specific attitudes toward change or risk-taking.

For example, a persona might feel frustrated with outdated processes but sceptical about adopting new technology due to past failures. 

7. Awareness of the problem

Understanding what the buyer knows about their pain points is critical: 

Are they aware of their problem? 

If so, how did they come to this realisation?

Include measurable details where possible (e.g., “Last quarter, production downtime was 7% of total production hours due to inventory issues”).

8. Awareness of solutions

A realistic persona should also reflect what the buyer knows (or doesn’t know) about potential solutions:

Are they trying to fix it internally or looking into external products?

What are their opinions on these solutions? For example, do they see them as too expensive or not scalable enough?

These details allow reps to practice positioning their product effectively against competitors or alternative approaches.

9. Existing solutions

If the buyer is already using another solution:

Why did they choose it over alternatives?

What problems does it solve for them, and what frustrations remain?

For instance, a persona might be using a competitor product but find it overly complex or lacking in customer support. 

This gives reps an opportunity to practise highlighting differentiators.

Complete example: a fully developed buyer profile

To illustrate what a fully developed buyer profile looks like, I’ve created one in Hyperbound that we will be using for the various sales conversations. 

As you will find out, the majority of the information about the person in question, their company, their opinions, and challenges will remain the same throughout the various scenarios. 

Like I mentioned earlier, my buyer persona is the CIO of DanFran Production A/S, more precisely, Morgan Fischer. 

Here is a bit more information about DanFran Production A/S:

The next is the organisational structure:

The next things I set up for Morgan are his (and his company’s) main priorities:

I also defined the most common objections that Morgan raises.

These are most likely to change from one scenario to another (I wanted to make the scenarios relevant and varied if you decide to give them a spin). 

Here are some opinions that I “gave” Morgan for the first scenario that I’ve created – the cold call:

As you can see, I’ve set the call scenario (remember this is for the cold call scenario) where Morgan is aware of the problem. This is what he knows about the problem: 

There will also be scenarios (e.g., the discovery call) where I put that Morgan is aware of the solution and knows something about it. Like this:

I’m sharing these as a strong example of what a well-defined buyer persona for sales roleplays can look like. 

And while they’re detailed, the good news is that with AI, you can build personas like these very quickly – Hyperbound lets you create solid buyer profiles in just a few minutes.

At this point, you’re probably saying, “Finally, scenarios! It was about time!”

So here we go!

Turn sales call insights into revenue-driving action

Hyperbound analyzes real sales calls in the context of live deals and surfaces exactly what reps need to fix — then reinforces it with realistic AI roleplays. The result: faster ramp, better deal execution, and more consistent performance.

TAKE ME THERE

Sponsored: I may earn a commission if you purchase through this link. I only partner with tools I’ve personally used or rigorously tested, and that I genuinely trust.

Sales roleplay scenarios & exercises (with AI practice bots)

Finally, we come to the meat of the article: the scenarios that you and your team can use to sharpen your selling skills. 

I have created 9 different scenarios in Hyperbound to give you a feel of how the tool simulates those: 

For each of the scenarios, besides the bot that will be available for you to try out, I will define the following:

• Call type – cold call, discovery call, competitive discussion, etc.
• Context – what you are selling and to whom
• Objective – setting up a discovery call (on a cold call), getting past the gatekeeper, initiating an upsell motion, etc.
• Objections/concerns – these will be raised by the buyer bot
• Key skills to practice – the goal of every roleplay scenario should be to focus on different skills (the more narrowly defined, the better)
• Roleplay exercise – what the seller and the prospective customers will be trying to do on the call (this will become clearer once we get into individual scenarios)
• Success criteria – usually one main objective (mentioned earlier), complemented by a few smaller wins
• AI practice bot – a bot you can try out in Hyperbound that will allow you to practice the specific sales roleplay scenario

Hopefully, the majority of you will want to try out the scenarios, so here is a bit more about your company and product:

Okay, so now that you know who you are and what you’re selling, here are some scenarios for you.

Scenario #1: Cold call roleplay

Call type: Cold call

Context:

You are a sales rep at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context). 

Your prospect, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context).

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Objective:

Your goal is to engage Morgan in a conversation and book a follow-up discovery call to explore his challenges further.

Objections/concerns: 

• “Our IT team is relatively small and inexperienced, and I am afraid introducing a new platform will only add complexity to our infrastructure.”
• “Our budget is tight, and we are not allowed to spend any money within the current fiscal year.”
• “I haven’t heard about you before, and nobody in my network has referred you to me within this context you are offering.”

Key skills to practice:

• Crafting strong openers to capture attention.
• Handling objections without sounding defensive.
• Asking appropriate, open and probing questions. 
• Practice different cold calling techniques
• Creating enough curiosity for the prospect to want to learn more.

Roleplay exercise:

• Rep’s role:
  • Initiate the conversation with an engaging opening.
  • Use active listening to respond to Morgan’s tone and objections.
  • Ask appropriate, open and probing questions, don’t stop at the surface level. 
  • Position the value of the solution effectively without pushing too hard.
  • Secure commitment for a follow-up call.
• Prospect’s role (AI bot):
  • Push back based on the predefined objections.
  • Stay skeptical but open to persuasion if the conversation is compelling.

Success criteria:

• The rep secures a follow-up call.
• The prospect expresses interest or curiosity, even if not fully convinced yet.

Scenario #2: Warm call roleplay

Call type: Warm call

Context:

You are a sales rep at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context). 

Your prospect, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context).

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Morgan filled out your contact information on this company’s website, and he may be expecting your call.

Objective:

Your goal is to engage Morgan in a conversation, do some pain investigation, and book a demo to show the product in action.

Objections/concerns: 

• “Our IT team is relatively small and inexperienced, and I am afraid introducing a new platform will only add complexity to our infrastructure.”
• “Our existing data infrastructure was built ad-hoc, we have a lot of different parts from various vendors and we’re worried about how a new solution will integrate.”
• “I know your solution is supposedly low-code, but I’ve heard horror stories of tools like that which turned out to be very difficult to use.”
• “My IT team has limited proficiency and bandwidth for trying out new stuff.”

Key skills to practice:

• Using effective questioning and active listening to learn what made the buyer get in touch.
• Building trust so that the buyer shares the underlying pains and costs of inaction. 
• Addressing concerns and objections without sounding too pushy or salesy.

Roleplay exercise:

• Rep’s role:
  • Approach the conversation from a consultant’s instead of a salesperson’s POV.
  • Use active listening to learn more about Morgan’s situation, pains, and concerns.
  • Position the value of the solution effectively without pushing too hard.
  • Schedule a demo of the product (make sure to ask who else could benefit from attending the demo).
• Prospect’s role (AI bot):
  • Push back based on the predefined objections.
  • Learn more about the EdgeFlow product.
  • Stay skeptical but open to persuasion if the conversation is compelling.

Success Criteria:

• The rep secures a demo.

Scenario #3: Discovery call roleplay

Call type: Discovery call

Context:

You are an AE at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context).

Your prospect, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context).

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Morgan spoke to an SDR from your company, and he heard some things that he liked about the platform you are selling.

He wants you to help him build a business case for the platform that he can present to the CEO, his team, and the rest of the company.

Objective:

Your goal is to engage Morgan in a deep conversation, learn as much as possible about their motivations, priorities, and pains, and collaborate on building a business case.

Objections/concerns: 

• “Our IT team is relatively small and inexperienced, and I am afraid introducing a new platform will only add complexity to our infrastructure.”
• “Our existing data infrastructure was built ad-hoc, we have a lot of different parts from various vendors and we’re worried about how a new solution will integrate.”
• “I know your solution is supposedly low-code, but I’ve heard horror stories of tools like that which turned out to be very difficult to use.”
• “My IT team has limited proficiency and bandwidth for trying out new stuff.”
• “Our budget is very tight, but if the business case is sound, you have a chance.”

Key skills to practice:

• Setting up a clear agenda and an upfront contract at the beginning of the call. 
• Using effective questioning and active listening to learn about the current situation at DanFran concerning the data infrastructure.
• Directing the conversation in such a way that the buyer will share the underlying pains and costs of inaction. 
• Acting as a trusted advisor, not just another vendor player. 

Roleplay exercise:

• Rep’s role:
  • Approach the conversation from a consultant’s instead of a salesperson’s POV.
  • Use active listening to learn more about Morgan’s situation, pains, and concerns.
  • Learn as much as possible about DanFran’s current data infrastructure, the money they are losing by not acting, and their main priorities. 
  • Position the value of the solution effectively without pushing too hard.
  • Collaborating with Morgan to help him build a business case for the EdgeFlow platform.  
• Prospect’s role (AI bot):
  • Push back based on the predefined objections.
  • Learn more about the EdgeFlow product.
  • Explain how the company requires a super-strong business case before the deal can move forward.

Success Criteria:

• The rep secures a collaborative workshop with Morgan and the entire IT team to demo the solution.
• The rep helps Morgan identify and define a few key value metrics to build a business case that can be presented to the rest of the company, including the CEO. 
• The rep learns what the buying process is like at DanFran, who also needs to be involved, what the budget is, what the priority is, and what the timeline looks like from the buyer’s side. 
• The rep gets Morgan’s buy-in to set up a digital sales room for the deal.

Scenario #4: Gatekeeper handling roleplay

Call type: Gatekeeper handling

Context:

You are a sales rep at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context). 

Your prospect, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context).

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Morgan has an assistant who acts as his gatekeeper, you know nothing about the gatekeeper. 

Objective:

Your goal is to get past the gatekeeper to talk to Morgan.

Objections/Concerns in This Scenario:

• N/A

Key skills to practice:

• Building rapport with a gatekeeper you initially know nothing about.
• Sharpen the ability to “read” the mood of the gatekeeper.
• Building confidence in trying different approaches to speaking with gatekeepers.
• Practice dealing with particularly tough gatekeepers

Roleplay exercise:

• Rep’s role:
  • Initiate the conversation with the gatekeeper
  • Use active listening to build rapport with the gatekeeper.
  • Find a way to persuade the gatekeeper that Morgan would not want to miss this call.
• Prospect’s role (AI bot):
  • Gatekeepers be gatekeepin’

Success criteria:

• The rep gets through to Morgan
• The rep gets an informal promise from the gatekeeper that they will inform Morgan of the attempt.
• The rep learns something about how Morgan prefers to be reached out to.

Scenario #5: Renewal call roleplay

Call type: Renewal call

Context:

You are an AE/AM/CSM at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context). 

Your customer, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context).

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Morgan’s company has been using EdgeFlow’s platform for three months, but you are seeing some usage statistics that show it hasn’t been adopted fully. You wish to be proactive and make sure you are on the same page and there is no churn risk.

Objective:

Your goal is to find out why DanFran is not adopting the EdgeFlow platform and using its capabilities fully. You wish to make sure that the renewal will be a non-event.

Objections/concerns: 

• “Some of the KPIs are still not improving, for example, inventory management when your company starts working with new vendors (companies that sell raw materials or components needed for the furniture).”
• “Some of the IT team and the rest of the company are unwilling to experiment with the platform to take advantage of its low-code nature (maybe a workshop or training are needed).”

Key skills to practice:

• Using effective questioning and active listening to learn about the current state of the product’s adoption.
• Problem-solving and guiding towards a collaborative solution to the issues that are mentioned.
• Acknowledging the issues without sounding defensive. 
• Gauging the customer’s satisfaction and the likelihood of renewing without being salesy.

Roleplay exercise:

• Rep’s role:
  • Approach the conversation from a consultant’s instead of a salesperson’s POV.
  • Use effective questioning and active listening to learn more about Morgan’s situation, pains, and concerns.
  • Learn as much as possible about DanFran’s current adoption of the EdgeFlow platform. 
  • Offer different ways to address the issues when they are mentioned.
• Prospect’s role (AI bot):
  • Push back based on the predefined objections.
  • Find out how the vendor can help your company adopt the product better and get more out of it.
• Success Criteria:
  • The rep gets a verbal confirmation that the renewal will go smoothly.
  • The rep learns what issues the customer is experiencing and suggests ways to correct them. 
  • The rep learns about potential other people who may need to be contacted specifically to discuss the adoption of the product and its utilisation. 
  • The rep gets a verbal agreement that the renewal is off the table.
  • The rep learns what issues the customer is experiencing and suggests ways to correct them. 
  • The rep learns about potential other people who may need to be contacted specifically to discuss the adoption of the product and its utilisation. 

Scenario #6: Upsell call roleplay

Call type: Upsell call

Context:

You are an AE/AM/CSM at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context). 

Your customer, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context).

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Morgan’s company has been using EdgeFlow’s platform for three months, but you are seeing some usage statistics that show it hasn’t been adopted fully. They seem otherwise happy with the product. 

Your company has just introduced a new (more expensive) package with more functionalities, some of which may be of interest to Morgan – especially the new data security abilities.

Objective:

Your goal is to get Morgan to see the value of upgrading to a new package.

Objections/concerns

• “Some of the KPIs are still not improving, for example, inventory management when your company starts working with new vendors (companies that sell raw materials or components needed for the furniture).”
• “Some of the IT team and the rest of the company are unwilling to experiment with the platform to take advantage of its low-code nature (maybe a workshop or training are needed).”
• “You are not sure that the new functionalities (in the new, more expensive package) will have any beneficial effects for your company.”
• “You are unwilling to add new functionalities when the existing ones are not being adopted or used as you hoped they would be.”
• “You will be getting a lot of pushback from the CFO.”

Key skills to practice:

• Using effective questioning and active listening to learn about the current state of the product’s adoption.
• Introducing the value of the new package by aligning it with Morgan’s and his company’s priorities.
• Framing the conversation as a consultation and not as a sales call.

Roleplay exercise:

• Rep’s role:
  • Approach the conversation from a consultant’s instead of a salesperson’s POV.
  • Use effective questioning and active listening to learn more about Morgan’s situation, current satisfaction with the product, concerns, and future plans.
  • Learn as much as possible about DanFran’s current adoption of the EdgeFlow platform. 
  • Try to paint a picture of how the new package would benefit DanFran even more.
• Prospect’s role (AI bot):
  • Push back based on the predefined objections.
  • Ask for cold, hard numbers – a true business case for upgrading.
• Success criteria:
  • The rep gets a verbal agreement that the customer will upgrade.
  • The rep sets up a meeting with Morgan, his team and/or other decision-makers to dig deeper into the functionalities found in the new package. 
  • The rep has initiated the upsell motion to any extent. 
  • The rep gets a verbal agreement that the customer will upgrade.
  • The rep sets up a meeting with Morgan, his team and/or other decision-makers to dig deeper into the functionalities found in the new package. 
  • The rep has initiated the upsell motion to any extent. 

Scenario #7: Objection handling on a resume call

Call type: Objection handling on a resume call. 

In this type of call, you can skip introductory parts of the call and go straight to certain points, such as handling specific objections/concerns. 

Context:

You are an AE at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context). 

Your prospect, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context).

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Morgan spoke to an SDR from your company and he heard some things that he liked about the platform you are selling.

Here’s how your discovery call has unfolded so far:

Get ready to handle some objections!

Objective:

Your goal is to listen to Morgan’s concerns, questions, and objections; remain calm and collected; and answer succinctly while emphasising the value of your solution. 

Objections/concerns: 

• “Our IT team is relatively small and inexperienced, and I am afraid introducing a new platform will only add complexity to our infrastructure.”
• “Our existing data infrastructure was built ad-hoc, we have a lot of different parts from various vendors and we’re worried about how a new solution will integrate.”
• “I know your solution is supposedly low-code, but I’ve heard horror stories of tools like that which turned out to be very difficult to use.”
• “Our budget is really limited and I need a super strong business case. Do you have some numbers for me?”
• “We’re in the EU, how familiar are you with all the data, security and whatnot regulations?”
• “Can you give me at least one example where a non-tech person (and also not C-level) used your platform to build a data stream with minimal help from IT?”

Key skills to practice:

• Listening actively and carefully to questions, concerns, and objections.
• Practice answering tough questions
• Remaining composed despite pushbacks. 
• Digging deeper into why Morgan is raising these specific points.
• Positioning as a trusted advisor, and not just another vendor.

Roleplay exercise:

• Rep’s role:
  • Approach the conversation from a consultant’s instead of a salesperson’s POV.
  • Use active listening to truly hear Morgan’s questions, concerns and objections.
  • Learn as much as possible about Morgan and DanFran’s current situation that has compelled them to raise these issues. 
  • Position the value of the solution effectively without pushing too hard.
• Prospect’s role (AI bot):
  • Push back based on the predefined objections.

Success criteria:

• The rep secures the next step, e.g. a collaborative workshop with Morgan and the entire IT team to demo the solution.
• The rep keeps their composure and answers the questions confidently, honestly and keeping the buyer’s best interests in mind. 
• The rep learns as much as possible about the buyer’s company by asking counter questions (when appropriate).

Scenario #8: Competitive selling on a resume call

Call type: Competitive selling on a resume call. 

In this type of call, you can skip introductory parts of the call and go straight to certain points, such as discussing potential competitors with the buyer.

Context:

You are an AE at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context). 

Here are three main competitors to EdgeFlow:

Your prospect, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context)..

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Morgan spoke to an SDR from your company, and he heard some things that he liked about the platform you are selling.

This is how the call has been going so far:

You are jumping straight into competitive selling. Better have your competitive battlecards ready!

Objective:

Your goal is to find out what other solutions Morgan is looking into and what he sees as their strengths (and weaknesses). Additionally, you want to position EdgeFlow as strongly as possible without trashing the competition.

Objections/concerns: 

• “Our IT team is relatively small and inexperienced, and I want the solution we choose to simplify our infrastructure and work, not complicate it.”
• “Our existing data infrastructure was built ad-hoc, we have a lot of different parts from various vendors and we’re worried about how a new solution will integrate.”
• “I know your solution is supposedly low-code, but I’ve heard horror stories of tools like that which turned out to be very difficult to use. Can you give me at least one example where a non-tech person (and also not C-level) used your platform to build a data stream with minimal help from IT?”
• “I see that your prices are not the cheapest among the solutions we’re considering. Can you justify the higher price?”
• “We’re in the EU, how familiar are you with all the data, security and whatnot regulations?”

Key skills to practice:

• Listening actively and carefully to questions, concerns, and objections.
• Demonstrating product knowledge
• Using the information you have on the competition to position EdgeFlow as a superior product (or at least one that will make the most sense for DanFran) without being negative about the competition. 
• Digging deeper (but tactfully) into which factors Morgan considers the most important to evaluate different products.
• Positioning as a trusted advisor and not just a vendor.

Roleplay exercise:

• Rep’s role:
  • Approach the conversation from a consultant’s instead of a salesperson’s POV.
  • Use active listening and tactful questioning to find out which solutions Morgan is evaluating and which factors Morgan considers the most important.
  • Learn as much as possible about Morgan and DanFran’s current situation which has resulted in them considering these specific solutions. 
  • Illustrate the value of EdgeFlow and present it as a superior product without being too obvious or pushing too hard.
• Prospect’s role (AI bot):
  • Grill the seller about the specific areas where their product is inferior to the competition.

Success criteria:

• The rep secures the next step (e.g., a collaborative workshop with Morgan and the entire IT team to demo the solution). 
• The rep keeps their composure and answers the questions confidently, honestly and keeping the buyer’s best interests in mind. 
• The rep learns as much as possible about the buyer’s current preferred solution and how they might further improve EdgeFlow’s position. 

Turn sales call insights into revenue-driving action

Hyperbound analyzes real sales calls in the context of live deals and surfaces exactly what reps need to fix — then reinforces it with realistic AI roleplays. The result: faster ramp, better deal execution, and more consistent performance.

TAKE ME THERE

Sponsored: I may earn a commission if you purchase through this link. I only partner with tools I’ve personally used or rigorously tested, and that I genuinely trust.

Scenario #9: Pricing negotiation on a resume call

Call type: Price negotiation on a resume call. 

In this type of call, you can skip introductory parts of the call and go straight to certain points, such as pricing negotiation with the buyer.

Context:

You are an AE at EdgeFlow, a company offering a low-code data streaming platform, especially useful for manufacturing companies whose factory-floor data is underutilised (refer to the seller persona image at the beginning of the sales roleplay & exercise section for additional context). 

Your prospect, Morgan Fischer, is the CIO of a mid-sized manufacturing company (refer to the buyer profile example section for more context).

Morgan sees IT as a strategic department for modernising the company and improving the bottom line. He is somewhat used to hearing pitches. 

He knows that modernising the data infrastructure would be highly beneficial for his company, but he is worried about the costs and the added work for his limited IT team.

Morgan first spoke to an SDR from your company, and he heard some things that he liked about the platform you are selling.

This is how the call has been going so far:

You are jumping straight into pricing negotiations.

Objective:

Your goal is to handle a pricing negotiation that was brought up by Morgan in the middle of your discovery process. Your objective is to find out if Morgan’s budget is even big enough to qualify DanFran as a potential customer, as well as answer any questions or concerns that Morgan might have about your pricing.

Objections/concerns: 

• “I see that your prices are not the cheapest among the solutions we’re considering. Can you justify the higher price?”
• “Our IT team is relatively small and inexperienced, and I want the solution we choose to simplify our infrastructure and work, not complicate it and cause us to have to hire more people and pour more resources into IT.”
• “What are the different pricing structures that you offer? Are there discounts for long-term plans?”
• “Are there any hidden costs that are not quoted in the price?”
• “We are thinking of going for an on-premise option; what are the costs associated with this?”

Key skills to practice:

• Listening actively and carefully to questions, concerns, and objections about pricing.
• Clearly and simply explaining the pricing structure. 
• Carefully framing the conversation in the direction of value instead of dollar price.
• Practice various competitor pricing negotiation tactics.
• Positioning as a trusted advisor and not just a vendor.

Roleplay exercise:

• Rep’s role:
  • Approach the conversation from a consultant’s instead of a salesperson’s POV.
  • Use active listening and tactful questioning to find out what Morgan thinks about the price and various pricing constructions.
  • Try to find out how much they are willing to spend on EdgeFlow. 
  • Illustrate the value of EdgeFlow beyond the dollar value – solving pains, removing obstacles, and aligning with DanFran’s business goals.
  • Disqualify if the price is deemed too high (especially if the value has been clearly articulated by the seller and understood by the buyer).
  • The standard price for one year of the EdgeFlow platform is $150,000.
• Prospect’s role (AI bot):
  • Find out as much as possible about pricing options and structures, including hidden costs, possible discounts, etc.
  • Agree to the price between $80,000 – $100,000 (avoid disclosing the budget to the seller as much as possible)

Success Criteria:

• The rep secures the next step – creating a quote for the buyer.
• The rep secures a conversation with additional decision-makers (e.g., CEO, CFO).
• The rep gets a verbal confirmation that the buyer is willing to purchase the product at an agreed-upon price.
• The rep disqualifies the prospect due to the prospect’s unwillingness or inability to pay anywhere close to the price.

Turn sales call insights into revenue-driving action

Hyperbound analyzes real sales calls in the context of live deals and surfaces exactly what reps need to fix — then reinforces it with realistic AI roleplays. The result: faster ramp, better deal execution, and more consistent performance.

TAKE ME THERE

Sponsored: I may earn a commission if you purchase through this link. I only partner with tools I’ve personally used or rigorously tested, and that I genuinely trust.

Conclusion

Repetition, realism, and structured feedback have always been the cornerstones of effective sales training – and the coaching required to reinforce it.

What makes AI-powered roleplays so exciting is how they take those fundamentals and amplify them.

With tools like Hyperbound, you’re no longer limited by schedules or availability. Commercial teams can practise as often as they like, refine their approach continuously, and tackle even the most nuanced sales scenarios.

The scenarios I’ve shared in this article are designed to help you do just that.

Whether it’s navigating a cold call, running an effective discovery call, or negotiating pricing, these exercises offer a practical, high-impact way to sharpen selling skills in a controlled, life-like environment.

And the best part is that you can try them yourself.

So why not take the next step?

Put the bots to the test and experience firsthand how AI can elevate sales development. You can also combine them with various sales training activities to truly take your training efforts to a whole other level.

I’m confident you’ll walk away with at least three roleplay scenarios you’ll want to use in your next training or coaching session.