Cold Email Templates for IT support providers
Three short first emails for IT support and managed services, a follow-up that adds something new, subject lines, and the public signs that a business may need you. Free to copy, no sign-up.
IT support is sold on reliability and trust, so a cold email from a stranger starts at a disadvantage. What helps is pointing at something specific and public that suggests risk or friction, without scaremongering. A company whose staff use personal Gmail addresses, a domain with no DMARC record so anyone can send mail that appears to come from it, an office move announced on LinkedIn, a team that has doubled in a year with no IT role on the payroll. Each can be checked with free tools in a minute. Explain the finding calmly, say what it means for the business, and offer a short, no-obligation review. Never imply they've been hacked, and never test their systems without permission. Established local offices are often the best fit.
Who buys IT support and managed services
Accountants, solicitors and architects hold sensitive client data and can't afford downtime.
Patient systems, imaging and phones all need to work every day, under strict privacy rules.
They've outgrown 'the person who's good with computers' but can't justify a full IT team.
Networks, phones, printers and security all have to be ready on a fixed date.
Tight budgets and many shared devices make reliable, simple support valuable.
Signs a business may need IT support and managed services
Each one is public and takes about a minute to check. Mention the one you actually found; it is what makes the email worth answering.
Look at the contact and team pages for Gmail, Outlook.com or Yahoo addresses.
Enter their domain in a free DNS checker such as MXToolbox and read the DMARC and SPF results.
Check LinkedIn posts, their news page and Google Maps for a new address or a 'we're moving' note.
Compare their headcount on LinkedIn over time and look for IT jobs on their careers page.
Load the site and check the padlock and the certificate's expiry date in the browser.
Three first emails for IT support and managed services
Replace everything in {curly brackets}. Send each one by hand, to one person, about one thing you noticed.
A free DNS lookup shows their domain has no DMARC policy.
Subject: email security for {Company}
Several public checks turn up small issues, one of them worth acting on soon.
Subject: a one-page it health check
They've announced a move to new premises in the coming weeks.
Subject: the it side of your office move
The follow-up
Send it once, four to seven days later, and only if it adds something. If there's still no reply, stop.
Subject: one more check for {Company}
Subject lines
- email security for {Company}
- a one-page it health check
- the it side of your office move
- staff email addresses on your site
- your website certificate
- it support as you grow
Mistakes to avoid
- Using fear. Phrases like 'you're about to be hacked' read as a scam and get deleted.
- Running scans or login attempts against their systems. Check only what's public, and ask before anything deeper.
- Opening with a long list of certifications and vendors. Lead with their problem and put credentials in your signature.
- Pitching a full managed contract first. A one-off fix or a move project is an easier yes and shows how you work.
Describe the clients you want and where. DealInSec's Client Radar researches real companies that fit, checks each one's own website, shows what it found with sources, and drafts a first email for you to read, edit and send yourself. Free plan, no card.
Cold email templates for other services
Cold emails for IT support and managed services: questions
What can I check about a company's IT without permission?
Only what's public: their website certificate, DNS records such as SPF and DMARC, which email provider their MX records point to, and anything they post about offices, staff and tools. Avoid port scans, login pages and vulnerability scanners on systems you don't manage, since running them without permission may be illegal where you or they are. If a finding needs deeper testing, ask first.
Should I mention a security weakness in a cold email?
Yes, if it's public and you explain it calmly, like a missing DMARC record. Don't publish it, don't share it with anyone else, and don't exaggerate the risk. Offer the fix rather than a scare story. If you find something serious, such as exposed data, consider reporting it through their security contact instead of using it as a sales opener.
Who should I contact at a firm without an IT person?
The managing partner, practice manager or office manager. In small firms, IT usually falls to whoever runs operations, and they feel the pain when things break. The About page or LinkedIn will often show who that is. Keep the email non-technical, since they're unlikely to be an IT specialist.