It's 7 p.m., and you're cross-referencing a spreadsheet against your practice management system because a batch of claims came back with duplicate denials. Your billing team didn't know a BCBA® had rendered another appointment on the same date of service after the first batch went out. The BCBA didn't know the claim had already been submitted. Both of them did their jobs correctly, and you still got the denial because the info lives in two systems that can't see each other in real time.
You fix it, move on, and file it under “things we deal with.”
The ABA practice management software that feels “fine” is usually the one doing the most financial damage. It may not be failing spectacularly, but it’s draining revenue, hours, and trust. And your team has gotten used to it. Many practice owners, when they think about their software costs, think about what it would take to switch. The bigger number is what it costs to stay.
Where "Good Enough" ABA Software Is Costing You Money Every Month
You probably don't think of your current software as a financial drain. It's a tool that runs and the team uses it. It was chosen because it worked well enough at the time. Now you’ve seen the gaps, but switching platforms feels like a project nobody has the bandwidth for. The longer you stay, though, the more that “well enough” system accumulates costs your team has learned to absorb as normal.
Three categories tend to take the biggest hit.
Denied claims and delayed reimbursements
Authorization issues are among the top causes of claim denials in healthcare, according to MGMA. And ABA practices, with their high session volume and complex authorization structures, are especially exposed.
Every denied claim costs staff time to investigate, correct, and resubmit. But the worst is the cash flow delay—45 to 90 days between the original service date and resolution, during which that revenue sits in limbo.
On a practice billing $3M to $5M per year, even a single-digit denial rate translates to six figures in delayed or lost collections annually. That's a position you couldn't fill, new client reinforcers you could purchase, new training content you could buy, or raises your team has been waiting on.
Most of these denials trace back to the same root: data that had to travel between two systems and arrived late, incomplete, or wrong. When your data collection and your billing run on separate databases, every claim carries a small risk at every handoff.
Staff hours spent in workarounds
This one won't show up on any financial report, yet it’ll hit your payroll every cycle.
When systems don't talk to each other, people fill the gap. Your admin exports a CSV, reformats it, and uploads it somewhere else. An RBT® finishes a session, signs the note, and then gets a message asking them to confirm the session occurred because it didn't come through.
One ABA practice with 300 employees tracked this before making a change and found their team was losing 100 hours per week to software troubleshooting and manual data reconciliation. Over a year, that's 5,000+ hours, the equivalent of two and a half full-time salaries going toward patching gaps between disconnected tools.
“We were spending 100 hours per week just trying to make the software work.”
— Kyle Quinn, President, ABC for Autism
That number only accounts for the time people knew they were losing. It doesn't include the quiet ten minutes here and there that staff absorb as normal: the re-checks, the redundant data entry, or the slow load times everyone has learned to wait through.
Clinical hours redirected to admin work
There's a third category that lives outside of finance entirely.
Your BCBAs spend supervision hours troubleshooting note and appointment discrepancies instead of reviewing treatment progress. New RBTs take two extra weeks to feel comfortable because the interface requires workarounds that nobody documented.
Ask yourself these three questions, and ask your team the same:
- How many times this month did someone re-enter data that should have synced automatically?
- When was the last claim denied because of an issue rendering the appointment?
- How long does it take a new hire to run a session and convert their appointment confidently in your current system?
If you don't know the answers, that's the point. When an ABA system is “good enough,” people stop measuring what it costs them.
“I stayed in a broken system because I thought switching would be too hard.”
— Amy Legan, Owner/Director, Aspire Behavior Solutions
Unfortunately, the cost of waiting doesn't pause while you decide.
Why Your Team Won't Tell You the Software Is the Problem
A study published in Harvard Business Review looked at why organizations choose not to act even when they know something needs to change. In more than half the cases, the issue wasn't satisfaction with the current setup. It was fear of making the wrong move.
In ABA, where your team already carries heavy caseloads and tight schedules, adding “evaluate new software” to the to-do list can feel like the last thing anyone needs.
Clinical staff develop workarounds and stop reporting the friction. RBTs assume the lag is normal because they've never used anything different. BCBAs absorb the extra reconciliation time as “part of supervision.” And admins learn to build buffer time into every billing cycle because they know something will need fixing.
Nobody escalates because the system works just enough that complaining feels like asking for disruption. And in a field where everyone is already stretched, disruption feels like a risk nobody wants to own.
That silence can look like satisfaction if you're not asking the right questions. But it's closer to resignation. The team has adapted to the dysfunction, and because they've stopped talking about it, you've stopped seeing it.
Every ABA leader who eventually made a change tells us the same thing: they didn't realize how much they were losing until the losses stopped. Their stories are worth reading.
How One Database Changes the Way Your ABA Practice Runs
Imagine one session lifecycle, start to finish.
A session ends. The RBT signs the note on the device, right there. The authorization hours update automatically. The claim queues with the correct CPT code and modifier attached. The BCBA sees the session data in the note in real time. The admin batches and submits the claim without rebuilding it from scratch.
That's what happens when clinical data and operational data live in the same database: the session record that your RBT signs is the same record your billing team works from.
Now contrast that with a fragmented setup, where each of those handoffs is a point where data can lag, get entered wrong, or sit in a queue nobody is watching. Every handoff is a place where “fine” software costs you a little more.
At the University of Washington Autism Center's APEX summer camp, the difference was measurable almost immediately:
“By our conservative estimate, Motivity saves us over 1,500 person-hours every summer.”
— Dr. Benjamin Aaronson, Director of APEX
That's staff time that went back to direct care, supervision, and parent communication.
Your ABA Practice Deserves Better Than “Fine”
You've invested in hiring the right people for your practice, training them well, and earning the trust of the families you serve. Your software should hold up its end of that bargain.
If what you've read here sounds familiar—if the denied claims, the workarounds, the slow load times, and the quiet frustration feel like a description of your Tuesday—then it's time to move on from the software you've been settling for.
The ABA leaders we work with say the same thing:
“The biggest regret I have about changing software is that we didn't do it sooner.”
— Kyle Quinn, President, ABC for Autism
Schedule a Motivity demo and see what changes when you manage your ABA practice from one connected system.