The Account Brief Standard: What a Rep Needs Before First Touch
You can grade any account brief pass or fail against a fixed evidence bar and name the single missing field that blocks it.
This guide gives sales leads a fixed evidence bar for deciding whether an account brief is ready to hand a rep for outbound. It is written for founders doing their own selling, account executives, SDR leads, and partnerships teams who need two people to grade the same brief the same way. You will finish able to score any brief pass or fail in one pass and name the single field that blocks it when it fails.
The problem this fixes is grading drift. Most account-research guides are an unbounded "dig deeper" checklist or a tool pitch, with no line for when research is done. So quality swings from rep to rep, managers cannot grade it, and reps drown in analysis paralysis. A Standard replaces that with a minimum bar and a stop rule.
What counts as a complete account brief
A brief is complete when five fields are present and current: ICP fit, a dated trigger, a mapped committee, verified contact data, and an account-specific hook. Depth beyond those five is optional; their absence is disqualifying. This is the whole standard, and everything below is how to apply and defend it.
The reason to anchor on five fields rather than a page count is that fields are gradeable and pages are not. Two people looking at the same brief can agree on whether an economic buyer is named. They cannot agree on whether the research is "thorough enough." The bar exists to remove that argument.
Here is what each field proves, and what it looks like when it lies.
| Required field | What it proves | What it looks like when it lies |
|---|---|---|
| ICP fit | The account is worth a rep's time | Passes on a stale funding or headcount value |
| Dated trigger | There is a reason to reach out now | A generic industry trend logged as an event |
| Committee map | The deal is threaded, not single-threaded | One name that is really the researcher's easiest find |
| Verified contact data | The message will reach a real inbox | CRM shows "valid" on a record 18 months old |
| Account-specific hook | The message could only go to this account | A value prop reworded to look bespoke |
The bar is deliberately short. A rep can carry five fields in their head. A grader can check five fields in three minutes. Anything longer stops being a standard and becomes the same open-ended checklist the standard was meant to replace.
The evidence bar, field by field
Each of the five fields has a pass condition specific enough that two graders reach the same verdict. Vagueness in the bar becomes drift in the grading, so each condition is written as a check, not a topic.
ICP fit. Pass when the account clears a fixed firmographic filter you set once and apply to every account. This is a five-minute check and a fail here stops everything. Note that some frameworks run signal-first: they start from a trigger and check ICP second, reversing the order. Either order works as long as both conditions are met before grading.
Dated trigger. Pass when one event from the last 30 to 90 days is recorded with a source link. The published validity test has three parts: the event is recent, it changes the account's status quo, and it opens a window where your solution is more relevant than before. Leadership change is the highest-converting type, because new executives re-evaluate the tech stack within their first 90 days. Roughly 99% of B2B purchases are driven by organizational change, so a dated org event is not a nice-to-have; it is usually the reason the deal is winnable at all.
Committee map. Pass when 3 to 6 roles are named for a mid-market deal, each with a title and function. At minimum the brief carries an economic buyer and a champion. Record three things per member: role and function, decision power (economic buyer versus champion versus user), and their specific pain or objection.
Verified contact data. Pass when email and phone for each named person were verified within the last 90 days, with unverified fields flagged. An unverified economic buyer is a fail, not a warning.
Account-specific hook. Pass when one relevance line ties the logged trigger to a named pain and is distinct from the value proposition. If the line could be pasted into another account's brief unchanged, it fails.
Why freshness beats depth
The load-bearing field is a verification date, not more insight. B2B email decays about 3.6% per month, so a brief researched a quarter ago is already unreliable even if every insight in it was correct when written. This is the single most important claim in the standard, because it reverses the instinct that more research is safer.
The mechanism is that a CRM displays stale records as valid. A contact who left a company 18 months ago still appears as an active record, complete with title, phone, and company affiliation, all of them wrong, and the system has no way to surface that decay. You do not find out until the send bounces. After twelve months without a refresh, 30 to 70 percent of contacts may reach the wrong person.
That is why the standard grades a date rather than an amount. Here are the refresh cadences the bar enforces, drawn from published decay rates.
| Field type | Refresh cadence | Bar for grading |
|---|---|---|
| Email, phone, title | every 90 days | Reject if last verified over 90 days ago |
| Company size, funding, tech | every 6 months | Refresh if over 6 months old |
| Signal or trigger data | continuous | Must be dated within 30 to 90 days |
| Bounce rate on send | monitored | Stop sending above 10% |
The bounce threshold is the hard floor. Under 2% is excellent; above 10% you stop sending, because that level of bad data damages your sending domain and takes weeks to recover. Verifying contact data before grading is cheaper than repairing a burned domain after.
Market scarcity should set how strict you are. In Refolk's index, the US Account Executive pool of 239,400 dwarfs Germany's 2,686 by roughly 89x, and the US SDR pool of 21,305 runs about 6.8x the UK's 3,130. In a thin market a rep cannot afford a burned contact, so hold the freshness bar strictest where the contact pool is smallest.
| Role | United States | Second market | US-to-market ratio |
|---|---|---|---|
| Sales Development Rep | 21,305 | UK 3,130 | 6.8x |
| Account Executive | 239,400 | Germany 2,686 | 89.1x |
Counts are from Refolk's index of professional profiles; the ratio is derived by division.
What personalization actually buys you
Account-specific personalization roughly doubles reply rate, from about 9% for generic messages to up to 18% for advanced personalization. Anchor the standard on that 2x lift. Larger "15x" claims come from vendor blogs comparing a best case to a worst case and do not survive scrutiny.
A separate large study of twelve million emails found personalized messages received 32.7% more replies than non-personalized ones. Both figures point the same direction: personalization is worth requiring, and it is worth exactly one well-aimed hook, not a dossier.
| Condition | Reply rate | What it tells the grader |
|---|---|---|
| Generic template | ~9% | Baseline; the hook field is doing no work |
| Advanced personalization | up to 18% | The hook is worth requiring |
| 1 to 2 contacts per account | 7.8% | Tight first-touch list signals intent |
| 10+ contacts per account | 3.8% | Wide blast reads as low intent |
Contact spread is a gradeable field in its own right. Reply rate nearly halves, from 7.8% to 3.8%, when a brief lists ten or more contacts instead of one or two, because buyers read a wide blast as low intent. The full committee belongs in the brief for sequencing; the first-touch list should stay capped at one or two.
Why a tight first touch beats a wide blast
- 7.8%1 to 2 contacts per account
recommended first-touch cap
- 3.8%10 or more contacts per account
nearly halves the reply rate
Require one well-aimed hook, not a dossier. Personalization doubles reply rate; it does not multiply it fifteenfold.
Questions practitioners ask
How much account research is enough before outbound?
Enough is a fixed set of five fields, not a time budget: ICP fit, a dated trigger within 30 to 90 days, a named economic buyer and champion, contact data verified within the last 90 days, and one account-specific hook. When all five are present the brief passes. Practitioners report spending 1 to 3 hours per account, which is well past the point of diminishing returns; a complete brief, not an exhaustive one, is the bar.
What should a sales account brief include?
A brief must carry ICP-fit confirmation, one dated qualifying trigger with a source link, a mapped buying committee of 3 to 6 named roles with title and function, contact data verified inside 90 days, and a single relevance hook tying the trigger to a named pain. Anything beyond those five fields is optional depth. The economic buyer and champion are the minimum committee coverage; a single-thread brief fails.
When is an account ready to work?
An account is ready when a second person can grade the brief pass on the five-field bar without adding research of their own. If any required field is missing, the account is not ready and the grader names the one blocking field. Trigger recency is usually the field that decides it: no dated event inside 30 to 90 days means not ready, regardless of how much other context exists.
How recent does a trigger event need to be?
A qualifying trigger must fall within the last 30 to 90 days, be specific to the account rather than the industry, and change the account's status quo. Leadership change is the highest-converting type because new executives re-evaluate the tech stack within their first 90 days. A generic industry trend or an event older than 90 days is a false positive: it reads relevant but fails the test.
How many contacts should a first-touch list name?
Cap the first-touch list at one to two contacts per account. Reply rate runs about 7.8% at one to two contacts and drops to 3.8% at ten or more, because buyers read wide blasts as low intent. The full committee of 6 to 10 people belongs in the brief for sequencing, but the initial send should stay tight.
How often should contact data be re-verified?
Re-verify email, phone, and title every 90 days. B2B contact data decays about 2.1% per month overall and email addresses about 3.6% per month, so a record left unchecked for a quarter is already unreliable. Company size, funding, and tech signals can refresh every six months. If a send would push bounce rate above 10%, stop; that level damages sending domain reputation.
Try it on your own search
Stop building boolean strings. Just describe the person.
Type one sentence and I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web live, then hand back a ranked shortlist with the reasoning behind every name. No filters to learn, no export to clean up, no sales call to sit through.
- One sentence in, a ranked shortlist out. No boolean, no filters, no seat to buy.
- Read live at search time, not from a database that went stale last quarter.
- Watch every step as it runs, and see why each name made the list.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
500 free credits on sign-up. No card, no demo call. See real searches.