The Year-One Hospital Sales Checklist Nobody Hands Med Device Startups | NPLUS Global

Selling to a hospital is not selling to a physician's office with more paperwork. It's a multi-stakeholder, multi-budget, multi-quarter process where the person most excited about your device is often the least powerful person in the room. Most first-year failures aren't product failures — they're process failures that show up months after the "yes."

Here's what actually trips up med device startups in year one, organized by where in the sales cycle it bites.

Before You Sign

Map the real buying committee before your first demo. Your clinical champion is not your buyer. Find out who sits on value analysis, who controls capital vs. operating budget, and who has veto power in biomed and IT security — and do it before you've built your whole pitch around one enthusiastic nurse manager. Org charts at hospitals turn over faster than most CRMs reflect, which is part of why data vendors like NPLUS Global exist in the first place — stale contact data is one of the quieter reasons deals stall.

Ask who owns the budget line, in writing. Capital equipment and operating expense approvals run through completely different committees with different timelines. If you don't know which bucket your device falls into, you don't know your actual sales cycle length.

Find out if the hospital is locked into a GPO contract. Group purchasing organization terms can block or slow adoption even when your champion has full authority to say yes. Ask directly, early, rather than discovering it during contracting.

Get IT and biomed in the room before they become a blocker. If your device touches the network, integrates with the EHR, or generates PHI, security review isn't a formality — it can add months. Loop them in during evaluation, not after the contract is signed.

Request the value analysis committee's submission requirements and meeting cadence in writing. Many committees meet monthly or quarterly, not on demand. Missing one cycle can cost you a full quarter.

Build your compliance packet before you need it. FDA clearance documentation, ISO certifications, insurance certificates, and clinical evidence should be assembled and ready to hand over the moment someone asks — not scrambled together under deadline pressure.

Read the contract for pilot-vs-commitment language. A "trial period" with no defined conversion terms or success metrics is not a sale — it's an unpaid evaluation with an exit ramp built in.

During Onboarding

Schedule training with named backups, not just the champion. If the only person trained on your device is the one who advocated for it, you have a single point of failure. Get names of at least two backup users into the training schedule.

Clarify data ownership and integration terms before go-live, not after. Who owns the usage data your device generates? Is it feeding into the EHR, a separate dashboard, or nowhere? Ambiguity here becomes a fight later, usually right around renewal.

Confirm every downstream sign-off your device requires. Sterile processing, pharmacy, infection control — depending on what you sell, one of these groups can quietly stall adoption even after contracting is done. Ask what approvals are still outstanding, not what's already been granted.

Set a 30/60/90-day check-in cadence before you leave the building. Put dates on the calendar, not a vague "we'll follow up." Hospitals are busy enough that "we'll circle back" turns into six months of silence.

Don't let your champion be your only line of communication. Get at least one additional named contact in materials management or clinical operations so you have visibility if your champion changes roles — which happens more often than startups expect.

After the First Delivery

Track actual utilization, not just installation. A device sitting in a supply closet counts as "installed" on your dashboard and as a failed adoption everywhere else. Set up a way to see real usage numbers, even if it's manual for now.

Talk to frontline clinical staff directly, not just your champion. Champions tend to report optimistic summaries. A five-minute conversation with the nurses or techs actually using the device will surface friction your champion may not mention.

Document outcomes as they happen, not at renewal time. Time saved, error rates, patient throughput — whatever your value story is, start capturing it in month one. Reconstructing outcomes data three months before renewal is a scramble that rarely produces convincing numbers.

Watch for champion turnover and have a response ready. If your primary advocate leaves or changes roles, you need a plan to re-establish the relationship immediately, not after you notice adoption quietly dropping.

Flag underuse early instead of waiting for the renewal quarter. If utilization is soft three months in, that's the time to intervene with more training or a workflow adjustment — not something to discover when the contract is up for renewal and it's too late to fix.

Before You Ask for Renewal or Expansion

Start the renewal conversation 90–120 days out, tied to the hospital's fiscal year. Hospital budget cycles are rigid. Showing up with a renewal ask after the budget's already locked is a self-inflicted delay of a full year.

Bring a specific outcomes summary, not a generic case study. Use the utilization and outcomes data you tracked from day one. A one-page, hospital-specific summary is more persuasive than a polished but generic deck.

Only pitch expansion after you've proven the first site. Startups often try to sell system-wide before a single unit has clean adoption data. One strong site with real numbers is a better expansion pitch than five sites with thin evidence.

Re-verify your stakeholder map before the renewal conversation. People change roles constantly in hospital systems. Confirm your champion, your economic buyer, and your committee contacts are all still in the seats you think they're in — don't assume the org chart from twelve months ago still holds.

None of this is exotic. It's mostly discipline — knowing who actually holds power, documenting outcomes as they happen, and not mistaking a signed contract for an adopted product. The startups that struggle in year one usually aren't outsold on the device. They're outlasted by hospital process they didn't map early enough.