Instead of SupportAbility
Stop renewing SupportAbility on its staff brackets. Own the provider system underneath.
We build your version around your services, registration, rostering and claiming rules, map the SupportAbility records that can move, and run it with you. One setup fee, then a retainer.
SupportAbility keeps its monetary price private. Subscriptions are annual, paid upfront and bracketed by active staff, with a 30-staff minimum.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription commits you to
SupportAbility wraps the whole provider record into one annual staff bracket
The vendor does not publish the amount. It does publish the shape of the bill: an annual subscription paid upfront, sized by active staff, starting at a 30-staff bracket and including every module whether you use each one or not.
A full year paid at the start
SupportAbility says every subscription is annual and paid at the beginning of the subscription year. The renewal decision arrives as one commitment, not a month-by-month choice.
The bracket follows everyone who logs in
Active staff include people entering case notes, signing off timesheets or generating invoices. SupportAbility says admin staff do not receive a different rate.
The first bracket begins at 30 staff
The published subscription FAQ says the smallest subscription is for 30 staff, even though the product can be used by a sole operator.
All modules come as one bundle
Every subscription includes all modules and features. SupportAbility says the fee cannot be reduced when a provider chooses to use only part of the product.
Some specialist services sit outside the bundle
Data replica subscriptions, training installations and custom finance or payroll integrations are listed as services that may carry additional fees.
Leaving creates a mapping project
SupportAbility provides a final raw data and document extract after the installation is offline. Its own guidance says the replacement provider must map records spread across multiple CSV files, while readable report exports need to be collected before shutdown.
What replaces the bundle
A provider record shaped around your services
Funding
See delivery, budget pace and claims together
Funding is joined to the support actually delivered, so finance and service teams work from the same record.
- check Track each service agreement against its dates, rates and remaining budget
- check Name agreements running under pace before the next plan review
- check List delivered shifts that still have no payment request
- check Keep every rejected claim visible with its recorded reason until it is resolved
Delivery
Put the checks inside the roster
The system checks the conditions for safe, claimable work when the shift is planned and completed.
- check Block a roster assignment when the worker's screening clearance will not be current
- check Stop overlapping shifts and work outside a signed, current agreement
- check Require the progress note before delivered support can move toward a claim
- check Record cancellation notice and apply your short-notice rule consistently
Assurance
Make overdue evidence impossible to hide
Incidents, worker records and service evidence stay on the attention list until the required action is recorded.
- check Keep reportable incidents open until the Commission notification is recorded
- check Show lapsed screening, missing notes and expiring plans in one review
- check Produce worker files, incident reports and participant statements in your brand
- check Retain exited participants, former workers and claim history instead of deleting the audit trail
Control
Change the operating record when your service changes
Your fields, rules and reports live with your organisation, not inside a vendor's product roadmap.
- check Ask questions across participants, workers, shifts, incidents and claims in plain language
- check Add a field, funding rule or review without waiting for a packaged feature
- check Connect payroll and finance around the database you own
- check Keep the free foundation or have Enterprise DNA adapt and operate it for you
Make it yours
Design your own SupportAbility replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from SupportAbility. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your SupportAbility data across and run it for you.
Switching
How to switch from SupportAbility
The move involves exporting the records your account allows, mapping them to the new layout, and checking the results before you stop using SupportAbility.
- 1
Export your SupportAbility records
Export readable client, staff, activity, hours and incident reports from SupportAbility. The available export options depend on your account, so check with SupportAbility about what you can export and how. SupportAbility also provides a complete raw data and document extract after termination. Plan how to obtain that extract as part of your move, and keep the exported material available for checking.
- 2
Load the records
Use the import to bring the mapped records it supports into Home Care for Claude Code. The free version expects a different export layout from SupportAbility, so the records need mapping before they fit. If your import offers a test run, use it before loading the records for real. Check that the data you intend to bring across is included, especially if you are using reports rather than the raw extract.
- 3
Review the import flags
Go through the issues the import flags and decide what needs fixing before you rely on the new records. The import is an audit as well as a transfer. For example, a client may have no recorded funding type, or a shift may have no covering service agreement. Check those records against SupportAbility and your own information, then correct the mapping or the underlying record as needed.
- 4
Run both systems side by side
Keep SupportAbility in use during the transition while you check the new records against it. Compare the clients, staff, activity, hours and incident information you rely on, and make sure unresolved import issues are understood. This gives you a chance to catch missing or mismatched records before the new system becomes the one you depend on. Agree who will check each part of the operation.
- 5
Switch off SupportAbility
Once you have checked the imported records and are satisfied the new system is ready for your operation, stop using SupportAbility. Arrange access to its complete raw data and document extract after termination, as SupportAbility says it provides this then. Keep the extract with your business records so you can refer back to it if needed.
Where the real effort goes
The real work is usually mapping your own SupportAbility fields and rules to the new layout, then deciding how much history to bring across. Readable reports cover clients, staff, activity, hours and incidents, while the raw data and document extract is available after termination. If Enterprise DNA runs the move, the mapping and reconciliation are part of that work.
Not ready for a call?
Get your SupportAbility switch plan by email
We will send you the step-by-step plan for moving your business off SupportAbility, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your SupportAbility switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways forward
Run the free foundation, or have us build and operate yours
Open source
Do it yourself
Free, open source
- 1 Clone the repo from GitHub and run npm run demo
- 2 Open it in Claude Code and ask what needs attention
- 3 Export SupportAbility client, staff and activity reports as CSV files
- 4 Ask your coding agent to map those columns to the ShiftCare-format import before loading them
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a retainer
- check We decide which readable reports and raw records need to move before SupportAbility goes offline
- check We map the records that can move, then check the result with you
- check We configure your registration, service, claiming and compliance rules
- check We add the worker-facing screens or phone experience your team needs and run it inside Omni by Enterprise DNA
Questions
Instead of SupportAbility, answered
SupportAbility does not show a price. How do we compare the cost? expand_more
Bring your current invoice, renewal notice and active-staff bracket to a 30-minute call. We compare the annual subscription and any extra services with the setup and ongoing work your own version needs. If the subscription remains the better fit, we will say so.
Can our SupportAbility history actually come across? expand_more
Some of it can, but it needs mapping. SupportAbility lets you export readable client, staff, activity, hours and incident reports. After termination it also provides a complete raw data and document extract. The free version expects a different export layout, so you map the SupportAbility records yourself; when Enterprise DNA runs the move, the mapping and reconciliation are part of the work.
What replaces the SupportAbility mobile app? expand_more
The free foundation has no worker phone app. It is useful for the coordinator, finance desk and owner. If workers need a phone experience, Enterprise DNA scopes and builds it around the same database.
Does owning the database make us NDIS compliant? expand_more
No system makes a provider compliant by itself. The foundation enforces useful record checks such as current screening before rostering, notes before claiming, incident follow-up and retained history, with the rules documented for review. Your organisation still decides whether an incident is reportable and remains responsible for its obligations.
We are a New Zealand disability provider. Is SupportAbility the right comparison? expand_more
SupportAbility's public material is built around Australian NDIS delivery. The underlying work is still familiar in New Zealand: people, funding agreements, rosters, notes, incidents and claims. Enterprise DNA replaces the Australian rules with your funder's contract, reporting terms and local operating requirements when building your version.
Price the system you need, not the staff bracket you inherited
Bring your SupportAbility invoice, active-staff bracket and the reports your team relies on. In 30 minutes with Sam, we separate the records you must keep from the product around them, identify what a safe move would involve, and outline the provider system your organisation would own. If it fits, Enterprise DNA builds and runs it. If it does not, keep SupportAbility or take the free foundation and run it yourself.
Home Care for Claude Code is free and open source, published by Enterprise DNA.
Done paying for SupportAbility?
Get your version built