Field Reimbursement Managers (FRMs): What They Do, Cost, and How to Deploy

TL;DR

A Field Reimbursement Manager (FRM) is a manufacturer-employed or CSO-deployed field specialist who educates HCP offices on reimbursement, prior authorization, coding, and payer policy for a specific specialty drug. FRMs are not sales reps. They should not discuss clinical data outside approved access materials, complete PA forms, or submit claims (OIG fraud-and-abuse guidance; PhRMA Code). FRM budgets should be built from territory coverage, therapeutic complexity, travel burden, compliance oversight, and hub support level rather than a generic headcount rule. FRM programs are most critical for physician-administered (buy-and-bill) drugs, specialty launches in the first 12 months, and any product treated across both medical and pharmacy benefits. Common deployment mistakes include rep-minded hiring, understaffing the territory, poor hub integration, and treating the FRM team as a commercial overlay rather than a market access function.

---

What FRMs Actually Do

FRMs sit at the intersection of market access strategy and hub operations. They are the in-person extension of a manufacturer’s patient access infrastructure, focused on removing reimbursement friction at the provider office before it generates a denied claim or an abandoned prescription.

The core activities cluster into eight primary functions:

1. Benefit verification education. Helping office staff interpret eBV results from the hub, identifying medical versus pharmacy benefit routing, and training billing coordinators on how to pull coverage detail when the hub output is ambiguous.
2. Prior authorization guidance. Walking office staff through payer-specific PA submission requirements, documentation standards, and electronic PA portals. FRMs do not complete forms on the office’s behalf. They educate.
3. Denial and appeals support. Providing clinical rationale templates, letter-of-medical-necessity frameworks, and peer-to-peer preparation coaching for denied claims. The actual appeal is submitted by the HCP.
4. Hub and specialty pharmacy triage. Routing stuck cases to the right hub intake queue or specialty pharmacy, coordinating data handoffs, and escalating when a patient’s time-to-therapy clock is running.
5. Copay enrollment assistance. Educating office staff on how to enroll eligible patients in copay support programs and explaining accumulator or maximizer plan detection at the point of benefit verification.
6. Buy-and-bill education. For physician-administered drugs, training practice managers on J-code assignment, HCPCS coding, ICD-10 diagnosis coding, ASP-based reimbursement economics, and site-of-care tradeoffs (hospital outpatient versus physician office versus home infusion).
7. Payer policy updates. Translating payer medical policies, formulary position changes, step therapy edits, and utilization management criteria into actionable guidance for target accounts.
8. Patient access escalation. Serving as the escalation path when an individual patient’s case stalls at the hub, the specialty pharmacy, or the office itself.

What FRMs Do NOT Do

The compliance boundary between FRM (access/reimbursement support) and sales (promotional) activity is a high-risk gray area in pharma commercial operations. FRMs must not:

• Discuss drug efficacy, safety, or clinical information with prescribers
• Complete prior authorization forms, submit claims, or file appeals on behalf of the office
• Make coverage determinations or represent payer decisions as fixed
• Carry or share promotional materials beyond approved non-branded access materials
• Coordinate clinical samples, off-label information, or investigator-initiated studies

Violations can create Anti-Kickback Statute and False Claims Act exposure. OIG and DOJ enforcement posture around remuneration, copay assistance, and reimbursement-linked support makes FRM programs risky when access help starts functioning as de facto inducement to prescribe (OIG fraud-and-abuse guidance; DOJ PSI settlement). The standard safeguards are organizational separation (FRM reporting to market access, not sales), documented compliance training, call-activity audits, and clear separation from the brand’s field force territory planning process.

A Typical FRM Week

FRM weekly activity should be split between proactive education at target accounts and reactive case management for individual patient escalations. A high-performing FRM will:

• Own a named account list of priority offices with documented touch plans
• Maintain a shared CRM record (Veeva or similar) for each account with open access barriers, recent case activity, and payer mix notes
• Coordinate weekly with the hub case management team on open cases originating from their territory
• Attend monthly payer policy reviews with the market access team
• Participate in a quarterly account planning cycle with the brand’s sales rep on the same territory, strictly bounded by compliance firewalls

The cadence bends sharply in launch year, when most accounts are brand-new and reactive case volume is least predictable.

---

FRM Cost Economics

FRM programs are among the most expensive line items in a launch commercial budget. The budget should include the field FTEs plus management overhead, CRM licensing, training infrastructure, compliance monitoring, and replacement coverage.

Fully Loaded Cost per FTE

For a back-of-envelope public planning band, Rx Almanac treats roughly $150K-$350K per dedicated FRM per year as a model output, not a vendor rate card. The basis is component math: current public salary benchmarks place U.S. field reimbursement manager base pay around the mid-$100,000s, with a cited 10th-to-90th percentile span of about $146K-$194K (Salary.com); BLS employer-cost data shows benefits are a material load on wages (BLS Employer Costs for Employee Compensation); and field roles need separate travel expense assumptions, with the IRS 2026 business mileage rate at 72.5 cents per mile (IRS 2026 mileage rate). The right RFP number still depends on geography, therapeutic complexity, travel burden, management span, CRM/tools, training, compliance monitoring, and whether the resource is in-house, dedicated outsourced, shared, or hub-embedded.

Component	Range	Notes
Base salary	Market-priced by role and geography	Higher in oncology, rare disease, and major metros
Variable compensation	Program-specific	Typically MBOs tied to account coverage and service quality, not Rx
Benefits and payroll load	Employer-specific	Health, retirement, payroll tax
Travel and expense	Territory-specific	Higher for geographically dispersed rare disease territories
Technology and tools	Tool-stack-specific	CRM seat, laptop, phone, training platform
Management overhead	Operating-model-specific	District managers, training, compliance
Fully loaded total	Build from components	Depends on geography, therapeutic area, and model

Shared-resource CSO models usually trade lower control for lower fixed commitment. Dedicated in-house teams offer more product and account continuity but require the manufacturer to carry recruiting, management, training, systems, and compliance infrastructure.

Territory Sizing

Territory sizing is the single most common deployment error at launch. The math has four inputs:

• Drug complexity. Specialty and rare drugs with high PA rates, complex coding, and site-of-care variability compress territory size. Primary care specialty drugs with simpler access patterns allow wider coverage.
• Payer concentration. Heavy Medicare Part B exposure (oncology, infusibles) increases FRM workload per account because of buy-and-bill billing complexity. Commercial-heavy mixes with strong ePA automation reduce it.
• Hub support level. A robust full-service hub with strong eBV, ePA, and field-integrated case management can meaningfully reduce FRM workload per office versus a light hub model.
• Account density. Tight-geography autoimmune or GLP-1 launches tolerate wider territories than rare disease teams covering a 500-mile radius.

The working ranges:

Therapeutic area	Territory size (practices per FTE)	Typical launch team size
Rare or ultra-orphan	Tight account list	Small, high-touch team
Oncology (medical benefit)	Moderate account list	Larger buy-and-bill team
Autoimmune / immunology	Wider account list	Larger broad-specialty team
Specialty primary care (incl. GLP-1 specialty lines)	Widest account list	Targeted access team
Cell and gene therapy	Certified treatment centers	Specialist access team

Rare disease teams run smaller account lists per FTE because each account interaction is higher-touch and covers more ground per case. Cell and gene therapy FRM roles are distinct: they cover certified treatment centers rather than prescriber offices, and the workload is dominated by one-time treatment reimbursement, outcomes-based contract administration, and site certification.

Deployment Models

There are four practical deployment models, each with a different cost and control profile:

Model	Fully loaded cost/FTE	Time to stand up	Best fit
In-house manufacturer	Highest fixed commitment	Longest stand-up	Established brands with enough portfolio scale to amortize infrastructure
Outsourced CSO (dedicated)	Dedicated contract team	Faster stand-up	Launch brands and single-product biotech
Outsourced CSO (shared)	Shared contract team	Fastest gap-fill	Smaller brands and geographic gap fill
Hub-embedded	Bundled with hub fees	Included in hub implementation	Hub-centric access programs

The outsourced model is often attractive for biotech companies that do not yet have enough commercial portfolio scale to justify recruiting, district management, training, CRM, and compliance auditing infrastructure. Hub-embedded FRMs are a related model where the hub vendor deploys a field layer directly integrated into the hub case management workflow.

---

FRM vs Other Field Roles

A common launch-team error is conflating the FRM role with the medical science liaison (MSL), nurse educator, or field sales rep. The four roles serve different audiences under different governance frameworks, and the launch staffing model needs to reflect that.

Role	Primary audience	Governance	Training background	Launch team size (specialty drug)
FRM	Practice managers, billing coordinators, office staff	Market access; non-promotional MLR	Payer, reimbursement, hub operations	Product- and territory-dependent
Sales rep	Prescribers (HCPs)	Commercial; PhRMA Code promotional MLR (PhRMA Code)	Clinical detail, product positioning	Product- and call-plan-dependent
MSL (medical science liaison)	KOLs, key prescribers	Medical affairs; scientific exchange (MAPS/APPA/IFAPP/MSLS MSL best practices)	PhD, PharmD, MD	Evidence-plan-dependent
Nurse educator	Patients and caregivers	Patient services; clinical MLR	RN, clinical care experience	Hub- and product-dependent

Three distinctions matter most:

FRM vs sales rep. The FRM does not promote product. The rep does not handle reimbursement. Territory alignment between the two roles should be transparent, but the reporting lines must stay separate. If an FRM escalates a territory-level payer issue, it goes to the market access team, not the district sales manager. Commingling the roles creates direct compliance exposure.

FRM vs MSL. The MSL is a clinical scientist engaging KOLs on trial data, mechanism of action, and scientific narrative. The FRM is a reimbursement operator engaging office staff on billing mechanics. Overlap is minimal. Blended roles (sometimes called “access MSLs”) exist at small biotechs but create compliance risk because the audiences, materials, and training differ.

FRM vs nurse educator. Nurse educators serve patients and caregivers, typically through the hub or via home visits for injection training. FRMs serve HCP office staff. Nurse educators deliver clinical content under a clinical governance framework. FRMs deliver access content under a non-promotional market access framework.

---

Territory Sizing Methodology

The right way to size an FRM territory starts with account-level workload modeling, not headcount targets. A disciplined process has five steps:

1. Build the target universe. Identify the highest-priority prescribing and treatment accounts using claims data (IQVIA Xponent, Symphony Health, or equivalent). For rare disease, add diagnosed-patient lists from the hub and patient advocacy organizations.
2. Tier the accounts. Tier 1 (highest priority, monthly touch), Tier 2 (quarterly), Tier 3 (semi-annual or call-down). Tiering is a function of volume, payer mix, and access barrier density.
3. Estimate workload per tier. Define touch cadence by account tier, then add reactive case load based on expected PA volume, denial rates, and time-to-therapy targets.
4. Model the hub offset. A strong hub with high eBV automation, effective ePA workflows, and clean escalation logic reduces reactive FRM workload. A light hub model forces the FRM to absorb case management that should have been centralized.
5. Set FTE count and territory shape. Convert workload hours into FTEs, then map geographies. Rare disease usually needs tighter coverage; primary care specialty can tolerate wider account lists.

The failure mode is setting the FTE count first (based on a budget number) and then asking the field team to cover whatever territory shakes out. That approach underweights high-density Tier 1 accounts and overweights Tier 3 call-down activity, leaving the most valuable accounts undercovered and the lowest-value accounts overinvested.

---

Who Provides FRMs (Deployment Vendors)

FRM deployment sits in a fragmented vendor landscape spanning contract sales organizations (CSOs), hub services vendors, and dedicated field reimbursement specialists.

Dedicated FRM CSOs

These vendors run large, purpose-built field reimbursement teams that can be deployed as dedicated or shared resources.

• Inizio Engage. Dedicated CCO with FRM, field-force, and patient-support deployment capacity. CD&R-backed following the Ashfield and Huntsworth merger in 2022 (Pharmaceutical Commerce). Strongest at launch surge deployment and therapeutic area depth.
• Syneos Health Commercial. Integrated CRO-plus-CCO model with FRM capability inside a broader commercialization offering. Took private by Elliott and Patient Square in September 2023 at a $7.1B enterprise value (SEC filing; PE Insights). Strong fit when an FRM program is bundled with medical communications or rep deployment.
• EVERSANA Field. End-to-end commercialization platform with FRM integrated into a hub-plus-market-access offering. Differentiated by data feedback loops between field and hub, and by the EVERSANA DIRECT integrated hub-plus-specialty-pharmacy model.
• Indegene. Digital-first commercial services vendor with a growing US FRM capability; strongest at data and analytics integration layered onto field activity.
• Publicis Health and other networked commercial services firms offer FRM capability as part of larger commercialization packages. Quality varies by program leadership.

Hub-Plus-FRM Bundled Models

Hub services vendors have built field layers on top of their hub platforms, allowing the field team to share a single CRM and case management system with the centralized operations.

• EVERSANA DIRECT. Hub, affordability, specialty pharmacy, and 3PL plus field reimbursement in a single platform. EVERSANA reports faster time-to-therapy in integrated deployments.
• Cencora / Lash Group. Legacy hub platform with FRM as a service extension. Strength in buy-and-bill reimbursement for physician-administered drugs. CareMetx acquired Cencora’s U.S. hub consulting services operations, previously conducted under Lash Group and including TheraCom free-goods pharmacy, on April 27, 2026, which manufacturers evaluating multi-year FRM contracts should factor into contingency planning (CareMetx acquisition announcement).
• CareMetx. Hub platform with integrated field support, strongest for rare disease and specialty.
• ConnectiveRx. Copay and hub specialist with field reimbursement extensions; Kohlberg-backed.
• AssistRx. Hub-plus-technology platform with integrated field capability; WCAS-backed.

Pros and Cons by Model

Model	Pros	Cons
Dedicated FRM CSO	Best talent quality, flexibility at launch, therapeutic area benches, full control	Highest cost, less integrated with hub, requires strong internal PM
Shared FRM CSO	Lowest cost, fast stand-up, useful for geographic fill-in	Variable quality, split attention, limited deep TA expertise
Hub-embedded FRM	Tightest field-to-hub data integration, single CRM, fastest case escalation	Narrower talent pool, lock-in to hub vendor, rate leverage declines post-launch
In-house	Deepest product and market access expertise, best retention, full IP ownership	Requires enough portfolio scale to amortize recruiting, management, training, and compliance infrastructure

For additional detail on CSO selection criteria, see the contract sales organizations comparison.

---

Integration with the Hub and Specialty Pharmacy

A poorly integrated FRM team is worse than no FRM team at all. The most common failure mode is an FRM deployed without visibility into the hub’s case management system, leaving the FRM blind to which of their accounts have cases pending and which are stalled.

Required Data Flows

At minimum, an integrated FRM program needs:

• Hub to FRM: case status feed. The FRM’s CRM should show, for every account in territory, every open and recently closed case with current status, days-in-queue, and escalation flags.
• FRM to hub: account intelligence. When the FRM identifies a new payer policy change, a billing coordinator turnover, or a new denial pattern at an account, that intelligence should feed back to the hub case management team.
• Hub to FRM: denial reason coding. Structured denial reason codes (not just “denied”) let the FRM spot patterns across their territory and build appeals strategies at the payer-plan level.
• Specialty pharmacy to FRM: fulfillment visibility. For specialty-pharmacy-dispensed drugs, the FRM should see shipment status on recently enrolled patients. Ship delays are the single most common trigger for office-level complaints.

Escalation Pathways

A clear escalation path between hub and FRM is non-negotiable. The standard pattern:

1. Hub intake receives BV, PA, or copay request from the office.
2. Hub case manager works standard playbook (ePA, appeal, copay enrollment).
3. If case stalls beyond the product-specific service-level threshold, case auto-flags to the FRM covering that account.
4. FRM visits or calls the office, diagnoses the root cause, and either unblocks the case or escalates to the market access team for payer-level intervention.
5. Resolution closes the loop in the CRM with attribution (hub, FRM, payer action).

Programs that skip step 5 cannot measure FRM ROI. Programs that skip steps 3 or 4 leave cases to die silently.

For deeper context on hub-SP coordination, see the hub services buyer’s guide and hub services market analysis.

---

ROI Measurement

FRM attribution is difficult. An FRM conversation with a billing coordinator that unlocks a stuck PA three days later does not show up cleanly in any single database. Sophisticated launch teams measure FRM impact across four dimensions:

Time-to-Therapy Reduction

The cleanest attribution metric. Compare time-from-prescription-to-first-fill at FRM-covered accounts versus non-covered accounts, controlling for payer mix and drug complexity. Well-deployed FRM programs should show faster time-to-first-fill at target accounts during the post-launch measurement window.

PA Approval Rate Lift

First-pass PA approval rates should rise in FRM-covered accounts as billing coordinators internalize payer-specific documentation standards. Track lift by therapy area and payer mix rather than relying on a universal benchmark.

Prescription Persistence and Adherence

Harder to attribute because persistence is a function of clinical tolerance, copay burden, and patient engagement as much as access friction. Teams with strong attribution models separate access-driven abandonment (copay sticker shock, PA denial) from clinical-driven discontinuation and measure FRM impact on the access-driven subset.

Denial Turnaround

Time from denial to reversal through appeal is a core FRM-attributable metric. Target a measurable reduction in median time-to-reversal at FRM-covered accounts through faster peer-to-peer scheduling, better LMN templates, and payer-specific appeal playbooks.

The Attribution Trap

The most common measurement error is crediting the FRM for any access success at a covered account. Without a credible non-covered control group, attribution numbers drift upward every quarter. The fix is to hold a small percentage of target accounts as control (or use statistical matching on payer mix and volume) to preserve a counterfactual. That discipline is common in consumer marketing and still rare in field reimbursement programs.

---

Common Deployment Mistakes

Seven failure modes show up repeatedly in first-time launch teams:

1. Understaffing the territory. A fixed headcount applied to an oversized target universe forces each FRM to touch too many accounts too rarely. Territory sizing before budget-setting catches this; budget-setting before sizing guarantees failure.
2. Rep-minded hiring. The reflex to hire ex-sales-reps into FRM seats is a common mistake. FRMs need reimbursement DNA (prior experience at a hub, payer, specialty pharmacy, or health system billing office), not product pitch skills. Reps who converted to FRM without real reimbursement training consistently score lowest in account feedback surveys.
3. Poor hub integration. FRMs deployed without CRM visibility into hub case status are reduced to guessing which accounts need attention. They end up over-visiting accounts with no open cases and under-visiting accounts with stuck cases. The symptom is high FRM activity with flat time-to-therapy metrics.
4. No clear escalation path. Case stalls at the hub are not automatically flagged to the FRM. The FRM finds out at the next office visit, by which point the patient has either abandoned or the prescriber has rotated to an alternative.
5. Lack of Veeva or CRM integration. Paper call notes and spreadsheets. No structured account intelligence flowing back to market access. No auditable activity record. A failure of basic ops hygiene that is still common at biotechs running their first launch.
6. Treating the FRM team as a commercial overlay. When the FRM team reports to sales leadership instead of market access, the compliance risk profile shifts from manageable to material. OIG and DOJ enforcement posture around inducements and patient-support funding makes commercially co-managed access support a higher-risk design (OIG fraud-and-abuse guidance; DOJ PSI settlement).
7. No attribution discipline. Without a measurement framework in place before deployment, there is no way to answer “should we grow, shrink, or redirect the FRM team next year.” The question becomes political. The budget becomes a guess.

For therapeutic-area-specific deployment patterns, see the rare disease launch vendor playbook and the oncology launch vendor playbook. For a broader overview of how FRM fits with hub and specialty pharmacy, see pharma services explained: hub, specialty pharmacy, and FRM.

---

Technology Stack

Modern FRM programs run on three core technology layers:

• CRM. Veeva Systems CRM (or Veeva Vault CRM in the newer deployments) is the industry default. Salesforce Health Cloud shows up at smaller biotechs. The FRM CRM should share a patient and account identifier with the hub platform, not sit in a siloed database.
• Hub case management portal. Read-only FRM access to the hub vendor’s case management system, scoped to accounts in territory, with real-time status on open cases.
• Payer intelligence tools. Structured access to payer policy databases, formulary position feeds, and PA criteria references. Most vendors build this internally; a few (Indegene, Inizio) offer it as a licensable platform.

AI-powered prior authorization platforms are reshaping the workload at the margins. As tools like Infinitus, Superdial, and emerging agentic PA platforms automate routine BV and PA tasks, the FRM role is shifting from transactional support (how to submit a PA) to strategic consulting (how to navigate complex payer landscapes, build appeals strategies, optimize site-of-care decisions). That evolution increases the skill threshold and cost per FRM but also increases the value delivered per account interaction.

---