Key Takeaways
- 90-day transition pressure: ABA and other behavioral health providers running Thoughtful AI bots on top of CentralReach and other common platforms are sourcing replacements inside a window that, for some operators, includes seven-bot suites and billing volumes covering hundreds of clients.
- Bot portability: A platform agnostic approach is necessary. While many providers are using CentralReach, automations touch a diverse set of platforms including Therap, Wellsky and dozens of others.
- CentralReach Preferred Partner dynamics: CentralReach launched its Preferred Partner Network in March 2024 with Simple Fractal as its first and only approved RPA vendor, citing concerns about unsupported third-party automations operating on the platform.
- Sanctioned API integration versus UI scraping: Simple Fractal Product Sales Lead Dan Heimerle says most of the company’s CentralReach automations run through sanctioned APIs rather than the user interface, which he says differentiates the approach from vendors whose bots were shut down for taxing platform bandwidth.
- Vendor capital structure as diligence criteria: Simple Fractal, founded in 2013 by Henry Xie, is positioning its independence from private equity as a feature rather than a constraint, as operators reassess vendor durability after a second segment wind-down in three months.
A regional center billing bot that processed 15,000 sessions a month for one California provider lost its runway on April 24, when Thoughtful AI told customers its stand-alone services would be discontinued in roughly 90 days. The provider, which Simple Fractal Product Sales Lead Dan Heimerle described in an interview, faced two options inside the window: rebuild a manual process that previously consumed 120 hours of staff data entry every month, or find a replacement automation vendor capable of standing up a comparable bot before the lights went out.
That decision, multiplied across an unknown number of ABA, dental, and pediatric therapy operators who built workflows on Thoughtful AI, is now defining a small but suddenly active replacement market in behavioral health automation. As Acuity reported last week, Thoughtful AI’s wind-down followed its May 2025 absorption into Smarter Technologies, the New Mountain Capital platform that combined the company with Access Healthcare and SmarterDx in a hospital-focused roll-up. The behavioral health book that Thoughtful had built among small and mid-sized ABA providers no longer fit the strategic center of gravity. The product is going away with it.
Heimerle said most operators should not approach this as a traditional vendor replacement cycle. “In a 90-day window, this is closer to incident response,” he said. “The priority is stabilizing the workflows that keep revenue moving. In practice, that often means focusing on a subset of critical workflows first, rather than attempting a full system replacement under time pressure.”
What the wind-down has surfaced, in conversations with operators and vendors active in the space, is a question that does not appear in most automation procurement checklists: how the vendor’s bots actually talk to the EHR. For ABA providers running CentralReach, the dominant practice management platform in the segment, the answer is shaping which replacement options are technically viable inside a 90-day window.
CentralReach Preferred Partner Network Reshapes the ABA Automation Vendor Landscape
In March 2024, CentralReach launched what it called the CR Preferred Partner Network, naming Simple Fractal its first preferred partner and the only approved RPA vendor. The framing of the announcement is worth reading in light of what has happened since. CentralReach Chief Executive Chris Sullens said in the release that the company saw a need to vet automation vendors after observing what he characterized as unsupported, makeshift solutions operating against the platform without sanction.
Heimerle, who joined Simple Fractal after a stint as Sales Director at SS&C Blue Prism, the enterprise RPA platform, was more direct. He said in an interview that CentralReach had previously shut down third-party automation activity from vendors whose bots were, in his phrase, running a little bit rogue. Among the vendors affected by that posture, Heimerle said, was Thoughtful AI.
Whether to characterize the dynamic as platform discipline or platform protectionism is a question reasonable operators will answer differently. What is not in dispute is that the technical mechanics matter. Heimerle said most of Simple Fractal’s CentralReach bots now run through sanctioned APIs rather than navigating the user interface, an arrangement he attributed to the company having worked with CentralReach’s largest enterprise customers and helping influence the API roadmap. CentralReach has publicly documented APIs that authenticate via OAuth 2.0 and use issued client credentials and API keys.
The distinction between API-based automation and UI-based screen scraping is not academic. UI-based bots are more brittle, break when the platform changes, and consume disproportionate platform resources at scale. They are also harder for the EHR vendor to monitor and govern, which is what appears to have driven CentralReach to formalize the Preferred Partner program in the first place. For an ABA operator now sourcing a Thoughtful AI replacement, the question of whether a candidate vendor’s automations are sanctioned by CentralReach is no longer a procurement nicety. It is a continuity-of-operations question. That distinction has become more visible in the current transition, as operators evaluate which automations are likely to remain stable and aligned with platform governance over time.
Reusable Bot Inventory and the 90-Day ABA Replacement Constraint
Simple Fractal, founded in 2013 and based in New York, has built much of its ABA practice around what Heimerle called reusable automation patterns that are configured to each client’s workflows. While each client’s workflows differ, the underlying patterns are often consistent across providers. The company markets named automation solutions including Reggie for regional center billing, Remy for appointment reminders, Archie for unconverted appointments, Presley for patient responsibility, and Connie for scheduling. Its public client roster includes Easterseals of Southern California, Acorn Health, Autism Learning Partners, 360 Behavioral Health, LEARN Behavioral, Care Options for Kids, Kyo, and Trumpet Behavioral Health, several of which were also named in Thoughtful AI marketing case studies before the wind-down.
Heimerle described the Reggie regional center billing bot as a representative example. According to Simple Fractal’s case study, the underlying problem at one client was a recurring 120-hour data entry burden in the first week of every month, when staff re-keyed sessions already documented in the EHR into California regional center portals. Heimerle said the bot reduced that work to three to four hours of exception management for a single staff member, with monthly billing costs falling from roughly $4,500 to $1,500, and total savings on that one bot reaching approximately $108,000 over three years. He said the same client now operates 70 bots across its administrative footprint.
Those figures are Simple Fractal’s, drawn from a single client engagement, and Acuity has not independently verified them. What they illustrate, regardless of magnitude, is the business case operators built when they handed administrative workflows to AI and RPA vendors over the past several years, and what is at stake when one of those vendors winds down inside 90 days.
A second example Heimerle described involved an ABA provider running a suite of seven Thoughtful AI bots across multiple back-office functions. He said building seven new bots from scratch in 90 days would be impractical without significant cost or risk, and that operators in that situation are likely to lean on vendors with existing automation patterns and the experience to configure them quickly under tight timelines. Whether that vendor is Simple Fractal, an outsourced RCM services provider, or one of the AI-native entrants competing for ABA back-office workflows, the underlying constraint is the same: 90 days does not accommodate replacing everything from scratch.
Vendor Diligence in Behavioral Health: What a Second Wind-Down Tells Operators About Private Equity
Heimerle’s read on Thoughtful AI’s exit, offered without prompting, was structural rather than personal. He said the wind-down reflects a familiar pattern in investor-backed healthcare technology, where strategic decisions made several layers above the customer relationship can sunset products that are still working for the providers using them. The Thoughtful exit is the second segment wind-down in roughly three months, following UNIFI Autism Care’s decision to wind down operations earlier this year. Heimerle framed Simple Fractal’s position as the inverse: bootstrapped, founded by Henry Xie, and structured to make decisions on a customer time horizon rather than an investor time horizon. “When automation becomes embedded in core revenue workflows, continuity becomes as important as capability,” Heimerle said.
That pitch is partly self-interested, and operators evaluating it should treat it accordingly. It is also a more pointed version of the diligence lesson Acuity flagged in the original wind-down piece: that vendor capital structure has become as material to behavioral health technology selection as feature set or accuracy. Operators who built operational dependencies on Thoughtful AI did so when the company was a $20 million Series A growth story with a customer-facing roadmap. The roadmap that ended up applying to them was set inside a private equity portfolio strategy two governance levels removed.
For ABA operators now in the 90-day window, Heimerle’s practical advice was less about vendor selection and more about contingency. He said operators should document each automated workflow as a Standard Operating Procedure before the bot goes dark, both because the documentation feeds any future bot build and because staff need a manual fallback if the replacement is not in place when Thoughtful AI services end. Acuity has previously covered the operational readiness questions that determine whether a behavioral health technology transition succeeds or fails, and the process discipline mistakes operators keep making with AI adoption. The Thoughtful AI customer base is now running that exercise on a clock.
Whether the replacement market produces a tidy migration story or a messier one will depend on a question that, until last week, most operators did not need to ask: when their automation vendor talks to their EHR, who is listening on the other end.
For operators inside the transition window, Heimerle said the first step is quickly assessing exposure and prioritizing which workflows must be stabilized first to maintain continuity. “The biggest mistake is trying to solve everything at once,” he said. “The teams that move fastest are the ones that identify their highest-risk workflows and focus on stabilizing those in the first few weeks.”
Frequently Asked Questions
What is the CentralReach Preferred Partner Network?
The CentralReach Preferred Partner Network is a vetted partnership program CentralReach launched in March 2024 to formalize which third-party vendors are approved to integrate with its EHR platform. Simple Fractal was named the first preferred partner and the only approved RPA vendor. Approved vendors typically have access to CentralReach’s sanctioned APIs, which allow automation to run without taxing the platform in the way that unsanctioned screen-scraping bots can.
How are ABA providers replacing Thoughtful AI bots in the 90-day transition window?
Operators are pursuing three broad paths: rebuilding workflows manually with new or reassigned staff, migrating to another automation vendor with an existing library of automation patterns that can be adapted quickly, or moving the work to an outsourced revenue cycle management firm. The viable option for most operators depends on bot complexity, EHR platform, and whether candidate vendors have sanctioned integrations with that EHR.
What is the difference between API-based and UI-based RPA automation in healthcare?
API-based automation uses sanctioned data endpoints exposed by the platform, which tend to be stable, governed, and resource-efficient. UI-based automation, sometimes called screen scraping, navigates the platform’s user interface as if a human were clicking through it. UI-based bots are typically faster to build but more brittle, harder for the platform vendor to govern, and more likely to consume platform bandwidth at scale. The distinction matters more in closed-ecosystem platforms like CentralReach.
Why does Simple Fractal say it is bootstrapped, and does that matter to ABA buyers?
Simple Fractal was founded in 2013 by Henry Xie and has not taken venture capital or private equity funding. The company’s argument, articulated by Product Sales Lead Dan Heimerle, is that capital structure shapes how a vendor weighs customer continuity against investor return events. Whether that argument is decisive depends on the buyer’s view of vendor durability risk, which the Thoughtful AI wind-down has made a more visible category of risk than it was a year ago.
What should an ABA provider do first if it is losing Thoughtful AI services?
Document each automated workflow as a Standard Operating Procedure before the bot is decommissioned. The SOP serves two purposes: it is the input any replacement vendor needs to configure or build a comparable automation, and it is the manual fallback staff will use if the replacement is not in production by the cutoff. Operators should also confirm whether candidate vendors have sanctioned integration with their EHR (particularly if they are running CentralReach), and weigh the readiness signals most operators miss before adopting new behavioral health technology.
