For practices that want self-contained software.
All-in-one — without the Salesforce overhead.
Lumary is enterprise ABA software built on Salesforce. Wilma is a self-contained all-in-one built by people who actually ran ABA practices — thought through end to end, with flat published pricing and no Salesforce overhead. Agentic AI and a built-in phone come on top.
Why operators compare them
Why practices choose Wilma® over Lumary.
All-in-one, done right — built by operators.
Lumary is enterprise all-in-one built on Salesforce. Wilma is all-in-one built from the ground up by people who actually ran ABA practices — a self-contained platform, thought through end to end, with no third-party platform to license or administer. That cohesion is the part operators call "impressive."
Self-contained — not built on Salesforce.
Lumary is built on the Salesforce platform, which can mean underlying Salesforce licensing and admin overhead. Wilma is a self-contained ABA platform — one system, no third-party platform dependency to license or administer.
Flat, published pricing.
Lumary is quote-only and, as a Salesforce-native product, customers often also bear Salesforce costs. Wilma publishes flat per-user pricing you can evaluate up front.
Agentic AI + built-in phone.
Wilma's agentic AI drafts notes and scrubs claims, and the platform includes native telephony/IVR. Lumary doesn't advertise these.
Right-sized for small and mid as well as enterprise.
Lumary is enterprise-positioned. Wilma scales from a single clinic on the full platform to multi-state, without replatforming — at flat per-user pricing.
Side by side
Wilma® vs Lumary, feature by feature.
| Capability | Wilma | Lumary |
|---|---|---|
| Self-contained (no third-party platform) | ✅ Native | ⚠️ Built on Salesforce |
| Practice management, billing/RCM, analytics | ✅ Native | ✅ Enterprise-grade |
| Credential-expiry tracking | ✅ Native | ✅ Yes |
| Built-in phone & IVR | ✅ Native | ❌ Not advertised |
| Agentic AI (notes + claim scrubbing) | ✅ Core of the platform | ❌ Not advertised |
| Fit for small practices | ✅ Full platform on entry tier | ⚠️ Enterprise-positioned |
| Pricing model | ✅ Flat $30/user, 10 min | ⚠️ Quote-only (+ Salesforce) |
| Published pricing | ✅ Yes | ❌ Quote-only |
Comparison based on publicly available information as of June 2026. Lumary is a trademark of its respective owner.
What you get on Wilma
What changes on one agentic platform.
No platform tax.
A self-contained system with no underlying Salesforce licensing or admin overhead to carry.
Transparent, flat cost.
Per-user pricing you can model in a spreadsheet, not a quote shaped by platform licensing.
Agentic AI + native phone.
Notes drafted, claims scrubbed, calls threaded to the record — built in, human-approved.
Scales down as well as up.
Full platform for a single clinic; grows to multi-state without replatforming.
Pricing and reviews
Comparing Lumary 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 a Lumary pricing page or quote requires a sales process.
Review signals
When reading Lumary 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 Lumary alternative?
Is Lumary built on Salesforce?
How does pricing compare?
Is Wilma only for small practices?
Does Wilma include a phone system? Does Lumary?
Can I migrate from Lumary 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 the platform sits on someone else's stack
Some ABA platforms are built on top of a general enterprise platform rather than from scratch. That brings genuine enterprise plumbing and a set of costs and constraints worth naming before you sign.
- 1Whose licence are you actually buying?Where an ABA product is built on an underlying enterprise platform, there can be licensing, support and upgrade implications from that layer as well as from the vendor. Ask plainly whether any part of your cost or upgrade timing depends on a third party.Red flag: Uncertainty about whether an underlying platform licence is included.
- 2How ABA-specific is the clinical layer?General platforms model records and workflows well and know nothing about trial-level data, prompt levels, task analyzes or authorization units that decrement. Check how deep the ABA layer goes rather than how capable the foundation is.Red flag: Program data held as attachments or custom fields rather than structured, graphable records.
- 3What does configuration cost in time?Highly configurable platforms are powerful and rarely fast to change. Ask what a routine change — a new program target type, a new payer rule — takes in practice, and whether it needs the vendor or a consultant.Red flag: Routine changes that require a professional-services ticket.
- 4Is the implementation a project or an onboarding?Enterprise implementations run in months and carry real cost. That can be entirely worth it at scale and is disproportionate for a 25-person practice. Match the implementation model to your size honestly.Red flag: An implementation timeline measured in quarters for a practice measured in dozens.
Before you sign
Questions worth asking on the demo
- Does any part of my cost or upgrade schedule depend on an underlying platform vendor?
- Show me trial-level data and a task analysis stored as structured records.
- How long does adding a new payer rule take, and who does it?
- What is the implementation timeline and fee for a practice my size?
- What does export contain if I leave — structured clinical data or documents?
Glossary
The terms you will hear
- Modular pricing
- A base platform with capabilities sold as separate line items. The quoted figure depends entirely on which modules are in the bundle, which is why reported prices for modular platforms vary so widely.
- Implementation fee
- A one-time charge for configuration, migration and training. Often four figures, frequently negotiable, and routinely left out when buyers compare monthly rates.
- Annual uplift
- The yearly price increase applied to existing customers. Ask what it has actually been for three years, not what the contract permits — those are different numbers.
- Total cost of ownership
- Subscription plus implementation, migration, per-claim fees, module add-ons and uplift, modelled across three years. The ranking of vendors often changes between year one and year three.
Keep reading
Related guides on running an ABA practice — the same operation, from a different angle.
- Noteable alternativeNotes and documentation compared against end-to-end practice management.
- ABA Engine alternativeA feature-by-feature comparison for practices evaluating both.
- SimplePractice alternativeWhy general therapy software struggles with ABA authorizations and EVV.
- 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.