Today we turn off the lights.

Not on a company. Not on a promise. On a piece of software — an application that carried this industry on its back for a decade in production, and fourteen years from its first line of code, and has earned the right to rest.

On Monday, August 24, 2026, the last of our customers completed their migration off our legacy platform. Every account. Every claim. Every patient record. Every workflow that a business owner built inside our walls because they trusted us enough to run their livelihood on it. And now, we power it down for good.

I did not expect to feel this the way I feel it. I've spent thirty years in healthcare and I am not a sentimental man about technology. But this one is different. This one started in my garage.

The Garage

In 2012 there was no company. There was a garage, a Microsoft Access database, and a conviction that the durable medical equipment industry deserved better than what it was being sold. I had spent my career on the payer side, in audit, in managed care, in hospital finance — I had seen exactly how the money moved and exactly where providers got left holding the bag. I knew the industry was being handed software that was built for billing companies, not for the people actually delivering equipment to patients who needed it to live.

So we built something else.

We built it slowly. We built it wrong a few times. We built it with money we didn't have, on nights and weekends that belonged to our families.

In 2016, four years into development, BFLOW® Solutions, Inc. became a real company with a real product and real customers who had every reason to choose a safer vendor and chose us anyway. Ten years in production. Fourteen years from the first line of code to today.

And somewhere along the way, that thing from the garage became a legend in this industry.

I don't use that word loosely. Legacy BFLOW® was a rock-solid business management and business development platform for the DME and HME space. It billed billions in claims. It kept the lights on for hundreds of businesses. It caught errors that would have sunk companies. It gave owners visibility into their revenue cycle that they had never had in their working lives. It did the unglamorous, load-bearing work — day after day, year after year — and it did it without asterisks.

That chapter is now closed.

To My Team

I want to name the people who carried this.

Vishal carried the legacy platform for fourteen years. I don't think our customers have ever fully understood what that meant. It meant two servers he would not let another soul touch, because if something went wrong, he was the one who was responsible — and he never once tried to be less responsible. It meant no true day off in fourteen years. It meant building the inventory system, the point of sale, the rentals, the refills, the entire claims engine, in an era before there was any AI to lean on — just him, the documentation, and long nights nobody watched.

And when I came to him and said we should tear it all down and rebuild it with AI, he told me no. He was ready to walk away from the whole idea. I called him on weekends. I called him in the middle of the night. I nagged him until he gave in an inch at a time. What finally convinced him wasn't me — it was standing at a trade show watching people look at the new platform and say this is impressive. Between the two of us, there are something on the order of a hundred thousand commits behind this company. Vishal, thank you. You built the thing we are retiring today, and then you had the courage to help me replace it.

Salman is unbreakable. During the migration he took every onboarding call, every angry call, every call I did not want to walk into — and he walked into all of them and came out with customers who felt heard. He got people excited about new software on days when the software was not yet cooperating. There is no version of this migration that succeeds without him holding the line while the rest of us were heads-down in the code.

Jeffrey is the modern-day architect of this platform. Vishal and I knew what we wanted to build. We did not know how to get it from a prototype to a production system that the modern world would recognize. Jeff did. He brought the infrastructure, the deployment discipline, and the engineering standards that took us out of the stone ages and into how software is actually built and shipped today. BFLOW® 10 does not exist without him.

And to our RCM, billing, and collections team — you absorbed the chaos on behalf of our customers so their cash kept moving. Thank you.

To every engineer, support rep, implementation specialist, and salesperson who has passed through this company over fourteen years and left their fingerprints on it: some of what you built is being retired today, and I want you to know it mattered. It fed families. It saved businesses. That doesn't disappear when the servers go quiet.

To Our Customers

Now the part I actually sat down to write.

Thank you.

Thank you to the ones who believed in us before there was much to believe in. Thank you to the ones who took a chance on a small company because you liked what we stood for more than you liked what the big vendors were selling.

And there has to be a first. Ours was At Home Medical.

Gary and Bennet Krantz did not buy software from us. There was barely software to buy. They invested in a vision — a vision held by a guy working out of his garage with a whiteboard full of ideas about what DME technology ought to be. They took that risk when no one else had, when there was no track record to point to, no customer list to reference, and every reason to go with a safer name.

All these years later, they are still with us. Still supporting the vision. Still here as we turn the page into what comes next.

Gary, Bennet — thank you for believing in us. There is no version of this story where the two of you aren't on the first page of it.

Thank you to the ones who left — and came back. That took humility on your part and it gave us a second chance we had not earned. We have not forgotten it.

Thank you to the ones who forgave our errors. And there were errors. We have never been the company that pretends otherwise. We broke things. We missed deadlines. We shipped fixes that created new problems. Every time, you had the option to walk, and every time, enough of you stayed and told us the truth instead. That is the only reason we're still here.

Thank you to our perfectionists — and you know who you are. The ones who send the detailed emails. The ones who find the edge case at 6:00 AM. The ones who will not let a rounding error go.

I want to be specific about this, because it is the thing I've reflected on most in the last few weeks. Two weeks ago I sat down in the new system and thought, this doesn't line up yet. This week I sat down in the same system and it does. That did not happen because we are clever. It happened because our toughest customers refused to let anything slide, and every one of those relentless, exhausting, unrelenting notes made the product better. You have been quality-assuring this platform on our behalf, and you have been doing it out of love for your own businesses and your own patients. Your input, your guidance, your patience, your resolve, and your loyalty built the thing we are retiring today, just as surely as any line of code we wrote.

And thank you to every one of you who celebrated our wins with us like they were your own. In a vendor relationship that is rare. In this industry it is nearly unheard of. We do not take it for granted.

Chapter Five

So what happens now?

Here is the honest answer, in the spirit of the way we have always tried to talk to you.

The new platform is not perfect. It is not yet exceptional. It is in its infancy. It will have rough edges that the old system had sanded down over a decade of daily use, and some of you are going to find them before we do. We are not going to stand up here and tell you that everything is flawless on day one, because you would know we were lying and you would be right.

What I will tell you is this: the old platform had reached its limits. Not its usefulness — its limits. There was a ceiling on what we could build inside it, and we hit that ceiling, and we made the decision that the harder road was the honest one. So we started over, and we brought all of you with us.

Most companies our industry's size cannot do what we just did. They have investors sitting on top of them, install bases too large to move, and layers of process that make a rebuild unthinkable. We were small enough to change — and disciplined enough to actually do it. That is not a weakness we're apologizing for. In this moment, it was our single greatest advantage, and we used it.

What sits in front of us now is not a better version of the last fourteen years. It is a new frontier. New architecture. New capabilities. A new vision for what this industry's technology is allowed to be.

This is Chapter Five. And in this chapter, we are not the scrappy alternative anymore. We are the thought leaders. We are the innovators. We are the team pushing the boundaries of what healthcare technology can do for the people doing the actual work of caring for patients.

We did not get here by being clever. We got here on the blood, sweat, and tears of fourteen years of building something rock solid — and on the backs of customers who refused to let us settle.

Today is a day worth remembering. We are retiring a legend, an old friend, and a faithful servant of this industry.

To all of our supporters, all who believed in us, all who worked alongside us, all who forgave us, and all who celebrated with us —

Thank you. From the bottom of my heart.

God bless every one of you.