By the Outsquid team · · How we write
Cold email template for users of a tool you work with
A first email to people who use a tool your product integrates with or works alongside.
When to use it
You know the company uses a tool your product connects to, or one whose users often need what you do — from their job posts, website or a technology lookup.
The template
Subject[tool] + [your product category]
Hi {{firstName|there}},
Looks like {{company|your team}} runs on [tool]. Teams that do often hit [a limit or gap people have with that tool].
We [what you do] and connect to [tool], so [what that means in practice — e.g. "replies land in the same record your reps already work from"].
Is [the gap] something you've had to work around?
Other subject lines
for {{company|your team}}'s [tool] setupusing [tool] at {{company|your team}}?
Why it works
- The tool gives you a real, checkable reason for writing.
- Naming a known limitation shows you understand their setup.
- The question invites them to describe their workaround — a natural start to a conversation.
Make it yours
The template is the frame. These are the parts that earn the reply:
- Where you learned they use the tool — get it right, or leave the email unsent.
- A limitation users of that tool actually talk about, in their words.
Before you send
- Fill in every [bracketed] part, and preview the email for a few real prospects — especially ones with missing fields. Writing follow-ups
- Send from a domain with SPF, DKIM and DMARC set up, and check it before the first campaign. Free DNS checker
- Ramp new mailboxes up slowly and keep each one to a modest daily volume. Ramping up a new mailbox
- Say who you are, give people an easy way to opt out, and stop when they ask. Unsubscribes in cold email