CentralReach Pricing: What It Costs and What to Ask Before You Sign

CentralReach does not publish pricing. Here is what is publicly reported, why the reported figures vary so widely, and the questions that actually determine your bill.

CentralReach is the largest platform in applied behavior analysis and one of the most established. It does not publish a pricing page, and pricing questions are routed through a demo and a sales conversation.

That makes it hard to compare, so here is what is actually knowable.

What is publicly reported

CentralReach does not publish rates. Third-party software directories and review aggregators report figures that vary substantially — some list entry pricing in the region of $59 per user per month, while others describe effective costs materially higher once modules and add-ons are included.

Treat all of those numbers as unverified secondary reporting, not as quotes. They come from aggregator listings and user reports rather than from CentralReach, and they are frequently out of date. The only number that means anything is the one on your proposal.

The wide spread does tell you something useful, though: this is a modular platform with a configurable bundle, so the range reflects genuinely different configurations rather than inconsistent pricing.

Why quote-based pricing is common at the enterprise end

It is worth being fair about this. Large platforms serving multi-site organizations have real reasons not to publish:

  • Requirements vary enormously between a 15-person clinic and a 600-person multi-state organization.
  • Implementation, migration and configuration are a significant part of the cost and genuinely differ per customer.
  • Enterprise agreements often include negotiated terms that a list price would misrepresent.

The trade-off is that evaluation takes longer and comparison is harder, which is the cost the buyer absorbs.

The questions that determine your bill

Go into the pricing conversation with these written down:

  1. What is the unit — per user, per client, or both? This single answer determines how the bill behaves as you grow.
  2. Which modules are in the quoted price, and which are extra? Ask specifically about data collection, scheduling, billing and claims, a parent or caregiver portal, reporting and analytics, and any AI features.
  3. What is the implementation fee, and what does it include?
  4. Is data migration included? Clients, authorizations, historical data and documentation. Get the scope in writing.
  5. Are there per-claim or clearinghouse fees on top?
  6. What is the minimum commitment and the contract term?
  7. What have annual increases actually been for existing customers over the last three years? Ask about actual history, not the contractual cap.
  8. What happens to my data if I leave? Export format, timeline, and cost.
  9. Are there charges for additional training, support tiers, or a dedicated account manager?

Modelling it properly

Because the quote is configurable, the mistake buyers make is comparing CentralReach's first-year number against a competitor's steady-state number.

Build the comparison over three years. Project staff and client counts separately, apply whatever unit CentralReach quotes you, add implementation and migration in year one, and apply the historical annual increase you asked about in question seven. Then compare that total against alternatives.

Practices frequently find the ordering changes once implementation is amortised and increases are applied.

Where a published price sits in the comparison

For reference in your model, Wilma publishes its pricing: $30 per user per month for the full Core platform, with optional AI at $20 per user and Phone at $10 per user, and a ten-licence minimum. There is no per-client component, so the bill tracks headcount rather than caseload.

That is not an argument that published pricing is automatically better — a quote-based platform may well come in lower for a given configuration. It is an argument that you should be able to build the model before the sales call rather than after it, and where a vendor publishes, you can.

If you are actively comparing, the side-by-side breakdown covers the capability differences alongside the commercial ones.

The summary

CentralReach does not publish pricing, third-party reported figures vary widely and should not be treated as quotes, and the real number depends on your module bundle, user count and negotiated terms. Ask about the pricing unit, module inclusions, implementation, migration, per-claim fees, minimums, actual historical increases, and data export. Then model three years rather than comparing month one.

Frequently asked questions

How much does CentralReach cost?

CentralReach does not publish pricing. Third-party directories report figures ranging from around $59 per user per month to considerably higher, but those are unverified secondary sources and reflect different module configurations. The only reliable number is the one on your own proposal.

Why does CentralReach not publish pricing?

It is a modular platform serving organizations from small clinics to large multi-state providers, where requirements, implementation scope and negotiated terms vary enough that a single list price would misrepresent most deals. The trade-off is a longer evaluation and harder comparison for the buyer.

What should I ask on a CentralReach pricing call?

Ask whether pricing is per user or per client, which modules are included versus extra, the implementation fee and its scope, whether data migration is included, whether per-claim or clearinghouse fees apply, the minimum commitment and term, what annual increases have actually been for existing customers, and what data export looks like if you leave.

How do I compare CentralReach against a published-price platform?

Build a three-year model. Project staff and client counts separately, apply each vendor's pricing unit, add implementation and migration in year one, and apply realistic annual increases. Comparing a first-year quote against a competitor's steady-state rate is the most common error.