MissionViewpoint Monthly Update — July 2026
The Rise of the Operating Layer
Most ABA providers already have an operating layer.
It is the collection of spreadsheets, reports, recurring meetings, workarounds, and institutional knowledge that sits between the systems where information is stored and the decisions required to run the organization. Providers did not design this layer. It emerged because the work demanded it.
A practice management platform can hold an authorization, record a session, and produce a utilization report. But deciding which authorization is at risk, why utilization is declining, or which staffing intervention is most likely to work requires information and judgment from somewhere else. That distinction is becoming increasingly consequential as organizations scale.
"The platform holds the record. The operating layer determines what happens next."
This month's three-part series examines the operating layer present inside every provider, the data spine required to support it, and how that foundation creates strategic adaptability. The Operator Spotlight on Behavioral Framework shows what this looks like in practice — operational knowledge around matching, cancellations, and utilization being translated into repeatable capabilities that sit on top of existing systems.
Also this month: provider growth continues despite a tightening environment, platform vendors make more deliberate choices about what they will own and what they will connect, and CAQH's transition to DataSpring raises a harder question about whether providers can reconcile their own workforce data.
Let's get into it.
Every Provider Already Has an Operating Layer
Ask a COO at an ABA provider what system runs their operations, and the answer will almost always reference their practice management platform. That answer isn't wrong. But it is incomplete in ways that compound as organizations grow.
The platform is where records live. But a remarkable amount of actual decision-making happens somewhere else — in a spreadsheet a scheduler built two years ago, in a process a coordinator carries in her head, in a standing Wednesday meeting where clinical directors review caseloads using a report someone exports, reformats, and emails every week.
This is not a failure of implementation. It is a description of how complex service organizations actually function. The authorization lives in the platform. The planning happens outside it. The matching logic lives in a coordinator's head. The utilization picture lives across multiple systems no single view assembles.
Every provider has an operating layer. The question is whether it remains visible, transferable, and scalable as the organization grows.
Read →Why Every Provider Needs a Data Spine
Most ABA providers have more connectivity than they think — and less than they need. The gap is not usually in moving records between systems. CRMs push referrals into practice management platforms. Authorization tools monitor deadlines. Documentation systems pull session records for review.
Those integrations create real value. But they generally move records. They do not assemble the information required to make operational decisions.
An authorization manager doesn't simply need to know when an authorization expires. The manager needs to know whether utilization, clinical progress, documentation readiness, staffing stability, and payor behavior support the renewal strategy. A matching coordinator doesn't simply need technician availability — the coordinator needs to evaluate fit across geography, insurance, schedule, experience, and family circumstances.
That requires decision connectivity. The question isn't whether a provider has integrations. It's whether those integrations reach the operational decisions that determine how the organization actually functions — or whether they stop at the record layer and leave the decision layer to human assembly.
Read →The Strategic Advantage of Adaptability
The value of an operating layer is not simply automation. It is adaptability.
A provider with a strong operating layer and data spine can change a workflow without waiting for its core platform to change. It can introduce a new engagement tool, authorization capability, treatment-planning approach, or decision process without rebuilding the organization around it. Parent engagement doesn't need to look the same across every provider. Matching, supervision, and care coordination can reflect the organization's own priorities rather than being defined entirely by the boundaries of a single application.
The long-term advantage may not belong to the provider with the most features or the largest technology investment. It may belong to the provider with the greatest freedom to evolve — the one that can keep improving how it operates as technology, payor expectations, and workforce conditions continue to shift.
Same systems. Same data. Same people. What the operating layer changes is everything between the record and the judgment.
Read →Behavioral Framework: Building an Operating Layer on Top of Its Systems
Behavioral Framework had the data required to support technician-client matching. Insurance eligibility, geography, availability, language preferences, and family constraints were already being captured inside Lumary. The challenge was applying that information consistently as the organization grew.
- Hard constraints: insurance, geography, baseline availability
- Weighted constraints: schedule fit, technician experience
- Flexible constraints: partial availability, trainable attributes
"Lumary is our system of record and does what it does well, but we've also chosen to invest in our own proprietary technology that builds on top of it — pulling from Lumary and our other systems to shorten the distance between data and decisions."
The result is FrameworkOne — an internal operating layer that surfaces ranked matches with visible reasoning, then extends the same pattern into utilization monitoring and cancellation processing. The system of record stays in place. What changes is the organization's ability to act on the data it already contains.
The most important part of the story isn't the software. It's the decision to take operational knowledge that previously lived in people and structure it into something that can scale.
Read the full spotlight →What CAQH's Move to DataSpring Means for ABA Provider Data
CAQH's transition to DataSpring has generated concern about whether deeper payor involvement in provider data could lead to more aggressive credentialing scrutiny, claim reviews, or recoupment activity. Whether those concerns prove warranted remains to be seen.
But they expose a more immediate issue: credentialing sits at the top of an operational chain. A single BCBA record spans HR, credentialing, learning management, practice management, scheduling, and billing. Each system owns part of the record. None necessarily owns the complete historical picture.
If those systems disagree about credential status, enrollment dates, or supervision assignments, a provider may struggle to reconstruct the facts when a payor questions services delivered months earlier. The first step doesn't require a new platform.
Pick one BCBA. Pull the records from each system. Determine whether they agree. If they don't, the problem is larger than credentialing. It's a provider-data architecture problem.
Read →Action Behavior Centers surpassed 9,000 LinkedIn employees in June, adding nearly 600 during Q2. At that scale, percentage growth compression is almost universal. Large organizations simply have more denominator to fight against. Action doesn't appear to have gotten that memo — the growth rate they're posting is more consistent with a provider in the 500–1,500 employee range than one approaching 10,000.
The broader dataset produced a counterintuitive signal. Despite persistent discussion of Medicaid reimbursement pressure, authorization scrutiny, and a tightening operating environment, all but one of the Top 20 providers added LinkedIn headcount from May to June. Average Q2 growth across the dataset was 4.2%. Provider sentiment may be increasingly cautious. Provider staffing behavior is not yet showing the same caution.
Three of the original Q1 cohort qualified again: Behavioral Framework, Golden Steps ABA, and Brighter Strides ABA. They were joined by ABA Centers of America and Action Behavior Centers. The gap has persisted long enough that it increasingly looks structural rather than temporary.
In May, the most visible pattern was platforms expanding beyond their traditional areas of focus. In June, vendors appeared to become more deliberate about what they intend to own — and what they intend to connect. Some are extending directly into adjacent workflows. Others are preserving a narrower product focus while using partnerships and interoperability to create a more complete provider experience.
That distinction is becoming strategically important. As individual feature lists converge, architectural choices may increasingly determine how platforms compete. The competitive question is becoming less about which platform has the longest feature list — it is increasingly about where each platform draws its boundaries, and how effectively information can cross them.
Silna Health introduced its Interoperability Agent, using agentic AI to exchange data with EHRs and practice management systems without requiring APIs or formal integrations.
Motivity announced a strategic partnership with Flychain focused on connecting operational and financial performance for ABA providers.
Hi Rasmus partnered with Camber to connect clinical documentation directly to billing workflows.
EarliPoint Health launched Skill Illustrator, extending its platform from objective developmental assessment into treatment planning and longitudinal progress measurement.
Lumary appointed Daniel Wyner as CEO. Lumary's U.S. ABA business represents approximately one-sixth of overall company staff. CentralReach also surpassed 400 U.S. LinkedIn employees, while Camber and Silna added headcount for a third consecutive month.
Full Platform SCUBA →Closing Thoughts
The operating layer is easy to mistake for a technology concept. It is really an organizational one.
Every provider already has operational knowledge about matching, utilization, authorizations, recruiting, clinical quality, and revenue cycle management. That knowledge is being applied every day. The difference is where it lives.
In many organizations, it remains distributed across spreadsheets, meetings, and the judgment of experienced individuals. At Behavioral Framework, part of that knowledge is being made more explicit and repeatable — not by replacing existing systems, but by building a layer that shortens the distance between information and action.
That is also why the data spine matters. Connecting records is useful. Connecting the information required to make a decision is more consequential.
Together, the operating layer and data spine create a foundation that allows providers to scale without forcing every workflow into one platform or one standardized operating model. They create room to adapt. And in a market where payor expectations, workforce conditions, care models, and technology choices continue to evolve, adaptability may become one of the most valuable operating capabilities a provider can build.
Until next time,— Scott P.S. I work with ABA providers, platforms, and investors on strategy, operations, technology, and market positioning. If that's relevant to your work, reach me at missionviewpoint.com.
Replacing a practice management platform is not simply a software decision. The visible costs are licensing, implementation, training, and data conversion. The less visible costs sit inside the operating model: embedded workflows, historical records, contract timing, reporting gaps, integration dependencies, and operational knowledge accumulated around the existing system.
That operating model cost is the one most organizations underestimate — and the one that most frequently determines whether a transition succeeds.
In August, I'll examine the decision from three perspectives: why providers begin considering a switch, how platforms must address the gaps that make replacement worthwhile, and what organizations should do before selecting a partner and beginning the transition. The economics of switching extend well beyond implementation cost. They begin with understanding what the organization is actually replacing.
