christopherswarup Market & Account Prioritizer
Most target-account lists answer the wrong question: "who could plausibly buy this?" That's nearly everyone, which is why the list ends up too big, too generic, and under-resourced per account. The fix is prioritizing in two passes, at two altitudes, in order.
Inputs to gather
Required:
- A candidate list — either segments/verticals to screen, or named accounts (whichever altitude you're working at)
Helpful, not blocking:
- Any market data on the segments (growth rate, category spend, recent funding/trigger events)
- Firmographics on named accounts (size, industry, tech stack, existing relationship if any)
- Sales capacity/coverage — who would actually work these accounts, and do they have bandwidth
- CRM data completeness on the accounts in question
If none of this is available: score qualitatively on what's actually known and say so explicitly — don't invent numbers to fill gaps. A segment or account with genuinely unknown data belongs in "needs research," not a guessed score.
Gate 1 — Market / segment screen (do this first)
Score each candidate segment on two axes before naming a single account:
External attractiveness — is this segment worth entering at all?
- Category spend and growth trend in this segment
- Live buying triggers (regulation, funding events, leadership change) affecting the segment
- Whether leading companies in the segment have already adopted this category
- Competitive whitespace — how crowded is this segment already
- General segment health/trajectory
Internal readiness — are we actually positioned to win here?
- How deep is our data/record coverage of this segment
- How strong is our product-fit for this segment specifically
- Do we have in-house domain expertise/credibility here
- Is messaging built for this segment or generic
- Does sales/channel coverage actually exist for this segment
Verdict per segment: Active (pursue now) / Nurture (revisit when readiness or attractiveness improves) / Dormant (park — don't spend here yet).
Gate 2 — Account screen (only within Active segments)
Score named accounts on three dimensions:
- Value Potential — growth trajectory, spend capacity, whitespace, number of buying centres in the account
- Winnability — budget realism, competitive entrenchment, data availability on the account, right-to-win
- Alignment Readiness — will sales actually engage this account (participation, SLA commitment, leadership mandate)
Rule: an account only makes the final list if it clears the bar on all three dimensions. A high score on Value Potential with weak Alignment Readiness (sales won't engage) is not a target account yet — it's a "fix Alignment Readiness first" item.
Why the order matters
Building the account list before the market screen means every downstream account-scoring effort is still operating inside "who could buy" — the account scores just look precise while the underlying pool is already wrong. Screening the market first shrinks the pool to where effort actually compounds, before spending analyst time scoring accounts that were never going to be worth pursuing.
How to apply it
- List candidate segments. Score each on external attractiveness + internal readiness. Cut anything landing in Dormant.
- Within Active/Nurture segments, pull named accounts.
- Score each account on Value Potential / Winnability / Alignment Readiness.
- Plot all three per account — flag any account that's strong on two dimensions but weak on the third as "fix first," not "target now."
- Final target list = accounts clearing the bar on all three, inside Active segments only.
Output format
- Segment verdicts (Active/Nurture/Dormant) with the specific factor that drove each call
- Account shortlist, scored on all three dimensions, with weak-dimension accounts flagged separately from ready-to-target accounts
- What to fix before targeting — for any account that's valuable but not yet winnable or aligned
Skill 2 of 6 diagnostic skills in the GTM Skills collection by Christopher Swarup — GTM Ops leader, 15+ years in RevOps/MOPS across Finastra, Equinix, Nutanix, Pleo, Contentsquare and DevRev.