How to tier a list without feeling like you are giving up
Tiering is a resourcing decision disguised as a strategy debate. Start from capacity rather than ambition: how many accounts can one person research properly in a month, how many conversations can your sellers hold at once, how many closed-door sessions can you actually run. That gives you a Tier 1 number, usually between 20 and 40 accounts, and it will feel too small.
Then group what is left. Tier 2 accounts are worth a cluster play when they share something real: the same platform, the same regulation, the same migration, the same region. A cluster lets one piece of work serve twenty accounts honestly, which is different from sending twenty accounts a generic message. Everything below that runs as a 1:many program you do not hand-build.
The accounts you deprioritize are not abandoned. They stay in the 1:many program and they get promoted the moment a signal appears. Tiering is a decision about this quarter, revisited every quarter, not a verdict on an account.
- Start from capacity: how many accounts can be researched properly
- Tier 2 works in clusters only when accounts share something real
- Promote accounts on signal, and revisit the tiers every quarter
Cluster plays, and why they outperform personalization at scale
A cluster is a group of accounts facing the same specific situation. Ports of a similar size with the same operational constraint. Companies on the same platform facing the same end-of-support date. Firms in one jurisdiction facing one new regulation. For a cluster you can write material that is genuinely specific without writing it twenty times, and you can put the group in a room together.
That second part is the leverage. A closed-door roundtable where eight peers discuss a shared problem does something no sequence can: it makes the buying group's internal conversation happen in front of you, and it builds the peer proof a champion needs. The yard and port management program we ran was built this way, with cluster ABM and closed-door CXO roundtables aimed at mid-segment ports most vendors never approach, and it produced $8M of pipeline in nine months.
Why speed of reply is the cheapest advantage you have
In every program we audit there is a gap between a reply arriving and a human answering it. A day is common. Three days is not rare. Nothing else in the program is as cheap to fix or as reliably valuable, because a buyer who replied was briefly in a buying mood and that mood does not survive the week.
The fix is an owner, a service level and a routing rule, written down. Not a tool. We set the service level in the first thirty days and report against it, because a program with excellent targeting and a three-day reply time is still a slow program.

