Healthcare Buyer Intelligence

Buyer Intelligence

How Healthcare RFPs Work, and When They Are Already Decided

See when the decisive work happens, whether a bid is still worth pursuing, and how a health system can write a fairer request.

Updated October 6, 2026

The short answer

A healthcare RFP is issued after the organization has decided to buy and now needs to choose defensibly. Responses are scored against weighted criteria agreed before any response arrives, which makes the criteria far more decisive than the responses. Before committing to a bid, compare those requirements with what your company can prove, identify any gaps that cannot be fixed, and decide whether the opportunity is still winnable.

Explained at three levels

1 Plain English

An RFP is a formal request where a hospital tells suppliers what it needs and asks everyone to answer the same questions, so it can compare fairly. The scoring is decided before the answers come in. If the questions favor a competitor, answering well does not fix that.

2 Informed buyer

Not every purchase involves one. Thresholds vary, GPO contracts can remove the need, and a sustainable sole source justification can bypass it. Newer software categories go to formal RFP less often than commodity supplies and capital equipment do.

3 Technical and professional detail

Scoring is typically weighted across functional requirements, technical and integration fit, security and compliance, implementation approach, references, and cost, with weights set in advance. Cost is rarely the largest weight and almost never the only one. Requests for clarification during the response window are usually distributed to all bidders, which is worth knowing before asking a question that reveals your strategy.

The sequence that actually happens

An RFP is the visible part of a longer process.

First a problem gets named internally. Then someone surveys what exists, frequently through an RFI or through informal vendor conversations. Those conversations produce the requirement list. The requirement list becomes the RFP. The RFP gets scored against weights that were set while the requirements were still being written.

So the decisive moment is not the response. It is the requirement-writing conversation, which happened before the document existed.

This is not rigging

It is worth being precise here, because vendors sometimes read this as evidence the process is fixed.

A hospital writing requirements has to get them from somewhere. Nobody on staff is a specialist in every category the organization buys. Talking to vendors is how requirements get informed, and a well-run process talks to several and publishes criteria that any of them could meet.

The process becomes a problem when requirements are written to match one product’s specification sheet rather than the organization’s need. Experienced supply chain teams watch for exactly that, because an RFP that cannot survive being questioned defeats the purpose of running one.

What follows for a vendor

An RFI is not free consulting. It is the clearest opportunity to get a requirement you genuinely meet, and competitors genuinely do not, into the document you will later be scored against. Answer it properly.

Cold responses are low probability. Not zero, and occasionally worth it when the category is genuinely open. But an organization that has never spoken to you before the RFP dropped has already had its requirements shaped by someone else.

Read the weights, not just the questions. Where they are published, they tell you what the organization actually cares about, which is often not what the requirement count suggests.

What follows for a buyer

If you are running the process, two disciplines are worth the effort.

Set the weights before you see responses, and write them down. It is the only thing that makes the eventual decision defensible when a losing vendor asks.

Write requirements from your workflow rather than from a vendor’s feature list. A requirement lifted from a specification sheet narrows the field to one supplier without anyone intending it, and you will not find out until the responses arrive.

For an integrated delivery network, state whether one contract, one implementation, and one standard are expected across every facility. A requirement written around the flagship hospital can produce a winning response that smaller sites cannot use.

What a healthcare marketing RFP needs to define

A healthcare marketing RFP follows the same procurement structure, though its requirements should describe an audience and a business result rather than a software feature list.

State whether the work covers a health system, a specialty clinic, a service line, a payer, or a healthcare technology company. Then define the job. Brand work, patient acquisition, physician referral growth, employer outreach, and product demand need different evidence and different teams.

  • The audience and service area.
  • The result the organization needs to improve.
  • The channels already in use and what the selected company will own.
  • Clinical, legal, privacy, and brand approvals that affect publishing.
  • Access to analytics and the baseline available for measurement.
  • Required team roles and who must attend working meetings.
  • Fee model, media budget, pass-through costs, and contract term.
  • Ownership of accounts, creative files, data, and work in progress at exit.

Do not ask every company for a complete unpaid strategy. Ask for its method, a relevant example, the people who will do the work, and how it would use the information you supplied. The organization should not need speculative campaigns in order to compare capability.

The same scoring rule applies: agree on the weights before proposals arrive. If measurable growth matters most, do not let a beautiful creative presentation quietly become the largest criterion in the room.

Where this goes next

Topics: rfp, procurement, sourcing, buying process

More in Buyer Intelligence