You’re blaming the rep. You shouldn’t be.
When MSP follow-up breaks down, the instinct is to look at behavior.
- The rep isn’t making the calls.
- The rep isn’t logging the activity.
- The rep is letting deals go cold.
All of that may be true, and none of it may be the actual problem. The actual problem in most of the MSP sales reviews Fox & Crow Group has worked through is that the data underneath the follow-up process is a mess.
Messy data doesn’t create lazy reps.
It creates reps who can’t tell what they’re supposed to do next, so they do nothing.
That’s a system problem, not a discipline problem.
What we looked at
Fox & Crow Group analyzed follow-up patterns across MSP CRM audits and pipeline reviews conducted with clients ranging from under $1M ARR to firms approaching $5M ARR. This is not survey data. These are working CRMs, live pipelines, and real reps who are either following up or not. What we found, consistently, is that when follow-up breaks down, the CRM record tells the story before anyone needs to ask the rep a single question.
What we looked for in each review:
- Is there a documented next step with a date?
- Is there a named owner for that next step?
- Is the contact record current, with the correct decision-maker attached?
- Is there a logged last touch with enough context to reconstruct the conversation?
- Is there an overdue activity on the record, and does anyone know it’s overdue?
When one of those five things is missing, follow-up gets inconsistent. When two or more are missing, follow-up stops.
Here are the patterns we see most often, what they look like in the data, and what they mean for your MSP.
Vague next steps create invisible stalls
The most common data problem in MSP CRMs is not missing data. It’s vague data.
“Follow up” is not a next step.
“Waiting to hear back” is not a next step.
These phrases appear constantly in the free-form notes fields of MSP opportunity records, and they all have the same effect: they give reps nothing to act on.
A usable next step has three components:
- It names the action.
- It names the date.
- It names the reason the action matters.
“Send the proposal summary to the CFO before Thursday’s board meeting” is a next step.
“Call to confirm the demo is still scheduled for the 14th” is a next step.
“Check in later” is a placeholder that lives in your CRM until the deal dies quietly.
When a rep has 30 open opportunities and none of them have a specific next step recorded, every morning starts with the same problem: What do I do today?
Reps must reconstruct the context for every deal before they can determine which ones need attention. That reconstruction takes time, relies on memory, and punishes the rep for the CRM’s failure to carry information forward.
The rep defaults to the deals they remember. The ones they feel good about. The ones that are newest, or the ones with the most recent activity. The older, quieter deals, which may be the most qualified, fall through the cracks. From the outside, that looks like poor prioritization.
If you want consistent follow-up in your MSP sales process, every opportunity in the CRM must have a next step with a specific date and a stated reason.
No owner means no accountability
Ownership in an MSP CRM sounds obvious until you look at how many records don’t have it.
The opportunity might have a primary rep assigned. But who owns the next action? Is it the rep, the vCIO who ran the discovery call, the sales engineer who did the technical assessment, or the owner who said they’d send a personal note?
In many MSPs, the answer is whoever remembers to do it first.
Which means nobody does it, because everyone assumed someone else would.
This is especially common in MSPs that use a team-selling model or where the founder is still involved in deals. When two or three people are touching an opportunity, the CRM needs to be explicit about who owns the next move. If it isn’t, the follow-up becomes a coordination problem on top of a sales problem.
The field structure in your CRM must capture this. A rep can own the deal and a vCIO can own the next deliverable. Both should be visible in the record without anyone having to ask.
When there’s no named owner for the next action, the only way leadership knows whether follow-up happened is to ask. Asking is fine—once. Asking every week is a management tax that compounds quickly across a pipeline of any size.
A CRM with clean ownership data makes the question unnecessary. You look at the record. You either see that the action happened and was logged, or you see an overdue activity with a name attached. The conversation then becomes specific: “This was due on Tuesday. What happened?” That’s a productive conversation. “Are you following up on things?” is not.
Ownership is the mechanism that makes accountability possible without micromanagement. An MSP owner who can inspect any opportunity record and see the last touch, next step, due date, and owner doesn’t need a weekly verbal status update. The data provides the update.
If you’re still running your pipeline review as a verbal recap, it may be time to audit your CRM for follow-up actions and next-step ownership.
If you’re about to invest in your first MSP CRM, or you’re wondering whether your MSP is outgrowing the CRM you’re using now, have a chat with Carrie Richardson at Fox & Crow Group. Schedule a call or call her at 517-243-3516.
Photo: Daenin / Shutterstock
This post originally appeared on Smarter MSP.