Ask most ABM teams how many accounts get genuinely coordinated, hand-built orchestration, and the honest answer is usually a specific, small number: the top 20 to 50 accounts someone on the team can personally track in their head. Everyone else on the target account list, often hundreds of accounts that technically qualify, gets something closer to generic nurture, because the real playbook doesn't scale past what a person can manually hold.

That's not a failure of ambition. It's an honest description of what happens when sophisticated, multi-stakeholder orchestration depends on a human tracking it manually. A person can genuinely hold the context for 50 accounts, who's engaged, what stage each stakeholder is at, what the next right touch is. Nobody can hold that context for 500, so the program quietly narrows itself to whatever a team can track, and calls the rest of the target list "in nurture" as a polite way of saying it's not really getting the ABM treatment at all.

This two-tier reality is the actual ceiling on most ABM program size, and it's rarely named directly, because naming it means admitting the program's real capacity was never determined by strategy or budget. It was determined by how many accounts a human team could personally track before the coordination broke down.

The fix isn't hiring enough people to manually track 500 accounts the way 50 currently get tracked, because that cost scales linearly with account count in a category where the whole point was supposed to be precision at scale. It's building the tracking and asset-generation into infrastructure that doesn't require a person to hold every account's context in their head to execute the real playbook consistently. Stakeholder-level engagement tracking, per-account signal detection, asset generation calibrated to each account's actual state, run the same way for account 400 as for account 12.

Most ABM leaders already know their tier-2 and tier-3 accounts are getting a diluted version of the program. Few of them frame it as an infrastructure ceiling rather than a resourcing gap, because resourcing gaps sound temporary and infrastructure ceilings sound like an admission the program was never built to actually scale. It's worth being honest about which one it actually is, because only one of those gets fixed by hiring more people.