4 Sales Roleplay Scenarios for B2B SaaS (With Scripts)

Selling into b2b saas: what the roleplay has to get right

SaaS buyers are the most sales-literate audience on earth — they run sales teams themselves or sit next to people who do, they've read the same playbooks your reps have, and they can smell a framework from the second question. Deals die in security review, in “we could build this,” and in procurement stacks that demand a business case the champion can't write alone. These scenarios drill the conversations that actually decide SaaS deals.

How to run these — roles, timeboxes, scoring, the re-run rule — is covered in how to practice sales calls; the general-purpose library is at 25 sales roleplay scenarios. Below are the b2b saas-specific reps.

“Our Engineers Could Build This”

The buyer CTO, genuinely capable of building it, using the possibility as a price anchor

Setup Late discovery, real pain confirmed — then the CTO leans back: “Honestly, this is two sprints for my platform team.” Half sincere, half negotiation.

Rep’s goal Agree they could, then move the frame to opportunity cost and maintenance: what the platform team isn't shipping while they build and babysit an internal tool.

Buyer I'll be straight — my team could build this in a quarter. Why would I pay you instead?

Rep They could. Our first three customers all had teams that could, and two of them had already started. The question that changed their minds: what's on your platform roadmap right now that's worth more than this — and does it get shipped if your best two engineers spend Q1 rebuilding our last four years?

Raise the difficulty The CTO reveals a half-built internal version already exists — someone's abandoned side project. Grade whether the rep uses it as evidence or attacks it.

Score on Agreement-first judo, opportunity-cost articulation, no defensiveness about the product.

Stuck in Security Review

The buyer Security engineer working a 240-question vendor questionnaire, incentivized to say no

Setup The deal has been in security review for five weeks. The champion has gone passive. The rep finally gets the security engineer live — who opens with “your SOC 2 scope doesn't cover the AI processing.”

Rep’s goal Treat the reviewer as the customer, not the obstacle: answer what's answerable, escalate honestly what isn't, and convert the questionnaire slog into a 30-minute call with your security lead.

Buyer Your SOC 2 covers the platform, but the model inference runs outside the audited boundary. That's a finding.

Rep That's a sharper read than most reviews give us, and you're right about the boundary. Two things: the inference sub-processor has its own attestation I'll send today, and rather than ping-pong the remaining forty questions over email, can I get you thirty minutes with our security lead this week? You'll get better answers and a shorter review.

Raise the difficulty One question genuinely has a bad answer — a control that doesn't exist yet. Grade honesty plus roadmap handling.

Score on Technical respect, honest-escalation instinct, whether the review got a faster path.

The CFO Business-Case Test

The buyer CFO in a downturn budget cycle, killing every tool that can't prove payback inside a year

Setup The champion got the rep fifteen minutes with the CFO, who opens with: “Every vendor says ROI. Your champion couldn't tell me the payback period. Can you?”

Rep’s goal Deliver a defensible payback story built on the champion's own numbers, concede what's uncertain, and leave the CFO with a one-page model they can interrogate.

Buyer I've cut eleven tools this quarter. Tell me the payback period, and don't say 'it depends.'

Rep Seven months, and here's the math you can attack: your team's numbers, not mine — 14 reps, ramp at six months today, our customers cut that roughly in half. The soft claims I left out; this model only counts ramp. If the model survives your red pen, is the timing this quarter or next?

Raise the difficulty The CFO asks what happens to the price if they cut the contract to six months to de-risk. Grade the structure creativity.

Score on Number readiness, claim discipline (no inflated ROI), whether the CFO got something concrete to challenge.

The Renewal With Falling Usage

The buyer VP of RevOps who owns the renewal, staring at a 40% drop in monthly active users

Setup Renewal in 45 days. Usage fell off a cliff after a champion left in Q2. The VP opens the call with the dashboard already shared: “Explain why I'm renewing this.”

Rep’s goal No retention discount reflex: diagnose the usage cliff honestly (adoption died with the champion), propose a re-onboarding plan with dates, and re-anchor to the outcome the tool was bought for.

Buyer Forty percent usage drop since June. Give me one reason this survives the budget review.

Rep The drop dates to the week Dana left — she ran your enablement on this, and nobody inherited it. That's partly on us; we should have flagged it in July. Here's what I want: a two-week re-onboarding sprint for the new team, and we walk into your budget review with September usage, not June's. If the September number doesn't recover, we should both question the renewal.

Raise the difficulty The VP reveals a cheaper competitor already quoted them. Grade whether the rep discounts immediately or holds the recovery plan frame.

Score on Ownership without groveling, diagnosis accuracy, plan concreteness, discount discipline.

Running these against an AI buyer

Each scenario above is a complete specification — persona, setup, twist, scoring criteria — which is exactly what an AI sales call simulator consumes. In FireCoach, the AI buyer additionally argues with your specific market’s objections and scores reps against your own top performer’s standard, and it escalates the situations a rep keeps failing. For b2b saas teams, that means the ““our engineers could build this”” conversation can be drilled twenty times before it happens once with a real buyer.

Frequently asked questions

What sales roleplay scenarios should b2b saas teams practice?

The ones built from this industry's real conversations, not generic sales theater: “our engineers could build this”, stuck in security review, the cfo business-case test, the renewal with falling usage. Each scenario on this page includes the buyer persona, a scripted key exchange, a difficulty twist, and what to score — so it can be run with a peer, a manager, or an AI buyer.

What is the most important objection for b2b saas sales reps to drill?

“We could build this in-house.” Never argue they can't — they probably could. Drill the real question: should they, and what does the eighteen months of not-having-it cost while engineering gets around to it?

Sales Roleplay Scenarios for B2B SaaS (With Scripts)