From a good pilot to a Value Analysis package

Tell me if this sounds familiar - you feel like you've had a successful pilot, the champion is happy and the clinical data looks strong. Someone on the hospital side says the next step is value analysis, and the room gets quiet. Everyone nods like that is a paperwork step. It is not.

In my experience, that is the moment a lot of companies discover that, while they have strong clinical interest, they're completely unprepared to navigate the Value Analysis Committee. The pilot proved the product can work in one setting with one motivated user. The committee is being asked to approve spend, workflow change, and risk for the institution. Those are different jobs.

This is the Adoption Gap in its most concrete form. Product-market fit in MedTech is not the same as in B2B SaaS. A hospital can like the product and still refuse to buy it. If the committee will not approve it, you do not have fit yet, no matter how strong the early cases look.

What the committee is actually doing

Value Analysis is a formal, multi-disciplinary review. The group is usually some mix of supply chain, finance, clinicians, quality, and operations, sometimes with IT or clinical engineering in the room. They are conservative by design. They care about total cost of care, not only unit price. They want clinical evidence, safety, real-world outcomes, and a clear argument for why this is better than what they already have, including the cost of switching.

The process often takes three to nine months, sometimes longer. Requests for more data are normal. A no is common, and it can be sticky. You do not get unlimited retries with the same thin package.

That is why clinical enthusiasm from the pilot champion is such a poor predictor of approval. The champion is answering “does this help me do the case?” The committee is answering “can we defend this purchase, this workflow change, and this ongoing cost?” If you only prepared for the first question, you will feel the second one as delay.

The path is shorter if you pick the right first site

The mistake I see most often is treating the first VAC submission as a volume play. Teams pick the biggest logo, or the system that would look good on a slide, and then invent the package under deadline.

I would start somewhere more manageable. Use the account where you already have a real clinical relationship and honest access to how that hospital buys. Before you write anything, ask the champion who else has to say yes, what the last similar product had to submit, how long review usually takes, and what killed the last request that looked a lot like yours. You can learn more in two of those conversations than in another month of polishing slides.

You also need a map of the buying group, not just the user. The end user cares about performance and workflow. Supply chain and finance care about budget impact, contract terms, and total cost. IT and operations care about integration, training load, and disruption. An executive sponsor cares whether this lines up with quality goals or service-line priorities. Department managers can slow you down even when they cannot sign. If you only stay close to the person who ran the pilot, you will meet the rest of them for the first time inside the review.

Build the package from the pilots you already have

Most teams do not lack data. They lack the right data, organized for a buyer who is not the investigator.

During the pilot you probably captured clinical performance. What usually never got written down is the operational and economic residue: minutes added or removed from a case, extra staff required, length of stay, complication or rework rates, wasted consumables, time to get a new user productive. Those numbers do not need to be a published health-economic model on the first pass. They do need sources, a baseline, and an honest statement of what you measured versus what you inferred.

Before you chase a new study, separate three piles:

1. What you can pull from current sites if you go back and collect it properly.
2. What you can only get from the next implementation if you instrument it now.
3. What you will not have in time for this committee and should not pretend you have.

I would rather see a short, sourced package with clear gaps than a long deck that treats directional estimates as proof. Committees notice the difference. So do the people inside the hospital who have to defend you after you leave the room.

What belongs in the first formal package

There is no universal template. Hospitals vary. The first package still needs to answer the same handful of questions in language a non-specialist can follow.

• Regulatory status and labeled use, bounded tightly. If the committee’s intended use sits outside what you can claim, say so early.
• Clinical evidence matched to the use they would actually buy, not every study you have ever run.
• Outcomes from real use that touch cost and operations, even if the sample is small, with methods visible.
• Implementation burden: training, IT, sterile processing, storage, support, who owns what after go-live.
• A comparison to the current alternative that includes switching cost, not only device price.
• A two-page briefing for people who will not read the appendix. If finance and supply chain cannot repeat your argument without you in the room, the package is not done.
• Treat that first submission as a learning cycle. Capture every question they asked, every document they requested, and every place they stalled. The goal of package one is not a perfect win rate. It is to stop building the argument from scratch on the next account.

Where teams get stuck

A few patterns show up so often I now look for them.

• Evidence collection stayed almost entirely clinical. The team has sensitivity and specificity, or a case series, and almost nothing on time, labor, or avoided cost.
• Every new opportunity restarts the research. Nobody owns a reusable set of claims, sources, and exhibits.
• VAC work lives in hallway conversations. There is no named owner, no date for a first formal package, and no list of what that hospital actually requires.
• The economic story is still a clinical story with a price slide attached.
• The process looks interesting but delayed for months. That delay is usually an unresolved issue in budget, authority, workflow, or evidence, not a scheduling problem.

When I see several of those at once, I tell teams to pause the hunt for the next logo and finish one complete package against a real committee calendar. Adding pilots on top of an empty commercial file makes the Adoption Gap wider.

How to tell you are actually moving

You do not need widespread approvals before you can say the path is working. A few signals are enough.

• You can describe the typical review process, timeline, and decision-makers at your priority accounts without guessing.
• You have written health-economic language for the committee, not only for clinicians.
• You have one formal package assembled for a hospital where the clinical relationship is real.
• You know which evidence gaps matter for the next twelve to eighteen months, and you are collecting against that list on live sites.
• Someone other than the founder can explain the economic case without inventing it in the meeting.

If those are missing, more pipeline will not fix it. The committee will keep asking for the same things you did not build.

A successful pilot is still an invitation. The commercial event is whether a hospital can approve the product, install it without heroics, and defend the spend. That is the work sitting between the last case and the first real purchase order.

If you want a structured read on where the gaps are before you assemble that first package, the free 7-Lever Self-Assessment is the starting point we use with teams in this exact spot. It will not write the submission for you. It will show you which parts of the commercial foundation are still missing. If you want to walk through the results and the first-account plan with us, click the Book a Call button to schedule a 30-minute strategy conversation.