This is the story of an ABA practice that switched platforms for two reasons at once — billing headaches and clinical software its team had quietly come to dread. We've kept them anonymous, but the second reason is one we hear almost word-for-word, over and over: "it just takes so many clicks to do anything."
Why "too many clicks" is a real number, not a complaint
It's easy to wave off click-fatigue as people being fussy. It isn't. A BCBA's time is the scarcest, most expensive resource in the building — the clinician you can't hire enough of, whose hours are split between billable supervision, treatment planning, parent training, and oversight. Every routine action their software makes slow comes straight out of that pool.
Their previous clinical system buried routine work under layers of navigation. Writing a session note, finding a program in a client's plan, logging a supervision session — each was a small expedition of clicks, screens, and saves. Trivial once. But a BCBA does these dozens of times a day, across a full caseload, every day. Multiply a handful of needless clicks by every action, every clinician, every shift, and you've quietly converted a meaningful slice of your most expensive clinical time into menu navigation. That's time not spent on the kid, the program, or the RBT who needs coaching.
And it has a second cost: friction is where documentation slips. When logging is a chore, notes get deferred to the end of the day and reconstructed from memory, supervision gets recorded "later," and the record drifts from what actually happened — which is both a clinical-quality problem and an audit problem.
What they tried first
The usual coping mechanisms: internal cheat-sheets for the clunkiest workflows, "click here, then here, then save" trainings for new hires, and a lot of working around the rough edges. It made the pain survivable. It did not make the software faster. The clicks were still there, every day — and onboarding a clinician to a tool that fights them is its own recurring tax in a field with constant hiring.
On top of that, the billing side had its own friction — the kind that quietly costs money. Two problems, one root cause: tools that made the people doing the work do more of it.
How Wilma helped: get out of the clinician's way
What their clinicians noticed first wasn't a feature — it was the absence of steps. How much less there was to do to get the same thing done:
- Fewer steps to the same outcome. The everyday actions — documenting a session, moving through a client's record, coordinating with the team — are designed to take a tap or two, not a tour of the menu. The thing you do fifty times a day is the thing that's fast.
- Building goals without the click marathon. Writing programs and goals is one of the most click-heavy jobs in legacy tools — often an evening of setup per client. In Wilma it's quick, and AI can personalize goals to the client (the AI add-on), so creating a program actually removes work instead of adding it.
- Data collection at the BT's fingertips. Behavior techs collect on any device, targets right there — no digging through menus, no tapping the same thing ten times. They can even run several timers at once while collecting other data, so a session with concurrent measures is captured live instead of reconstructed afterward.
- One-tap supervision logging. Supervision is logged in the moment and tracked automatically toward BACB hour and ratio requirements — so it's captured when it happens, not reconstructed at renewal time when nobody can remember the exact dates.
- Documentation that drafts from the data. Session notes can be drafted from the data already collected during the session, for the BCBA to review and sign (the AI add-on). Writing becomes editing — the slowest part of the day becomes one of the fastest.
- Billing and clinical on one record. Because the same platform handles both, the clinical work and the billing work stop living in separate systems that have to be reconciled by hand — the friction the practice was feeling on the billing side came from the same disconnection.
"One of our BCBAs called it a BCBA's dream. After years of clicking through everything, software that just gets out of the way feels like that." — Clinical director
"But switching is painful" — the fear that keeps practices stuck
The reason most teams tolerate software they've outgrown is the dread of moving: the data, the retraining, the imagined month of chaos. It's worth naming — and it's fair to be skeptical — because the fear is almost always bigger than the reality. This practice moved because the daily pain had finally outgrown the one-time pain of switching. Then the switch itself surprised them: bringing everything across — clients, historical data, open claims — took about a week, not the months they'd braced for. Wilma runs the migration; it isn't a project the practice is left to manage alone.
"Honestly, we expected this to take months. We were fully moved over — clients, data, claims, all of it — in about a week. That was the part that surprised us most." — Clinical director
The results
- Far fewer clicks on the daily workflows clinicians repeat dozens of times a day — expensive BCBA time back on cases instead of on the tool
- Goal-building and in-session data capture cut from a click marathon to a few taps — with AI personalizing goals (AI add-on) and BTs collecting on any device, simultaneous timers and all
- Supervision captured in the moment and tracked automatically toward BACB requirements — no renewal-time scramble, a cleaner record
- Notes drafted from collected data (AI add-on) — the slowest part of the day became one of the fastest
- Clinical and billing unified on one record, removing the reconcile-between-systems tax that was driving the billing friction too
The names are hidden. The pattern isn't: when software makes every routine task a small ordeal, it isn't a training problem — it's a design problem, and it compounds across every clinician and every day. When the tool gets out of the way, your most expensive people go back to doing the work only they can do.
Frequently asked questions
What do "too many clicks" actually cost me?
Individually nothing; in aggregate, a tax on every clinician, every day. When writing a note, finding a program, or logging supervision each takes a tour of the menu, your team spends energy fighting the tool instead of thinking about the case — multiplied across every clinician and every session.
Switching clinical software sounds painful — is it worth it?
That fear is exactly why practices stay stuck on tools they've outgrown. The team in this story moved for two reasons at once — billing friction and clinical click-fatigue — and what they noticed first was simply how much less there was to do to get the same thing done. Wilma's team manages the switch, including your data.
What makes Wilma "a BCBA's dream"?
That's a real quote from a BCBA in this story. After years of clicking through everything, software that takes a tap or two for everyday actions — documenting a session, moving through a record, logging supervision — feels like it gets out of the way so you can do the clinical work.
Do I lose my data and history when I switch?
No — migrating your history is part of how Wilma handles a switch. The goal is that your clinical and billing record comes with you onto one platform, so you stop reconciling between disconnected systems.
Does Wilma handle session notes and supervision tracking?
Yes. Supervision is logged in a tap and tracked automatically toward BACB hour and ratio requirements. Session notes can be drafted from the collected data for the BCBA to review and sign (the AI add-on), so writing becomes editing.
Can Wilma handle clinical and billing together so I'm not reconciling two systems?
That's the point of one platform — clinical and billing live on the same record, so the work stops living in separate systems that have to be stitched together by hand.