You Just Got Rural Health Transformation Money. Don't Spend the Tech Budget on the Wrong People.

If you run a rural hospital, a clinic network, or a community health center — or you're in a state health agency reading project narratives right now — you already know the number. Fifty billion dollars. The Rural Health Transformation Program is real, the first ten billion is moving in 2026, and every state got a slice: somewhere between $147 million and $281 million in year one.

Here's the part that wasn't in the press release. A lot of that money comes with a deadline attached. Reporting to CMS starts in August. Next fiscal year's spending starts in October. States are under genuine pressure to put the first year's funds to work fast and show CMS something that actually worked — because the next round of funding depends on it.

So this isn't a someday conversation. It's a this-quarter one. And a real chunk of that money points straight at technology: health IT, telehealth, cybersecurity, and AI. Which means a lot of people who have never hired a software firm in their lives are about to hire one. This post is for them.

First, the honest part: some of this you should just buy

We've written a whole post on build-versus-buy, and the rule holds here. If what you need is an ambient AI scribe so your clinicians stop charting until 9pm, buy one — there are good ones, and you shouldn't pay anyone to build a custom version. Same with billing-and-coding automation, and same with most of what a modern EHR already does. The 5% cap CMS put on EHR replacement is a hint: this money isn't meant to rebuild commodity software, and neither should you.

If a firm tells you everything should be custom-built, that's a sales pitch. Walk.

The part that's worth building well

But some of what this program funds genuinely doesn't exist off the shelf. The rural technology catalyst fund alone lets states put up to 10% of their award into testing and scaling new, technology-driven solutions for chronic disease — things a vendor has to actually build. Patient-facing tools. Monitoring wired into your specific workflows. AI that does something particular to how care gets delivered in your community, not in general.

That's the spending where the vendor you pick is the whole ballgame. A demo-grade prototype will not survive a federal audit. A tool that breaks the first time the underlying AI model updates will not show CMS the outcomes you promised. Here, getting the builder right matters more than getting the idea right.

Why we'd raise our hand

So, bluntly — here's why we think we're a good place to spend that part of the money.

We've already built one. Clintuition is an AI clinical simulation platform we built: realistic patient encounters, rubric-aligned assessment, used by medical education programs and clinical training environments. It is not a slide deck or a weekend demo. It's a running product that institutions depend on, cohort after cohort, year after year. We built it to be secure, explainable, and defensible — because healthcare is exactly the place where "the AI said so" is not an acceptable answer.

That's the same standard this grant money demands. The real reason a careful firm is worth hiring for an AI project is the unglamorous stuff: knowing when the AI is wrong, keeping it away from data the user shouldn't see, catching it when the model quietly changes underneath you, and leaving an audit trail you can hand a regulator. We've been writing about those failure modes for months — and we build against them every day, on a healthcare AI platform that's live right now.

We're also small and sharp, which on this timeline is a feature, not a caveat. The RHT clock does not wait for a big firm's procurement cycle.

Hold us to the outcomes

One more thing, and we mean it. The smart guidance on this program recommends performance-based contracting — tying what a vendor gets paid to outcomes you can actually measure. Good. We want that. If a software firm flinches when you suggest their payment should depend on the thing working, that flinch is your answer. Write the measurable outcome into the contract. We would rather be held to it than not.

When we're not the firm for you

If your RHT plan is mostly buying equipment, swapping telehealth carts, or standing up a new service line — that's not us, and we'll say so on the first call. If you need a giant systems integrator to wire forty facilities onto a state health information exchange, we'll point you toward one. We're a fit for the custom, AI-shaped, patient- or workflow-facing piece: the part that has to be built, and built to last. Not everything in your plan is that part — and a partner worth hiring will tell you which part is.

The question to sit with

You're about to spend public money, on a deadline, in front of an auditor. Before you pick anyone to build something, ask them one thing: "Show me something you built that's still running, and still trusted, two years later."

If they can, keep talking. If they can't, you already have your answer.