What you'll get
- 10 copy-ready blocks
- 6 min read
- 1. Trigger event
- 2. New leader in the chair
- 3. Hiring signal
- 4. Ageing system
- 5. Peer proof
- 6. The useful asset
- and 4 more
Cold email templates for IT services fail in one predictable way: they describe the sender. A list of services, a client count, an offer of a call. These ten do the opposite. Each opens with something true about the reader's company, which means each needs a minute of research before sending. That minute is the price of a reply.
How to use these templates
- Fill every [bracket] with a researched fact, not a guess. The Trigger Event List shows where to look.
- Keep each under 90 words after filling. Cut yours, not the fact.
- Send to a named person who owns the problem, never info@.
- One template per account at a time. Follow up twice, then stop or switch.
The named-account set these extend is cold email templates for named accounts. The Cold Email Writer assembles drafts from your own inputs. More for your sector under sales for IT services.
Templates 1 to 4: Something changed at the account
1. Trigger event
Subject: [event] and [system area]
[First name], saw [company] announced [event, with source]. Teams usually
hit [specific problem] within a few months of that.
We handled the same for [peer company]: [one-line outcome].
Worth 15 minutes to compare notes before it bites? If [better role] owns
this, happy to be pointed there.2. New leader in the chair
Subject: your first 90 days and [system area]
[First name], congratulations on the [role] move. New [role]s usually
inherit one system everyone has learned to work around.
At [peer company] that was [system]; we [one-line fix and result].
If something similar is on your list, 15 minutes might save you a quarter.3. Hiring signal
Subject: the [role] openings
[First name], [company] has [n] open roles for [skill]. That usually means
either a big build or a backlog.
If hiring is slow, we have put [skill] teams into [peer company] inside
[timeframe], alongside their own hires rather than instead of them.
Useful to compare numbers?4. Ageing system
Subject: [system] end of support, [date]
[First name], [system]'s [version] support ends [date, with source].
Migrations booked late cost more and land badly.
We moved [peer company] off it in [timeframe]: [one-line outcome].
Want the one-page plan we used? No call needed; happy to send it.Templates 5 to 7: Proof does the talking
5. Peer proof
Subject: how [peer company] handled [problem]
[First name], [peer company], about your size in [sector], had [problem].
We [what was done] in [timeframe]: [one measurable outcome].
If [problem] is on your plate this year, I will walk you through exactly
what we did, including what went wrong. 15 minutes.6. The useful asset
Subject: [problem] checklist, no strings
[First name], we wrote a one-page checklist for [problem] after doing it
[n] times, including the two steps everyone misses.
Want it? Reply "send it" and it is yours. If it is useful, you know who
wrote it.7. The honest question
Subject: [problem] at [company]?
[First name], quick question, feel free to say no: is [specific problem]
something [company] has in hand, or still on the list?
Asking because [one researched reason]. If it is handled, I will not
follow up. If not, I have a view that might save you some time.Templates 8 to 10: Routes and exits
8. Partner route
Subject: [platform] work at [company]
[First name], as a [platform] partner we see [company] runs [platform
product, with source]. Teams often use only part of what they pay for.
We did a [scope] review for [peer company]: [one-line outcome].
Worth a look before renewal?9. The forwardable
Subject: who owns [problem] at [company]?
[First name], I think [problem] sits near your team but maybe not with
you. Could you forward this to whoever owns it?
For them: we solve [problem] for [sector] firms; [peer company] saw
[one-line outcome]. Happy to share how in 15 minutes.
Thanks either way.10. The break-up
Subject: closing the loop
[First name], three notes and no reply usually means not now, which is
fine. This is the last one.
If [problem] comes back, two things age well: the [asset] from my first
note, and this address.
Good luck with [the thing they are building].Worked example (illustrative, not a real company)
Tessaro Analytics sells data engineering to logistics firms. Sam Carter targets Northfield Logistics, which has announced a new distribution centre and four open data roles. Template 1 goes to the operations director naming the centre; template 3 to the head of data naming the roles. The ops director forwards it (template 9's effect without sending it) and the head of data replies "send it" to the checklist offer. Two threads inside one account in a week, both from researched facts. All names are invented.
Five mistakes to avoid
- Listing services. "We do cloud, data and AI" describes you. Every template here opens with them.
- Faking the research. An invented trigger is worse than none; one wrong fact and the domain is remembered for it.
- Writing 200 words. Senior readers decide in two lines. Under 90 words, every time.
- Asking for an hour. The ask is 15 minutes, a forward or a one-word reply. Small asks get granted.
- Sending all ten to one person. One template, two follow-ups, then switch person or park the account. Ten angles at one inbox is a blacklist application.
Why this works on named accounts
Common questions
Do cold email templates still work for IT services?
Templates work when the opening fact is real and the reader owns the problem. What stopped working is the capability blast sent to a scraped list. Research per account, under 90 words and a small ask still earn replies in 2026.
Who should IT services cold emails go to?
The person who owns the problem day to day, usually a head of function, an IT or engineering director or an operations lead. CEOs forward at best. For enterprise accounts, map the full committee first and write to two or three roles with different angles, not the same email to all.
How many follow-ups should you send?
Two after the first email, each adding something new: a fact, an asset or a name. Then stop, or switch to another person in the account. The break-up template exists so the last note leaves a good taste rather than a block.
More from the Academy
12 Cold Email Templates for Named Accounts
For anyone writing a first email to a senior buyer in a large company.
You leave with 12 templates under 110 words, the research each one needs, one filled-in example and a five-point check.
The Trigger-Event List: When to Approach an Account
For sellers with a good account list and no idea which account to work this week.
You leave with 12 trigger events, where to spot them and who to approach when one lands.
ChatGPT and Claude Prompts for Writing Cold Emails
For sellers who use ChatGPT or Claude to draft outreach and get emails that sound like everyone else's.
You leave with a set-up prompt, a research block, 10 prompts that draft, cut, criticise and fact-check, and one worked draft.
Cold Email Writer
Three email drafts assembled from your own research, plus a prompt for your own AI assistant. Template-based, no model call. Runs in your browser.
Want this in your inbox?
Optional. We use your email only to send you this, nothing else.