B2B Sales Role Play: 8 SaaS Deal Scenarios With a Scorecard

TL;DR

• B2B sales role play works best when each scenario matches a stage of a real deal: the renewal, the new stakeholder, the security review, procurement, the CFO, the expansion, the bake-off and the build-versus-buy debate.
• The eight scenarios below use SaaS buyers. Each has a rep brief, private buyer instructions, likely branches, pass criteria and a debrief question, so you can copy it into a team session or an AI roleplay tool.
• Two items should be pass or fail in every B2B role play: the rep makes no claim the product or the security documents can't back, and the rep offers nothing outside their authority.
• Run one scenario for 8 to 12 minutes, score every row with a quote from the call, then retry the same scenario with one hidden fact changed.
• These scenarios pick up where cold calls and discovery end. For those calls, use the cold calling roleplay and discovery call roleplay guides.

B2B sales role play scenarios at a glance

How to use these scenarios

Quotain publishes this post and sells AI roleplay software. The companies, prices and limits in the scenarios are invented. Replace each bracketed placeholder with your own product, pricing authority, approved security answers and battlecards before you run them.

The rep brief is all the seller sees. The private buyer instructions are only for the person or AI playing the buyer. For a live session, use three people (rep, buyer and an observer holding the scorecard) and rotate after each call.

These eight scenarios cover the later and harder parts of a B2B deal. For earlier calls, the 12 sales roleplay scenarios guide covers openers, gatekeepers and first objections, and B2B sales discovery questions covers the questions to bring to a first meeting. The Quotain scenario library has 32 more scenarios with printable scorecards.

8 B2B sales role play scenarios

1. Renewal with a usage drop

Rep brief: The customer renews in [60] days: [120] seats at [$X] a year. Last quarter, [55] seats logged in. You may renew at current pricing, right-size to no fewer than [90] seats, or offer a [90-day adoption plan] run by their CSM. Discounts need [deal desk] approval.

Private buyer instructions:

• Opening line: "Only half our seats logged in last quarter. Why would we renew all of them?"
• Hidden facts: The drop sits almost entirely in the [EMEA] team, whose manager left in June and was never replaced. The US team uses the product daily. Your CFO has asked every department to cut tool spend by [30%].
• Pressure: Ask to renew at 60 seats. If the rep offers a discount first, ask for a bigger one.
• Reveal rules: Mention the EMEA manager only if the rep asks where usage fell or who owned the rollout there.

Likely branches:

• If the rep defends the product with features, hold at 60 seats.
• If the rep asks where the drop happened and brings usage by team, reveal the EMEA gap and ask what a recovery would take.
• If the rep proposes a plan with a named owner and a checkpoint date, agree to take it to your CFO.

Pass criteria:

• Find where usage fell, and why, before discussing seats or price.
• Use the customer's own usage data by team.
• Propose a recovery plan with an owner and a date, or a right-size within authority.

Debrief: What did the rep know about the EMEA team before the first number came up? For a renewal where the customer also wants to expand, see the renewal with expansion scenario.

2. The champion who left

Rep brief: Your champion, the Director of RevOps, left two weeks ago. The contract was in legal review. Her replacement, the new Head of Sales Operations, accepted a 15-minute call. You have the business case she built: [faster forecast reviews, fewer spreadsheets].

Private buyer instructions:

• Opening line: "I've inherited about forty open projects. Remind me why this one should stay on the list."
• Hidden facts: You haven't read the business case. In your first 90 days you must deliver [a cleaner forecast for the next board meeting]. At your last company you used [a competitor], chosen by someone else.
• Pressure: Ask, "What did she promise you?" Keep the call to 15 minutes.
• Reveal rules: Mention the board meeting only if the rep asks what you need to deliver in your first quarter.

Likely branches:

• If the rep repeats the old business case word for word, say, "That was her priority, not mine."
• If the rep asks about your goals and links the product to the board forecast, engage and ask about timing.
• If the rep asks to bring in the CRO before learning your priorities, decline.

Pass criteria:

• Acknowledge the change and ask for the new person's priorities before pitching.
• Re-test the business case against those priorities, and say which parts no longer hold.
• Agree on who else to involve and a dated next step.

Debrief: Which part of the old business case still mattered to the new buyer?

3. The security questionnaire stall

Rep brief: The business side said yes three weeks ago. Your champion, an engineering manager, says the security questionnaire has been "with InfoSec" since you returned it [ten days ago]. Your quarter ends in three weeks. Answer only from [your approved security documents]. Your product doesn't have [SSO].

Private buyer instructions:

• Opening line: "Still waiting on security. Nothing I can do, they have their own queue."
• Hidden facts: InfoSec sent back four follow-up questions a week ago. You haven't forwarded them because one asks about SSO, and you're worried it kills the deal. InfoSec reviews vendors at a weekly meeting on Thursdays.
• Pressure: Stay vague about timing. Get defensive if the rep pushes for a date.
• Reveal rules: Mention the four follow-ups only if the rep asks whether InfoSec has come back with anything, or what the review status shows.

Likely branches:

• If the rep pushes for a signature date or offers a quarter-end discount, go quiet and promise to "chase them."
• If the rep asks what came back and offers a call between their security lead and your reviewer, admit the follow-ups and agree to the call.
• If the rep says the product has SSO or that it's "coming soon" without a date, the call fails on the pass or fail item.

Pass criteria:

• Find out who has the questionnaire and what is still open.
• Offer a direct route to the reviewer, with a date before the Thursday meeting.
• State any gap plainly, with the approved answer, and make no claim the documents can't back.

Debrief: What was blocking the deal, and who knew about it? For the call with the security reviewer, use the security reviewer scenario in the sales engineer demo practice guide.

4. Procurement asks for a discount

Rep brief: The VP Sales approved a [$96,000] annual quote for [80] seats. A procurement analyst now owns the paperwork. Your authority: up to [6%] off for a two-year term or annual prepayment, and [an onboarding package] at no cost. No change to the per-seat price below [$X].

Private buyer instructions:

• Opening line: "Our benchmark shows you're 22 percent above market for this category. We'd need to get closer before I can send it for signature."
• Hidden facts: The benchmark blends three vendors, one of them a cheaper tool with fewer features. Your file needs a documented saving of at least [5%], and a multi-year price cap counts. The VP Sales wants onboarding to start on the 1st.
• Pressure: Repeat "22 percent" twice. Ask for an answer today.
• Reveal rules: Say what your file needs only if the rep asks what a good outcome looks like for procurement.

Likely branches:

• If the rep offers 10% straight away, thank them and ask for 22.
• If the rep asks what the benchmark compares, admit it's a blend and soften.
• If the rep offers a conditional package (term or prepayment for a discount or price cap), take it to the VP Sales.

Pass criteria:

• Ask what the benchmark includes before responding to the number.
• Trade every concession for something: term, prepayment or start date.
• Stay within authority, and bring in the VP Sales if procurement stalls.

Debrief: What did the rep get for each concession? For more negotiation drills, see sales negotiation roleplay, and for a procurement lead with a different agenda, the procurement enters late scenario.

5. Multi-threading into the CFO

Rep brief: Your champion, the VP Sales, got you 20 minutes with the CFO before the budget meeting. The deal is [$140,000] a year. The champion's case: new reps ramp faster. You have the champion's numbers: [14] new hires planned this year and a [six-month] ramp today.

Private buyer instructions:

• Opening line: "Dana says this is the priority. I have twelve requests on my desk that all say that. What happens if we don't buy it this year?"
• Hidden facts: Your plan already assumes 14 hires. You want payback inside the fiscal year, and you want to retire [two existing tools]. You don't trust productivity figures that aren't from your own data.
• Pressure: Interrupt any answer longer than a minute. Ask, "Where does that number come from?"
• Reveal rules: Name the two tools only if the rep asks what this spend would replace.

Likely branches:

• If the rep repeats the champion's pitch with features, ask for a one-pager and end the call.
• If the rep works from your hiring plan and asks what you need to see, give your criteria: payback period and tools retired.
• If the rep quotes an ROI figure that isn't from your data, ask for the source. If there isn't one, the call fails.

Pass criteria:

• Answer "what happens if we don't buy" in the buyer's own numbers.
• Ask what the CFO needs to approve the spend.
• Leave with the CFO's criteria and a next step that includes the champion.

Debrief: What does the CFO now believe that he didn't at the start of the call?

6. Expansion into a second team

Rep brief: The sales team ([60] seats) has used your product for eight months. Your sponsor in sales introduced you to the Head of Customer Success, whose team of [25] runs renewal and QBR calls. Your goal: learn how the CS team works and agree whether a pilot makes sense.

Private buyer instructions:

• Opening line: "Sales loves it. Why would my CS team need it?"
• Hidden facts: Your team has a new retention target this year. Last year you bought a different tool that your team stopped using within a month. CS budget sits with the COO, not the CRO.
• Pressure: Say, "We're not sales. Don't sell me." Lose interest if the rep shows sales use cases.
• Reveal rules: Mention the failed tool only if asked what you've tried before. Name the COO only if asked how CS buys software.

Likely branches:

• If the rep demos what the sales team does, check your phone and ask to wrap up.
• If the rep asks about renewal calls and the retention target, engage.
• If the rep proposes a full team rollout, say no. If the rep proposes a small pilot with a named owner, agree to discuss it with the COO.

Pass criteria:

• Learn the CS workflow before showing or claiming anything.
• Use proof from the sales team only where the work is the same.
• Find the budget owner and agree on who would own a pilot.

Debrief: Did the rep sell the sales team's use case to a team that does different work?

7. The competitive bake-off

Rep brief: You're in a two-week bake-off with [a cheaper competitor]. Each vendor gets a 45-minute final session with the evaluation team. Use only [your approved battlecard] claims. The buyer has a scoring sheet you haven't seen.

Private buyer instructions:

• Opening line: "Relaybase does most of this for half the price."
• Hidden facts: Your scoring sheet gives [30%] of the weight to admin setup time, where the competitor's trial went badly. Your manager prefers the cheaper option. One criterion, [EU data residency], hasn't been confirmed by either vendor.
• Pressure: Bring up price twice. Ask, "Why should I pay double?"
• Reveal rules: Share the scoring weights only if the rep asks how the team will decide. Mention data residency only if asked what's still open.

Likely branches:

• If the rep criticizes the competitor, defend them.
• If the rep cuts the price, note it for the comparison and ask for more.
• If the rep asks for the scoring sheet and maps proof to each criterion, share the weights and ask for a setup walkthrough.

Pass criteria:

• Get the decision criteria and their weights.
• Back each claim with proof from the approved battlecard, with no disparaging of the competitor.
• Confirm what is still open and how the final decision will be made.

Debrief: Which criterion did the rep win, and with what proof? The "We already use another solution" scenario covers the earlier version of this call, and the sales battlecard template covers how to write the claims.

8. "We'll build it ourselves"

Rep brief: Sales leadership wants your product. The VP Engineering has proposed building an internal version instead and agreed to a 30-minute call. You know the build would need [your integrations and data model]. You can offer [a technical review with your SE].

Private buyer instructions:

• Opening line: "This is a couple of sprints for my team. Why would we pay you every year for something we can build?"
• Hidden facts: Your team is a quarter behind on the core roadmap. The last internal tool you built, [a quoting tool], took six months instead of six weeks and still takes half of one engineer's time. You don't want to own another internal tool, but you won't say that first.
• Pressure: Question every estimate the rep gives.
• Reveal rules: Tell the quoting tool story only if the rep asks what your team has built in-house before and what it costs to maintain.

Likely branches:

• If the rep says your team can't build it, dig in and end the call early.
• If the rep offers to price the build together (sprints, maintenance and roadmap delay), engage and share your numbers.
• If the rep suggests your team owns the integration work while the vendor owns the core, show interest and ask about the technical review.

Pass criteria:

• Treat the build as a real option, and price it with the buyer's own numbers.
• Make no claim about the team's ability.
• Agree on a decision criterion and a next step with the SE.

Debrief: Whose numbers did the build-versus-buy comparison use?

Copyable B2B sales role play scorecard

Use one scorecard for all eight scenarios and mark a row N/A when the call doesn't test it. The two pass or fail rows apply to every call. The other rows score 0, 1 or 2.

How to score it:

• A miss on either pass or fail row fails the call, however good the rest sounded.
• Otherwise, score out of 10 across the five 0-to-2 rows, with a pass mark agreed before the session, for example [7].
• Every score needs a quote or a timestamp. "Good discovery" is not evidence. "Asked where usage fell at 1:20 and got the EMEA answer" is.
• Keep the scorecard fixed for the retry so the rep can see what changed.

The sales call scorecard guide covers how to write criteria two reviewers score the same way.

How to run B2B role play with your team

A 30-minute session

1. Pick the scenario that matches the deal most likely to slip this week: scenario 2 or 3 if a champion has gone quiet, scenario 4 if procurement has the paper.
2. The rep reads the brief and writes down a goal for the call (2 minutes).
3. Run the call (8 to 12 minutes).
4. The observer scores it, with evidence for every row (5 minutes).
5. The manager asks the debrief question (5 minutes).
6. Retry with one hidden fact changed, such as a different reason for the usage drop.

Run one account through the whole deal

Use the same fictional account for several scenarios in a row: the champion leaves (2), the new contact brings in security (3), procurement takes over (4) and the CFO signs off (5). Reps learn to carry what they found on one call into the next. For scenarios 5 and 6, add a second person playing the champion on the same call and score the stakeholder row for each buyer.

Run these scenarios with AI buyers

Colleagues make good buyers, but a manager's calendar limits how often reps can practice the late stages of a deal. With Quotain for B2B SaaS, the scenarios above become AI buyers reps can practice with before the real call:

• Quotain builds buyers from your playbook, CRM, Knowledge library and recorded calls, and grades each attempt on the scorecard for that call.
• Call stages are configurable, so renewal, QBR and expansion calls can sit next to discovery, demo and negotiation, each with its own scorecard.
• Name the competitor and the buyer pushes back with it in mind. When the scorecard checks factual claims, Quotain compares what the rep said with your Knowledge library and marks each claim supported, contradicted or unsupported.
• On team plans, a multiparty call puts a lead buyer and up to three more stakeholders on the same call, which suits scenarios 5 and 6.
• Recorded calls from Gong, Fathom, Chorus, Salesloft and other recorders, or uploaded recordings, are graded on the same scorecards through real-call grading.
• AI buyers speak 32 languages.

Quotain is preparing for a SOC 2 Type II audit and does not offer SSO yet. The trust center lists its current controls.

Frequently asked questions

What is B2B sales role play?

B2B sales role play is a practice call where a seller works through a business-to-business sales situation, such as a renewal, a procurement negotiation or a call with a CFO, while a colleague, manager or AI plays the buyer. The buyer follows private instructions about what they know and how hard to push, and an observer scores the call on a written scorecard.

What are good B2B sales role play scenarios?

Good B2B sales role play scenarios match the stages where deals stall: a renewal with falling usage, a champion who leaves, a security review that stops moving, procurement asking for a discount, a first call with the CFO, an expansion into a new team, a competitive bake-off and a buyer who wants to build the product in-house. Each scenario should give the buyer a hidden fact the rep has to find.

How long should a B2B sales role play be?

Most B2B sales role plays should run 8 to 12 minutes, long enough to reach the hard moment and agree a next step. With scoring, a debrief and one retry, a session takes about 30 minutes. To practice one moment, such as the first answer to "we need 22 percent off," a two-minute drill repeated three times works better than a full call.

How do you role play a renewal call?

Give the rep the account's real situation: seats, usage, renewal date and pricing authority. Give the buyer a private reason for the problem, such as one team that stopped using the product, and a pressure move, such as asking to cut seats. Score whether the rep found the reason before discussing price and left with a recovery plan that has an owner and a date.

How do you practice multi-threading in sales?

Practice multi-threading with scenarios where the rep must reach a new stakeholder: a CFO introduced by the champion, a replacement for a champion who left, or a second team at an existing customer. Add a second person playing the champion on the same call, and score whether the rep speaks to each person's concern and learns who else must agree.

Can AI play the buyer in a B2B sales role play?

Yes. AI roleplay tools can play the buyer from a written scenario, so reps can practice a renewal or a procurement call before it happens. Check that the tool builds buyers from your own product and deal context, holds back hidden facts until the rep earns them, scores on your criteria and can put more than one stakeholder on a call.

Start with the deal most likely to slip this quarter

Pick the deal in your pipeline that worries you most, match it to one of the eight scenarios and run it with the rep who owns it this week. To let reps practice every stage of a SaaS deal without a manager playing the buyer, see how Quotain works for B2B SaaS and AI sales simulations, then book a demo to see a buyer built from one of your accounts. You can also run a free practice call or start from the scenario library.