The Three Questions Hospital Procurement Will Ask That Will Kill Your Deal

Question one: who else in our IDN uses this

The first killer question is not about your product. It is about your customer list, and specifically about your customer list inside the buyer's own integrated delivery network.

Hospital procurement does not want to be the first site inside an IDN to deploy a new vendor. They want to know that another facility inside the same corporate parent has already gone through the security review, the integration work, and at least one budget cycle without breaking. If you cannot name that reference, procurement will slow the deal down until you can, or until they can find a competitor who can.

This is the death of most Series A HealthTech deals. The founder has a great pilot at one facility. They cannot yet point to a second site in the same IDN. Procurement stalls. The champion loses momentum. The renewal at the pilot site becomes shakier. The deal never converts to enterprise.

Question two: what happens when our EHR upgrades

The second killer question is about the EHR relationship, and it is designed to expose whether the founder actually understands the platform they are integrating with.

The question is some variant of: what happens to your integration when our EHR vendor pushes a major upgrade. If the founder answers with confidence, that is often a bad sign — because it means they do not know how disruptive those upgrades actually are. The honest answer is that a major EHR upgrade will require re-validation of every third-party integration, and that the burden of that re-validation falls partly on the vendor and partly on the health system.

Procurement is asking this question to find out who is going to eat the cost. If the founder cannot describe a realistic model for handling it, procurement assumes the health system will end up eating it, and prices the deal down accordingly. Or kills it.

Question three: how do you price when we consolidate

The third killer question is about consolidation math. Health systems assume they are going to acquire other facilities, or be acquired themselves, within the contract term. Procurement wants to know what happens to pricing when the covered lives count changes materially.

Most founders have not thought about this. They price per bed, per user, per encounter, or per some other unit that assumes the customer's size is stable. Procurement asks the consolidation question to expose whether the pricing model will punish the health system for growing — and if it will, procurement negotiates aggressive floor pricing upfront.

The founders who survive this question have a pre-built consolidation clause with defined tiers. The founders who do not are forced to negotiate one on the spot, from a weak position.

Why these three

These are not the only questions procurement will ask. But they are the three that most consistently kill deals at the late stage, because they expose a founder's lack of experience with health-system dynamics.

All three can be prepared for. Most founders do not prepare for them because their advisors are ex-SaaS operators who have never sat through a health-system procurement review. If your board and your advisor bench does not include someone who has, you will learn these questions the expensive way, one blown deal at a time.