Named account vs. target account: what's the difference

Every territory planning cycle, someone in the room uses "named account" and "target account" like they mean the same thing. They don't, and mixing them up is how a rep ends up prospecting a company that already belongs to someone else's book, or how a named account sits untouched for two quarters because nobody flagged it as a priority.
Named account: assigned, owned, tracked
A named account is a specific company that has been formally assigned to a rep, a pod, or a territory. It's on the list. It's in the CRM with an owner field filled in. Nobody else on the team is supposed to touch it without a hand-raise in Slack first.
Named accounts show up in two flavors most sales ops teams recognize:
- Strategic named accounts. The logos that matter enough to get a dedicated owner regardless of territory lines. Usually a short list, usually reviewed by leadership.
- Territory named accounts. Every company that falls inside a rep's assigned patch, whether that's a geography, a vertical, or a segment by employee count or revenue.
Ownership is what defines a named account, not size or revenue potential. If it's named, someone owns it, and that ownership is what the comp plan and the territory map are built around.
Target account: a priority flag, not a claim
A target account is a company a team has decided to pursue with above-average effort, usually because it matches the ideal customer profile tightly, shows active buying signals, or sits inside a named list of accounts marketing and sales agreed to chase together for an ABM motion.
Target accounts aren't necessarily owned yet. A company can be a target before anyone has been assigned to it, before there's even a named account record for it in the CRM. Marketing might build a target account list from firmographic fit and intent data, hand it to sales ops, and only then does it get carved into territories and assigned real owners.
So the practical difference: named is about who owns it. Target is about why it matters. Every named account in a book isn't automatically a target, and not every target account has been named yet.
Where the confusion costs you
This isn't just semantics in a glossary. The mix-up shows up in three places that cost real pipeline:
Territory disputes happen when a rep treats a target account like it's theirs because it's on a hot list, but the account hasn't been named to their territory yet. Compensation and credit arguments follow.
Account coverage gaps happen the other way. A named account sits in someone's book, technically owned, but it never made anyone's target list, so it gets zero proactive outreach and the rep only touches it when the renewal date forces a conversation.
Stale account lists happen when the target list was built once, a year ago, and nobody has gone back to check whether those companies are even still worth the "target" flag. A company that was a target account because it was expanding into a new region two years ago might have finished that expansion, opened three more locations since, or quietly shut down the division sales was chasing.
That last one is the gap most territory planning tools don't close. A CRM field can tell you an account is named and tagged as a target. It can't tell you the account just broke ground on a second facility, or that the site everyone assumed was still active has sat with an empty parking lot for six months. That's the kind of thing that should move an account up or down a priority list, and it usually only gets caught when a rep happens to drive past.
Territory Watchlist was built for that specific gap: a standing weekly check on a named territory or a target account list, so a new building permit, a site expansion, or a visible change on the ground lands as a dated alert instead of something someone eventually notices three months late.
Keep the named list and the target list straight, then let the watchlist tell you when either one changes.