Hub Services Buyer's Guide 2026: Complete Vendor Evaluation Framework

Thesis

Hub vendor selection is a high-consequence operating decision because the chosen partner controls the patient access workflow during the launch window: intake, benefit verification, prior authorization, affordability, specialty pharmacy coordination, data reporting, and escalation. A weak fit can slow first fills, obscure operational problems, and make later switching expensive.

The best hub is not universally the largest or cheapest vendor. The right choice depends on therapy complexity, patient volume, distribution channel, payer friction, internal manufacturer capacity, and the degree of control the brand team needs over data, patient experience, pharmacy routing, and future vendor-switching optionality.

Implications

For shortlist design: Build the shortlist around the product archetype. Rare disease and cell/gene programs need high-touch clinical operations and specialty handling; high-volume autoimmune or metabolic launches need throughput, payer coverage, automation, and surge capacity.

For RFP scoring: Weight technology and operations heavily, but keep therapeutic experience, quality, and reporting as hard gates. Price should not outrank time-to-therapy, data ownership, implementation reliability, or patient-facing quality.

For diligence: Require live demonstrations, reference checks, and evidence from comparable launches. Treat vague data ownership language, no patient-level reporting, shared-only staffing, unclear PA metrics, and vendor-owned phone/fax channels as material risk, not minor contract points.

For contracting: Protect against the known failure modes: delayed implementation, underperformance, change of control, data lock-in, unauthorized subcontracting, and poor transition support. The cost of a failed launch or mid-program switch dwarfs modest differences in annual vendor fees.

Cluster Boundary

This guide intentionally does not rank vendors or publish pricing ranges. Use it to run the evaluation process. Use:

• Hub services platforms to decide whether ConnectiveRx, AssistRx, CareMetx, EVERSANA, or another hub archetype belongs in the shortlist.
• Hub pricing benchmarking to normalize bids once proposals arrive.
• AI hub operations ROI to test automation claims and savings pass-through.
• Hub services market analysis to understand M&A, platform ownership, and market structure.

When You Need a Hub (and When You Don’t)

Not every drug needs a hub. The decision hinges on three factors: payer complexity, patient burden, and distribution channel.

You need a hub when:

• The product requires prior authorization from most commercial payers
• The therapy is specialty-distributed (buy-and-bill or specialty pharmacy) with AWP above $10,000/year
• Patients face meaningful out-of-pocket exposure requiring copay assistance or PAP
• The product has REMS requirements, restricted distribution, or complex administration (injection training, infusion coordination)
• Your internal patient services team has fewer than 20 dedicated FTEs

You likely don’t need a full hub when:

• The product is a traditional retail pharmacy drug with broad formulary coverage
• Prior authorization rates are below 20% across major payers
• The patient population is large enough to justify building in-house (typically 50,000+ patients)
• You already operate a mature patient services function from a prior launch

The scale question matters. A small rare disease program serving 500 patients needs a very different hub than an autoimmune launch expecting 50,000 enrollees in year one. Some vendors specialize in high-touch, low-volume programs; others are built for high-volume operational throughput. Mismatching scale to vendor capability is one of the most common and costly errors in hub selection.

Programs launching into competitive therapeutic areas with established standard-of-care therapies need hub services operational from day one. For first-in-class therapies in rare disease, a phased approach can work: start with core access services (BV, PA, PAP) and layer on adherence and clinical support as the patient base grows.

---

The 7 Capability Areas to Evaluate

1. Technology Platform

Weight in RFP scoring: Typically 25% of total evaluation weight — determines the ceiling on operational performance.

What “good” looks like:

• eBV completes in under 60 seconds with a success rate above 85% for commercial plans
• ePA is fully electronic, integrated with payer portals, and returns determinations (not just submission confirmations). About 43% of ePA submissions now process automatically without manual intervention; best hubs push this higher through payer-specific routing logic
• CRM tracks every patient interaction with a single patient identifier — no spreadsheet side-systems. Configuration changes happen through configuration, not custom code
• Web portal provides patients, providers, and brand team with real-time visibility
• All data owned by the manufacturer, delivered via SFTP and real-time API, refreshed daily

Red flags: Vendor cannot demonstrate a live patient portal during RFP. eBV requires manual fallback for more than 30% of transactions. Separate databases for hub and pharmacy operations with no real-time sync. Vendor proposes “Phase 2” for API integration.

Key questions:

1. What is your eBV electronic success rate by payer tier (top 10, regional, Medicaid managed care)?
2. Walk through a PA submission from provider enrollment through determination — how much is fully electronic vs. manual?
3. How are configuration changes handled — does adding a new copay program tier require a code release or configuration change?

2. Operations

What “good” looks like:

• Dedicated team model with named supervisors and team leads assigned to the brand
• First-call resolution rates above 80%, with multi-reason call tracking
• Workforce models that adjust staffing daily based on volume forecasts, not monthly
• Staff trained on product-specific disease education, compliance requirements, and adverse event reporting
• Monthly attrition reporting with visible career paths for hub staff (reducing the 30-40% annual attrition that plagues the industry)
• Near real-time reporting on call center performance: intraday abandonment rates, wait times, resolution metrics

Red flags: Vendor proposes “portfolio” or “shared services” model sharing agents with 10+ other brands. No dedicated team lead. Training is one-week onboarding with no ongoing disease education. Vendor cannot provide attrition data.

Key questions:

1. Staffing model: how many FTEs dedicated to our program vs. shared? Minimum program size for a fully dedicated team?
2. Average tenure and annual attrition rate for hub agents? How does that compare to industry benchmarks?
3. Contingency plan for a 50% volume spike — how quickly can you add trained FTEs?

3. Prior Authorization and Reimbursement

What “good” looks like:

• First-pass PA approval rates above 75% (disease-area dependent; oncology with NCCN guideline support can exceed 90%)
• Automated identification of PA requirements at the payer-plan level during benefit verification
• ePA submission with real-time status tracking communicated to both HCP offices and patients
• Structured appeals process with letter templates, clinical rationale support, and peer-to-peer scheduling assistance
• PA turnaround reduction from weeks to days through digital workflows

Red flags: Vendor cannot cite first-pass approval rates for comparable TAs. PA status tracking limited to “submitted” and “approved/denied.” Appeals handled by same generalist agents who do intake. No payer-specific intelligence maintained.

Key questions:

1. First-pass PA approval rate for [therapeutic area] programs — how do you benchmark against payer-reported data?
2. How do you maintain and update payer-specific PA requirements? Refresh frequency for payer intelligence database?
3. Describe your appeals process — who writes the appeal? How do you support peer-to-peer reviews?

4. Financial Assistance Programs

What “good” looks like:

• Full-service copay administration as secondary insurance with electronic adjudication at POS
• Support for both pharmacy and medical benefit copay (buy-and-bill programs now account for roughly half of specialty product assistance)
• Proactive accumulator and maximizer detection and mitigation. As of late 2025, about 39% of commercially insured lives are enrolled in plans actively using accumulators or maximizers — and rising
• Integrated PAP with income verification, Rx validation, and DUR
• Fraud and misuse controls with real-time claims monitoring
• Digital enrollment pathways (not just fax-in forms)

Red flags: Copay and hub on separate platforms with no shared patient record. No accumulator/maximizer strategy beyond “we monitor it.” PAP processing exceeds 10 business days. No medical benefit copay support.

Key questions:

1. How do you identify and respond to accumulator/maximizer programs? What mitigation strategies?
2. Copay claims adjudication — real-time at POS or batch-processed? How do you handle medical benefit copay?
3. Average time from PAP application receipt to first free drug shipment?

For copay-heavy programs, treat ConnectiveRx as one affordability-capable hub operator to diligence, not as the benchmark for every processor bid. Use Copay Processors Comparison when the buying decision is specifically the copay / affordability processing layer.

5. Clinical and Nurse Support

What “good” looks like:

• Licensed nurses or nurse navigators assigned to the program with therapeutic area expertise
• Structured adherence programs with evidence-based touchpoints (not just reminder calls)
• Predictive analytics identifying at-risk patients before they abandon therapy — with new-to-brand abandonment rates hitting 35-40%, early intervention models are replacing reactive adherence programs
• Injection training via telehealth or in-home visits, with completion tracking
• Integration with the hub CRM so clinical interactions are documented alongside access and financial assistance data

Red flags: “Nurse support” is a phone line staffed by LPNs with no disease-specific training. Adherence programs consist solely of automated refill reminders. No telehealth capability. Clinical notes stored in a separate system from the hub CRM.

6. Reporting and Analytics

What “good” looks like:

• Real-time dashboards showing enrollment, PA status, time-to-fill, copay utilization, and adherence metrics — not static monthly PowerPoints
• Patient-level data with full journey visibility from enrollment through ongoing fills
• Geographic analysis of enrollment, prescriber activity, and payer mix — actionable intelligence for field teams
• Payer-level analysis: approval rates, turnaround times, denial reasons by payer
• Complete data ownership by manufacturer with daily SFTP feeds and real-time API access

Red flags: Monthly aggregate summaries only. Patient-level data requires special request. No API — data delivered by email. Dashboards unavailable until 90 days post-launch. Vendor resists data ownership clauses.

7. Compliance and Quality

What “good” looks like:

• Documented Program Quality Plan developed collaboratively during implementation
• CAPA process with root cause analysis, corrective action timelines, and trend tracking
• Complaint tracking with manufacturer visibility into all complaints and resolutions
• Contractual provision for vendor reimbursement for errors causing financial or regulatory exposure
• Regular quality metrics reporting: error rates, complaint volumes, CAPA closure timelines

Red flags: No formal CAPA process. Self-reported quality metrics. Vendor resists error-reimbursement clauses. One-time compliance training with no refresher cadence. Cannot produce evidence of recent quality audit.

---

Pricing Checkpoint, Not Pricing Benchmarks

The RFP should force pricing transparency, but this guide should not be used as the pricing benchmark. Require every bidder to submit a pricing bridge that separates:

Bucket	What the RFP should require
People	Dedicated FTEs, shared FTEs, supervisors, nurses, pharmacists, bilingual coverage, overtime rules, and ramp-down rights
Workflow volume	Enrollments, BV, PA, appeals, copay, PAP, adherence touches, outbound calls, and pharmacy triage events
Technology	Portal, CRM, API, reporting, data feeds, AI/OCR tools, EHR integrations, and implementation/configuration costs
Change risk	New indication launches, payer-policy changes, REMS amendments, formulary exclusions, supply disruption, and transition support

Then use Hub Pricing Benchmarking to normalize proposals. This keeps the buyer’s guide focused on process and avoids implying that a generic rate card is reliable across therapy areas.

---

Red Flags and Deal-Breakers

These should eliminate a vendor from consideration or trigger serious contract protections:

• Vendor owns phone numbers and PO box. Manufacturer must own all customer-facing contact channels. If the vendor owns them, you lose patient access on switch.
• No patient-level reporting. If only aggregate dashboards are available, the vendor either lacks the data infrastructure or is hiding operational problems.
• Cannot demonstrate PA first-pass approval rates. Any vendor unable to cite these for comparable TAs either doesn’t track them or doesn’t want to share. Both are disqualifying.
• No dedicated team model option. Shared/portfolio staffing only means your program will be deprioritized when larger clients need surge capacity.
• Conflicts of interest. A hub vendor owned by a distributor, PBM, payer, or specialty pharmacy handling competitors’ products creates structural conflicts around patient routing, data firewalls, and operational prioritization. Cencora’s April 2026 transfer of legacy Lash Group / TheraCom U.S. hub operations to CareMetx is a concrete reminder that ownership and preferred-partner context can change mid-contract.
• No CAPA process or quality management system. Creates compliance risk that falls on the manufacturer.
• Data ownership ambiguity. If the contract doesn’t explicitly state manufacturer owns all data with full portability upon termination, walk away.
• Offshore staff without prior approval. Manufacturer should retain right to review and approve use of subcontractors or offshore resources. Unauthorized offshoring creates HIPAA and quality risks.

---

The 15 Most Important RFP Questions

Drawn from a comprehensive 73-question RFP framework across 12 evaluation domains (see Hub RFP framework analysis for the full set). These are the questions that most effectively differentiate vendors:

1. Implementation plan — Detailed project plan from contract execution to go-live with milestones, dependencies, and on-time delivery track record.
2. eBV success rate by payer tier — Broken down by top 10 commercial payers, Medicare, and Medicaid managed care.
3. PA workflow walkthrough — From initiation through determination, including ePA routing, manual fallback, and status communication.
4. Copay adjudication and accumulator handling — Electronic POS adjudication for pharmacy and medical benefits, plus accumulator/maximizer mitigation strategy.
5. Program org chart — Dedicated FTEs, roles, reporting structure, and experience of proposed program director.
6. Staff attrition rate — 12-month data with retention strategies and career path structure.
7. System testing protocol — Mock simulation scenarios, UAT process, configuration validation before go-live.
8. Correspondence generation — How the system generates and tracks correspondence, with turnaround times from trigger event.
9. Free drug pharmacy process — Rx validation, DUR, shipment scheduling, inventory management, FEFO protocols, destruction procedures.
10. Real-time data integration — APIs between hub CRM and pharmacy system, patient data flow across systems.
11. Quality management system — CAPA process, complaint tracking, metrics reported to clients.
12. Data transition on termination — What data received, in what format, within what timeframe.
13. Business continuity plan — Remote/onsite flexibility, pharmacy backup, advance notice of business changes (M&A, system migrations, leadership changes).
14. Underperformance remedies — What triggers escalation, what remedies are contractually available.
15. Therapeutic area references — Named programs of similar size, complexity, and distribution model with specific launch metrics.

---

How to Run the Evaluation Process

Timeline

Start the RFP process 12-18 months before target launch date:

Phase	Duration	Timing Relative to Launch
Internal requirements definition	4-6 weeks	18 months pre-launch
RFI to market (broad scan)	3-4 weeks	16 months pre-launch
Shortlist 3-5 vendors	2 weeks	14 months pre-launch
Formal RFP	4-6 weeks	13 months pre-launch
Vendor presentations and Q&A	2-3 weeks	11 months pre-launch
Site visits (finalists only)	2-3 weeks	10 months pre-launch
Selection and contracting	4-6 weeks	9 months pre-launch
Implementation begins	Immediately	8 months pre-launch

Stakeholders

Assemble a cross-functional evaluation team. Market access professionals are the primary decision-makers in roughly one-third of hub selections, with another two-thirds influencing:

• Brand/Commercial lead — owns budget and strategic priorities
• Patient services/Market access — owns operational requirements and day-to-day vendor management
• Medical affairs — evaluates clinical support capabilities and adverse event processes
• Legal/Compliance — reviews data ownership, HIPAA provisions, OIG compliance
• Procurement — manages commercial terms, pricing negotiation, contract structure
• IT — evaluates technology platform, API integration, data architecture

Scoring Methodology

Category	Suggested Weight	Rationale
Technology Platform	25%	Determines operational ceiling and scalability
Operations	20%	Directly impacts patient experience and outcomes
Therapeutic Experience	15%	Reduces implementation risk and accelerates time-to-value
Quality and Compliance	15%	Protects against regulatory and reputational risk
Organizational Design	10%	Staffing quality and stability drive long-term performance
Reporting and Analytics	10%	Enables continuous optimization and commercial intelligence
Pricing and Value	5%	Important but should not drive the decision

Pricing carries only 5% weight for a reason: the difference between cheapest and most expensive vendor on a $5M program might be $500K-$750K annually. The cost of a failed launch or a mid-program vendor switch dwarfs that delta.

Reference Checks

Ask references:

• How did implementation timeline compare to what was proposed?
• Biggest operational challenge and how the vendor responded?
• Responsiveness to program change requests?
• Would you select this vendor again for a new launch?
• What does the vendor do poorly that you’ve learned to work around?

---

Common Mistakes

Choosing on price alone. A vendor undercutting by 20% is either understaffing, using undisclosed offshore resources, or planning to renegotiate after lock-in. The lowest bid is rarely the best value.

Not visiting the call center. An in-person or virtual site visit reveals more in two hours than an RFP response does in 200 pages. Listen to live calls. Talk to agents. Walk the floor.

Underestimating implementation timeline. Hub implementations are multi-month cross-functional programs, not procurement paperwork. Starting the RFP close to launch increases the risk of going live with partial workflows, weak data feeds, or under-tested payer logic.

Not negotiating data ownership clauses. If the contract doesn’t explicitly state all data is manufacturer-owned and fully portable, the vendor has leverage that grows monthly. Negotiate before signing.

Choosing a vendor that’s the wrong size for your program. At a Tier 1 full-stack hub (EVERSANA, Cencora/Lash Group, Optum), a $3M program may not command senior leadership attention. At a Tier 3 emerging vendor, a $10M program may exceed operational capacity. Match program scale to vendor sweet spot.

Ignoring the M&A environment. The hub services market is in active consolidation. PE firms are building platforms around ConnectiveRx, CareTria, AssistRx, Valeris, and CareMetx, while distributor-owned and PBM-adjacent operators keep reshaping their access-service footprints. Build contractual protections for change-of-control events. See hub services market analysis for consolidation landscape.

Overlooking specialty pharmacy integration. Integrated hub-plus-SP models can reduce handoff friction, but they can also concentrate channel risk. Even if you choose a standalone hub, evaluate how the vendor coordinates with the specialty pharmacy network, who controls routing decisions, and how patient-level data flows across the handoff. Use Hub Services Platforms for the specialist-vs-integrated shortlist decision.

---

Frequently Asked Questions

How long does it take to implement a hub program? Typical implementations are multi-month efforts from contract execution to go-live, and complex programs with custom technology builds or multiple service lines take longer. Validate on-time delivery through reference checks and require a milestone plan with named dependencies.

Can we switch hub vendors after launch? Possible but costly and disruptive — transitions require parallel operations, data migration, contact-channel continuity, and payer/pharmacy retraining during cutover. Best protection is selecting the right vendor upfront with strong contractual terms including data portability, change-of-control provisions, and performance guarantees.

Should we choose a vendor with its own specialty pharmacy? An integrated hub-plus-SP model can reduce handoff delays and improve data continuity. However, it can limit distribution flexibility and concentrate risk. Evaluate whether the vendor’s SP has the therapeutic expertise, payer contracts, LDD access, data-sharing model, and conflict controls your product requires.

What KPIs should we track from day one? Five core metrics: time from enrollment to first fill, PA first-pass approval rate, PA turnaround time, call center first-call resolution rate, and copay utilization rate. Add adherence and persistence metrics after 90+ days of patient data.

How do we protect ourselves if the hub vendor is acquired? Include change-of-control clause giving termination rights (without penalty) on material ownership change. Require 6-month advance written notice of M&A activity, system migrations, or leadership changes. Ensure data portability provisions survive termination.

---