If you're building or running cold outreach — whether that's a side-project SaaS or an internal sales tool — you've probably seen the classic persona template: a stock photo, a fake name, favorite podcasts. It's useless for outbound, because none of it compiles down to anything executable. You can't filter a company database by hobbies.
Here's the mental model that actually works: a persona is only as good as the queries it generates. Every question you answer about your buyer should map to one of two outputs — a filter on your prospect list, or a variable in your email's first line. If an answer changes neither, delete the question. Think of the persona doc as a spec that a list-building script and a copywriter can both execute against without asking you anything.
Filter at the account level first
In B2B, the company buys, not the person. So before profiling any human, define the account-level WHERE clause — your ideal customer profile. Every field should be something you can actually query in a data source:
- Industry — real classification codes, not vibes
- Headcount and revenue band — big enough to have the pain, small enough to buy without a 9-month procurement cycle
- Geography — where you can legally email and realistically serve
- Tech stack — tools your product plugs into or replaces (detectable via job posts, BuiltWith-style footprints)
- Observable proof of the problem — a job posting, a license, a fleet size
The underrated half of this: define disqualifiers with the same rigor. Every account you correctly exclude is a contact you didn't buy, verify, write to, and burn sender reputation on. Exclusion filters save more money than inclusion filters ever will.
Model three people per account, not one
A single persona hides the actual decision graph. Most deals worth pursuing involve three recurring roles: the problem owner (lives with the pain daily), the economic buyer (owns the budget), and the blocker (often IT, legal, or finance — can quietly kill everything). For each one, answer the questions that change your copy:
- What exact job titles show up in databases, including the messy real-world variants?
- What KPI are they judged on? A persona is ~80% defined by the number in their bonus letter.
- What are they using today instead of you — a competitor, a spreadsheet, an intern, nothing?
- What's their fastest reason to delete a cold email — length, jargon, wrong assumption about their role?
You usually email the problem owner or the buyer, but knowing the blocker changes how you write for both.
Triggers turn a static persona into a schedule
Two identical companies respond completely differently depending on timing. A logistics director who just inherited a broken WMS migration replies to the exact email she deleted six months ago. So ask: what observable events mean the problem just became urgent? Hiring sprees, funding rounds, leadership changes, tech migrations — the key word is observable. A trigger you can't detect from outside is a theory; one you can monitor becomes a cron job that feeds your list. In practice, catching a trigger lifts reply rates more reliably than another round of copy polish.
Validate against reply data, not opinions
Your persona doc is a hypothesis. The test is campaign data: a well-targeted cold B2B campaign should land somewhere in the 3–8% reply range. If a segment consistently underperforms, the persona is wrong — wrong titles, wrong pain, or wrong trigger — and the fix is editing the filters, not rewriting the email for the fifth time. Treat it like any other feedback loop: ship the segment, measure replies, patch the spec, redeploy.
One page per segment is enough. If it doesn't fit on a page, you haven't finished deciding who you're actually targeting.
Full breakdown with sample funnel and selection parameters in the original: B2B Buyer Persona Questions for Cold Outreach Targeting.
Top comments (0)