The PBM RFP Process Has Too Many Steps: Why PfRs Reduce Procurement Waste

The Pharmacy Benefit Manager (PBM) Request for Proposal (RFP) process is often treated as the default path for selecting a pharmacy benefit partner.

For health plans, coalitions, unions, specialty pharmacies, employer groups, and procurement teams, referred to as requestors moving forward, the RFP can feel familiar, formal, and defensible. It gives stakeholders a known sequence: define requirements, issue the request, collect responses, compare vendors, negotiate, and contract.

But familiar does not always mean efficient.

The PBM RFP process can become a long chain of steps that consumes time, legal attention, pricing resources, executive review, consultant effort, and proposal labor before requestors even know which PBM offerings are truly strong fits.

That waste matters. Every hour spent managing unnecessary procurement complexity adds cost to the system. PBMs absorb proposal and pricing labor. Requestors absorb internal review and advisory costs. Members ultimately live with the consequences of pharmacy benefit decisions that may have taken too long, cost too much to evaluate, or narrowed the field before the best options were fully understood.

The Basic PBM RFP Process Has Many Moving Parts

A basic PBM RFP process often sounds simple until the actual workflow is mapped.

A requestor may need to:

• Identify internal stakeholders
• Define goals and requirements
• Gather claims, utilization, and plan design data
• Draft RFP documents
• Review questions with consultants, legal, finance, clinical, and procurement teams
• Engage and collaborate with Subject Matter Experts (SMEs)
• Select PBMs to invite
• Manage bidder questions
• Collect proposal responses
• Normalize pricing and rebate assumptions
• Review network, specialty pharmacy, clinical, and mail service capabilities
• Compare service guarantees and reporting commitments
• Conduct finalist interviews
• Request revised pricing or clarifications
• Negotiate business terms
• Begin legal review
• Prepare for implementation

For complex arrangements, this level of detail may be justified. Some PBM contracts require significant customization, stakeholder participation, and careful review.

The problem is that many opportunities are pushed through this full sequence even when requestors primarily need to understand what credible PBM offerings are already available.

That is where the waste begins.

Every Step Has a Labor Cost

The PBM RFP process does not only take calendar time. It uses expensive labor on both sides of the transaction.

Requestors may need support from procurement leaders, benefits teams, finance, legal, consultants, executives, clinical advisors, and operations stakeholders.

PBMs may need proposal writers, pricing analysts, sales leaders, account teams, clinical experts, network teams, implementation staff, compliance reviewers, legal counsel, and executives.

Those people are not cheap, and their time is not unlimited.

When the work is necessary, the cost can be justified. A truly custom PBM arrangement deserves serious analysis. But when the work is repetitive, avoidable, or created mostly by the structure of the RFP itself, the cost becomes harder to defend.

The industry should be honest about this: unnecessary procurement bloat does not create value for members. It consumes resources that could be used for better pricing, better service, better implementation, better reporting, or better member support.

The Middle of the RFP Process Can Benefit From Complexity

The traditional PBM RFP process often creates work for everyone in the middle.

Consultants, advisors, procurement teams, internal reviewers, legal teams, and proposal teams may all perform important functions. This article is not arguing those roles are unnecessary. Many are essential when a contract is complicated or risk is high.

But a process can become too dependent on intermediated work.

When comparison requires long documents, repeated clarification rounds, manual spreadsheet normalization, and multiple pricing revisions, the workflow itself becomes a cost center. The requestor may get a formal process, but not necessarily a faster or clearer decision.

The PBM may get a chance to compete, but at the cost of substantial proposal and pricing effort.

The member rarely benefits from the fact that the procurement process took more steps than necessary.

A better process should preserve judgment while removing avoidable administrative friction.

PfRs Are Designed to Remove Waste

Proposals for Requestors (PfRs) are a vendor initiated alternative procurement method designed to make structured business offerings available to qualified requestors through a controlled online marketplace.

A PfR is not a public sales pitch. It is not buyer initiated. It is not tailored to one specific requestor. It is an available offering created by a vendor using standardized templates and made discoverable only after access requirements are met.

That difference changes the workflow.

Instead of beginning with a requestor building a custom RFP from scratch, the requestor can discover structured PBM offerings that already exist. Instead of asking every PBM to recreate similar response materials for every opportunity, PBMs can present defined offerings in a consistent format. Instead of delaying comparison until after documents are submitted, requestors can begin comparing relevant fields earlier.

In simple terms, the RFP starts with a custom request.

The PfR starts with structured availability.

That is why PfRs can reduce waste.

A PfR Compresses Discovery Into One Marketplace Step

The “single step” nature of a PfR should be understood carefully.

It does not mean that the entire PBM selection process becomes one click. It does not eliminate contracting, legal review, implementation planning, or expert judgment.

It means the initial discovery step changes.

With a traditional RFP, requestors often need to create a procurement event before they can see what PBMs are prepared to offer. With a PfR, qualified requestors can search, browse, and compare available structured offerings once access requirements are met.

That removes a major front-end burden.

The requestor does not need to start by building a long document. The PBM does not need to start by assembling a custom proposal. Both sides can begin from organized offering data.

From there, serious conversations can happen faster.

AI Helps When the Data Is Structured

Artificial Intelligence (AI) has a practical role in this model, but only if the procurement data is organized first.

AI cannot responsibly replace procurement judgment, legal review, fiduciary responsibility, consultant expertise, or executive decision making. It can assist those functions.

When PBM offerings are structured through templates, AI can help requestors identify relevant options, summarize differences, flag missing information, compare fields, and surface questions that deserve deeper review.

That is different from asking AI to read a pile of inconsistent RFP responses and guess which proposal is best.

The better model is structured data first, AI assistance second, human decision making always.

For Rapid Request, the goal is not to add technology for its own sake. The goal is to remove bloat and cost from PBM procurement so requestors and PBMs can focus more directly on fit, value, and member outcomes.

The Goal Is Not Less Review. It Is Less Waste.

PBM procurement should remain serious.

Pricing, rebates, formularies, networks, specialty pharmacy, mail service, clinical programs, implementation timelines, reporting, guarantees, and audit rights all deserve careful evaluation.

But careful evaluation does not require every opportunity to begin with a long custom RFP.

The traditional PBM RFP process often asks requestors and PBMs to spend too much time proving that a conversation is worth having. PfRs reverse that burden by making available offerings easier to discover and compare before deeper review begins.

That is the core difference.

RFPs are built around a sequence of custom steps.

PfRs are built around structured marketplace discovery.

When a PBM opportunity requires extensive customization, an RFP may still make sense. But when the requestor needs speed, clarity, and a better starting point, PfRs are designed to remove the unnecessary steps that slow the market down.

The future of PBM procurement should not reward the process that creates the most paperwork.

It should reward the process that helps requestors and PBMs identify strong fits faster, reduce waste, and support better pharmacy benefit decisions for members.

For a general procurement overview of how the Request for Proposal (RFP) process is traditionally used, the Chartered Institute of Procurement & Supply provides a helpful explanation.