Suppliers evaluating a move away from established platforms like Brightree commonly point to three recurring themes: interface and usability frustrations, longer staff onboarding than expected for newer hires, and a sense that legacy systems have accumulated add-ons rather than being rebuilt around modern workflows.
Why This Surfaces More as a Supplier Grows
These concerns tend to surface most acutely as a supplier grows. A system that worked adequately at a smaller scale can become a bottleneck once a business adds locations, staff, or product lines — particularly if reporting, inventory, and delivery functions were bolted on over time rather than designed together. Suppliers considering newer, smaller vendors are often driven less by dissatisfaction with any single feature and more by a cumulative sense that daily workflows take more clicks, more manual reconciliation, and more training time than they should.
The Real Cost of Switching
At the same time, switching software is a genuinely significant undertaking for any DME business, and suppliers weighing a move are right to scrutinize it carefully. Data migration accuracy, claims-in-flight during a transition, staff retraining, and the risk of temporary disruption to collections are all real costs of switching — not just to a smaller vendor, but to any new platform. The suppliers who report the smoothest transitions are typically the ones who prioritized structured onboarding and dedicated implementation support as heavily as they weighed feature comparisons, since a strong feature set delivered through a rushed or unsupported migration can still create months of operational disruption.
How to Actually Evaluate the Decision
For a supplier gathering input before a decision, the most reliable source isn’t general sentiment about a vendor category but direct reference conversations with similarly sized suppliers who’ve completed a recent migration, asking specifically about data migration accuracy, time to full staff proficiency, and how billing continuity was maintained during the transition.
Smaller Doesn’t Mean Less Capable
It’s also worth noting that ‘smaller vendor’ doesn’t inherently mean less capable — for many mid-size suppliers, it means a platform built more recently, with fewer legacy constraints and a more direct line to product and support teams during onboarding. The tradeoff suppliers weigh isn’t really size, it’s whether a newer vendor has the depth of DME-specific functionality (payer rules, CMN workflows, inventory, and delivery) to match what an established platform already covers. The suppliers who report the best outcomes tend to be the ones who tested that depth directly, through a demo built around their own claim types, rather than assuming smaller automatically means less capable or larger automatically means more reliable.
