Your Practice Is a Living Creature. Your Software Had Better Be One Too.
In functional medicine, you already know the patient in front of you is never the same patient twice. Their labs shift. Their protocols evolve. Their needs change with the season. Here’s the part most practice owners haven’t reckoned with yet: the same is true of your practice — and the software underneath it.
I didn’t set out to build a software company. FxMedSupport wasn’t supposed to be anything. It started a decade ago with one medical provider who was drowning operationally — and a hunch that if I could quiet some of the noise around her, her practice would have room to grow.
The drowning had a specific shape. It was repetitive mouse clicks inside her Cerbo EHR. It was her staff leaving Cerbo to do manual tasks somewhere else, then coming back. It was the same three or four minutes spent creating the same Zoom appointment, twenty-five times a week. It was hours of chart prep done the same way, every visit, by hand. None of it was complicated. All of it was eating her practice alive.
So we built two things. The first was an integration into her ecommerce platform — and almost immediately her supplement profit margin jumped eighteen percent. The second was an integration with Zoom — and overnight, the time her staff spent flipping between Cerbo and a browser window evaporated. That was the moment I understood what I was actually building.
In the end, aren’t they all an ask, a wish? “I wish Cerbo did this.” Every tool we’ve ever built started there.
The practice that hired you yesterday is not the practice you run today
This is the part I want to put in front of every owner I talk to. In integrative and functional medicine, you have already accepted — at the clinical level — that your patient is a dynamic creature. Their inflammation profile this quarter is not their inflammation profile last quarter. Their gut, their thyroid, their stress load, their sleep — none of it is fixed. You treat the body as a system that’s in motion. You’d never hand a patient a static, ten-year-old protocol and call it care.
Why, then, do we accept static, ten-year-old software running underneath the practice that delivers that care?
Your business is the same kind of creature your patient is. The volume changes. The visit mix changes. The supplement catalog changes. The staff turns over. The payer landscape moves. The patient expectations move faster than that. A practice in month thirty-six is not the practice you opened in month one — even if the front door looks the same.
This is the line I want you to underline: If you are going to be a medical provider in the integrative and functional space, you are already acknowledging that every single day, your patient is a new dynamic creature. If you are going to rely on medical software to run that practice, your medical software must hold the same underlying principle as you do — adaptive, reactive, continually innovative — or you will be statically and technologically put out of place by your own software.
Static software is not neutral. It is actively pulling you backward.
I want to be careful here. This is not a complaint about Cerbo. Cerbo is the best EHR in functional medicine — always has been, always will be — and everything we build sits on top of it because of that. The point isn’t that any single platform is the problem. The point is that any platform, left frozen in place while the practice around it evolves, becomes a cage.
I’ve watched it happen. A provider opens with a set of workflows that fit her practice perfectly in year one. Year three, she has three providers, a supplement line that’s tripled, a chronic care program she didn’t offer before, and a front-desk team that’s twice the size. The software hasn’t moved. The workflows haven’t moved. Every new thing the practice wants to do has to be bolted on with sticky notes, spreadsheets, and a staff member who “just knows how we do it here.” That is not a software problem. That is a software that stopped evolving alongside its owner.
The discipline of building a creature, not a product
Once I understood what FxMedSupport actually was, the way I built it changed. I stopped trying to ship a finished product. I started trying to grow an organism.
Auto Encounter is a good example. Nobody asked me for Auto Encounter. I noticed, watching that first provider’s workflow, that every time her office manager left Cerbo to set up a Zoom appointment, eventually an encounter was going to be created anyway. So why make her do it twice? Auto Chart Prep is another. I watched the same chart prep get repeated for the same appointment type, visit after visit, and the answer was obvious. Build it once. Let the practice run.
Did anyone explicitly ask for those? No. But aren’t they all an ask? Somewhere, a provider was thinking I wish Cerbo did this automatically. The wish was there before the request was. That’s what it means to build a creature: you build with the assumption that the people you serve are evolving, and your job is to evolve a step ahead of them so they never feel the friction.
Your software must be malleable. Not because malleable is trendy. Because your practice is alive.
What this means for the practice owner reading this
If you take one thing from this piece, take this: when you evaluate the tools running underneath your practice — your EHR, your integrations, your automations, your reporting — stop asking “does this do what I need today?” That is the wrong question. The right question is: does this evolve at the same rate I do?
Because here is the uncomfortable truth. The practice that fails three years from now will not fail because the owner ran out of patients, or out of expertise, or out of heart. It will fail because the operational layer underneath it stopped breathing — and the owner spent so much energy compensating for static software that there was nothing left for the patient. That is a preventable death. It is preventable in the exact same way you prevent it for your patients: with a system that adapts.
That is the entire thesis behind FxMedSupport. Cerbo is the heart of the practice. We are the connective tissue that keeps it adaptive. We optimize, integrate, automate, and leverage what Cerbo already does so that as your practice evolves, the software underneath it evolves with it — quietly, continuously, and on your terms.
Ten years in, I am more convinced of this than I was on day one. The practices that thrive in the next decade will not be the ones with the fanciest stack. They will be the ones whose stack is alive. The ones whose software, like the patient in front of them, is allowed to change.
Build a creature. Not a product. Your practice deserves nothing less.
Kevin Mackey is the founder and CEO of FxMedSupport, the official Cerbo integration and development partner. For a decade, FxMedSupport has built tools, automations, and integrations that extend Cerbo for hundreds of functional, integrative, and hybrid medical practices — turning provider wishes into production software.