Prospecting
Why did the account tiering die by February?
Account tiers die when re-ranking costs more than anyone budgeted. The January model was probably right — in January. If refreshing fit and timing takes a planning cycle, sellers default to whichever accounts answer, and the tier list becomes wallpaper. A tiering survives when re-scoring an account costs minutes, not a meeting.
An attention strategy that’s expensive to re-run is a memo
It’s planning season again. Somewhere in the next few weeks, a spreadsheet with every account in the territory will get scored, sorted, and presented, and the tiers will be right — genuinely right, for a while.
Here’s the collision that kills it. Tiering is an attention decision: it says where the hours go. But the decision was priced as an event — nobody budgeted what it costs to make it again in February, when three tier-one accounts have gone quiet and two tier-threes just hired the right VP. If re-ranking an account takes a planning cycle, it doesn’t happen. Sellers drift to whoever answers, the tiers become wallpaper, and October rebuilds from scratch what February silently abandoned.
The model didn’t fail. The maintenance did — and it was never on the invoice.
June. A rep is asked why she’s deep in a tier-three account. She shares her screen: the account just consolidated vendors and hired an operations lead. “Where does it say that?” It doesn’t. The tier list still says January.
Illustrative year
The tier list's year
The same document, four moments. Nothing dramatic happens — that's the point.
- What the model cost
- One planning season
- What the maintenance cost
- Never budgeted — so, everything
Next move: this planning season, decide what moves an account between tiers before you decide the tiers.
Illustrative example. The dates vary by team; the shape — one verified moment, three unverified ones — is the pattern this post exists to break.
1. Why February wins
What does it cost to re-rank one account in your system?
Answer it honestly, in steps: someone notices the world changed, someone re-gathers the evidence, someone re-scores, someone updates the artifact, someone tells the rep. In most teams that’s five manual steps across three owners — for one account. So it happens never, and the tiering’s accuracy is set on day one and decays daily.
The economics are the same ones that kill playbooks: the value of the tiering accrues to the team, but the maintenance bills specific people who have quarters to hit. Unbudgeted work loses to budgeted work every single week — not through defiance, just arithmetic.
2. Calendars don’t move accounts. Events do.
What should move an account between tiers?
The annual rebuild treats account priority as a season. It isn’t — it’s a response to evidence, and evidence arrives on its own schedule. A leadership change, a funded initiative, a stall in the very problem you solve: each of those is a re-ranking trigger the moment it’s known, whether it’s known in February or August. That’s what a signal is actually for — not a send trigger, a re-ranking event.
Flip the design: tiers hold between events, and named events reopen the question for one account at a time. Tier moves become small, frequent, and evidenced, instead of large, annual, and archaeological. The double-down call stops being a ceremony and becomes a standing verdict — the same fit-and-timing test, re-run whenever one account’s facts change.
3. The tiering that survives June
What’s different about a tier list you’d still trust mid-year?
Three properties, none of them about the scoring model:
Re-scoring one account is a minutes-job. The evidence is already gathered and dated, so a tier move is a decision, not a research project.
Every tier assignment shows its evidence and its age. A tier-one badge with a 130-day-old justification is visibly due for a check — the list itself tells you where it’s rotting, the same freshness discipline as the target-list test.
Demotion is respectable. An account that goes quiet moves down with a re-entry event attached, so nobody defends stale tier-ones out of sunk cost.
Run it manually to start: the tier sheet gains two columns — evidence as of and what would change this — and a fifteen-minute weekly pass moves what the week’s events say to move. That version works, and then meets the usual wall: watching a whole territory for tier-moving events, and keeping every account’s evidence dated, is a full-time job nobody was hired for.
Systematize exactly that half. Narrative AI keeps each account’s evidence current, dated, and watched, so a tier move costs the minutes it should — while the leader still owns the verdicts; every message a seller sends stays rep-initiated, and every AI-suggested CRM change waits for the rep’s approval.
Build the model in October if you like. Just don’t let October be the last time it’s true.
The Prospecting motion
This is one step of prospecting — see how the whole stage runs, end to end.
Explore Prospecting