The One-Throat-to-Choke Lie: Why Chasing Every Hospital Budget Kills Health Tech Companies Before They Ever Scale

I helped build Bluvision into a real RTLS supplier for Mayo Clinic, and the hardest discipline in that entire run wasn’t landing the account. It was saying no to almost everything Mayo asked us to bolt on afterward.

This is the part nobody writes about. Everyone writes about how hard it is to get in the door at Mayo Clinic, Cleveland Clinic, Kaiser Permanente, Johns Hopkins Medicine, Mass General Brigham, NewYork-Presbyterian, UCLA Health, UCSF Health, Stanford Health Care, Cedars-Sinai, Northwestern Medicine, Penn Medicine, Houston Methodist, Intermountain Health, and Geisinger. Almost nobody writes about what happens after you get in, when the same institution that made you jump through eighteen months of credentialing and validation turns around and asks you to become their asset tracking company, their environmental monitoring company, their nurse call company, and their supply chain company, all at once, for a budget that was only ever sized for one of those things.

Fifteen different markets, fifteen different credentialing systems

Before any strategy conversation matters, the operational reality has to be named plainly. These fifteen systems are not one market. Cleveland Clinic runs vendor credentialing through Symplr. Many other large systems run it through GHX Vendormate or IntelliCentrics. Each platform requires its own profile, its own document uploads, its own fee, typically starting around $600 a year per system, and there is no shared database between them. A rep credentialed at Mayo starts from zero at Cleveland Clinic and starts from zero again at Kaiser.

The buying logic is just as fragmented. Mayo Clinic runs a formal qualification program called Solutions Studio, where digital health vendors go through a structured validation process before a solution ever reaches a clinician. Kaiser Permanente is an integrated payer and provider, so it evaluates technology on total cost of care and population health outcomes, not departmental efficiency alone, because Kaiser absorbs the downstream cost itself. Academic flagships like Johns Hopkins, Penn Medicine, Stanford Health Care, and UCSF Health weigh research sponsorship and publishable validation as heavily as budget approval. Intermountain Health and Geisinger built their reputations on value-based care, so total cost of ownership gets scrutinized harder there than at systems still running fee-for-service. Mass General Brigham and NewYork-Presbyterian are both products of major hospital mergers, meaning a system-level win still has to survive site-by-site clinical sign-off at every legacy campus.

The money mechanics hospitals never explain up front

Every one of these systems draws from two different pools of money, and confusing them is how deals die quietly instead of loudly. Capital budgets fund equipment and infrastructure and are typically set once a year, planned against a fiscal year that starts at different times depending on the institution, and every dollar in that budget competes against things like a new MRI suite or a facility expansion. Operating budgets fund recurring costs like software subscriptions and services, get approved on a shorter cycle, and don’t have to fight a capital committee for a seat at the table. A product priced and packaged as a capital expenditure is choosing to compete against the hospital’s most visible, most politically defended spending decisions. The same product repackaged as a subscription, priced against an operating line, can move through approval in a fraction of the time.

Layered on top of that is the group purchasing organization system. Vizient, Premier, and HealthTrust negotiate standardized contracts on behalf of member hospitals, and a huge share of hospital purchasing runs through GPO-negotiated pricing. Getting onto a GPO contract can shorten future price negotiations and lend credibility, but it typically takes six to twelve months to execute, and being on the contract does not obligate a single member hospital to actually buy from you. Chasing a GPO contract too early, before you have a handful of reference accounts that prove the product works, is a slow, expensive way to buy a piece of paper that doesn’t generate revenue by itself.

That’s the terrain. Now here’s the strategy for actually operating in it without going broke.

Design the product for one department’s metric, not the hospital’s mission statement

Every pitch deck in this category opens with a slide about “transforming the patient experience” or “digitizing the modern hospital.” Throw that slide away. Nobody signs a purchase order against a mission statement. Somebody signs it against a number they’re personally accountable for.

Design the first version of the product around one metric owned by one department. Biomedical engineering is measured on equipment uptime and survey readiness. Nursing operations is measured on time lost searching for equipment. Infection prevention is measured on compliance rates tied to hand hygiene and hospital-acquired infection reduction. Supply chain is measured on capital avoidance, meaning fewer units purchased because utilization improved. Pick one. Build the product to move that number, prove it moves in a pilot, and resist every temptation to widen scope before that number is nailed down cold.

Find the beachhead, not the hospital

The beachhead is never “Mayo Clinic.” It’s one unit, one department, one budget owner inside Mayo Clinic who can authorize a pilot without three committees. At Bluvision, the wedge into large systems was never a platform pitch. It was a narrow, provable use case, tracked against one metric a single department already owned, that could be piloted in one unit before anyone talked about hospital-wide rollout. Land the department. Prove the number. Let the department champion pull you into the next department, rather than you pushing a platform story into a budget that doesn’t exist yet.

Mayo’s own Solutions Studio model validates this instinct from the buyer’s side. Vendors go through a rigorous qualification on a specific, narrow claim before Mayo lets them anywhere near a broader rollout. Mayo doesn’t onboard a company as “our operational intelligence platform.” It qualifies a specific solution against a specific validated use, then expands access once that use is proven. Build your go-to-market to mirror that logic instead of fighting it.

The pilot graveyard, and how to avoid it

Nearly every one of these fifteen systems runs some form of innovation center, and every one of those centers will happily run a pilot with you. That is not the same thing as a sale, and confusing the two is one of the most common ways vendors burn a year of runway for nothing. Innovation offices are frequently funded from a separate discretionary pool, exist to generate goodwill and headlines, and often lack the authority to convert a successful pilot into an enterprise purchase order. You can get glowing feedback, a case study, even a quote from a chief innovation officer, and still walk away with zero revenue, because the group that ran the pilot was never the group that controls the budget.

There’s an internal discipline problem hiding inside this too. A lot of your own sales team will report a pilot as a win, because getting an innovation office to say yes feels like closing the deal, and their incentives often reward activity over accuracy. As the leader, tracking the true stage of every account, not the stage your rep believes it’s in, is your job, because every month spent treating a pilot as a sale is a month your real cost of sale is quietly climbing while the pipeline looks healthy on paper. A lot of reps in this space also carry more confidence about the product than they’ve earned. Being persuasive in a room is not the same as understanding what the product actually does clinically or technically, and a rep who oversells that expertise to a CMO or CNO can cost you credibility you don’t get back.

Dealing with the CMO and CNO is necessary, and it is genuinely political

At some point in almost every one of these deals, the conversation reaches the Chief Medical Officer or Chief Nursing Officer, and this is where a lot of technically sound companies stumble, because it stops being a product conversation and becomes a relationship with a person who has an agenda that isn’t only about your metric. These are senior physicians and nurses who got to that chair through decades of clinical practice, politics, and institutional standing, and they will evaluate you partly on merit and partly on how you make them look internally.

At research and teaching hospitals especially, a CMO or physician sponsor will often want your deployment structured as a formal research study rather than an operational rollout. That instinct comes from real incentives: publication and grant activity drive academic promotion, and a study built around your product can generate peer-reviewed validation no marketing claim can buy. It’s also slower, because it now runs through an institutional review board, and the terms of what data you can access and when you can talk about results are no longer fully in your control.

Intellectual property comes up more often than outsiders expect. Some clinical sponsors will push to co-invent, request patent rights on a workflow they helped shape, or ask for enough customization that the result functionally becomes their own protocol wearing your product’s name. Decide in advance what’s negotiable, generally credit and co-authorship on clinical findings, and what isn’t, generally ownership of your core technology, and hold that line consistently across every account.

Almost every institution will tell you their patient population, their workflow, or their clinical protocol is unique, and roughly nine times out of ten that claim is more about protecting turf and justifying a custom deal than a real technical difference. The other one time out of ten, they’re right, and a team with genuine clinical fluency on staff is the only way to tell the difference in real time.

Some leaders are followers who move only once Mayo or Johns Hopkins already has. Others want to be first, and telling them you already deployed the same thing down the street can kill the deal on the spot.

Read which type is in the room before you decide whether your pitch leads with social proof or with exclusivity. The single best defense against all of this is having credible subject matter experts inside your own company, not just on an advisory board slide. A known, practicing or recently practicing nurse or physician on staff can sit across the table from a CMO or CNO as a peer, not a vendor, and that changes the entire tone of the conversation. They can push back credibly on an inflated uniqueness claim, translate clinical workflow into product requirements without losing nuance, and navigate an IRB conversation or a co-authorship request with fluency no amount of commercial polish can substitute for.

The one-throat-to-choke request is a margin trap, and you need to know when to say no

Once you’re in, the same procurement logic that made the sale so hard now works against you in a different way. Hospitals hate managing dozens of point vendors, so the instinct on their side is to ask the vendor who already earned trust in one area to expand into adjacent ones. It feels like a growth opportunity. It is usually a trap, for one structural reason: hospital budgets are siloed by department, and “can you also cover X” rarely comes with new budget attached.

Every dollar and every engineering hour spent building a feature for one system’s one-off ask is a dollar and an hour not spent making your core product better for the next fifty systems on your list. That’s the real cost, and it’s invisible until you look up two years later and realize your roadmap is a patchwork of one-off asks from three hospitals instead of a product that scales to three hundred. This is death by a thousand paper cuts, and it kills more healthcare IoT companies than any competitor does.

The discipline is simple to state and hard to hold: expand scope only when new budget and a new named champion come with it. If a hospital wants you to become their one-stop shop, quote it as a new statement of work with new pricing, tied to a new department’s metric, evaluated on its own merits. Never let scope creep ride in on the goodwill of the original contract.

The gate nobody warns you about

Vendor credentialing gets you through the front door. It says nothing about whether your device is allowed on the hospital’s network, and that’s a separate, slower, and far less forgiving review. Any connected device or platform touching a hospital’s infrastructure has to pass a cybersecurity and data governance review run out of the CISO’s office, a completely different department from supply chain and completely disconnected from whichever clinical champion has been championing you internally. That review typically wants a network segmentation plan, a data flow diagram, and increasingly a HITRUST CSF or SOC 2 Type II attestation before they’ll sign off. If the product is medical device adjacent, FDA premarket cybersecurity expectations can enter the conversation too.

None of this is disclosed up front, and it doesn’t run on the same clock as the clinical pilot. Build the security package before you need it, not after IT asks for it, because by the time they ask, the champion who fought to get you in the room has already started losing patience.

Best practices for onboarding

Pre-credential ahead of the sales cycle, not during it. Know which platform your target system uses, whether that’s Symplr, Vendormate, or IntelliCentrics, before you’re in front of a buyer, so credentialing never becomes the reason a deal stalls in month four.

Identify the clinical or operational champion before you pitch, not after. That person needs to already care about the metric you move, because you cannot manufacture urgency around a number nobody in the room is accountable for.

Map the procurement calendar early. Capital budgets at most systems are set annually, and missing that window by even a few weeks can push a deal a full year, regardless of how strong the pilot data looks.

Best practices for managing the relationship

Assign one named integration owner on your side for each account. Hospitals do not want to re-explain their environment to a rotating cast of account managers, and every re-explanation is a chance for the relationship to cool.

Treat renewal and expansion as two separate motions with two separate business cases. Bundling them trains the customer to expect free scope every time a contract comes up for renewal.

Track opportunity cost explicitly. Every time an account asks for something outside the core product, run the math on what else that engineering time could build before agreeing, and say no more often than feels comfortable.

Best practices for delivering and proving value

Instrument the one metric you promised to move, and report on it relentlessly. A quarterly value report tied directly to the department’s own KPI language is the single most effective tool for expansion, because it hands your internal champion the exact ammunition they need to go ask their own leadership for more budget.

Let the customer pull you into the next department. The fastest, cheapest, highest-trust expansion inside any of these systems comes from one department champion telling another department “you need to see what this did for us,” not from your sales team cold-pitching a platform story to a stranger three floors up.

The EHR is the real gatekeeper, and it isn’t optional

Almost every strategy conversation about hospital IoT eventually runs into the same wall: the electronic health record. Epic now holds roughly 44 percent of the acute care hospital market and close to 57 percent of hospital beds, and its dominance is even heavier among the exact institutions on this list. Mayo Clinic, Cleveland Clinic, Kaiser Permanente, Johns Hopkins, Stanford Health Care, and NewYork-Presbyterian all run Epic as their core clinical system, and Intermountain Health is in the process of moving to it as well. A smaller group runs Oracle Health, built on what used to be Cerner, and that customer base has been visibly less stable, with KLAS reporting rising dissatisfaction since the Oracle acquisition.

For a product team, this concentration is both a shortcut and a trap. It’s a shortcut because one deep, well-maintained integration to Epic covers a huge share of the addressable market in one motion. It’s a trap because that integration work is its own project, entirely separate from the hospital sales relationship. The difference between building against Epic’s modern FHIR APIs versus an older HL7v2 interface engine can be the difference between an integration that takes a few weeks and one that requires a dedicated systems integration engagement lasting months.

How a CPO designs for this market

CPO stands for Chief Product Officer, the executive responsible for what gets built, in what order, and why, as distinct from the CTO, who is responsible for how it gets built and run. Most product leaders coming out of consumer or general enterprise software design for breadth first and depth second. That instinct will bankrupt a healthcare IoT company. A CPO operating in this sector has to design for depth first, inside one department’s workflow, and treat breadth as something earned module by module.

Build the product in modules mapped to buyers, not to features. A biomedical engineering module, a nursing operations module, and an infection prevention module are three different products wearing the same core platform underneath, because they solve for three different metrics owned by three different budget holders. Price each module against the value it delivers to its specific department, not as an add-on line to a master contract.

Treat compliance and core integration as infrastructure you build once and reuse everywhere. What should never be standardized is the workflow layer, because a nurse’s search behavior for a missing infusion pump looks different at Northwestern Medicine than it does at Houston Methodist. Resist the instinct to chase every clinical department that shows interest during a pilot. A CPO’s real job in this sector is triage.

How a CTO executes without drowning in technical debt

The CTO’s job is to make sure the CPO’s module-by-module strategy is technically possible without every new hospital integration turning into a bespoke fork of the codebase. That means building one hardened core, with configuration at the edges, from day one. The moment a hospital-specific ask requires a code branch instead of a config change, that’s the moment technical debt starts compounding, and in this industry compounding debt shows up two years later as an outage during a Joint Commission survey.

Plan execution around the hospital’s calendar, not your sprint calendar. Most large systems run IT change freezes around EHR upgrades, survey windows, and flu season. Instrument technical debt the same way you’d instrument uptime, with a number leadership actually looks at.

Build reliability into the product like biomedical engineering builds it into a ventilator, because that’s the standard hospitals will judge you against whether you like it or not.

How to budget and control capital while building for this market

Everything described in this article happens on the hospital’s clock, not yours. The single biggest capital mistake a company makes in this sector is modeling its runway on a generic B2B sales cycle instead of the real one. A twelve to eighteen month gap between first pilot conversation and signed purchase order is normal here, not a worst case. Model the real cycle, then add a buffer on top of it.

Hardware changes the capital math again: non-recurring engineering costs for FCC and UL certification, inventory built ahead of confirmed demand, and field service costs that show up the moment a pilot goes live, months before any revenue does. Accounts receivable is its own drag, since invoicing is often tied to internal milestone sign-off from a committee, not your delivery date, and sixty to one hundred twenty day payment cycles are common even after a deal is fully signed.

Concentration risk deserves its own line in the capital plan. A marquee logo can consume a wildly disproportionate share of engineering time and working capital relative to the revenue it generates in year one. Capital discipline means capping how much of the balance sheet any single account is allowed to absorb before a second, independent account proves the model is repeatable. One logo, however prestigious, is a reference case. It is not a business model.

Finally, budget the compliance treadmill as a recurring operating cost, not a one-time setup fee. Credentialing renewals, security re-attestation, and the ongoing cost of maintaining HITRUST or SOC 2 status scale with the number of accounts and the number of field reps touching each one. Fund the core platform with equity capital, and push hospital-specific customization work into billable services revenue whenever the deal allows it, so growth capital isn’t quietly spent building one-off features for one account’s convenience.

Where this playbook comes from

None of this is theoretical for me. I co-founded Bluvision, and after HID Global acquired the company in 2016, I spent years inside HID as VP of Product for IoT and Healthcare, running a large, revenue-significant global portfolio that included the RTLS and asset-tracking lines built on what Bluvision started. That gave me a view most operators in this space never get: a firsthand education in what it actually takes for a strong IoT product line to reach its full potential once it becomes one piece of a much larger organization, where sales structure, integration complexity, and competing priorities shape the outcome as much as the technology itself.

That background is why this article isn’t written from the outside looking in at healthcare IoT. It’s written from having sat in the room during Mayo’s qualification process, having managed the aftermath of a hospital asking for more than a contract was ever sized to cover, and having seen firsthand what it takes to keep a strong product line performing as it scales inside a larger organization. JHG exists to bring that operator-level pattern recognition to founders, CPOs, and CTOs building in this space now, whether that means fractional product and technology leadership while a team is still finding its footing, or identifying underleveraged technology inside a larger organization and helping it reach a market it hasn’t fully captured yet.

The takeaway

Getting into Mayo Clinic proved the technology worked. Staying disciplined about what we said yes to after that is what kept the business from collapsing under its own ambition. The companies that win in this sector long term are not the ones that say yes to becoming the one-stop shop every hospital procurement officer wishes existed. They’re the ones with the discipline to own one narrow, provable thing at a time, expand only when the budget and the champion are real, and let the math, not the flattery of being asked to do more, decide what gets built next.