What you'll be able to do after this guide: give an agent a structure and a set of rules for first emails that sound like a person who did their homework, not a template.
Worked example first
Here's a first email drafted by a Fernhill agent for the operations director of a 40-person company. The research found a job advert for a "Competitor B administrator" on the company's careers page.
Subject: Your Competitor B administrator role
Hi Dana,
I'm Priya, one of the founders at Fernhill. I saw you're hiring someone to look after Competitor B.
Hiring a dedicated person to look after one tool is a real cost for a team of 40. Is it taking more of your team's time than you expected?
Fernhill handles the setup and the hosting for you, so much of that work comes off your team's plate, and our team is a message away when something needs changing.
On what I can see, this looks like a strong fit for how you're set up. Would you be open to a short call so I can understand the detail and be sure?
Priya
About 100 words. Every sentence comes from the research or the product. Now the rules that produced it.
The four moves
Each email has four short paragraphs, each doing one job:
- Hook. Something specific enough that it couldn't have been written without looking at this company. Written in the first person with a subject: "I saw...", "I noticed...", "I've been looking at...". In a cold email, introduce yourself here too.
- Why it matters. A consequence, a cost, a deadline or a piece of evidence. The most common failure is simply restating the hook in other words.
- Benefit. One or two benefits that answer this hook, written for this reader. Never list everything your product does.
- Ask. A short call, stated with confidence about the fit, with the call there to confirm the details. Don't open with "this might not be a fit"; that's an apology before you've started.
If you include a link, put it straight after the paragraph it supports, with a natural lead-in such as "I have a page about this if it's useful:". Only link to a page that matches the evidenced problem closely. A loose match is worse than no link.
Before drafting: two questions
Does this organisation sell your kind of thing, or use it? A company that delivers your kind of product to its own clients needs a different benefit from one that uses it internally. Research tools tend to surface one kind more than the other, so judge the organisation, not the shape of the evidence.
Is this person the decision-maker? If not, write an ally email: aim the benefit at their own working week and ask whether it would help them. Never play down their role or ask who the "right person" is. Test: would any sentence land badly if they forwarded it to their boss?