Every GTM org says it does ABM. Ask the team what the list of accounts they want in pipeline is, and count the different answers. Last quarter Henry talked to 86 revenue leaders about ABM. Many could not answer that question, and most were missing at least one of the four things below.
The four things are not complicated. A true list of accounts everyone can find. Named buyers at those accounts. Signals that are proven to change conversion. And the context of every prior touch, brought together in one place the whole team works on top of.
ABM, AI-orchestrated workflows, SDR outbound: none of it works until those four are in place. That is why armies of RevOps, SalesOps and GTM engineers exist, stitching them together in real time, over and over. This play is how to build them once.
1. A true account list
Not "companies that look like this." A concrete, named list: these accounts, this many, and anyone in the GTM org can open it in seconds. The rule that builds the list re-runs so it never goes stale; what everyone works from is still a list with names on it.
A true list is
Concrete: named accounts and a count you can say out loud
Findable: one place, no export, the same answer for sales, marketing and CS
Focused: the part of the market you actually win in, not the whole market
Off the shelf: customers, open opportunities, rep-owned accounts and companies with no sales function already scrubbed out
Alive: the rule re-runs, so accounts that grow into the profile appear and accounts that fall out drop away
Why concrete beats theoretical. A profile lets every team interpret it differently. A named list is a shared fact. If sales and marketing are working different lists, you do not have ABM, you have two campaigns.
Why the scrub is part of the list, not a later step. A list that still needs a second pass before anyone can use it is not off the shelf. Scrub at the account level, against your own CRM, before the list is published.
2. Named buyers at those accounts
Not "sometimes the CISO, sometimes the VP of Infrastructure." Specific people, by name, at every account on the list. Start from which functions have a stake in the decision, then find the named contacts inside each one, and keep watching them, because named buyers move.
For every account
The functions that influence, approve, implement and expand
A named person in each function
Role, seniority and influence recorded, not guessed
Where coverage is thin, so the gap is visible
Changes tracked: a champion moving in or out, a new hire into a committee function
Why names, not personas. A persona tells you who to look for. A name tells you who to call. The difference is the entire gap between a strategy deck and a working list.
Why the list of buyers needs watching. A list of names that was right in January is wrong by June. A champion who changes jobs is both a maintenance task here and one of the strongest signals in step 3.
3. Signals that are proven to matter
What makes a signal matter? Data. When this signal occurs, accounts on the list convert at a meaningfully higher rate. If you cannot show that, it is not a signal. It is a hunch.
Signals worth testing
The obvious ones
Visited the pricing page, or a product or integration page
A champion who bought before just moved to this account
Hired a new member of the buying committee
Just raised funding
The less obvious ones
A job posting that describes the problem you solve
A new executive hire in a function you sell to
Adopted or dropped a technology in your category
A surge of research on the topic you solve
Freshness rule. A pricing-page visit last week is worth acting on. The same visit last year is noise. Let old signals expire rather than pile up, and let several fresh signals on one account combine into one score, with a plain reason attached.
Why proof and not instinct. Every signal feels important to the person who suggested it. Conversion data settles the argument and stops the list of "signals" growing until it means nothing.
4. Context
Signals tell you an account is moving. Context tells you what to say. Before anyone acts, the record should answer the questions a good rep would ask in the first five minutes.
Context to capture
Have we talked to this account before, and what happened
Were they a customer, or a closed-lost opportunity, and why
What they told us about their current provider
Their tech stack
Exec connections between their team and ours
Investor overlap
Why context is the thing most teams skip. It lives in six systems and three people's heads. Pulling it into one record is unglamorous, and it is the difference between outreach that lands and outreach that gets the reply "we spoke to you in 2024."
Bring it together, then orchestrate
Accounts, buyers, signals and context in one record the whole GTM org works on top of. Not four spreadsheets and a weekly reconciliation. Only then does the motion start, and the record decides which play each account goes to.
From the foundation to the plays
Buying window open, no relationship → the Always-On Outbound Engine
Existing relationship, bigger problem than the first contact → the Champion Engine
A website visit or form fill from an account on the list → fast follow-up
On the list, no signal yet → keep in touch and keep watching
Why orchestrate last. Most teams start here, on top of a list nobody agrees on. That is why the automation looks busy and the pipeline does not move.
Isn't a re-running rule the opposite of a concrete list? No. The rule is how the list stays current. The output is still a named list with a count, and that is what everyone works from. Store the rule, publish the list.
Watch this play utilized on GTM Studio
FAQs
How big should the list be?
As big as the part of the market you actually win in, and no bigger.
What if we can't prove a signal changes conversion?
Then it is not a signal yet. Run it for a quarter, compare conversion on accounts with and without it, and decide. Until then it does not affect the score.
Do we need all four before we start?
You need the list and the buyers before anything else works. Signals and context make the motion sharper; without the first two there is no motion to sharpen.
Where does ZoomInfo data do the work?
Building and refreshing the list (1), naming and watching the committee (2), monitoring and scoring the signals (3). Context (4) is mostly your own CRM, surfaced on the same record.
Is this different from the Always-On Outbound Engine?
It sits underneath it. Outbound assumes the list, the scrub and the contact scores exist. This play is how you build them, and the last section hands a ready account to that engine.