Sales roleplay that actually changes behavior: why practicing with a colleague fails and how to run it weekly with AI

Vitor AlvesCEO, Contorna AI9 min read
Key takeaways
  • Sales roleplay is a rehearsal of a real conversation before it happens, with someone playing the buyer.
  • Roleplay with a colleague usually fails for three reasons: it is awkward, the buyer changes every round, and it happens rarely.
  • Good roleplay needs a coherent buyer, your product's real objections, feedback that quotes the conversation, and weekly repetition.

Sales roleplay is a rehearsal of a real conversation before it happens: someone plays the buyer, the rep runs the call, and afterwards both look at what worked. It works when the buyer stays coherent, the objections are the ones your product actually gets, the feedback points to specific moments in the conversation, and the practice repeats every week. Without those four things it becomes an awkward meeting everyone quietly avoids. AI makes all four easier to get.

The idea is old and sound. Athletes rehearse the play before the game; pilots rehearse the engine failure in a simulator. Most sales reps rehearse on real buyers, during the month they are supposed to be closing.

Why does roleplay with a colleague usually fail?

Almost every manager has tried it. You block an hour on Friday, pair people up, one is the rep and the other is the customer. Week one gets some laughs. By week three it no longer happens. The format has three structural problems, and none of them is a lack of effort.

It is awkward. Failing in front of peers and your boss is expensive for someone with a quota and an ego. Reps play it safe, repeat the pitch they already know and avoid exactly the situation they needed to practice. The colleague playing the buyer goes easy too, because tomorrow the roles flip.

It is inconsistent. Every colleague plays the buyer differently. One caves at the second objection, another invents one no customer would ever raise, a third drops character and starts giving tips. You cannot compare one round to the next, so you cannot tell whether the rep improved.

It is rare. Peer roleplay needs two calendars and ideally the manager’s. That is why it shows up at kickoff, at the annual meeting and during onboarding week. The research on deliberate practice, associated with psychologist K. Anders Ericsson, makes a point every sports coach already knows: skill is built through frequent repetition, with feedback, aimed at the weak spot. One session a quarter builds nothing.

There is a fourth, quieter problem: the feedback is opinion. “I thought that went well” or “you could have been firmer” does not tell the rep which sentence lost the conversation.

What does good sales roleplay need?

Remove the awkwardness, the inconsistency and the rarity, and what remains is what matters. Useful roleplay has four ingredients.

  1. A coherent buyer. They have a profile, a situation, a reason to be on the call and a reason to hesitate, and they hold onto it from start to finish. They do not cave out of sympathy or invent absurd objections to make it harder.
  2. Your product’s real objections. “It’s too expensive,” “we already have a vendor,” “I need to run this by my partner,” “just send me the pricing on WhatsApp.” The lines your team hears every week, in your industry, at your price point, not generic textbook objections.
  3. Evidence-based feedback. The feedback quotes the moment: “here the buyer said the problem was implementation time and you answered with a discount.” A rep cannot argue with that, and can fix it.
  4. Repetition. The same scenario, again, the following week. The second and third attempts are what show whether the behavior changed.
Roleplay with a colleagueRoleplay with an AI-simulated buyer
AvailabilityDepends on two or three calendarsWhenever the rep has fifteen minutes
BuyerChanges every round and with every colleagueKeeps the scenario’s profile and objections
Social pressureHigh: you fail in front of the teamLow: you fail alone, no audience
FeedbackOpinion of whoever watchedPoints to moments in the conversation
Comparing roundsHardSame scenario, same yardstick
Manager’s roleAct and judgePick scenarios and coach

Which scenarios should every sales team practice?

Do not try to train everything. Start with the five moments where B2B deals slip away most often.

1. Discovery with a buyer who barely talks

The buyer answers with “yes,” “no” and “it depends.” The drill is asking open questions, digging into the pain and resisting the urge to pitch before you understand the problem. Reps who skip discovery lose the negotiation later.

2. The price objection

The buyer says it is too expensive. The classic mistake is offering a discount before knowing whether the issue is perceived value, budget or a comparison with another option. The drill is to explore first. We break it down in our piece on the price objection.

3. “I’ll think about it” and the partner who decides

The call goes well and ends on a polite line. The drill is finding out what sits behind it: a decision-maker who was not in the room, fear of getting it wrong, no urgency. The pattern is taken apart in “I’ll think about it”.

4. The incumbent vendor

“We already use another solution and it works.” The drill is not attacking what the buyer chose, but understanding what they would be willing to change and where the current option falls short.

5. The lead who wants to do everything over WhatsApp

“Just send me the price here.” In Brazil, where Contorna was built, a large share of B2B selling starts and ends in a WhatsApp thread, and the same is true in many markets with text-first buyers. The drill is keeping the conversation alive, qualifying over text and earning the meeting without dumping the price list in the first reply.

For more beyond these five, our guide to sales objections organizes the most common ones.

How does sales roleplay with AI work?

The mechanics are simple. The AI plays the buyer, by text or voice, based on a scenario built from your company’s products, objections and script. The rep runs the conversation the way they would in a meeting or a message thread. At the end they get feedback that quotes the conversation: where they explored well, where they answered too early, which objection was left unhandled.

A short price scenario:

Buyer: I liked the demo, but the number came in above what we planned for.

Rep: Understood. Above by how much, and planned based on what? Did you have a reference from another vendor, or is this the annual budget?

Buyer: It’s the budget. Our tools budget for the year is already committed.

Rep: So the question is when, not how much. If it made sense to start in the next cycle, what would need to be clear by then?

In the feedback, the rep’s second line is the high point: instead of offering a discount, they separated “too expensive” from “no budget right now,” which call for different moves. Had they offered a discount in their first reply, the report would point to that exact line.

Two things matter here. First, nothing leaves the simulation: no real message is sent, no contact is created, no purchase happens. The rep is free to fail. Second, the simulated buyer is only as good as the material behind it. A scenario built on generic objections produces generic practice.

How does a manager run a weekly roleplay routine?

What separates a team that improves from a team that “did a training” is the routine. A structure that fits into any manager’s week:

  1. Monday: pick one scenario. Just one, tied to whatever is stalling the pipeline right now. If proposals are dying on “I’ll think about it,” that is this week’s scenario.
  2. Tuesday to Thursday: each rep practices two or three times. Fifteen to twenty minutes per session, at a time they choose. Repetition is the point.
  3. Thursday: read the reports. Look for the pattern, not the score. Three reps answering price with a discount is a team problem; one is a coaching conversation.
  4. Friday: fifteen minutes together. With the team, show one strong moment and one to fix, without singling anyone out. With whoever needs it, a one-on-one grounded in the evidence.
  5. Next week: same scenario or the next one. If the pattern is gone, move on. If not, run it again.

The side effect is the most valuable part: the manager stops spending Friday acting as a customer and spends their time on what only they can do, which is coaching. New reps also get a safe place to fail before they talk to real buyers, which matters a lot in sales rep onboarding.

Common mistakes when rolling out roleplay

  • Turning it into a test. If practice scores feed performance reviews, reps go back to playing it safe. Practice is where failing is allowed.
  • Training what never happens. A polished scenario with objections no customer raises. Use the lines from your real conversations.
  • Too many scenarios at once. Five themes in one week becomes none.
  • Reading only the score. The number shows whether it improved; the quoted moment shows what to change.
  • Stopping when the month gets tight. That is exactly when the team makes the most mistakes.

Where Contorna fits

Contorna’s Roleplay puts reps in front of an AI-simulated buyer, by text or voice, with scenarios built from your company’s products, objections and script. The feedback quotes the conversation, managers follow the training reports, and no real message, contact or purchase ever leaves the practice.

You can evaluate it on the Business plan for seven days without a card, starting with a scenario built from the objections your team hears most.

Frequently asked questions

What is sales roleplay?

It is a simulated sales conversation in which a rep practices with someone playing the buyer. It is used to train discovery, objection handling and closing before mistakes happen with a real buyer.

How often should a sales team roleplay?

Every week, in short sessions. One long session per quarter produces good intentions and little change; fifteen to twenty minutes a week on a single scenario builds the habit and shows progress.

Does AI roleplay replace the sales manager?

No. The AI plays the buyer and returns consistent feedback; the manager picks the scenario, reads the reports and coaches the rep on the pattern that keeps showing up. The manager's time moves from acting to coaching.