For practices that want all-in-one done right.

All-in-one, done right — built from experience.

ABA Matrix is a capable all-in-one — and so is Wilma, built by people who actually ran ABA practices, so the whole thing is thought through end to end. Agentic AI, a built-in phone, and flat published pricing are bonuses on top.

Why operators compare them

Why practices choose Wilma® over ABA Matrix.

All-in-one, done right — built by operators.

ABA Matrix is a genuinely broad all-in-one. So is Wilma — but it's built by people who actually ran ABA practices, so the whole platform is thought through end to end and just fits the work. That cohesion is the part operators call "impressive."

Agentic AI, native to the platform.

ABA Matrix is a genuinely broad all-in-one with strong data and graphing. Wilma adds an agentic AI layer above all-in-one: she drafts session notes from data, scrubs claims pre-submission, and prepares work within your rules, pending sign-off.

A phone system that's built in.

Wilma includes native business telephony — IVR routing, call recording, two-way SMS — threaded to the client record. ABA Matrix doesn't publicly offer built-in telephony, so calls stay in a separate tool.

Pricing you can see and model.

Wilma publishes flat pricing: $30/user/month Core, +$20 AI, +$10 phone. ABA Matrix bills on a quote-only, usage-based model. Flat per-user pricing is predictable and budgetable up front.

Both are real all-in-ones — Wilma leads on AI + telephony.

We'll be straight: ABA Matrix has native billing, EVV, and payroll-style operations. The honest differences are Wilma's agentic AI, her built-in phone/IVR, and transparent flat pricing.

Side by side

Wilma® vs ABA Matrix, feature by feature.

Comparison based on publicly available information as of June 2026. ABA Matrix is a trademark of its respective owner.

What you get on Wilma

What changes on one agentic platform.

AI prepares the work.

Notes drafted from data, claims scrubbed before they ship, caseload trends surfaced — within your rules, pending approval. That agentic layer is the core of Wilma.

Calls become client context.

Intake and family calls route with context into the client record. The phone is part of the platform, not a separate vendor.

Budget it on one line.

Flat per-user pricing you can model in a spreadsheet — no usage-based quote to decode.

One record, one login.

Clinical, billing, scheduling, and telephony on a single source of truth.

Pricing and reviews

Comparing ABA Matrix pricing and reviews? Start with the buying questions.

Bottom-funnel buyers usually need three answers: what it costs, what real operators say after implementation, and whether the platform owns the workflow or depends on add-ons.

Pricing clarity

Wilma publishes flat pricing: Core is $30/user/month with a 10-licence minimum, so an account starts at $300/month, plus optional AI and Phone add-ons. Use that as the baseline when an ABA Matrix pricing page or quote requires a sales process.

Review signals

When reading ABA Matrix reviews, separate ease-of-use praise from operational outcomes: clean claims, authorization control, onboarding speed, support responsiveness, and whether teams still need extra tools.

Native vs integrated

The strongest reviews usually come when scheduling, notes, billing, data, EVV, phone, and AI share one record. Every separate vendor adds another support path and another place work can drift.

FAQ

Questions operators ask before they switch.

Is Wilma a good ABA Matrix alternative?

What does ABA Matrix do well?

How does pricing compare?

Does Wilma include a phone system? Does ABA Matrix?

Does either run standardized assessments like VB-MAPP?

Can I migrate from ABA Matrix to Wilma?

Is Wilma HIPAA compliant?

See the whole platform in 30 minutes.

Bring your hardest workflow. We'll show you Wilma end to end — and a price you can model on one line.

Evaluating the switch

What to check when you are outgrowing your current platform

Most switches at this size are not about a missing feature. They are about a system bought for twelve people starting to creak at forty.

• 1Can it bill under more than one entity?Multi-entity billing — separate NPI, tax ID and billing address per location — is the wall most growing practices hit first. Adding a second location should be a settings change, not a second subscription or a second instance to keep in sync.Red flag: A second location handled by 'we would set you up with another account'.
• 2Does access control survive an audit?An RBT should see their clients, a BCBA their caseload, a biller financial data without clinical detail they do not need, and a regional director their region. Roles that can only be scoped by job title push practices into shared logins, which breaks both compliance and the audit trail.Red flag: Access scoped by job title only, with no location or caseload dimension.
• 3What breaks first as volume rises?Ask what the largest practice on the platform looks like, in staff and in clients. A vendor whose biggest customer is your current size cannot tell you what year three looks like, and you will find out yourself.Red flag: No concrete answer about the largest deployment.
• 4Does the price curve match your growth curve?Per-client pricing rises every time you fill a schedule; per-user pricing rises when you hire. Those diverge sharply for a growing practice. Model both against your own three-year projection rather than comparing month one.Red flag: A quote that will not name the unit it is based on.

Before you sign

Questions worth asking on the demo

• Show me multi-entity billing with two NPIs on one account.
• Can I scope a user's access to one location as well as one role?
• What is the largest practice running on this, in staff and clients?
• Is pricing per user or per client, and what does my bill look like at double the caseload?
• What have annual increases actually been for existing customers over three years?

Glossary

The terms you will hear

Single record

Scheduling, data collection, notes and billing reading and writing the same rows, rather than separate systems reconciled on a schedule. It is what makes an unbillable session impossible to bill rather than merely reportable.

Integration seam

The join between two vendors' systems. Where data is copied rather than shared, the seam is where records drift apart and where neither vendor owns the failure.

Clean claim rate

Share of claims paid on first submission with no correction. The clearest single measure of whether the billing half of a platform is actually working.

Authorization units

Billable 15-minute units a payer approved over a date range. Sessions decrement the balance; delivering past it usually means the service is not reimbursable.

Keep reading

Related guides on running an ABA practice — the same operation, from a different angle.

• Raven Health alternativeHow the platforms differ once you look past data collection.
• Lumary ABA alternativeSalesforce-based platforms versus purpose-built ABA software.
• Noteable alternativeNotes and documentation compared against end-to-end practice management.
• CentralReach alternativeWhere Wilma and CentralReach differ on scope, pricing model and rollout.
• ABA practice management softwareOne platform for the whole ABA practice, from first call to paid claim.
• ABA data collection softwareTrial-by-trial, duration, frequency and interval data captured in session, graphed live.