A better MSP sales team starts with the process

Bring on a salesperson before you’ve documented your sales process, and you’ve just funded an expensive experiment. Your new rep will improvise, optimize for their own comfort, and leave you wondering where you went wrong.

The pattern is consistent:

Owner hires for capacity.

Rep asks for structure.

Owner delegates the problem back to the rep.

Rep builds a personal system that leaves when they do.

Reset.

Better training won’t end the cycle. Building the process first will.

Define what has to be true before a deal moves

A real MSP sales process defines what has to be true before a deal moves from one stage to the next.

Every stage needs a name that means something specific to your team. It also needs entry criteria the rep must confirm before a deal moves in, exit criteria that must be met before it moves forward, a reasonable amount of time a deal can sit there without moving, and a person responsible for advancing it.

A common MSP sales pipeline moves from target accounts that fit your ICP through first contact and a real two-way conversation, followed by a scheduled discovery meeting, completed discovery, proposal, negotiation, and closed won or closed lost with a reason logged.

Completed discovery should mean you know the prospect’s staff count, how they get IT support today, when that arrangement renews, and what’s broken.

If you can’t answer, “What does the rep need to confirm before this stage?” for every stage, it isn’t defined yet. Go back and define it.

Be as specific as possible. If you train a rep on a vague process, your entire sales system becomes vague. That leads to unclear CRM notes, ineffective pipeline reviews, and training that misses the mark. Vague stages are also why so many MSP pipelines stop matching reality.

Document what the rep does at each stage

Once your stages are defined, document exactly what a rep is supposed to do at each one.

Outcomes tell you where a deal is. Activities tell you how it got there.

For each stage, write down what the rep says or sends to move the deal forward, how many attempts they make before changing its status, which tools they use, and what gets logged in the CRM.

For example, consider a prospect who has had a qualifying conversation with a sales rep but hasn’t scheduled a discovery meeting. Your documentation should tell the rep how quickly to send a calendar invite, when to follow up by phone if there’s no response, when to move the prospect to nurture with a dated task to reconnect, and what to log after each attempt.

Without this structure, two reps will handle the same prospect two different ways. You’ll end up with an MSP sales pipeline that’s impossible to read because every record contains whatever the rep decided to enter, or nothing at all, instead of the information your process requires.

Activity documentation also protects your rep during performance reviews. If the process calls for a set number of follow-ups and the rep makes every one, a deal going cold points to the process or targeting. If the rep made one attempt and stopped, it points to execution. You can only tell the difference when activities are documented and logged.

Define what complete discovery looks like

Discovery is where a lot of MSP sales processes fall apart.

Your process should spell out what discovery must capture every time. This should be a required standard the rep can’t skip.

At minimum, discovery for a managed services sale should capture:

  • The current environment
  • The current provider and when that arrangement renews
  • The specific problem the prospect described and what it costs them
  • Who approves the spend
  • Whether this is a “now” problem or a “someday” problem

If a rep can’t fill in those answers after a discovery call, the call isn’t complete. Either they go back for another conversation or the deal doesn’t advance.

Your CRM should have a field for each one. If a required field is blank, the stage doesn’t change. If the information isn’t in the CRM, it can’t be coached, reported, or used for forecasting.

Document the process for proposals and closing

Every activity in your sales process, including the steps that begin with creating a proposal, needs to be treated as part of a formal process.

This is where MSPs lose deals they should win.

Start with how proposals get delivered. Price belongs in a conversation with the person who can approve the spend. Train reps from the beginning that a proposal is never emailed before it’s been presented and isn’t shared without the decision maker in the room. The rep should ask for the decision and address objections during that meeting.

Then document what happens if the business isn’t won during the proposal meeting. How does the rep schedule the next conversation? How many attempts should they make before the deal is considered dead?

Document the objections your reps hear most, then train them to surface and address those objections early, before the proposal is presented rather than after.

Document the handoff, too. Who takes over when the customer signs? When does the account stop belonging to sales and start belonging to service? Is there a clear checklist for that transition?

Every lost deal should also get a specific reason. “Price” isn’t a reason. “Our price was higher than the incumbent’s at renewal, and the prospect didn’t see enough difference to switch” is.

If you skip closed-lost documentation, you’ll never know whether you’re losing on price, timing, competition, or because your discovery missed something.

You’ll just know you’re losing.

It’s impossible to train a sales rep to win more managed services deals when you don’t know why they’re losing them.

Train your rep to the process you built

Before you hire, train, or spend money on lead generation, open your CRM and make sure it reflects the process you’ve documented.

Every stage should have entry and exit criteria the CRM can show.

Every discovery requirement should have a field.

Closed-lost reasons should be categories, not free text.

A CRM that can’t tell you whether your sales rep is following your process creates another problem: reporting that doesn’t show where your rep needs more support.

If you’re not yet using a CRM, The MSP Sales Process by Fox & Crow Group helps MSP owners create high-performing MSP sales reps right out of the box.

To schedule your MSP sales diagnostic, book a call with Fox & Crow Group or call Carrie Richardson at 517-243-3516.

Photo: Sorapop Udomsri / Shutterstock

This post originally appeared on Smarter MSP.