The owner of a $2M commercial HVAC shop sends a cold email to a building manager.
The email is clear, well-written, mentions the building's age. No reply.
Three days later, the owner sends another. No reply. He gives up.
Here's what actually happened: that building manager opened email 1, was busy,
told themselves "I'll get to it later," and forgot. Email 2 hit during a meeting.
They glanced at it, didn't recognize the sender, archived it.
Single-touch outbound converts at <5%.
Five-touch structured cadence converts at 15–20%.
That's not a marketing claim — it's the math we run at FilterSwap.
The reason most shops don't do 5-touch is that it feels pushy, and they don't have
a structure that doesn't feel pushy. Below is the structure we use.
Five emails. Specific spacing. Each one does one job. No tricks, no "RE: Following up?"
subject-line games, no fake personalization.
Steal it.
Subject:<their building/property> — quick question
Hey <First Name>,
Drove past <specific landmark or property attribute — "the 3-story office on Main and 4th" or "the medical complex with the metal roof"> last week — looks like you're running <specific guess: "rooftop units that age" or "boiler heat in the basement">.
Quick one: when's the last time someone gave you a real preventive-maintenance schedule for that, not just "we'll come out when it breaks"?
If the answer is "never" or "I don't remember," I built a one-page diagnostic that shows the 3 things that fail first on properties your size. Reply "yes" and I'll send it.
— <Your First Name>
<Your Company>
Why this works: Specific reference (proves you didn't just blast the list). Diagnostic question (not "do you need HVAC?" — "what does your current schedule look like?"). Soft ask ("reply yes" is lower friction than "book a call"). The promised deliverable is real value, not a sales meeting.
Subject:Keep email 1's subject — reply to the thread
Hey <First Name> — bumping this up. Got your morning slammed? Just reply with "send it" or "not interested" and I'll get out of your way either way.
Why this works: Acknowledges they're busy (operator empathy, not pressure). Binary response option (yes/no — both are useful). "Get out of your way" is the operator-respect phrase that disarms.
Subject:<their building> — what we found at <similar property nearby>
<First Name>,
Last note on this — wanted to send you something concrete instead of asking again.
We did a walk-through at <similar property type, vague enough to anonymize> on <Street/area>. Three things we found that almost always apply to your kind of property:
<Specific issue 1 — e.g., "filters being changed but not the right MERV rating for the building's air-quality zone">
<Specific issue 2>
<Specific issue 3>
If any of those sound like maybe-issues at <their property>, reply "walk-through" and I'll come look. No charge for the look — only for what we'd actually fix.
— <First Name>
Why this works: "Last note" sets a soft deadline. Concrete findings prove competence. Free walk-through reduces commitment friction. "Only charge for what we'd fix" is operator-trust language.
Subject:Should I close your file?
Hey <First Name> — figured I'd ask before I stop bugging you.
Three options:
"Send the diagnostic" — I'll send it.
"Not now, check back in 6 months" — I'll set a reminder.
"Not interested, ever" — I'll close the file. No hard feelings.
Whichever's right.
— <First Name>
Why this works: Multiple-choice format (lowest possible response friction). Option 3 is real — people who say "not interested ever" are gold, they remove themselves cleanly. "Bug" framing acknowledges the cadence. Often produces the highest reply rate of the entire sequence.
Subject:<First Name> — quick check-in (no pitch)
Hey <First Name>,
Reached out a couple months ago and never heard back — totally fine.
Sending this because I just wrapped a project at <similar property type> and remembered you. If anything's changed at <their building> since spring (or you ever want a no-charge walk-through), just hit reply.
Otherwise, ignore this and have a good <month>.
— <First Name>
Why this works: 60 days is long enough that the silence is forgotten. "No pitch" framing is operator-respect. Reference back to a recent specific project keeps it grounded. The "ignore this" close is permission to not reply, which paradoxically increases replies.
Cadence summary
| Email | Day | Time | Subject treatment | Word count |
|---|
| 1 | 0 | Tue/Wed 9:30 AM | Specific hook | <80 |
| 2 | 3 | Fri 11:00 AM | Reply to email 1 thread | <30 |
| 3 | 7 | Tue 9:00 AM | Proof drop | <100 |
| 4 | 14 | Tue 2:00 PM | "Should I close your file?" | <40 |
| 5 | 60 | Tue 9:30 AM | Reactivation | <60 |
What you'll need (the unsexy truth)
This sequence works ONLY if you can deliver on three things:
1. Real personalization in email 1. Drive by the property. Look at the roof. Check the building's permit history. Specific = genuine. Generic = ignored.
2. A real deliverable for "send it" responses. When someone replies "yes" to email 1 or 3, you need to send them an actual diagnostic, not "great, let's hop on a call." If you don't have the diagnostic built yet, build it before sending email 1.
3. A 90-day discipline to actually run the cadence. Most shops set this up, send email 1, then forget emails 2–5. Run it from a CRM or sequence tool (Instantly is cheap and it works) — NOT from your inbox manually.
The 3 mistakes that kill this sequence
Mistake 1: Generic email 1. If your email 1 says "Hi, I noticed your business and wanted to reach out about HVAC services," you're done. Specific reference is non-negotiable.
Mistake 2: Fake "RE:" subject lines. "RE: Following up on our conversation" when you've never spoken — recipients sniff this out immediately and it permanently damages your sender reputation.
Mistake 3: Ditching the cadence after a single positive reply. If someone replies "yes, send it" to email 1 and you panic-pitch them on a call, you'll lose them. Stay in the structured flow: send the diagnostic, ask the qualifying question, THEN go to call.
This sequence is what we run at FilterSwap and what Anson built at Tailored Stays.
We're not a marketing agency. We're operators who built the systems behind both businesses,
and we ship the same systems to other service businesses.
Built by Anson Roberts. Tailored Intelligence. 2026.