Growing an ABA Company Without Breaking It

Growth is the only strategy that reliably makes an ABA company harder to run. Handled deliberately it produces scale; handled reactively it produces accounts receivable, turnover and an exhausted owner.

The difference is sequencing.

What breaks first

In roughly this order:

Billing. More claims through the same process surfaces every configuration weakness at once, and AR climbs before anyone notices.
Credentialing. New clinicians can't bill on day one, so hiring ahead of credentialing converts payroll into pure cost.
Supervision. BCBA capacity is consumed by supervision requirements before it's consumed by caseload; growth silently eats the clinical leadership you already had.
Scheduling. Coordination that worked informally at twenty clients fails at sixty.
The owner. Everything that still routes through one person becomes the constraint on everything else.

Notice that clinical quality isn't on that list. Growth rarely breaks the therapy. It breaks the machine around it.

Sequence capacity ahead of caseload

The rule of thumb that holds up: add the infrastructure for the next increment before you add the clients.

That means credentialed clinicians ready before intake volume increases, billing capacity increased before claim volume does, supervision capacity confirmed before caseloads expand, and scheduling coordination in place before the schedule gets denser.

It feels expensive because you're carrying cost slightly ahead of revenue. It's cheaper than the alternative, which is carrying revenue you can't collect.

Adding a location

A second site is a step-change in fixed cost and a step-change in management complexity. Before signing:

Is there enough referral density within a reasonable radius to fill it, evidenced by actual waitlist and referral data rather than population statistics?
Is there clinical leadership for it who isn't you?
Does the payer mix in that specific area match what you already know how to bill?
Can existing billing, credentialing and scheduling absorb it, or does each need to grow too?

The failure mode is a second site that's really a first site again, run part-time by the owner.

Entering another state

Multi-state expansion multiplies work that doesn't scale for a single company: licensure, Medicaid enrollment, state-specific documentation and supervision rules, EVV requirements, and a separate payer landscape with its own closed panels.

It can be very much worth doing. It just needs to be scoped honestly as a nine-to-eighteen-month project with its own credentialing critical path — not as a marketing decision.

Growth that doesn't require more of you

Not all growth means bigger. For many owners the right version is the same size with less owner dependence — which is a real project with real steps: naming the decisions only you make, building or hiring for each, installing a weekly rhythm that runs without you, and testing it by actually being unavailable.

A company that operates without its owner is worth more, is easier to grow, and is far more pleasant to own. Those three things are the same project.

Where shared scale changes the equation

Every constraint above — billing capacity, credentialing throughput, recruiting pipeline, multi-state knowledge, reporting infrastructure — is expensive to build for one company and cheap to share across several.

That's the practical argument for shared infrastructure: not that independence is a problem, but that rebuilding the same overhead alone is the specific thing that makes independence expensive.