Technical sales conversations fail in specific, repeatable places. Below are twelve of them, with scripts for the six that cost the most.
Every scenario assumes the rep is selling managed services, cloud, or security to a buying committee that includes at least one person who knows the technology well. That constraint is what makes these different from general B2B roleplay.
Displacement scenarios
Nearly every MSP deal is a displacement, of either another provider or an internal person. The skill is criticising a situation without criticising a human being, which is harder than it sounds and almost never practiced.
Scenario 1: the internal IT person
Setup. A twelve person business has one internal IT generalist. Challenge. Position coverage depth without implying the person is inadequate.
Honestly, Dave handles everything fine.
I am glad, and I would not want to change that. My question is narrower: what happens on the day Dave is unavailable and something is down? Who picks it up, and how long does it take?
It waits, usually.
That is the part I would want to solve. Not replacing Dave, covering the hours he cannot.
Coaching takeaway. Narrowing the scope of the challenge to a specific gap, and never making the incumbent the villain.
Scenario 2: the incumbent provider with a long contract
Setup. The prospect is eighteen months into a three year agreement and frustrated. Challenge. Build the case now for a decision later without wasting the cycle.
You are locked in for another eighteen months, so let me be direct: I am not trying to get you out of that today. What would be useful is understanding what has gone wrong, so that when renewal comes you have a documented comparison rather than starting from scratch.
That is fair. The response times are the issue.
Coaching takeaway. Playing a long cycle honestly, which produces a warm renewal-window deal instead of a wasted quarter.
Scenario 3: the prospect burned by a previous MSP
Setup. A buyer who has been oversold before and opens defensively. Coaching takeaway. Asking for the post-mortem in detail before positioning anything, since the failure they describe is the objection you have to answer.
Technical credibility scenarios
These four drill the moments where a rep either earns technical trust or loses it. The scoring here should reward accuracy and honest limits, not confidence.
Scenario 4: the credibility test
Setup. An IT director asks a specific technical question in the first ten minutes. Challenge. Answer honestly without losing authority.
What is your actual recovery point objective on the backup tier?
I am not going to guess at a number that specific, because if I get it wrong you will find out later and that is worse. I will have our architect confirm it today. What I can tell you is how the tiers are structured and why, if that is useful now.
Coaching takeaway. The honest non-answer as a credibility move. Most reps bluff here, and technical buyers detect it immediately.
Scenario 5: cloud migration objections
Setup. A buyer with a half-finished migration and a bad experience. Challenge. Separate what failed in execution from what failed in the plan.
We moved two workloads and it cost twice the estimate. We are not doing that again.
That is a common outcome and usually a scoping problem rather than a cloud problem. Where did the overrun come from, licensing, egress, or rework?
Coaching takeaway. Technical diagnosis as discovery. The follow-up question demonstrates competence better than any claim.
Scenario 6: translating technical value to a CFO
Setup. The rep has convinced the IT lead and now faces finance. Challenge. Convert uptime and risk into a number.
I do not need the technical detail. What am I buying?
Fair. You are buying a reduction in unplanned downtime. Last year you had two incidents that took the warehouse offline. What did a day of that cost you? That is the number this is measured against.
Coaching takeaway. Switching register between stakeholders in the same deal, which is the skill that separates senior technical sellers.
Scenario 7: the security stakeholder who joins in week four
Setup. A CISO or compliance lead enters late with different priorities. Coaching takeaway. Restarting discovery for a new stakeholder rather than summarising, since the late arrival has not agreed to anything yet.
Commercial scenarios
The last group is where technically strong reps most often stall. The service is understood, the buyer is convinced, and the conversation turns to price and terms.
Scenario 8: SLA tier pushback
Setup. The buyer wants the top tier response time at the mid tier price. Challenge. Explain what the tier actually funds without sounding defensive.
Why is a one hour response double the cost of four hours?
Because a one hour response means staffed coverage rather than best-effort, and that is a people cost rather than a margin choice. The better question might be which systems genuinely need one hour, because it is rarely all of them.
Coaching takeaway. Reframing a pricing objection as a scoping conversation, which usually protects margin and improves fit at the same time.
Scenario 9: the per-user pricing comparison
Setup. A prospect compares your per-seat figure to a cheaper competitor. Coaching takeaway. Establishing what is included per seat on both sides before defending the number.
Scenario 10: the QBR that should produce an upsell
Setup. A quarterly review with a satisfied client and no expansion conversation planned. Coaching takeaway. Using performance data to open a needs conversation rather than reporting and leaving.
Scenario 11: the project-only buyer
Setup. A prospect wants a one-off migration and no ongoing agreement. Coaching takeaway. Deciding whether to take it, and how to structure it so managed services is a natural follow-on.
Scenario 12: the renewal after an incident
Setup. A renewal conversation three weeks after a significant outage. Coaching takeaway. Owning the failure directly, then re-earning the contract on what changed rather than on the relationship.
What to score in a technical roleplay
Technical sales roleplay needs a different rubric than general sales practice, because a rep can be technically correct and still lose the room. Five criteria cover it, and the third is the one most teams forget to include.
| Criterion | What a pass looks like |
|---|---|
| Technical accuracy | Nothing stated that is wrong, and nothing implied that is unsupported |
| Honest limits | Says "I do not know" where true, with a named follow-up and a timeframe |
| Commercial translation | Technical detail converted into a consequence the buyer cares about |
| Incumbent handling | Gap identified without characterising a person or provider |
| Register switching | Language adjusts between engineer, owner, and finance in the same call |
Scoring honest limits explicitly is what stops the rubric rewarding confidence. Without that row, a rep who bluffs smoothly scores better than one who defers accurately, which trains exactly the wrong behavior for a technical buyer.
Building these on your own stack
Generic versions of these scenarios are useful for a week. After that the value comes from your own service catalogue, because the objections your reps actually hear reference your tiers, your response times, and the specific migration you quoted last month.
- Load your service catalogue and SLA tiers so pricing scenarios use real numbers
- Build the incumbent persona from your three most common displacement situations
- Take the technical questions your reps could not answer last quarter and make those the credibility test
- Add one persona per stakeholder type, including the security lead who arrives late
The credibility test in particular should be built from real questions. Every MSP sales team has a short list of things a prospect asked that nobody could answer, and that list is the most valuable practice material you own.
How to run these as a practice rotation
Start with scenarios one, four, and eight. In most MSPs those three account for the majority of lost or discounted deals, and they are the three where practice transfers fastest.
- Week one: the internal IT person, three attempts per rep, difficulty raised each time
- Week two: the credibility test, scored on the honest non-answer rather than the answer
- Week three: SLA tier pushback, scored on whether the rep reframed to scope
- Week four: the CFO translation, scored on whether a number was established
The argument for why generic programs cannot cover this ground is in why generic coaching fails technical sales teams. For the framework behind the objection scenarios, see the objection handling guide, and FunnelX for IT services shows how the personas are built.