Simple Fractal pricing at a glance
| Engagement type | Estimated cost | Best for |
|---|---|---|
| Custom RPA build | $50,000-$150,000+ depending on process count and complexity | Practices with unique workflows no turnkey bot covers |
| Turnkey bot products | Subscription-based; not publicly disclosed | Practices matching standard ABA/home-health use cases (Presley, Reggie, Remy, Archie, Connie) |
| Performance-based engagement | Pay-per-outcome; unit costs vary by volume | Workflows where ROI is easy to measure in dollars or transactions |
| Managed services | Ongoing fees; typically 15-25% of initial development cost annually | Existing customers expanding scope |
Estimates are based on industry RPA benchmarks. Simple Fractal quotes all engagements post-discovery.
How Simple Fractal pricing works
Simple Fractal's pricing model is built around flexibility rather than published tiers. Quotes come post-discovery, and the structure varies depending on the type of engagement. Three models cover most of what they sell.
Custom RPA builds: quoted post-discovery
Custom is Simple Fractal's core offering. A discovery process maps the workflow, defines the bot scope, and produces a project quote. Because Simple Fractal builds its own bots rather than reselling licensed RPA software, it can scope smaller initial projects to prove ROI before expanding the engagement.
Industry benchmarks put simple bot development at $2,000-$8,000 per process, with complex multi-system builds running $15,000-$40,000. Legacy system integrations can add $20,000-$200,000 on top, depending on how many systems are involved and how well-documented they are.
Mid-range RPA implementations, covering multiple processes with standard integrations, typically land in the $50,000-$150,000 range. Simple Fractal's project quotes likely sit within this range, scaled to the specific bot scope.
Turnkey bot products: subscription per bot
Simple Fractal also sells named, pre-built bots that target common ABA and home-health workflows.
- Presley: patient responsibility billing
- Reggie: Regional Center billing (used primarily by California developmental disability providers)
- Remy: appointment reminders
- Archie: unconverted appointment recovery
- Connie: scheduling
These products are sold as subscriptions. Pricing isn't published, but the structure is cleaner than the custom model: subscribe to the bot, the workflow is already built, and Simple Fractal handles ongoing operation.
Performance-based engagement: pay for outcomes
For workflows where ROI is easy to measure (like recovered patient payments, billing throughput, and claims processed), Simple Fractal offers performance-based pricing. The buyer pays a share of the savings or a fee per successful transaction rather than a fixed project price.
This model lowers the upfront commitment but introduces variability as volumes scale. A workflow that runs 10,000 transactions a month at a per-transaction fee can become more expensive than a flat managed service once volume grows past a certain point.
What hidden costs make Simple Fractal pricing climb?
Most of what makes custom RPA expensive doesn't show up in the initial quote. Here are four cost drivers buyers tend to encounter once the engagement scales.
1. Every new workflow is a new scoping conversation
Custom bots handle the workflows defined in the original engagement. When the practice grows or adds new operational needs (a new payer, a new specialty, a new reporting requirement), each new bot is a new scope, a new statement of work, and a new build cycle. The per-unit cost doesn't shrink much as you scale.
2. Maintenance is included, but breakage isn't free
Simple Fractal's managed-services model includes bot maintenance, but external changes (a payer portal redesign, a billing system migration, a new compliance requirement) typically trigger re-engineering work that sits outside the original scope.
General RPA industry benchmarks put ongoing maintenance at 15-25% of initial development costs annually, with that figure climbing when the underlying systems change frequently.
3. Performance-based pricing can outrun fixed-fee pricing at scale
The performance-based model is attractive at low volumes (you pay nothing if the bot doesn't deliver), but the math flips at scale. A bot processing 50,000 transactions a month at a per-unit fee may end up costing more than a flat managed-service contract that would handle unlimited volume.
Modeling out the 24-month total cost across multiple volume scenarios is worth doing before signing a performance deal.
4. The discovery process is slower than platform onboarding
Custom RPA discovery typically runs four to eight weeks before the first bot reaches production. For practices that need to move faster (a sudden volume spike, a payer contract change, a new compliance deadline), this timeline can be a real cost in delayed revenue.
Modern AI-native browser automation platforms can deploy a first workflow in days, which is a meaningful difference for time-sensitive operational needs.
Which Simple Fractal engagement should you choose?
Choose a custom RPA build if your workflows are unique enough that turnkey bots won't cover them, and you have time for a multi-week discovery process.
Choose a turnkey bot product (Presley, Reggie, Remy, Archie, Connie) if your practice runs standard ABA or home-health workflows that match one of the named bots. You skip the discovery cycle and get to production faster.
Choose performance-based pricing if you can clearly measure outcomes (recovered dollars, billable transactions, completed tasks), and you want to minimize upfront commitment. Model out the cost at full volume before signing.
Choose managed services if you're already a Simple Fractal customer, expanding scope, and ongoing operations matter more than build-cycle speed.
For healthcare ops teams comparing options for the first time, the meaningful split is between bespoke custom RPA and platform-based browser automation. They're different categories of products with different cost shapes.
Is Simple Fractal worth the cost?
Simple Fractal has a proven track record in ABA: nearly a decade in the market, and a named bot roster that solves specific ABA pain points. The trade-off is speed. The custom-build model is slower than platform automation, and every new workflow restarts the scoping process.
Post-discovery pricing means buyers can't compare alternatives without a sales cycle first. It's a fit for ABA workflows that match their named bots. Platform tools usually win on broader ops automation.
What are the best alternatives to Simple Fractal for healthcare ops teams?
If the goal is healthcare-specific automation without the custom-build cycle, three alternatives cover most of the market.
| Tool | Pricing | Best for | Why choose it |
|---|---|---|---|
| Silna Health | Custom quote | ABA prior auth and benefit checks | AI-first, deep on PA and eligibility |
| Kaizen | Usage-based, typically one-third of the labor cost replaced | Full-scale healthcare portal automation | Plain-English workflows, deploys in days, not weeks |
| UiPath | $25/month entry; $150,000-$500,000/year at production scale | Enterprises with internal RPA teams | Largest platform ecosystem |
Silna raised $27M in 2025 and goes deep on prior auth for ABA and specialty practices, but the scope is narrower than Simple Fractal's: prior auth, eligibility, and benefits only.
Kaizen is a full-scale automation platform with plain-English workflow definition and ROI-based pricing. Workflows deploy in days rather than weeks, a better fit for broad portal-based work than named-bot use cases.
UiPath starts at $25/month, but real production deployments can hit six figures annually once unattended robot licenses, Orchestrator, and AI modules are added. UiPath has healthcare customers, but no ABA-specific templates, so adopters typically need internal RPA engineering capacity.
Where browser automation beats custom RPA
Custom bots work well for the specific workflows Simple Fractal has built them for. For the broader browser-based work that runs healthcare operations (CAQH attestations, payer enrollment, prior auth across United and Aetna, verification of benefits, license tracking, claims-status checks), a platform built for browser execution is often the faster, cheaper fit.
That's where Kaizen sits. The browser agent logs into payer portals, fills out forms, pulls status updates, monitors CAQH re-attestation deadlines, and handles 2FA-gated claims work. Workflows are defined in plain English and run deterministically, without per-bot scoping cycles.
If your credentialing, prior auth, and VOB work still run through manual portal steps, we can automate it without a custom build cycle. Book a call to see how we handle your portal workflows.
Frequently asked questions
Does Simple Fractal offer fixed pricing for its turnkey bots?
Yes, Simple Fractal's turnkey bots (Presley, Reggie, Remy, Archie, Connie) are sold as subscriptions, which is a more fixed pricing model than the custom RPA builds. Specific subscription rates aren't published. The turnkey bots are designed for common ABA and home-health workflows and skip the multi-week discovery process required for custom builds.
What is the ROI on Simple Fractal RPA?
Simple Fractal claims projects pay for themselves within a year, with up to 13x ROI over a five-year period. Actual ROI depends on the workflow being automated, the labor cost being replaced, and how often the underlying systems change in ways that trigger maintenance work.
What is the best Simple Fractal alternative for ABA practices?
The best Simple Fractal alternative for ABA practices depends on the workflow. Silna Health is the strongest direct alternative for prior authorization and front-end revenue cycle work. Kaizen is the strongest alternative for broad browser-based portal automation.
