Building a Target Account List

Outcome: a named, tiered target account list with written entry and exit rules, sized to what your team can actually work.

Surface: App
Level: Intermediate
Uses: Formula columns · CRM sync
Credits: 0 to define; signals cost separately
Prerequisite: Lessons 02–05

Why a named list changes the motion

Signal plays without a target list are broad campaigns with better timing. That is fine, and it works.

ABM is different: you decide in advance which accounts matter, then use signals to decide when to act on them. The list is the commitment; the signals are the timing.

The practical consequence is that the list must be small enough to justify per-account effort, and stable enough that the effort compounds.

Sizing

Work backwards from capacity, not from ambition.

Motion	Accounts per rep	Why
One-to-one ABM	20–50	Individually researched, personally worked
One-to-few	100–300	Segment-level personalization, some per-account work
One-to-many	500–2,000	Signal-driven, mostly automated

A target list of 2,000 accounts worked by three reps is not a target list — it is a database with a label. If nobody can name the accounts in their tier, the list is not doing the job a target list exists to do.

Who chooses

Not one person, and not an algorithm alone.

Start with the score

The fit score from your TAM work. Free, objective, and it produces a defensible starting set.

Have reps add and remove

They know about relationships, past conversations and in-flight opportunities the data does not show. Cap the number they can add so it stays a decision rather than a wishlist.

Have leadership confirm the tiers

Tier 1 is a commitment of real effort. It should be agreed, not assumed.

Record why each account is on the list

One line. It is what you check when the list is reviewed next quarter.

Tiering

Tier	Size	Treatment
Tier 1	20–50 per rep	Individual research, multi-threaded, personal outreach, exec involvement
Tier 2	100–300	Segment-personalized sequences, signal-triggered
Tier 3	The rest of the ICP	Automated, signal-triggered only

The tiers are treatments, not quality grades. A Tier 3 account with a strong signal may get worked before a quiet Tier 1 — the tier decides how you work it, the signal decides when.

Entry and exit rules

Write both. Lists without exit rules only grow.

Entry

Fit score above a threshold, or
Rep nomination with a stated reason, or
A qualifying signal at an in-ICP account

Exit

Closed-won → moves to the customer motion
Closed-lost with a stated reason → return date set, not permanent removal
Fit score falls below threshold for two consecutive quarters
Acquired, dead, or out of market
No engagement after a full cycle of plays → demote a tier rather than remove

Demotion is better than removal. An account that did not respond this quarter is not disqualified — it is unproven, and moving it to Tier 3 keeps it in the signal pipeline at near-zero cost rather than deleting the work you did on it.

Keep it stable

An ABM list that changes every month cannot compound. Set a review cadence and hold to it:

Quarterly review of Tier 1 and 2 membership.
Monthly re-score, but changes only take effect at the review.
Immediate exit only for the hard cases: acquired, dead, closed-won.

Stability is what allows the multi-touch, multi-threaded work that makes ABM different from outbound.

Do this now

Compute capacity

Accounts per rep, per tier, honestly.

Score and sort your ICP

Take the top N as the starting set.

Let reps adjust, with a cap

Write the reason per Tier 1 account

One line each.

Write entry and exit rules

Both. Exit especially.

Set the review cadence

Quarterly for membership, monthly for scoring.

Sync to the CRM

So the tier is visible where reps work, not only in the table.

Check your work

List size matches actual capacity per tier
Every Tier 1 account has a stated reason
Entry and exit rules are written
A review cadence is set and diarized
Tiers are visible in the CRM

Where this breaks

A target list with no exit rule becomes a list of everything anyone ever thought was interesting, and at that point tiering means nothing — Tier 1 fills with accounts nobody is working and the reporting on it becomes noise. Write the exit rule at the same time as the entry rule, and apply it at the first review even when it is uncomfortable.

Further automation

Sync tier and score back to the CRM so account owners see them without opening another tool. A tier that only exists in a spreadsheet does not change behaviour; one that shows on the account record does.

Next lesson

07 — Scoring accounts across signals, combining several triggers into one number.

Reference for this lesson: CRM integrations, Tables, TAM Sourcing, GTM Engineering — scoring and gating.