The account gate
If you decide which accounts your sales reps work, you own the most important number in outbound, and it never shows up on a dashboard: how many accounts on the list should be there at all.
Most teams try to fix outbound by changing the copy.
They test subject lines, add a personal first line and swap the CTA.
That's the cheap part to change, and it's rarely the problem. When the list is wrong, good copy just reaches the wrong people faster.
This post is for the person who builds that list, whether your title is VP Sales, Head of SDR, RevOps or founder: one play from our own client work, the data behind it, and a framework you can run this week.
What we saw when we looked
Two things we worked on this year changed how we build lists.
First: some companies tell you what they need. We ran a hiring-signal play on one job title, GTM Engineer, across the US and Canada. The discovery step found 59 companies hiring for it. A company that posts that role has already admitted three things in public: it has a GTM data problem, it has budget, and someone senior thinks it's urgent. You don't have to guess at intent, because the job description lays it out.
The job descriptions were the most useful part. When we pulled the postings word for word and searched them for repeated phrases, the same pains kept coming up: work done by hand, too many tools doing the same job, and building the function from scratch. That's language you can reuse in outreach, and the buyer wrote it.
Second: a good list can still burn your domain. We coached a hardware-services team whose reps were running their own cold outbound. Their audit covered 765 sends over three months. 20.8% bounced, and 153 were blocked as spam, almost all of them by Gmail citing low domain reputation. The copy wasn't the problem. Unverified contacts went into sequences, and every bounce cost them reputation. Their opens and clicks also read above 100%, because security scanners were counting as opens. The dashboard looked healthy while the domain was failing.
The first story shows a reason an account belongs on the list. The second shows what happens when nobody checks the list before it reaches the reps.
The framework: the 4-check Account Gate
No account goes to a rep until it passes all four checks. If it fails any of them, it waits. Don't spend enrichment credits or sends on it, and don't hand it to a rep.
1. Reason: is there a public reason this account has the problem now?
A structural signal qualifies: an open role your offer maps to, a new sales leader, a tool change, a filing. Firmographics alone don't. "500 employees, SaaS, US" describes a company. It doesn't tell you anything is wrong there.
Test: write the reason in one sentence. If the sentence would also be true of their nearest competitor, it's a category, not a reason.
2. Words: do you have their language (not your sales jargon)?
Pull the source word for word, whether that's the job post, the earnings call or the leader's own post. Mark the pain phrases. Your first line should use their words.
Test: if you could send the line to another account with only the name changed, it fails.
3. Clock: is the signal still live?
Signals decay. A role posted this week is a trigger. A posting that says "no longer accepting applications" means the moment has passed, and they've probably already hired the person who'll fix it. We rank by pain first and recency second, and the best accounts score high on both: high pain and posted within the last 7 days.
Test: write the date of the signal on the account. If you can't find one, it fails.
4. Clean: can you reach them without landing in spam?
Use verified contacts only. Set daily caps per mailbox and ramp up slowly. Keep cold mail off your main domain. Judge results on replies and meetings, not opens.
Test: if the contact isn't verified, it doesn't go in a sequence. The send isn't free. It spends reputation you need for the next hundred sends.
In short: Reason, Words, Clock, Clean. The first two decide whether an account is worth a message. The last two decide whether you can send that message now.
How to run it this week
Pick one job title whose existence implies a need you solve. Don't pick a whole industry.
Find every company hiring for it. Drop recruiter and "Confidential" posts, because you can't research them.
Pull each job description word for word and highlight the pain phrases.
Score every account on the four checks. Hold anything that fails.
Give your reps only the accounts that pass, each with its reason, its words and its date written next to it.
The list will be much smaller than your usual one. That's fine. A shorter list your reps believe in will get more done than a long one they work on autopilot.
Get the Hiring-Signal Playbook. It's the step-by-step version of this issue: how to find every company hiring a given role, pull the pain language, and rank accounts by pain and recency, then run every account through the gate.
Reply and tell me which job title you'd run this on first. I read every reply.
CT