Hub Services Pricing Benchmarking: What Should Manufacturers Pay?

Thesis

The buyer’s job is therefore not to find “the” market price. It is to translate each proposal into comparable unit economics: cost per active patient, cost per successful first fill, cost per BV/PA transaction, cost per adherent patient, hub spend as a share of expected patient revenue, and cost of switching if the program underperforms.

Distinct Buyer Job

Use this page after vendors have submitted bids. For earlier stages:

• Use Hub Services Platforms to build the shortlist.
• Use Hub Services Buyer’s Guide to run the RFP and score the finalists.
• Use AI Hub Operations ROI to test automation savings and pass-through economics.
• Use Hub Services Market Analysis to understand platform ownership and M&A context.

The Four Pricing Models

Model	What the manufacturer is buying	Best fit	Main risk
FTE-based	Dedicated or shared operating capacity	Complex programs with predictable volume and high-touch needs	Paying for unused launch capacity or opaque staffing markups
Per-transaction	BV, PA, call, appeal, copay, PAP, adherence, or triage events	Variable-volume programs where activity is measurable	Rework and duplicate touches can inflate volume
Per-patient	Active or enrolled patient-months	Programs where patient population is the cleanest unit of work	”Active” and “enrolled” definitions can be gamed
Performance overlay	Bonus / penalty tied to time-to-therapy, conversion, adherence, quality, or satisfaction	Mature programs with clean baselines and shared KPI definitions	KPI disputes, payer-policy noise, and exclusion logic

Most serious proposals are hybrids. A useful bid separates base capacity, variable activity, technology, implementation, analytics, and change-order terms instead of bundling them into one monthly fee.

Proposal Normalization

Convert every proposal into four buckets before comparing vendors:

Bucket	What to normalize
People	Dedicated FTE count, shared-FTE assumptions, supervisor ratios, clinical licensure mix, overtime rules, and ramp-down rights
Workflow volume	Expected enrollments, benefit investigations, PAs, appeals, copay enrollments, PAP screenings, adherence touches, and outbound calls
Technology	Platform license, integrations, reporting, API connections, OCR / AI tools, CRM configuration, data warehouse feeds, and client-portal access
Change risk	New indication launches, payer-policy shifts, formulary exclusions, REMS amendments, supply interruptions, state copay-rule variation, and vendor transition support

A manufacturer should treat any pricing proposal that lacks FTE assumptions, utilization assumptions, transaction definitions, data-feed scope, and automation assumptions as incomplete.

Cost Drivers to Isolate

Driver	Why it changes price
Therapy complexity	Rare disease, oncology, CGT, REMS, and buy-and-bill products require more clinical judgment, documentation, and escalation than standard pharmacy-benefit specialty products.
Payer and benefit mix	Medical-benefit products, Medicaid-heavy mixes, and high PA friction create more manual work than clean pharmacy-benefit products with strong ePA coverage.
Pharmacy model	Free goods, bridge, PAP dispensing, cold-chain, and limited-distribution handoffs add cost and governance complexity.
Data requirements	Patient-level feeds, real-time APIs, field-team dashboards, payer analytics, and data-lake integration should be priced explicitly.
Automation	eBV/ePA, OCR, voice AI, and rules engines can reduce labor but may also introduce implementation, QA, exception-handling, and vendor-savings-retention questions.
Launch phase	Pre-launch staffing, UAT, SOP build, training, and first-90-day surge coverage should be separated from steady-state economics.

Negotiation Leverage Points

1. Bid both fixed and variable structures. Ask each finalist to submit an FTE-based model, a transaction/patient model, and its recommended hybrid.
2. Demand a staffing bridge. Require named roles, dedicated/shared split, supervisor ratios, licensure mix, overtime rules, and ramp-down triggers.
3. Define transactions tightly. A PA resubmission, missing-information call, duplicate BV, appeal, and abandoned case should not become surprise billable events.
4. Unbundle technology. Separate platform license, integrations, API, reporting, analytics, AI/OCR, CRM configuration, and data warehouse fees.
5. Cap change orders. New indications, formulary changes, REMS updates, payer-policy shifts, and dashboard changes should have pre-negotiated bands.
6. Share automation savings. If a vendor claims AI or ePA will reduce labor, the contract should say how savings flow back to the manufacturer.
7. Protect transition rights. Data export, phone/fax/PO box ownership, transition support, and post-termination fee caps preserve leverage.

Contract Controls That Preserve Optionality

The pricing model should include a credible exit path. For first-launch biotech programs, the most important commercial data often appears in the first 6-12 months: payer denials, abandonment points, PA criteria, patient affordability friction, FRM escalation patterns, and SP handoff quality. If the vendor controls those data without strong portability terms, a nominally cheaper hub contract can become expensive when the manufacturer wants to switch, insource, or add a second vendor.

Minimum contract controls:

• Patient-level and account-level data export rights in a defined format.
• A 90- to 180-day transition-support obligation with capped fees.
• Clear definitions of active patient, enrolled patient, closed case, abandoned referral, and unresolved payer barrier.
• Separate pricing for implementation, steady-state operations, change orders, and custom analytics.
• A right to re-baseline staffing after launch volumes stabilize.

---

Key Takeaways

1. There is no reliable public universal rate card. Force comparability through normalized assumptions, not generic benchmarks.
2. The pricing model changes incentives. FTE pricing buys capacity; transaction pricing buys activity; patient pricing buys enrolled population management; performance overlays buy measured outcomes.
3. Technology savings need contract language. Automation claims matter only if the manufacturer receives lower fees, better SLAs, or measurable speed-to-therapy lift.
4. Definitions are the economics. Active patient, enrolled patient, closed case, abandoned case, appeal, successful BV, and transition support must be defined before award.
5. Exit rights are part of price. A cheaper contract that locks up data, phone numbers, or transition support can become more expensive than a higher bid with portability.

Implications

Manufacturers should ask every hub bidder to submit a pricing bridge from staffing to unit economics. The bridge should show staffing assumptions, technology fees, transaction fees, subcontractor markups, expected patient volume, expected PA/BV mix, change-order triggers, and how savings from automation are shared. That is the only way to compare a full-stack vendor, independent hub, and AI-native entrant on the same basis.

Contract language should protect against the three common failure modes: paying for unused launch capacity, absorbing uncontrolled transaction spikes, and losing leverage after the vendor owns the data and workflow. Use phased implementation fees, capped change orders, audit rights, data-export obligations, and performance overlays tied to time-to-therapy, first-fill conversion, PA approval, and patient satisfaction rather than activity volume alone.

---

Related Pages

• Hub Services Market Analysis
• Hub Services Buyer’s Guide 2026
• Hub Services RFP Framework
• Copay Processors Comparison
• Gross-to-Net Dynamics