CRO territory planning by state is the norm for any US business development team past about five people, and most sales intelligence tools are built around country. A BD lead in a 17-person CRO group put it simply: in the US they have territories based on states.
That mismatch is not cosmetic. Country-level territory design in the US puts Massachusetts, the Bay Area and New Jersey into whatever patch happens to contain them, and those three clusters hold a disproportionate share of sponsor activity. One rep gets a queue they cannot work. Three others get a quiet quarter and a performance conversation they do not deserve.
Why HQ country is the wrong unit
Biopharma clusters geographically to an unusual degree. Proximity to academic medical centres, investor networks and a specialised labour pool concentrates sponsors into a handful of metro areas. A country-level view flattens all of that.
The practical consequences show up in three places:
- Workload is unbalanced by construction. The rep covering the Northeast has more qualified accounts than they can contact, so coverage becomes arbitrary rather than prioritised.
- Travel planning becomes impossible. Conference and site-visit planning is a state and metro activity. A country-level list does not tell you who to see while you are in Boston for two days.
- Comparison is meaningless. You cannot assess two reps against each other when one patch holds four times the addressable programmes.
Building a state-level sponsor universe
State-level territory design is a quarterly exercise you do once and then maintain, rather than a filter you re-apply every week. The sequence that works:
- Build the country universe first. Filter sponsors by therapeutic area, highest phase and modality to get the set that matches what you sell. This is the step that removes academic centres and irrelevant modalities, and it is where most of the noise goes.
- Resolve state from the company record. For the resulting list, HQ location is on the account. This is a one-time pass per account, not a recurring cost, because companies rarely move.
- Group into clusters, not individual states. Wyoming does not need an owner. Build four to eight clusters that reflect where sponsors actually are: Greater Boston, the Bay Area, San Diego, the New Jersey and Philadelphia corridor, Research Triangle, and a remainder patch.
- Record the assignment somewhere durable. An account list per territory, or a CRM field. The point is that next quarter's rebalance starts from last quarter's map rather than a blank page.
Balancing by trial volume, not headcount
The most common mistake after getting to state level is balancing on company count.
Company count is a poor proxy for workload. A twelve-person biotech with one Phase 1 study and a mid-cap with nine active programmes across four therapeutic areas both count as one account. They are not remotely the same amount of work or the same amount of opportunity.
Better balancing inputs, roughly in order of usefulness:
| Input | Why it is better than company count | Effort to obtain |
|---|---|---|
| Active trials in your therapeutic areas | Directly proportional to addressable work | Low, visible per account |
| Programmes at your target phase | Filters out the pipeline you cannot serve | Low |
| Recent financing events | Indicates which accounts have budget now | Low |
| Existing relationships | Prevents splitting an account someone has nurtured | Medium, needs CRM hygiene |
Balance on the first two, sanity-check against the fourth. A territory with forty accounts and eighty relevant active studies is a bigger patch than one with seventy accounts and thirty.
Scoring inside a territory
Once a rep owns a patch, the question changes from who owns this to what do I do on Monday.
Scoring inside a territory should be about recency and phase fit, not size. The largest sponsor in a patch is usually the one with the most entrenched vendor relationships. The account worth the call is the one where something changed in the last fortnight and the programme sits at the phase you serve.
In practice that means a tracked account list per territory with the signal digest filtered to it, so each rep opens their patch and sees only what moved in it.
See Salesmotion on a real account
Book a 15-minute demo and see how your team saves hours on account research.
Keeping it current
Territory maps rot. Three habits keep them usable:
Quarterly rebalance, not annual. A quarter is short enough that a reassignment is a conversation rather than a negotiation, and long enough that reps are not constantly handing over relationships.
Add new sponsors to a holding queue. When a new company registers its first trial in your therapeutic area, it should land somewhere defined rather than being claimed by whoever notices first. A weekly review of new registrations, assigned in the same pass, prevents this.
Record why, not just what. A note on the territory map explaining that Greater Boston was split because one rep was covering ninety relevant programmes saves the argument next time.
Frequently asked questions
How do I build the state-level view? Build the universe with the therapeutic area, phase and modality filters, then resolve state from the account records as a one-time pass. Companies rarely move, so this is a setup cost rather than a recurring one, and the resulting map is what you rebalance each quarter.
How many territories should a CRO BD team have? Fewer than you think. Four to eight US clusters covers most teams up to about twenty reps. Splitting further tends to create patches too thin to build a rhythm in, and increases the number of accounts that sit exactly on a boundary.
Should territories follow therapeutic area instead of geography? Sometimes, and it depends on how your buyers behave. Geography works when relationships are built face to face at sites and conferences. Therapeutic area works when your differentiation is scientific depth and the buyer cares more about your experience in their indication than where you are based. Some teams run both as a matrix, which is harder to administer but reflects reality.
What happens when a sponsor moves or is acquired? Acquisition is the common case and it is disruptive, because the acquired pipeline usually transfers to the acquirer's existing vendor relationships. Treat acquisitions as a territory event worth reviewing immediately rather than waiting for the quarterly pass.
If you are rebalancing territories this quarter, it is worth seeing what your sponsor universe looks like once therapeutic area and phase filtering is applied, because that is usually where the count changes most. See how it works for CRO business development.
