Ask a generic sales training program to prepare a rep for a conversation about backup retention windows, SLA response tiers, and why a client's current provider missed an incident. It cannot, and that is the whole problem.
MSP and IT services selling is technical sales dressed as relationship sales. The rep has to earn credibility with someone who knows more than they do about part of the stack, and then translate that credibility into a commercial conversation. Generic coaching frameworks were not built for that, so reps end up learning it on live prospects.
Why MSP sales is a different problem
Three things make it different. The buyer is often technically expert, the product is a promise about future reliability rather than a demonstrable feature set, and the incumbent is usually a person, sometimes an internal IT manager whose job the deal implicitly criticises.
None of those show up in standard sales training. A workshop on discovery questions does not prepare a rep for the moment an IT director asks what your RPO actually is and the rep does not know. The credibility loss in that moment is not recoverable with better rapport.
The four conversations generic coaching cannot simulate
These are the moments where technical selling diverges from general B2B selling. Each requires a rep to hold two conversations at once, the technical one and the commercial one, and each is where deals actually go.
The credibility test in the first ten minutes
Technical buyers test early, often with a question they already know the answer to. The purpose is to find out whether they are talking to someone who understands their environment or someone reading from a deck.
What reps need to practice is not the answer, it is the honest non-answer. "I do not know, and I will not guess. Our solutions architect will, and I will get you a specific answer today" preserves credibility. Bluffing destroys it permanently.
"We already have an IT person"
The hardest objection in the category, because the honest answer implies criticism of someone the buyer likes. Reps who handle it well never position the internal person as the problem. They position coverage, escalation depth, and what happens on a Friday night as the problem.
We have got Dave. He handles all of this.
That is usually a good thing, and I am not here to replace Dave. What I would want to understand is what happens when Dave is on holiday, or when something breaks at two in the morning, or when something needs a specialism he has not had to build. Where does the load land then?
SLA and pricing pushback
MSP pricing is compared against a number the buyer usually has wrong, because they are comparing a managed service to the cost of reactive fixes they have already forgotten about. Reps need to practice reconstructing the true current cost from the buyer's own history rather than asserting a saving.
The security stakeholder joining late
A security or compliance stakeholder appearing in week four changes the conversation entirely, and the rep who was doing well with the operational buyer often loses the room. Practicing that specific handover, with a persona whose priorities are risk rather than cost, is something no generic program provides.
What technical sales practice needs to include
The requirement is not more training content. It is repetition against personas that behave like your actual buyers, with scoring on whether the rep translated technical accuracy into commercial clarity.
- Personas across the real buying committee: business owner, IT lead, CFO, and a security stakeholder
- Scenarios that include an incumbent, because almost every MSP deal is a displacement
- Practice on the honest "I do not know," which is a learnable skill and rarely taught
- Scoring on whether technical detail was translated into business consequence, not on whether it was recited correctly
- Drills built from your own service catalogue, SLAs, and stack, since a generic library cannot cover them
Why the problem is worse for small teams
Most MSPs run small sales teams, often two to five people, sometimes with the owner still selling. There is no enablement function, no formal onboarding, and no capacity for a manager to review calls. Every rep's performance is a material share of company revenue.
That combination is why shadowing dominates as a training method in this category and why it fails. Shadowing occupies your best seller, produces observation rather than skill, and takes months. Salesforce's State of Sales research has repeatedly found reps spend only around 30 percent of their time actually selling, and in small teams the ratio is worse because everyone is also doing something else.
What MSP reps are actually being asked to do
It helps to state the job precisely, because the size of it explains why generic training does not cover it. An MSP rep has to hold enough technical detail to be credible with an engineer, translate that detail into a financial consequence for a CFO, displace an incumbent without insulting anyone, and do all of it while selling a promise about future reliability that cannot be demonstrated in a demo.
That is four distinct skills, and only one of them appears in standard sales curricula. It is also why hiring in this category is difficult: the profile is a technical communicator with commercial instinct, and there are not many of them, which makes developing the ones you have the more reliable strategy.
The three ways MSPs currently train, and what each costs
Shadowing
The default. It occupies your best seller, aligns two calendars, and produces observation rather than skill. In a five person sales team, taking your top performer off calls for a week is a measurable revenue event.
Vendor certification
Useful and insufficient. Vendor programs teach the product accurately and say nothing about how to sell it into a business with an incumbent provider and a skeptical IT lead. Certification tells you a rep knows the technology, not that they can hold the conversation.
Learning on live prospects
What actually happens between the other two. Reps develop by getting it wrong on real opportunities, which works and is the most expensive method available, since the cost is paid in deals rather than in training hours.
What changes when technical practice exists
The measurable shifts in MSP teams that add structured practice tend to show up in three places rather than in a single headline number.
- Fewer deals lost at the technical credibility moment, because reps have rehearsed the honest non-answer
- Less discounting on SLA tiers, because reps reframe to scope instead of conceding price
- Faster new hire productivity, because the credibility test and the incumbent objection are practiced before the first prospect call rather than during it
The third one is where small teams feel the difference first, since a new hire in a five person team represents a fifth of your selling capacity and every week of ramp is a visible number.
Where practice fits in an MSP sales motion
Three placements produce most of the return. New hires practice the credibility test and the incumbent objection before their first prospect call. Tenured reps drill the security stakeholder conversation, since it happens rarely enough that nobody is fluent. And the whole team runs the SLA pricing conversation whenever the service catalogue changes.
On live calls, guidance grounded in your own service documentation is what keeps a rep accurate when a buyer asks about a retention window mid-sentence. That is the difference between a practice tool and a coaching system.
Start with the objection that costs you most
For most MSPs it is the internal IT person. Write down the exact sentence your last three prospects used, and make that this month's practice. It is a narrow start and it is the one that moves revenue.
For the scenario library version of this, see twelve MSP and IT sales roleplay scenarios. FunnelX for IT services covers how this is configured, and how managers multiply their coaching impact addresses the small-team capacity problem directly.