How PBMs Judge RFPs: 12 Hidden Bid/No-Bid Decision Markers Behind PBM Procurement

Pharmacy Benefit Managers (PBMs) do not automatically bid on every Request for Proposal (RFP) they receive.

For organizations new to PBM procurement, this can be easy to overlook. A requestor may assume that if the opportunity is serious, PBMs will naturally want to compete. Sometimes they will. But before a PBM commits to a full proposal response, it usually has to make a bid/no-bid decision.

That decision matters.

For health plans, coalitions, unions, specialty pharmacies, employer groups, procurement teams, and self-funded employers, referred to as requestors moving forward, understanding how PBMs judge RFPs can improve the quality of vendor participation. It can also help requestors design a procurement process that attracts serious, qualified responses rather than quietly discouraging good-fit vendors.

A PBM RFP is not a simple request for a price quote. Responding may require pricing analysis, rebate modeling, network review, specialty pharmacy review, legal input, clinical program validation, implementation planning, reporting commitments, compliance review, and executive approval.

That is a lot of work before a PBM knows whether it will win.

The bid/no-bid decision is how a PBM decides whether the opportunity is worth that investment.

What Is a Bid/No-Bid Decision?

A bid/no-bid decision is the internal process a vendor uses to decide whether to respond to an RFP.

For PBMs, the decision is usually based on a practical question: does this opportunity make enough business sense to justify the effort and risk of responding?

That does not mean PBMs only care about deal size. A PBM may pursue a smaller opportunity if the fit is strong, the requirements are clear, the timeline is realistic, the pricing model works, and the requestor is serious. A PBM may decline a larger opportunity if the requirements are unrealistic, the margin risk is too high, the implementation is too difficult, or the process appears unlikely to lead to a fair comparison.

How PBMs judge RFPs depends on both the opportunity and the process.

A strong opportunity can become less attractive if the RFP is poorly organized. A complex opportunity can still attract strong participation if the goals, data, requirements, and decision criteria are clear.

1. Basic Fit: Is This the Right Kind of Opportunity?

The first question is basic fit.

A PBM may ask whether the requestor’s needs match the PBM’s business model, service capabilities, operational strengths, geographic reach, network approach, clinical programs, pricing structure, and implementation capacity.

For example, one PBM may be a strong fit for a self-funded employer looking for a transparent pass-through model. Another may be better suited for a large health plan with specific formulary, network, or reporting requirements. Another may have strengths in specialty pharmacy, clinical management, or a particular segment of the market.

Fit does not mean the PBM is good or bad.

It means the opportunity matches what the PBM is built to deliver.

If the requestor’s needs do not align with the PBM’s strengths, the PBM may decide not to bid. That can be a responsible decision. A poor-fit proposal wastes time for both sides.

2. Bid Requirements Versus Organizational Exceptions

PBMs also review whether the RFP requirements match what they can actually agree to.

Some RFPs include mandatory requirements. Others include preferred requirements. Some include terms that are negotiable, while others may be treated as pass/fail.

This matters because a PBM may have organizational exceptions. An organizational exception is a requirement the PBM cannot accept as written because of legal, operational, financial, compliance, platform, or service constraints.

Examples might include a specific contract term, an audit requirement, a reporting format, a pricing condition, a network obligation, a service guarantee, or a customization request.

The more mandatory exceptions a PBM sees, the harder the bid decision becomes.

If the PBM believes it cannot meet several core requirements, it may decline rather than submit a response full of caveats. If the PBM believes the requirement can be clarified or negotiated, it may still bid.

Requestors should be clear about which requirements are truly mandatory and which are open to discussion. Treating everything as mandatory can discourage participation.

3. Pricing: Can the PBM Win and Still Make the Contract Work?

Pricing is one of the most important parts of how PBMs judge RFPs.

A PBM has to evaluate whether it can offer competitive pricing while still supporting the contract economically over the full agreement period. That includes administrative fees, rebate guarantees, discount guarantees, specialty pharmacy terms, retail network pricing, mail service terms, performance guarantees, and any required services or customization.

The question is not only, “Can we win?”

The better question is, “Can we win at terms that make sense?”

A PBM may model the potential gain or loss over the contract period. If the RFP requires pricing that is too aggressive, services that are too customized, guarantees that are too risky, or assumptions that do not match the requestor’s data, the PBM may decide not to bid.

This is especially important when the RFP data is incomplete.

If the PBM does not have enough claims data, rebate history, utilization detail, specialty pharmacy information, formulary expectations, or network requirements, it may have to price with assumptions. That increases risk for everyone.

4. Experience: Has the PBM Done This Before?

PBMs also consider whether they have relevant experience for the requestor’s needs.

Experience can include market segment experience, employer size, health plan complexity, union or coalition experience, specialty pharmacy management, clinical program management, reporting requirements, implementation complexity, or similar account structures.

For requestors, this is important because experience reduces uncertainty.

A PBM that has successfully managed similar arrangements may feel more confident bidding. A PBM that lacks experience in a specific requirement may be more cautious.

This does not mean requestors should only choose vendors that look exactly like the incumbent or exactly like prior PBM relationships. It means that experience affects how vendors assess delivery risk.

If the RFP requires a major capability the PBM does not commonly support, that may influence the bid/no-bid decision.

5. Ability to Meet State and Federal Requirements

PBMs also consider whether they can meet applicable state and federal requirements associated with the opportunity.

This area can become complex, and requestors should avoid treating it casually. Depending on the arrangement, PBM services may intersect with requirements related to plan type, geography, reporting, pharmacy access, audit rights, claims administration, transparency, or other regulatory obligations.

The basic point is simple: a PBM needs confidence that it can operate within the requirements that apply to the opportunity.

If the requestor has unique state requirements, multi-state coverage, government-related plan obligations, or special reporting expectations, the PBM will usually need to evaluate those carefully.

A PBM may still bid, but regulatory complexity can affect pricing, staffing, implementation timelines, legal review, and operational commitments.

6. FTE Requirements: How Much Staffing Will the Account Require?

Some RFPs require dedicated or semi-dedicated Full-Time Equivalent (FTE) support.

An FTE requirement may involve account management, reporting, clinical support, implementation support, call center expectations, data analysts, or other service resources.

PBMs need to evaluate whether the account requires additional staffing and whether the economics support that staffing.

If a requestor expects dedicated resources, custom reporting, frequent scorecards, specialized meetings, or high-touch service, the PBM has to account for that work.

This does not mean those requests are unreasonable.

It means they are not free.

FTE requirements can affect the bid/no-bid decision because they change both cost and operational commitment.

7. Formulary Change: Will the Opportunity Require a Different Drug Strategy?

Formulary requirements can also influence whether a PBM bids.

A formulary affects drug coverage, tiering, exclusions, prior authorization, step therapy, rebates, member disruption, and clinical strategy. If a requestor wants a formulary approach that differs significantly from the PBM’s standard model, the PBM has to evaluate whether it can support that change.

Questions may include:

• Does the requestor want a standard formulary or a custom formulary?
• Are there restrictions on exclusions?
• How much disruption is acceptable?
• Are specific drugs or therapeutic classes sensitive?
• How does the formulary affect rebate guarantees?
• Does the requestor require special exception handling?

A formulary change can create operational work, financial impact, and member communication needs. PBMs may still support it, but they need to understand the scope before bidding confidently.

8. Program Change: Are Custom Clinical or Service Programs Required?

PBMs also review whether the RFP requires program changes.

Program changes might include clinical management programs, prior authorization workflows, specialty pharmacy support, adherence initiatives, opioid management, reporting programs, member communication programs, or custom employer initiatives.

Some program changes may be routine. Others may require new workflows, new reporting, new staffing, new technology configuration, or additional vendor coordination.

If the requestor needs significant program customization, the PBM has to decide whether the opportunity justifies the operational work.

Program changes are not automatically bad. They may be necessary for the requestor’s goals. But they should be clearly described, because vague customization requests increase uncertainty and can make PBMs less likely to bid.

9. Platform Change: Does the RFP Require New Technology or Configuration?

Some RFPs create platform questions.

A platform change may involve claims system configuration, data feeds, reporting tools, eligibility files, member portals, mobile tools, integration with other vendors, prior authorization systems, or custom analytics.

PBMs will consider whether the requestor’s requirements fit their existing platform or require material changes.

A requestor may ask for a custom report, a unique file format, a specific dashboard, a special integration, or a new workflow. Each item may seem reasonable on its own. Together, they can create significant implementation and maintenance work.

A PBM may still bid, but if the RFP requires too much custom technology work, the bid becomes more complicated.

Technology customization affects cost, timing, risk, and staffing.

10. Quality Measures and Performance Expectations

PBMs also review quality measures and performance expectations.

Quality measures can include claims accuracy, call center performance, implementation milestones, reporting timeliness, mail service turnaround, member service standards, issue resolution, clinical program performance, or other service commitments.

These measures can be useful, but they need to be clear.

A PBM will look at how performance is measured, what data is used, what remedies apply, how exceptions are handled, and whether the measure is within the PBM’s control.

For example, a service guarantee tied to PBM-controlled claims accuracy may be easier to evaluate than a broad outcome measure influenced by many parties.

The basic rule is this: quality measures should be meaningful, measurable, and tied to the services the PBM can actually manage.

If quality expectations are unclear or unrealistic, the PBM may view the RFP as higher risk.

11. Reporting, Scorecards, and Custom Materials

Reporting requirements can strongly influence the bid/no-bid decision.

Many requestors want regular reporting, executive summaries, savings reports, utilization reports, rebate reports, specialty pharmacy reports, network reports, guarantee reports, and performance scorecards.

That can be reasonable. Reporting helps requestors manage the relationship.

But reporting has a cost.

If the RFP requires custom scorecards, custom meeting materials, unique dashboards, unusual data cuts, or frequent reporting cycles, the PBM has to evaluate whether it can support that work and whether the contract economics justify it.

For PBMs, reporting is not just a document. It may require data extraction, validation, analysis, account management review, and presentation time.

Requestors should be specific about reporting needs, but they should also understand that customization increases response and service burden.

12. Timeline and Implementation Risk

PBMs also judge the timeline.

A short RFP response window may make it hard for the PBM to produce a thoughtful response. A compressed implementation timeline may create member disruption, eligibility issues, data problems, pharmacy transition challenges, or plan setup risk.

PBMs will consider whether the timeline is realistic for the scope of work.

If a requestor wants major formulary changes, network changes, reporting customization, platform configuration, and member communication support, the implementation timeline needs to reflect that complexity.

A timeline that looks aggressive but possible may still attract bids.

A timeline that looks unrealistic may discourage participation.

Why Requestors Should Care About Bid/No-Bid Decisions

Bid/no-bid decisions may sound like an internal PBM concern, but they affect requestors directly.

If a PBM decides not to bid, the requestor may never see an option that could have been a good fit. If several PBMs decline, the requestor may assume the market is limited when the process itself may have discouraged participation.

This is why understanding how PBMs judge RFPs is valuable.

A requestor can improve its chances of strong participation by making the RFP clearer, more organized, more realistic, and more focused on the information that matters.

That does not mean lowering standards.

It means reducing unnecessary friction.

A strong PBM RFP should help qualified PBMs understand the opportunity quickly, decide whether they are a fit, and respond with information that supports fair comparison.

How PfRs Lower the Barrier to Initial PBM Engagement

Proposals for Requestors (PfRs) offer a different way to start the procurement conversation.

A PfR is a vendor initiated procurement method made available through a controlled online marketplace after access requirements are met. It is structured using standardized templates and represents a vendor’s available offering. It is not public sales collateral. It is not buyer initiated. It is not tailored to one specific requestor.

Because PfRs are always available to qualified requestors in the marketplace, PBMs do not have to weigh the risks and rewards of every individual early-stage opportunity before deciding whether to enter a lengthy custom RFP process.

The barrier to initial engagement is lower.

A PBM can structure an available offering once and make it discoverable to qualified requestors. The PBM does not need to build a new custom response just to begin the conversation. The requestor does not need to launch a full custom RFP just to understand which PBM offerings may be a fit.

That changes the sequence.

Traditional RFPs often require PBMs to make a bid/no-bid decision before the requestor has seen much structured information. PfRs allow requestors to review available offerings earlier and focus deeper questions on stronger-fit options.

This does not eliminate the need for careful evaluation. Complex PBM arrangements may still require custom pricing, consultant review, legal review, negotiation, buyer-specific follow-up, and implementation planning.

But PfRs can reduce the amount of early risk on both sides.

PBMs can participate in marketplace discovery without committing to every possible custom RFP. Requestors can compare structured offerings before asking vendors to invest in deeper custom work.

That is a more efficient starting point.

Better Procurement Starts Before the Bid Decision

The bid/no-bid decision is not just a vendor-side gate.

It is a signal.

If qualified PBMs are declining an RFP, the requestor should ask whether the opportunity is clear enough, the data is strong enough, the timeline is realistic enough, and the requirements are focused enough to attract serious participation.

PBMs judge RFPs because they have to protect time, resources, pricing discipline, operational capacity, and implementation quality.

Requestors should understand that reality.

A well-designed PBM procurement process does not make every request easy. It makes the opportunity clear. It explains what matters. It provides the data needed for serious evaluation. It distinguishes mandatory requirements from preferences. It avoids unnecessary customization too early. It gives qualified PBMs a reason to participate.

How PBMs judge RFPs is not a mystery.

They look at fit, economics, requirements, risk, staffing, customization, platform needs, quality expectations, reporting burden, and implementation feasibility.

The more clearly a requestor addresses those issues, the better chance it has of attracting strong PBM participation.

And when a full custom RFP is not the right starting point, PfRs offer a structured alternative that lowers the barrier to initial engagement and helps both sides move toward better-fit conversations sooner.

---

Rapid Request is building a structured marketplace approach to PBM procurement, designed to help qualified requestors review vendor initiated PfRs earlier and reduce the need for every initial opportunity to begin with a heavy custom RFP response.

To understand why this matters, read more about why PBM RFP response burden can reduce vendor participation.