Capital S Consulting
For a launch, the target list is the strategy. We define tiering criteria with your commercial team, run the deciling against the claims and prescription data you already license, and load balanced territories into Salesforce before your reps take the field
Most of a launch's revenue comes from a thin slice of the prescriber universe. Finding that slice is not a mystery. The signal already sits in the claims and prescription data you license from vendors like IQVIA, Komodo Health, or Symphony Health. What goes wrong is the translation. Raw feeds become a spreadsheet, the spreadsheet becomes a target list, and six months later nobody can explain why a given provider landed in Tier 2. We treat HCP targeting and segmentation as an engineering problem with governance built in, sitting on the same commercial data warehouse that feeds the rest of your reporting
We have built target lists from claims data enough times to know where they break. It is almost never the data itself. It is what happens to the data after it arrives
The feed arrives, an analyst pivots it in Excel, and the target list lives in a workbook on a shared drive. Version four gets emailed to the field. Version five never does
A regional director says a provider is Tier 1. Nobody writes down why. The director moves on, the reasoning leaves with them, and the tier stays where it was put
Territory mapping happens in the pre-launch scramble and is never revisited. Headcount shifts, prescribing patterns move, and two reps end up calling on the same health system
A rep hears from a colleague that an account moved. No request, no approval, no record. Sales operations finds out during the next alignment, three months after the fact
Six pieces of work. Most commercial teams need all six, though we have started with the first two when the launch date was close and the field needed something to work
Provider tiering starts with criteria. We bring a starting set to the table, then run working sessions with your commercial team to work through the tradeoffs and settle what qualifies a target: specialty, prescribing behavior, institutional affiliation, payer access. Then we apply those criteria against your claims and prescription data to produce a tiered target list. Deciling ranks providers by prescription volume, but volume on its own puts a high-writing generalist above a specialist who sees your exact patient. Therapeutic relevance carries weight in the final tier
For rare disease programs, we map where diagnosed and suspected patients concentrate, inside centers of excellence and outside them. A real share of patients are managed by community providers who are missing from every conference agenda. HCP segmentation that only reads academic affiliation walks past them. The target list should reflect where the patients are. That same map is the starting point for patient-level targeting
We build territories against the rep headcount you have today. Zip-to-territory assignment logic keeps account ownership unambiguous, including the cases that usually break territory design: multi-site health systems, providers practicing in three zips, the large account sitting on a state line. Every zip resolves to exactly one territory, and every provider resolves to exactly one owner. Some programs align by health system or specialty instead of zip code, and the assignment logic supports both
Tiered targets and territory assignments load into Salesforce so reps open the app on day one and see their list rather than an empty account page. We validate every record's NPI against your customer master first. A target list full of duplicate or retired NPIs erodes field trust in about a week, and you spend the next quarter earning it back
A target change request workflow with sales manager and sales operations sign-off. The rep submits the change, the manager reviews it, sales operations approves and applies it. Target tiers, institution changes, adds and drops all leave a paper trail you can hand to compliance or pull up in a business review without reconstructing it from email
We refresh the list as new files arrive that could shift the landscape. A target list built once before launch is stale by the national sales meeting. The refresh runs as a scheduled job against the warehouse, so nobody has to fund it again next year
Targeting in rare disease is a different exercise. There is no long tail to work through. The entire treating universe might fit on two screens, and getting one provider wrong is a measurable share of the launch
With a few hundred prescribers, tier assignment stops being a sorting exercise and becomes a set of individual decisions. Your commercial and medical leadership should be able to defend each one by name, which is only possible when the criteria are written down
Rare disease programs sometimes align territories to health systems or specialties instead of geography, because the treating centers cluster in ways a zip map does not follow. We build the assignment logic either way, and the tier and target data reads the same underneath
Targeting is one piece of a rare disease launch platform, alongside the CRM, the data foundation, and patient services. Sequencing matters here. Territories drawn before the warehouse exists get redrawn, usually twice
The pipeline that normalizes feeds from vendors like IQVIA, Komodo Health, or Symphony Health and the Salesforce configuration that consumes it are built by the same team. The handoff between them is a code review, not a status meeting between two vendors pointing at each other
We do not arrive with a tiering framework and ask you to adopt it, and we do not hand you a blank page either. We drive the discussion: a starting set of criteria, the tradeoffs each one creates, and what your data can support. You make the call, and we write the reasoning down so it is still legible when someone asks a year later
Everything we build refreshes on a schedule and runs without us. If the target list only works the day it is delivered, we have handed you the same spreadsheet problem in a more expensive wrapper
Claims and prescription data at the provider level, plus your customer master for NPI validation. We work most often with feeds from vendors like IQVIA, Komodo Health, or Symphony Health, and we have loaded plenty of others.
If you have not licensed a feed yet, we help steer the licensing decision toward what the targeting question needs: which fields, what refresh cadence, what level of aggregation. Buying a cut of the data that does not match the question is expensive to unwind, so it is worth working through before you sign.
Deciling ranks providers by prescription volume and splits them into ten buckets. It is arithmetic, it is useful, and it only measures how much someone writes.
Tiering adds strategy on top of that. Therapeutic relevance, formulary access, patient concentration, and institutional affiliation all move a provider up or down from where raw volume placed them. A decile 3 specialist treating your exact patient population can outrank a decile 9 generalist who will never write your product. The decile assignments are an input to the tier, not the tier itself.
Yes, through a governed workflow rather than side emails. The rep submits a target change request in Salesforce, the sales manager reviews it, and sales operations approves and applies it.
Every change records a reason code and a timestamp. That matters when a compliance question comes up months later, and it matters more when you are trying to work out why a territory's target count drifted by forty providers over two quarters.
We refresh the list whenever new files arrive that could shift the landscape. Re-tiering more often than the underlying data changes just creates churn in the field.
Most commercial teams we work with settle on quarterly re-tiering with monthly incremental updates for new, retired, and relocated providers. Launch teams often run tighter for the first two quarters, then ease off once the prescriber universe stops moving.