Pricing that scales as you deploy, not before.
AnyBio pricing has two parts: a platform fee for the compliance infrastructure you run on, and usage that scales with how much you actually deploy. You pay for the foundation and for what you use, so the cost grows with your program instead of capping it.
The foundation that has to exist before patient one.
The platform fee covers the part that has to exist before a single patient is monitored: the compliance foundation, the governed environment, the processor-of-record role, the audit and the BAAs.
Scales with what you actually deploy.
Usage scales with real deployment, so a first program of a few hundred patients and a full deployment of tens of thousands run on the same rails. You pay in proportion to what you're actually running, so the infrastructure grows with you rather than forcing a new build at each stage.
It comes out of a code you already bill.
Remote monitoring pays through two kinds of code, and they fund different things. Knowing which one covers infrastructure is the fastest way to know what this should cost you.
CPT 99454 and 99445 pay for supplying a connected device and transmitting the data, roughly $52 per patient per 30 days at the Medicare national average. This is a practice-expense code: no staff-time requirement, no minute thresholds.
You can't bill it without a layer that does the transmission. That layer is what AnyBio is, and it costs a fraction of the code. The rest stays with you.
CPT 99457, 99470 and 99458 pay for your clinical staff's time with the patient, including interactive communication. This is where the labour money is.
None of this is ours, and we don't want it. We don't bill, and we never substitute for the time you bill. CMS's proposed 2027 rule requires it to come from a direct employee of your practice. What we change is how many patients one clinician can carry to that threshold.
Figures are Medicare national averages and vary by locality; Medicaid and commercial rates differ. The 2027 changes are proposed, not final.
From working session to a number.
We walk through your program.
Your monitoring footprint or your first deployment, your team's workflow, and what proving prevention looks like for your risk pool.
Pricing for your actual program.
The platform fee plus usage at your scale, whether that's agents on the monitoring you already run or a first deployment from the device catalog.
Same rails as the pilot.
A pilot and a full deployment run on the same rails, so the pricing model doesn't change as you scale; the numbers follow the program.
Why we don't publish a number here.
What you pay depends on what you're deploying and at what scale, so a single sticker price would be misleading. We'd rather understand your program and show you exactly what it looks like for you. That's part of what the working session is for.
Talk to us about pricing for your program.
