Ranking 400 Accounts Into a Dial Order: A Territory Build You Can Finish in an Afternoon

The list is not a plan

Somebody dropped 400 accounts in your CRM on a Monday and said go. Maybe it came out of a filter in ZoomInfo. Maybe your manager split the old patch three ways because two new reps started. Either way you now own a list, and a list is not a territory.

What most people do next is open it, sort by company name, and start at the top. I have watched new reps do this for years and I did a version of it myself early on. It feels productive. You are dialling, you are logging activity, the numbers in the CRM go up. Then week eleven arrives and you notice that the three accounts most likely to buy from you this quarter are sitting at the bottom of the sheet under W, untouched, because you never got there.

Alphabetical order is a random ordering with extra steps. So is "whatever the CRM shows me first" and so is "whoever I feel like calling today". The whole job of sdr territory planning at the individual rep level is deciding what to dial first, and then having the discipline to actually dial in that order when Tuesday afternoon gets ugly.

The good news is that the build is not a two-week research project. You can do 400 accounts in an afternoon if you limit yourself to things you can verify quickly and refuse to go down rabbit holes.

Score on three things, and only three

The reason territory builds take forever is that reps try to research their way to certainty. They open the 10-K. They read the CEO's last four LinkedIn posts. Forty minutes per account, and after twelve accounts they are exhausted and the other 388 get nothing.

So cap it. Two minutes per account, three questions, and if you cannot answer a question in that window the answer is zero. Ruthlessness here is the whole trick.

Trigger recency

Has something happened at this account recently that makes my problem urgent for them?

A trigger is anything that changes the status quo: a funding round, a new executive in the function you sell to, an acquisition, a big hiring push, a facility opening, a regulatory deadline they have publicly acknowledged, an earnings call where they named the thing you fix. The key word is recent. A leadership change from two years ago is context. A leadership change from six weeks ago is a reason to pick up the phone this week.

I score it zero, one, or two. Two means something happened in roughly the last quarter that I can name in a sentence on the call. One means something happened this year, or the signal is real but soft — steady job postings for the role you sell into, say. Zero means I looked and found nothing, which is a perfectly common answer and you should not feel bad about it.

The test for a two is whether you could say it out loud and have it land. "I saw you brought on a new VP of Talent in March" is a two. "I noticed you have a website" is a zero.

Fit to the pain you remove

Not fit to your ICP slide. Fit to the specific pain your product takes away.

Those are different. Your ICP slide probably says something like "companies with 200 to 5,000 employees in North America". That is a filter, not a qualifier. The real question is whether the mechanism that causes your customers pain is present at this account, structurally, whether or not anyone there has noticed yet.

If you sell scheduling software to staffing firms, the pain is caused by high-volume light industrial placement across multiple branches with hourly workers who no-show. A staffing firm that does exclusively retained executive search has none of that. Same SIC code, same headcount band, zero fit. If you sell asset monitoring into utilities, the pain lives with organisations running aging distributed assets they cannot easily inspect — which is why the thirty-second opener for a Head of Asset Management works on some utilities and dies on others that outsourced the whole function.

Score it zero, one, two again. Two means the mechanism is clearly present and you can point at the evidence — their service pages, their job postings, their branch count, their fleet. One means probably present but you are inferring. Zero means the mechanism is absent or you cannot tell.

This is the column that saves you the most time over a quarter, because a zero here means you should not call at all. Trigger and reachability can be worked around. Absent pain cannot.

Reachability of the person who owns the number

The third question is the one almost nobody scores and it is the one that quietly decides your quarter. Can I actually get a human being on the phone who owns the outcome?

Two parts to this. First, is there an identifiable person in the role — named, current, with a title that implies budget or strong influence over it? Second, do I have a way to reach them: a direct line, a mobile, a switchboard that transfers, a branch number that a manager actually answers.

A two means I have a direct number or a mobile for a named person in the right seat. A one means I have a named person and a main line I think I can navigate. A zero means either no named person or no phone path at all — corporate switchboard with a hard IVR and no extension list, or a gatekeeping structure you already know from experience does not pass calls through.

Be honest here. Reps inflate this column because admitting an account is unreachable feels like giving up. It is not giving up, it is triage. An account with perfect fit and a hot trigger that you cannot phone is an email and LinkedIn account, not a dial account, and mixing those two up is how you end up with a call block that produces nothing but voicemail.

The spreadsheet

Here are the columns. Nothing clever.

Account name. Segment or sub-vertical. Trigger score. Trigger note. Fit score. Fit note. Reachability score. Contact name. Contact title. Best number. Total score. Tier. Date of first touch. Touch count. Last touch date. Next action. Outcome.

The two note fields matter more than they look. The trigger note is your opener. The fit note is your reason-to-believe when they push back. If you write the note during the build, you are not improvising on the call at 9:40am, which is the moment most reps sound like a survey. One short sentence in each. "Opened third branch in Tampa in August." "Job posts show 40+ light industrial reqs across four branches." That is enough.

Total score runs zero to six. Then tier: five or six is an A, three or four is a B, one or two is a C, zero is dead and you delete the row. Delete it properly. Do not keep it in a hidden tab for sentimental reasons.

One override rule I keep: a fit score of zero drops the account to dead regardless of the other two columns. A red-hot trigger at a company that cannot use what you sell is a red-hot waste of a morning.

How many A accounts can one rep actually run

Fewer than you think. This is the part of the build reps get wrong even when everything else is right.

An A account is not a phone number, it is a campaign. You are calling multiple people at different times of day, sending a real email between attempts, watching for new triggers, reading the room, and adjusting. That is genuine cognitive load per account, and it does not scale by working harder. It scales by working fewer.

In my experience the number of accounts a single rep can hold in their head with real context is closer to two dozen than to a hundred. Not accounts you can dial — accounts you can dial well, where you know the trigger without looking it up, you remember what the receptionist said last time, and you can tell that the second call needs a different angle than the first. Past that number the quality collapses and you are just a person reading names off a screen.

So cap the A tier. If your scoring produces sixty fives and sixes out of 400, congratulations, you have a good patch — now take the top twenty-five or thirty and demote the rest to B for now. They are not worse accounts. They are queued. When an A dies you promote the next one in, and you keep the working set constant.

The B tier is where most of your list lives and it is worked in batches rather than campaigns. C is a single pass. More on both in a second.

Cadence by tier, decided in advance

Write the cadence down before you dial anything, because in the middle of a week your emotions will make this decision for you and your emotions are terrible at expected value. They will send you back to the account where somebody was nice to you and away from the account where somebody was short with you, and niceness is not buying intent.

For A accounts I run something like eight to ten call attempts across three to four weeks, spread across at least two named people, with time-of-day rotation — early, mid-morning, late afternoon — and an email after the second and fifth attempts. Voicemail on maybe every third attempt, not every one, because a voicemail on every call reads as desperation and eats your block.

For B accounts, three to four attempts over two weeks, one contact unless something interesting happens, one email. Batch them. Twenty B accounts in a block is a rhythm you can hold.

For C accounts, one call and one email. That is the whole cadence.

The reason to spread attempts across weeks rather than hammering in two days is simple: the person you want is travelling, in a QBR, on site, or off. Attempts on Tuesday and Wednesday of the same week are close to one attempt in disguise.

When to demote instead of dialling again

The hardest discipline is knowing when an A is not an A.

My rule is that an account gets demoted when I hit the attempt cap with zero human contact, or when I get human contact that tells me the fit score was wrong. Wrong fit is an instant demotion or a delete — no ego about it, you scored it from the outside and the inside said no.

The cap case is different and it is where reps cheat. You have called nine times, never spoken to a soul, and every instinct says the tenth is the one. It usually is not. What you have discovered is that your reachability score was optimistic, and the fix is not more of the same dial — it is a different number, a different person, a different channel, or the bench. Send the account to B, put a follow-up date sixty days out, and go spend the hour on the queued account you have never called.

One exception. If you have reached a human and been told a specific reason and a specific time — new system going live in Q3, budget locked until January — that is not a demotion, that is a calendar entry. Note it in the next-action column with the date and get out. Those callbacks are some of the easiest conversations you will ever have, precisely because you are the rep who actually called back when they said to.

Why the C tier gets one call, not zero

The argument for skipping C entirely is that your time is better spent up-tier. It is a reasonable argument and it is wrong, for two reasons.

First, your scoring is a guess made from the outside. Trigger and reachability are the columns most likely to be wrong, and both are wrong in the direction of underscoring — you did not find the trigger because it was not published, and you did not find the number because it was not in your data tool. One call surfaces both. I have had C accounts turn into first meetings inside three minutes because the person who answered said something I had no way of knowing from a browser tab.

Second, the C pass is cheap and it is good reps training. A block of C dials is where you can try a new opener without risking anything. If it dies, you learned something on an account you had written off anyway.

One call, one email, and then genuinely leave them alone until the next quarterly re-score. C is not a place accounts go to be nagged.

A worked example on a staffing patch

Say the patch is 400 staffing and recruiting firms, and what you sell removes the pain of filling high-volume hourly reqs across branches.

First pass is fit, because fit kills fastest. Anything that is pure executive search, pure perm placement, or a single-office boutique with no light industrial or clerical volume gets a zero and comes out. On a list like this that is a large share of the rows and you can do it from service pages alone, seconds per account. Say you are left with something like 240 live rows.

Second pass is trigger. New branch openings, a new VP of Recruiting or VP of Operations in the last quarter, a visible surge in open reqs on their own job board, an acquisition of a smaller agency, a big new logo announced in a press release. Score two, one, or zero, and write the note. This is the slowest pass and it is worth the time because these notes become your first lines. If you are calling into this vertical, work them into an opener that names the branch or the req volume rather than your category — the structure in the staffing and recruiting cold call script exists for exactly this, and it holds up better with a real trigger in the first sentence.

Third pass is reachability. In staffing this skews high, which is a gift. Branch managers answer phones. Branch numbers are published because the branch wants candidates and clients to call. A named branch manager plus a published branch line is a two, and it is often a better two than a VP with a mobile you are not sure about.

Now sort. Suppose the scoring gives you forty fives and sixes, a hundred and thirty threes and fours, and seventy ones and twos. Take the top thirty by total score, break ties by reachability, and those are your A accounts. The other ten fives and sixes go to the front of the B queue, flagged, ready to be promoted the moment an A drops out.

The A thirty get a multi-contact campaign — branch manager and the VP above them, because in staffing the branch feels the pain and the VP owns the spend. The B hundred and thirty get batched by sub-vertical so you can reuse the same framing across twenty calls in a row, which is how you get good at the framing. The C seventy get one call, one email, and a re-score date in your calendar for the start of next quarter.

That is a whole territory, and honestly it is an afternoon of work plus a coffee. The same shape holds in other patches with different signals — in construction the trigger is usually a project award or a new yard and the reachable human is a general superintendent rather than a corporate title, which is why the construction and trades opener leans on job-site specifics instead of company-level flattery.

Re-score quarterly, not never

A territory build has a shelf life. Triggers age out. People change seats. A B account gets a new VP in month two and should have been an A since week six.

So put ninety minutes in the calendar at the start of each quarter and run the three columns again on everything that is not currently in an active cadence. Most rows will not move. A handful will, and those are usually the best meetings you book that quarter, because you are calling on a fresh trigger while everyone else is still working a list somebody handed them in January.

The payoff of all this is not that you dial more. It is that the first hour of every day goes to the account with the highest expected value in your patch, and you know it does, because you decided it on a quiet afternoon with a spreadsheet instead of at 8:55am with a coffee and a bad feeling.

Once the order exists, the bottleneck moves to whether you can actually hold a conversation with the person who picks up — and that is a different skill, trained separately. That is the part I built DrillCall for: if I were sitting where you are, I would take the top ten A-tier openers straight out of my trigger-note column, run them as live reps against a prospect who pushes back, and fix the wording before I spend a single real dial on my best account.