There is a version of the MSP sales process that most owners recognise. A good discovery call. A proposal that lands well. A promising response. And then silence. A follow-up email. More silence. Another email a week later. Still nothing. The deal goes cold and the prospect eventually signs with someone else.
The deal did not die because the prospect chose a competitor. It died because the follow-up stopped at exactly the wrong moment.
Because follow-up is treated as persistence rather than value delivery.
The typical follow-up sequence looks like: send proposal, follow up two days later with "just checking in," follow up again a week later with "wanted to make sure you received this," wait another week, give up. None of these touchpoints give the prospect a reason to re-engage. They are reminders that a proposal exists. The prospect already knows a proposal exists.
The follow-ups that work treat each touchpoint as an opportunity to deliver something new. A relevant case study. A specific answer to an objection the prospect is likely sitting with. A development in their industry that connects to the problem being solved. The framing is not "are you still interested?" It is "I thought this was relevant to your situation."
Too early. The majority of B2B deals close after five or more contact attempts. The majority of salespeople stop after two. This gap, between where follow-up typically stops and where deals typically close, is one of the most consistent sources of lost revenue in MSP sales.
The MSP who sent a strong proposal and followed up twice has done about 40% of the work required to close most deals. The 60% that remains is staying in play long enough for the prospect's timing to align with the MSP's solution. Prospects go quiet for reasons that have nothing to do with disinterest: a budget cycle delay, an internal project that jumped the queue, a leadership change that paused all vendor decisions. The MSP who is still present when those constraints lift is the one who closes the deal.
It maps each touchpoint to a specific value delivery. After a proposal goes out, the sequence might include a relevant case study from a similar client at day three, a piece of content addressing the most common objection in deals like this one at day seven, a specific industry development that connects to the prospect's situation at day fourteen, and a direct ask with honest framing at day twenty-one.
The length of the sequence matters. Most MSP deals do not close in the first two weeks after a proposal. MSPs who close the most competitive deals are often the ones who stay in play the longest, not with high-frequency contact but with spaced, valuable touchpoints that maintain presence without creating pressure.
Timing acknowledgment is one of the most underused tools in follow-up. "I know timing is not always right when proposals land. If this has moved down the list for now, I am happy to check back in next quarter" creates a graceful re-entry point for prospects who have deprioritized the evaluation rather than decided against it. It generates more responses than any check-in email.
Why do MSP deals go cold after a strong proposal?
Usually because follow-up stopped before the prospect's timing aligned with the solution. Prospects go quiet for reasons unrelated to disinterest: budget cycles, internal priorities, leadership changes. The MSP who stays present through those constraints is the one who closes the deal when they lift.
What is the most common follow-up mistake MSPs make?
Treating follow-up as a persistence exercise rather than a value delivery exercise. Check-ins remind the prospect that a proposal exists. They do not give a reason to re-engage. Each follow-up touchpoint should deliver something new: a relevant case study, a specific insight, an honest timing acknowledgment.
How long should an MSP follow-up sequence run?
Long enough to stay in play through the prospect's actual buying timeline. For most MSP deals, that means six to eight touchpoints over four to six weeks, with decreasing frequency and increasing value density. Sequences that end after two touchpoints leave most of the closing work undone.