Most owners we talk to run clinical work by day and payroll by night, with a billing backlog waiting for the weekend. You cannot fix that with longer hours. You can fix a good deal of it by running one system instead of three.
Apply for beta access Take the interactive tourSessions delivered, clean-claim rate, auth units at risk, credentials expiring. The thing you read with your morning coffee, without anyone spending a week assembling it.
Free for the whole beta, and 30 days written notice before any number applies to you. We have not set pricing yet and the pricing page explains why rather than putting a sales call in front of it.
Eligibility is checked from the client's insurance record before the session, authorizations are tracked against what actually gets delivered, unbilled sessions flag themselves, and validation catches problems on the way out rather than after a payer rejects them. A denial that never happens costs you nothing, and the ones that do happen take weeks to chase.
Approving time off shows you the coverage gaps it creates in the same click, and credential expiries alert you before they turn into unbillable sessions. The payroll export pulls straight from GPS-verified hours, so there is no triangle of spreadsheets to reconcile on a Sunday.
Second location? Locations, org chart, cross-site reporting and per-location compliance are built in. You will outgrow the space you are renting long before you outgrow the software.
Clean exports of everything, at any time, from inside the platform rather than by request. Our plan for keeping you is to be better next quarter, and it does not involve making the door hard to find.
You are being asked to move a working practice onto software from a company you have not heard of, so here is the state of things without the varnish. The platform is built and running. What is not settled is the price. The beta starts on Oct 1, 2026, and the business associate agreement is signed with your practice before a single client record goes in.
Two things that follow from that, and they are the reason this is worth a look rather than a wait. You cannot be surprised by a bill, because you will see the price 30 days before it applies. And you cannot be trapped, because the exports are yours from day one. Everything else is a judgement call you get to make with the product in front of you.
Typically two to four weeks of parallel running. The import wizard does the data work: your admin uploads exports, maps columns once, and your BCBAs validate everything in a staging workspace before go-live. Beta practices get the done-for-you version, where we drive the wizard on your data and you sign off at every step. Your RBTs learn a two-button mobile app either way. The full playbook.
Nothing during the beta, and we have not set pricing yet. When we do, you get the price list in writing 30 days before it applies to your practice, and if the number does not work you take clean exports of everything and owe nothing. Clearinghouse pass-throughs sit on top of any software price and we show you those before you commit to anything.
Today the honest answer is keep it in-house, or keep the biller you have, because Managed Billing has not launched. You can generate and submit claims from inside ABAVault™ through your own clearinghouse, with Manual, Office Ally and Availity supported. When Managed Billing launches, we will show you what it would cost your practice next to a part-time biller, including where doing it yourself is cheaper.
We do not have a date, and we would rather say that than invent one you would plan around. It starts when the business associate agreement and the beta terms come back from counsel. Applications are open now, a person reads every one, and applying commits you to nothing.
Fair question, and the answer is that the exit is written down before you come in. Clean exports of everything at any time, no bill for the beta months, and 30 days to look at the price before it applies. A direct line to the people writing the code is the one thing a small vendor can offer that a large one structurally cannot.