The 600-Contact Spray
Elena sells managed cybersecurity and IT support to mid-market companies. She has 600 contacts pulled from an old trade-show list and a co-hosted webinar, and she is expected to book 12 meetings a quarter from outbound.
Her sequence is five emails over 18 days. The subject line is 'Quick question,' the body runs about 250 words, opens with 'I hope this email finds you well,' lists six certifications and a 24/7 SOC, and attaches a 12-page brochure. She sends from her own address, Monday at 7 a.m., and follows up by phone once. Reply rate is 2.1%, meeting rate 0.3%, and two prospects have asked to be removed. When she does reach someone, they often say they already have a provider or 'we're not looking right now.'
Her prospects are IT directors at companies with 200-800 employees; most have a small internal team, a compliance audit coming up, or a recent incident. Elena believes the problem is that she needs a bigger list.
1. Diagnose why Elena is failing to earn attention, given how today's buyers research before they engage with a rep.
Read the worked answer
Elena's buyers are largely self-educated by the time she appears. They have already read vendor sites, peer threads, and review platforms, and they can identify a mass email in the first line. That changes what earns attention: relevance to something already happening inside their company, not a list of vendor credentials.
What is failing:
- 'Quick question' and 'I hope this email finds you well' signal a template. The buyer's first question is 'is this about me?' and nothing in the first two lines answers it.
- The body is vendor-centric. Six certifications and a 24/7 SOC describe Elena's company, not the IT director's audit deadline, headcount constraint, or recent incident.
- The 12-page attachment asks for effort before trust exists and often triggers spam suspicion.
- One segment for 600 contacts ignores the three different situations she named - audit, small team, incident - which require different openings.
- Monday 7 a.m. is a guess, not a personalization.
A bigger list multiplies a message that isn't landing. The 2.1% reply rate is what a relevant-market message with no relevance looks like.
2. Rewrite the first touch for the compliance-audit segment. Give the structure and a short sample, and explain what you deliberately left out.
Read the worked answer
Structure for a first touch:
- Subject line tied to their world, not the sender's: 'Audit evidence for the 200-800 seat range' rather than 'Quick question.'
- First line about them: the specific situation that triggered the segment.
- One useful insight or observation they may not have - something that proves Elena understands the problem, not the product.
- One low-friction ask with a clear reason to reply, and no attachment.
- Under 100 words, sent from a person, with a real signature.
Sample: 'Most IT directors we speak with at your size are preparing for an audit with a team of three or four and no dedicated compliance analyst. The part that usually slips is evidence collection for endpoint and patch status - it is spread across tools nobody owns. We put together a one-page checklist of the evidence auditors ask for first. Want me to send it over?'
Left out deliberately: certifications, SOC language, the brochure, the company history, and any request for a 30-minute meeting on the first touch. The goal of touch one is a reply, not a demo.
3. What should Elena measure instead of reply rate alone, and how should she run a test so she learns something?
Read the worked answer
Measure positive reply rate (replies that engage with the problem rather than unsubscribe or 'not interested'), meetings booked per 100 contacts, and meetings held, all split by segment and by message variant.
Why not reply rate alone: it counts 'remove me' alongside 'send the checklist.' A message can raise replies while lowering quality. Meetings held is the real outcome, since a booked meeting that no-shows teaches nothing.
Test design:
- Split the list by the three situations she described - audit, small team, recent incident - and write a first touch for each. Send the same follow-up structure to all three so the variable is the opening.
- Change one thing at a time: subject line, opening line, or ask. Changing all three at once makes the result unreadable.
- Use enough volume per variant to be meaningful - roughly 100-150 contacts per cell, not 20 - and give it two to three weeks before judging.
- Track by segment so a strong audit segment is not hidden by a weak generic one.
Then scale the variant that produces meetings, and retire the rest.