Win managed-services clients away from break-fix IT with cold email

The easiest MSP prospect is not a company with no IT support. It is a company with IT support that already frustrates them: a one-person break-fix contractor who answers slowly, an outgoing MSP after a bad renewal, or an internal IT hire who just quit. These businesses have a working budget line for IT and a live reason to switch, which means your email lands on a problem they are already thinking about.

In FirstSales, build this list with AI Leads. Describe the target directly: company size (typically 15 to 150 employees, the sweet spot where a business needs real IT support but can't justify a full-time hire), industry verticals you service well (professional services, healthcare practices, manufacturing, whatever your team knows), and geography if you do on-site work. AI Leads finds and enriches matching companies and the quality funnel filters out weak matches before they cost you credits.

You can also import a CSV if you already track prospects that mentioned IT complaints on LinkedIn, in local business groups, or in RFPs you lost. Combine both: AI-sourced volume plus a hand-picked list of accounts you know are unhappy.

Watch company size closely, since it changes the whole pitch. A 15-person company usually has no formal IT budget line at all, just whoever answers the phone when something breaks, so your pitch there is really about giving them a budget line for the first time. A 100-person company already has a line item, often paying an incumbent, so the pitch shifts to displacing a specific vendor rather than creating demand from nothing. Segment your list by that distinction before you write a single line of copy, since the two groups respond to different opening arguments.

At a 20-person company, the owner or office manager usually owns the IT vendor relationship. At 80 to 150 employees, it is often an operations director, a controller, or occasionally a fractional IT lead. None of these titles want a sales pitch about your ticketing SLAs. They want their systems to stop breaking during business hours.

Titles worth targeting: Owner/President (under 30 employees), Operations Manager, Office Manager, Controller/CFO (for companies where IT budget rolls up to finance), and IT Manager if one exists but is overwhelmed and would welcome backup rather than replacement.

Avoid pure IT Director titles at larger orgs. Someone with that title usually has budget authority to build a team, not outsource it, and will read your email as a threat rather than help.

FirstSales runs automatic prospect research before drafting, and the transparency view shows exactly what it found and used per contact. For MSP outreach, the useful signals are recent hires (a growth spurt usually means more devices and more support tickets), office expansion or a new location, a job posting for an internal IT role that has been open a while (a sign their current support model is not working), or a recent security incident mentioned publicly.

You don't need to manually dig through LinkedIn for each one. Review the research summary before a campaign goes live and confirm it is pulling company-level signals rather than generic firmographic data. If a contact has thin research, hold that draft rather than sending a generic version.

Create your campaign and set the goal to book a meeting. In Campaign guidance, work through Describe, Teach, and Practice. In Describe, don't write "we provide managed IT services." Write the actual differentiator: response time. Something like "we guarantee a technician responds within 15 minutes and resolves most issues remotely same day, compared to the multi-day turnaround businesses get from break-fix contractors."

Response time is the single strongest lever in MSP sales copy because it is the thing prospects can feel immediately: the last time their printer, VPN, or server went down and nobody answered. If you have a real number (average first-response time, average resolution time, uptime percentage you maintain for clients), put it in Describe so the AI has it available. Never invent one.

In Practice, run through a handful of sample drafts against contacts with different research signals (one with a recent hire spike, one with a stale IT job posting) and confirm the AI is referencing the actual signal, not a generic industry line.

Paste 2 or 3 real emails your best rep has sent, or write samples yourself, into the writing style step. MSP buyers are burned by vendor pitches constantly. The winning tone reads like one business owner talking to another about a problem, not a sales rep reciting SLAs.

Subject: quick question about your IT setup

Hi Sam,

Saw [Company] added a few people this quarter, congrats. Quick question: who handles it when something breaks, like a laptop dies or the VPN goes down mid-day?

We work with a handful of companies your size around town and the thing that usually gets us in the door is speed. Most break-fix setups take a day or two to even respond. We're at under 15 minutes, most of the time resolved same day without anyone driving out.

Worth a 15-minute call to compare notes on what you're paying now vs what a flat-rate plan would look like?

Jordan

Keep it that short. One specific observation, one differentiator, one low-friction ask.

Set up a multi-step sequence with delays between touches, and remember steps stop automatically the moment someone replies, so you don't need to manually track who has responded. A good MSP sequence runs 3 to 4 steps over about two weeks.

Step 1 leads with the response-time angle above. Step 2, a few days later, can reframe around cost predictability: break-fix bills are unpredictable, a managed contract is a flat monthly number they can budget against. Step 3 can offer something low-commitment, like a free network or security review, which doubles as the trigger content in the next playbook. A final short breakup email ("should I stop reaching out?") often gets replies from people who were quietly interested but busy.

Keep each step to a few sentences. Nobody re-reads a wall of text on the third touch from a stranger.

Every reply that comes in goes to your unified inbox, and AI reply handling responds to what the person actually asked rather than a canned template. This matters more in MSP outreach than almost any other vertical: if your pitch is "we respond faster than your current IT company," and then you take two days to reply to an interested prospect, you have undercut your own pitch.

Check your inbox daily during an active campaign. Bounce handling auto-suppresses bad addresses so your list stays clean without manual cleanup, but a live reply from a warm prospect still needs a human eye on it quickly, even if the AI drafted a solid first response.

Check analytics for opens, replies, and meetings booked, broken down per step. Standard B2B cold email typically lands 2 to 5 percent reply rate and 0.5 to 1.5 percent meeting rate; that is a reasonable early benchmark for MSP outreach to businesses that don't know you yet.

If replies are low but opens are fine, the subject line and opening line are the problem, not the list. If opens are weak, check your sending domain setup first. If step 1 outperforms steps 2 and 3, your response-time hook is working better than your cost-predictability angle. Rewrite the weaker steps before you burn through more of the list; a bigger list with the same weak copy just gets you the same low percentage, faster.

Meetings booked matters more than raw reply count here. A campaign can post a healthy reply rate full of polite no's and still book nothing, while a smaller campaign with fewer replies but a sharper qualifying question in step 1 books more calls. Look at your meeting-to-reply ratio specifically. If it's low, the issue usually isn't your hook, it's a weak or missing call to action at the end of the email.