I want to start with a confession, because I think it explains why I'm qualified to write this and also why I'm slightly bitter.
In 2019 I signed a four-year contract for a DME platform after a 45-minute demo. Forty-five minutes. I'd spent longer picking out a delivery van. The salesperson was lovely, the slides were clean, and I was so tired of our old system that I basically wanted someone to tell me the pain would stop.
It did not stop. It relocated.
Since then I've sat through more software demos than I care to count — some for my own company, a lot more as a favor to other owners in the region who call me and say "hey, you've done this, can you sit in?" Somewhere around demo number nine I started keeping actual notes instead of vibes. This list is those notes, cleaned up, with the swearing removed.
A few ground rules before we get into it:
I'm not ranking these on feature count. Every platform on this list has a feature checklist that will make your eyes glaze over by row 40. Feature lists don't tell you whether your intake coordinator can get through 60 orders on a Tuesday without crying.
I care a lot about the delivery side. That's where I've watched the most money quietly evaporate. A missed signature is a denied claim four weeks later, and by then nobody remembers what happened.
Your mileage will vary. A 12-person respiratory shop and a 300-employee multi-state operation have almost nothing in common operationally. I'll flag who each of these actually fits.
Okay. Let's go.
1. NikoHealth
I'll put my cards on the table: this is the one I'd pick if I were starting a DME company tomorrow, and it's the one I most often tell people to look at when they call me frustrated with a legacy system.
The reason is boring and it's the best reason: it was built recently, by people who clearly watched somebody do this job.
That sounds like marketing fluff until you've used the alternative. A lot of DME software in this industry was architected when Bush was president, and it shows in ways that are hard to articulate on a feature grid but obvious within ten minutes of using it — nine clicks to do a thing that should take two, screens that only make sense if you already know what the database looks like underneath, a "modern UI" that turns out to be a web wrapper around a 2006 client-server app.
NikoHealth doesn't have that problem. Intake, documentation, inventory, billing, and delivery live in one place and actually talk to each other. My favorite specific thing: the delivery workflow is genuinely built for delivery, not bolted on. Drivers get a real mobile experience, signatures and delivery confirmations attach to the order automatically, and the proof of delivery is where it needs to be when billing goes looking for it. If you've ever chased a driver's paper route sheet across three days, you know exactly why I'm excited about something this unglamorous. Their breakdown of hme delivery management is worth reading even if you never buy the thing — it's a decent framework for auditing your own process.
The other honest reason it's first: onboarding didn't take a year. Every legacy migration horror story I've heard involves a nine-to-eighteen month implementation where the vendor's team disappears at month four. The implementations I've seen on this side were measured in weeks, and the people running them answered email.
Who it's for: Small-to-mid DME/HME providers who want one system instead of four, and larger operations who've finally accepted that their current platform isn't going to modernize on its own. If you're specifically comparing against an older incumbent, they've got a straight-up DME Works comparison that's less spin than you'd expect from a vendor page.
What I'd push on in a demo: Ask them to walk your actual payer mix through billing. Ask for a real driver's-eye view of the mobile app, not a screenshot. Ask what happens when a delivery fails and needs to be rescheduled — that edge case tells you a lot.
The catch: If your operation depends on some deeply custom homegrown workflow you've built over 15 years, you're going to have to give some of it up. Honestly, in most cases I've seen, that's a feature. But it's a real conversation to have.
2. Brightree
The big one. If you've been in DME for more than a week you've heard the name, and there's a reason: enormous install base, deep payer connectivity, an ecosystem of integrations and third-party tools built around it.
If you're a large, complex, multi-location operation and you need the safety of "everyone knows this system," it's a reasonable choice. Hiring is easier — you can post a billing job and get candidates who already know the software.
What I'd push on: cost as you scale, and how much of the "full solution" is actually included versus a separate module with a separate line item. Also ask specifically how nimble support is. Big platform, big support queue.
Who it's for: Larger providers who value ecosystem and established payer connections over speed and simplicity.
3. Bonafide
Bonafide has a reputation for being strong on the revenue cycle side, and the folks I know running it are generally pretty positive about the billing and collections workflow specifically.
It's less of a "everything in one beautiful pane of glass" experience and more of a solid, businesslike tool that does the financial side properly. If your primary pain is AR and denials rather than field operations, it deserves a look.
What I'd push on: the operational and delivery side. Make them show you the day-to-day for your intake and field teams, not just the billing dashboard.
Who it's for: Providers whose bleeding is mostly financial, not operational.
4. TIMS Software
Long-tenured, particularly common in pharmacy-adjacent and mixed-line operations. If you've got a complicated business — DME plus pharmacy plus something else — TIMS has handled that kind of complexity for a long time.
The trade-off is the one you'd expect from a mature platform: it's capable, and it feels its age in places. The people I know who love it really love it, usually because they've been on it a decade and know every shortcut.
Who it's for: Complex mixed-line operations, especially ones with existing TIMS institutional knowledge.
5. HDMS (Universal Software Solutions)
Flexible and configurable, with a reputation for a team that will actually work with you on custom needs. I've heard consistently decent things about the relationship side — people feel like they can get someone on the phone, which in this industry is not nothing.
The flip side of configurability is that you have to actually configure it. Budget for that. A flexible system with nobody driving it becomes a mess in about 18 months.
Who it's for: Mid-size providers with someone internal who enjoys owning the system.
6. Fastrack
Been around, does the core job, tends to show up on shortlists for smaller providers who want something established without the largest price tag in the category.
I'd call it competent rather than exciting. Which, depending on where you are in your software trauma recovery, might be exactly what you want.
Who it's for: Smaller shops who want proven and straightforward.
The part nobody tells you
Here's what I wish someone had said to me before the 45-minute demo disaster:
Demo with your own data, or don't bother. Every platform looks incredible with the vendor's clean sample data. Ask them to load 20 of your real orders, including the ugly ones — the weird payer, the patient with three open rentals, the resupply that keeps failing.
Talk to a reference the vendor didn't give you. Ask in a Facebook group or your state association. The references vendors hand out are the happiest customers on earth, by design.
Ask the implementation question early and specifically. Not "how long does onboarding take" — they'll all say 60-90 days. Ask: "Who specifically will be on my implementation, how many other clients are they running at the same time, and what happens if we hit month five?"
Count clicks. Seriously. In the demo, count how many clicks it takes to do the single most common task in your shop. That number, multiplied by 200 a day, multiplied by every employee, is the real cost of the software.
Don't sign four years. I know. But don't.
The right answer here genuinely depends on your size, your payer mix, and how much pain you're currently in. But if you're on something old and you've been telling yourself "we'll switch next year" for three years running — that's not a software problem anymore, that's a decision problem. The switching cost gets worse, not better.
Go book some demos. Bring your ugly data. And for the love of everything, take more than 45 minutes.
