What is the recommended Pharmacy Benefit Manager (PBM) sales and operations tech stack in 2027?

Direct Answer

A pharmacy benefit manager in 2027 runs a stack built around real-time claim adjudication, network management, rebate accounting, and client reporting — and the technology choice signals the business model. The marquee apps are Capital Rx JUDI (now operating under Judi Health) for cloud-native adjudication in the transparent pass-through camp, SS&C RxClaim for legacy adjudication still running the big-three PBMs and most mid-market clients, Surescripts for e-prescribing and specialty routing, Salesforce Health Cloud for client and member servicing, Snowflake plus Tableau and ThoughtSpot for analytics, and Workday plus SAP or Oracle Cloud ERP for finance and HR.

Genesys or Twilio Flex run the member-and-pharmacist contact center; specialty pharmacy fulfillment runs on Accredo, CVS Specialty, or proprietary tooling.

Why the Pharmacy Benefit Manager Stack Works Differently

A PBM is not a payer, not a pharmacy, and not a traditional health-tech company, and four mechanics force a specialized stack rather than off-the-shelf enterprise SaaS.

1. Adjudication runs in real time at massive volume. A pharmacist swipes a prescription, and the PBM has to return an accept-or-reject decision in under two seconds — applying formulary, prior authorization, copay tier, accumulator, deductible, and network logic across millions of transactions a day. The big-three PBMs each process more than two billion claims a year. No general-purpose ERP or rules engine handles this volume at that latency; the adjudication platform is its own category.

1. Rebate economics are opaque, contractual, and political. Manufacturer rebates, administrative fees, GPO fees, and pass-through versus retained spreads all live in master contracts that have to be modeled, tracked, allocated, and reported to clients with full audit trails. Transparent and pass-through PBMs (Capital Rx, Navitus, Costco Health Solutions, Rightway) are competing on technology that proves the math; legacy PBMs are competing on scale. The accounting layer for rebates is not a feature of NetSuite — it is bespoke or built into platforms like JUDI.

1. Regulatory pressure is intensifying and recent. The 2024 FTC report on PBM consolidation, CMS Star Ratings for Medicare Part D plans, the Inflation Reduction Act's drug-price negotiation provisions, state-level transparency laws (Florida, Texas, New York), and ongoing Congressional scrutiny all create reporting and audit obligations no other industry faces. The stack has to retain claim-level detail for 10+ years and produce regulator-ready evidence on demand.

1. The participants in a transaction are unique. A single claim touches the patient, the prescriber, the pharmacy, the wholesaler, the manufacturer, the plan sponsor, and CMS. Each one is a separate counterparty with its own contract, fee schedule, and data feed. Surescripts is the connective network for prescribers; NCPDP standards govern the message formats; and the PBM has to translate among all of them.

The Core Stack, Layer by Layer

This is the recommended set of products by functional layer at a PBM. The count reflects what a real operator runs; layers that do not apply are skipped.

Claim Adjudication Engine — SS&C RxClaim for legacy and mid-market PBMs (Capital Rx JUDI for cloud-native, transparent operators; ClaimDOC for self-funded TPA-style adjudication). This is the spine. RxClaim is the AS/400-era platform that still runs the majority of US adjudication volume, including most big-three PBM transactions, with a long tail of mid-market clients on SS&C's hosted service.

JUDI is the modern alternative built by Capital Rx (rebranded Judi Health in late 2025 after a $400M funding round); it powers a transparent flat-fee, 100%-rebate-pass-through model and has crossed five million contracted lives. RxClaim is enterprise-quote; JUDI is licensed by tier with most mid-market deployments landing in the $1M-$5M/year range plus per-claim fees.

ClaimDOC is the choice for direct-to-employer reference-based-pricing-style PBMs.

E-Prescribing Network — Surescripts. The connectivity layer between roughly 95% of US prescribers and the PBM. Surescripts routes the electronic prescription, returns benefit verification, processes electronic prior authorization (ePA), and powers the specialty medications gateway used by Accredo, CVS Specialty, and Kroger.

There is no direct license fee for the PBM; costs are bundled into transaction fees that flow through Surescripts' member fee schedule. Specialty pharmacies using the Surescripts Specialty Medications Gateway report 2-day reductions in time-to-fill and 44% fewer prescriber phone calls.

Specialty Pharmacy Fulfillment — Accredo (Cigna Evernorth), CVS Specialty, or proprietary tooling. Specialty drugs are now more than half of PBM-managed spend, so specialty fulfillment is its own operational layer. The big-three vertically integrate (Express Scripts/Accredo, CVS Caremark/CVS Specialty, OptumRx/Optum Specialty); independent and transparent PBMs partner with specialty pharmacies or build limited in-house capability.

AdvancePCS-era infrastructure persists in places; newer entrants build on modern fulfillment platforms.

Client and Member CRM — Salesforce Health Cloud (plus heavy custom build). Client success teams managing Fortune 500 plan sponsors, member-services reps handling formulary questions, and pharmacy network teams managing relationships with retailers all live in Salesforce Health Cloud.

Pricing runs roughly $325/user/month for Health Cloud Enterprise. Almost every PBM extends it with custom objects for plan design, formulary change requests, and rebate reconciliation tickets. A custom-built client portal sits on top.

Data Warehouse & Analytics — Snowflake plus Tableau plus ThoughtSpot. Claim-level data lands in Snowflake at roughly $2-$4/credit with most PBMs spending $500K-$10M/year depending on scale. Tableau Server runs about $75/user/month for Creator licenses and powers client-facing reporting packs.

ThoughtSpot adds search-driven analytics for executive and account-team self-service at roughly $95/user/month on the team tier and enterprise-quote at scale. Together they replace the 1990s-era flat-file reporting that legacy PBM clients still receive in places.

Regulatory & Compliance Tooling — Custom build plus dedicated CMS reporting tools. PBMs file Medicare Part D Star Ratings data, Health Plan Reporting submissions, and increasingly FTC reporting tied to consolidation oversight. Most PBMs build a regulatory reporting layer in-house on top of Snowflake, supplemented by purpose-built tools for CMS Plan Finder data submissions and state-level transparency filings.

Expect $1M-$5M/year in fully loaded regulatory tech spend at a mid-market PBM.

Contact Center — Genesys Cloud (Twilio Flex for digital-first PBMs). Member-services reps, pharmacist help-desk agents, and prior-authorization clinical staff all need a contact center with PHI-grade security, FCR tracking, and integration with the adjudication record. Genesys Cloud runs roughly $75-$150/agent/month depending on tier.

Twilio Flex is the choice for PBMs that want a programmable, developer-driven contact center; pricing is consumption-based at roughly $1/agent-hour plus telephony.

ERP & Finance — SAP S/4HANA at the big three; Oracle Cloud ERP for large mid-market PBMs (NetSuite for under $500M revenue). Multi-entity finance, rebate accounting, accounts receivable from plan sponsors, and payments to pharmacies all run through enterprise ERP. SAP S/4HANA at the big three runs into eight figures annually.

Oracle Cloud ERP for a large mid-market PBM runs roughly $2M-$8M/year. NetSuite at $1,500-$3,000+/month plus modules supports smaller transparent PBMs early on.

HR & Workforce — Workday HCM. Pharmacists, clinical staff, account executives, and developers need a real HCM with credentialing, license tracking, and continuing-education compliance. Workday is the default at PBM scale; pricing is custom-quoted and typically lands at $22-$45/employee/month for the full HCM-plus-Financials suite.

Productivity, Collaboration, and IT Security — Microsoft 365 E5 plus Okta plus CrowdStrike. Microsoft 365 E5 at roughly $57/user/month covers email, Teams, SharePoint, and embedded security. Okta runs identity and SSO at roughly $15/user/month for the Workforce Identity Cloud.

CrowdStrike Falcon covers endpoint at roughly $8-$15/endpoint/month — non-negotiable given the PHI handling and the breach exposure.

Layers deliberately skipped: PBMs do not need a separate marketing automation suite (sales-led B2B with long cycles); do not need a generic field-service platform; and do not need iPaaS at small scale because Snowflake plus point-to-point integrations cover most flows.

Real Operators & What They Run

Public footprints and industry reporting point to the following stacks at named operators.

• CVS Caremark — runs SS&C RxClaim-family adjudication at massive scale alongside proprietary tooling, vertically integrated with CVS Specialty for specialty fulfillment, SAP S/4HANA for finance, Salesforce Health Cloud for client servicing, and an enterprise Snowflake and Tableau analytics footprint.
• Express Scripts (Cigna Evernorth) — operates Cigna's proprietary adjudication stack with deep Surescripts integration, vertically integrated with Accredo specialty pharmacy (which has cut specialty fill times by 2+ days using the Surescripts gateway), SAP-class ERP, and an extensive custom client portal.
• OptumRx (UnitedHealth) — runs UnitedHealth's proprietary RxClaim-derived adjudication, integrated with Optum Specialty and the broader Optum data platform, Workday for HR, and one of the largest healthcare data-warehouse footprints in the industry.
• Capital Rx (Judi Health) — operates entirely on its own cloud-native JUDI platform with flat-fee transparent pricing and 100% rebate pass-through, Salesforce Health Cloud for client management, Snowflake for analytics, and Workday for HR. JUDI now powers more than five million contracted lives.
• Navitus Health Solutions — pass-through PBM owned by SSM Health, running a hybrid stack with RxClaim-family adjudication, custom rebate-accounting tooling, and standard Salesforce-and-Workday enterprise SaaS.
• MedImpact — independent PBM running proprietary adjudication built over decades on AS/400 foundations, with a substantial custom client-reporting stack and Oracle ERP.
• Costco Health Solutions and Rightway — newer transparent PBM entrants competing on technology and member experience, leaning toward cloud-native adjudication (JUDI in some cases, custom builds in others) and modern data platforms.

Integration Architecture

The stack only works when adjudication, e-prescribing, rebate accounting, client reporting, and the contact center share data instead of living in silos. The adjudication engine (RxClaim or JUDI) is the system of record for claims; Surescripts is the connectivity edge; Snowflake is the analytical truth; Salesforce Health Cloud is the relationship layer; the ERP owns the money.

The most important integration is the loop between adjudication and the warehouse: every claim has to land in Snowflake within minutes so that client reporting, regulatory filings, and rebate accruals all reconcile to the same source of truth. The second-most important is the link from Surescripts and the pharmacy POS into adjudication, since that is the real-time path a member experiences at the counter.

The data flow below shows how a single prescription moves from prescriber to paid claim to rebate reconciliation.

Failure Modes

Four stack mistakes show up repeatedly when PBMs lose clients or get marked down at audit. (1) Bolting reporting onto legacy adjudication without a warehouse. RxClaim flat-file extracts and overnight batches cannot produce the same-day client analytics that modern plan sponsors expect — PBMs that skip Snowflake-class warehousing lose mid-market clients to transparent competitors who can.

(2) Underinvesting in rebate accounting. When the rebate ledger is a spreadsheet maintained by finance, the PBM cannot prove pass-through math to a sophisticated buyer or a regulator, and contract disputes turn into multi-month forensic exercises. (3) Fragmented client and member servicing. When Salesforce Health Cloud and Genesys do not share the live claim record, account executives and member-services reps give conflicting answers, and client NPS collapses.

(4) Treating regulatory reporting as a project rather than a platform. CMS Star Ratings, FTC reporting, and state transparency laws are continuous obligations — PBMs that build each filing as a one-off project burn clinical and analytics talent on rework instead of on competitive offerings.

Budget & Sizing

Monthly software cost scales with covered lives, claim volume, and business model.

• Small transparent PBM (under 500K lives, regional, pass-through model). JUDI or RxClaim hosted tier, Surescripts membership, Salesforce Health Cloud, Snowflake, Tableau, NetSuite, Workday HCM, Genesys Cloud, Microsoft 365 E5, Okta, CrowdStrike. Expect roughly $200,000-$600,000/month in software plus per-claim fees.

• Mid-market PBM (500K-5M lives). Full RxClaim or JUDI deployment, Surescripts enterprise, Salesforce Health Cloud with custom client portal, larger Snowflake footprint, Tableau plus ThoughtSpot, Oracle Cloud ERP, Workday HCM and Financials, Genesys Cloud at scale, full Microsoft E5 plus Okta plus CrowdStrike. Expect roughly $1.5M-$6M/month in software.

• National PBM (10M+ lives, big-three or near-big-three). Proprietary or heavily customized adjudication, integrated specialty pharmacy, Surescripts enterprise, custom client portal on Salesforce Health Cloud, enterprise Snowflake and Databricks, SAP S/4HANA, Workday at full scale, multi-region Genesys, and a custom regulatory data platform. Software spend is $30M+/month with custom integration spend layered on top.

30/60/90 Day Implementation Plan

A staged rollout protects claim continuity, since the adjudication engine cannot go dark for even a few minutes without member impact.

Days 1-30: Stand up the adjudication spine. Migrate or stand up RxClaim or JUDI, load formularies, plan designs, and member eligibility, and run a parallel-processing period against the prior platform to validate every claim path. Wire Surescripts connectivity and confirm e-prescribing flows.

No client-facing changes yet — the adjudication engine is the priority.

Days 31-60: Add the analytical and servicing layers. Stream claim-level data into Snowflake; build the first wave of Tableau reporting packs for client account teams. Stand up Salesforce Health Cloud, import client and member records, and integrate with the adjudication system for real-time claim visibility.

Light up Genesys Cloud for the member-services and pharmacist help-desk lines.

Days 61-90: Integrate finance, rebates, and regulatory reporting. Connect the ERP to the rebate ledger and the pharmacy payment cycle. Build the first CMS Star Ratings and client-quarterly-business-review reporting packs out of Snowflake.

Finalize Workday, Okta, and CrowdStrike across the workforce. Exit with one cross-system view the CRO and the head of operations trust.

FAQ

RxClaim or JUDI for a new PBM build? JUDI if you are competing on transparency, flat-fee pricing, and modern client and prescriber experience — that is the bet Capital Rx made and has now scaled to five million lives. RxClaim if you need proven big-volume capacity, an extensive third-party integration ecosystem, and a hosted operating model.

The choice is a business-model signal as much as a technology pick.

Do we really need Surescripts, or can we connect directly to prescribers? You need Surescripts. It is the de-facto e-prescribing network connecting roughly 95% of US prescribers, and recreating that connectivity is a multi-year, multi-hundred-million-dollar undertaking with no business case. Pay the membership fees.

How do transparent and pass-through PBMs handle rebates differently in the stack? The rebate ledger is a first-class system rather than a finance spreadsheet — every manufacturer rebate, admin fee, and pass-through line item is tracked at claim-and-contract granularity, with client-facing dashboards proving the math.

JUDI bakes this in; legacy adjudication generally requires custom build on top.

Salesforce Health Cloud or a custom client portal? Both, in practice. Salesforce Health Cloud handles the internal account-team and member-services workflows; a custom-built client portal handles the high-stakes plan-sponsor-facing reporting and self-service. Trying to do plan-sponsor reporting purely inside Salesforce is the path to a churned client.

What is changing fastest in the PBM stack right now? Cloud-native adjudication, AI-powered prior authorization, real-time client analytics, and rebate transparency tooling. The 2024 FTC report and the 2025-2026 wave of state transparency laws have pushed the entire industry toward platforms that can prove their math at audit-grade detail.

What is the one tool to invest in first if budget is tight? The adjudication engine. Get it right — RxClaim if you are buying scale and ecosystem, JUDI if you are competing on transparency — and everything else can be built around it. Get it wrong and no amount of CRM and BI investment will save you.

Sources

• Capital Rx / Judi Health — JUDI platform documentation and 2026 contracted-lives milestone reporting
• SS&C Technologies — RxClaim and pharmacy benefit management solutions overview (2026)
• Surescripts — e-prescribing network and Specialty Medications Gateway product documentation (2026)
• Federal Trade Commission — Pharmacy Benefit Managers Interim Staff Report (2024) and updates
• Centers for Medicare & Medicaid Services — Medicare Part D Star Ratings methodology and Plan Finder data submission requirements (2026)
• Drug Channels Institute — Adam Fein's annual PBM market share and economics report (2026)
• Salesforce — Health Cloud edition pricing and PBM customer footprint (2026)
• Snowflake and Tableau — platform pricing pages and healthcare reference architectures (2027)
• Genesys — Genesys Cloud CX pricing tiers (2026)
• Workday — HCM and Financial Management pricing guidance for enterprise healthcare (2026)