Enterprise DNA

Instead of CareCall

Stop renting CareCall for your own care hours. Own your home support system.

We build your version around your funder contracts and the way your coordinators schedule, bring your CareCall clients, workers and visits across, and run it for you.

Netsoft does not publish CareCall pricing. Cost is set by private quote.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the CareCall arrangement covers

A quoted contract wrapped around records your organisation already creates

Clients, support plans, workers, visits, notes and claims to ACC, Te Whatu Ora and Whaikaha. Those are the asset. Netsoft prices the system that holds them by private quote, so the number is whatever your contract says.

request_quote

No public price to check against

Netsoft lists no CareCall price, plan or licence model. You find out what you pay in a sales conversation, and you cannot see what a provider your size pays elsewhere.

phone_iphone

The worker app is its own product

Remote Worker, the phone app that gives support workers their schedule, route and visit verification, is listed as a separate Netsoft product next to CareCall.

account_balance_wallet

Individualised Funding is a separate module

Managing Individualised Funding under Whaikaha contracts sits in its own module.

route

Travel and guaranteed hours inside their logic

In between travel and guaranteed hours are handled the way the software was built to handle them, and fitting them to your own needs means customising Netsoft's system.

query_stats

Questions that cut across records

Which clients got fewer hours than their plan, which workers are close to a clearance date, which funder claims came back: Netsoft's pages do not describe asking questions like these across records.

lock

Your care history on their platform

Netsoft's pages describe no self-serve export. Years of visits and notes sit in a system you rent.

What your organisation runs instead

One home support record for every funder, kept by you

Scheduling

Visits that cannot be booked wrong

The schedule refuses a booking that breaks a rule, instead of a report finding it next month.

  • check No visit for a worker whose clearance has lapsed by the visit date
  • check No visit outside a current, signed support agreement
  • check No worker booked with two clients at the same time
  • check Late cancellations kept with their notice, so you know what can still be claimed

Funders

Each contract's rules written into your version

The free version ships with the Australian NDIS rules. For a New Zealand provider, we write your contracts in instead.

  • check ACC, Te Whatu Ora and Whaikaha contract terms set up as your own rule book
  • check Each rule recorded with the contract clause it comes from
  • check Your travel and guaranteed hours arrangements written the way your staff agreement reads
  • check A new contract added by describing it, not by buying a module

Money

Delivered hours followed through to paid

Coordinators see care that was delivered and never claimed, before the month closes.

  • check Completed visits with a note and no claim, oldest first
  • check The claim file prepared for a person to check and send to the funder
  • check Rejected claims kept in view with their reason until they go back in
  • check Hours delivered against each client's plan, so under-delivery shows early

Ownership

A record that stays when the contract ends

Your database, your rules and your name on the paperwork.

  • check No quote to renew and nothing charged per worker or per coordinator
  • check Nothing deleted: former clients and former staff stay on record
  • check Incident reports and client statements produced in your own brand
  • check Free and open source, so there is no subscription to leave

Make it yours

Design your own CareCall replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from CareCall. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your CareCall replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your CareCall data across and run it for you.

Switching

How to switch from CareCall

A move involves requesting your records from Netsoft, mapping them to the new database, checking the import, and running both systems side by side before you switch.

  1. 1

    Request your records

    Netsoft does not describe a self-serve export, so ask them how to get your CareCall records as files. Request your clients, workers, agreements and visit history. Ask what export formats are available, such as CSV or Excel, and check with CareCall if you are unsure what your account allows.

  2. 2

    Load the records

    Use the import process to bring your files into Home Care for Claude Code. If the import offers a test run, start with that before loading the records for real. The aim is to bring across the records you requested, not to assume every CareCall field has a direct match in the new database.

  3. 3

    Review import flags

    After the import, check what it flags before relying on the new records. Look closely at clients without funding details, visits without a covering agreement, and any fields or records that did not map cleanly. Resolve those gaps or decide how to handle them before your team treats the new database as the source of truth.

  4. 4

    Run both systems

    Keep CareCall running while you use the new database alongside it for a short period. Compare the records and day-to-day work you need to rely on, including clients, agreements, workers and visit history. Use the overlap to catch missing or mismatched information and settle any process questions before you stop using CareCall.

  5. 5

    Switch off CareCall

    Once you have checked the imported records and are ready to rely on the new system, make the switch and stop using CareCall. Keep the exported files and your agreed record of what was moved, so you can refer back to them if questions come up after the change.

construction

Where the real effort goes

The real work is usually mapping your own CareCall fields to the new records, setting the rules that match your funder contracts, and choosing how much history to bring across. Some fields or rules may not carry over directly, so the import needs review rather than a blind copy. When Enterprise DNA runs the move for you, they request the files, map the columns and test the result before you switch.

Not ready for a call?

Get your CareCall switch plan by email

We will send you the step-by-step plan for moving your business off CareCall, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Two ways to switch

Try the free version, or have us build and run yours

Open source

Run it yourself

Free

  1. 1 Clone the repo from GitHub and run npm run demo on the sample data
  2. 2 Open the folder in Claude Code and type /attention
  3. 3 Ask Netsoft for your clients, workers and visit history as files
  4. 4 Ask Claude Code to map the CareCall columns to the import, do a test run, then load them
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA build and run it

One setup fee, then a monthly retainer

  • check We get your records out of CareCall, map them across and check the totals before you switch
  • check We write in your ACC, Te Whatu Ora and Whaikaha contract rules and your Individualised Funding work
  • check If your team needs one, we add a support worker phone app for schedules and visit notes, and connect your payroll and accounts
  • check It runs inside Omni, our managed Command Centre, beside the rest of your business
Book a discovery call

Questions

Instead of CareCall, answered

The free version is built for the NDIS. Does it suit a New Zealand provider? expand_more

The records are the same: clients, agreements, workers, visits, notes, incidents and claims. The rules are not. When Enterprise DNA builds your version, we replace the NDIS rule book with your own funder contracts and reporting, so the checks match what your funders ask of you.

Our support workers rely on the Remote Worker app. What replaces it? expand_more

The free version has no phone app today. A simple app for workers to see their schedule, confirm visits and write notes is part of the version we build for you when your team needs one.

How do we get our records out of CareCall? expand_more

Netsoft's pages do not describe a self-serve export, so start by asking Netsoft for your clients, workers, agreements and visit history as files. When we do the move, we request those, map the columns across and run a test against CareCall before you switch it off.

We have hundreds of support workers. Can this handle that? expand_more

Yes. It is a database, and nothing about it is priced per worker. What we scope with you is the worker app, the funder claiming and the payroll connection, not seats.

Is this an approved system for our funders? expand_more

It keeps the records your contracts ask for, with each rule written down beside its source, and nothing is ever deleted. Whether your reporting meets a particular contract stays your call and your funder's. None of this is legal advice.

See what your own home support system would look like

30 minutes with Sam. Bring your CareCall contract and the list of funders you deliver for. We go through what you pay Netsoft and for which pieces, what your coordinators use every day, and sketch the version we would build and run for you. If it fits, we build it and move your records across. If it does not, the free version is still yours.

Home Care for Claude Code is free and open source, published by Enterprise DNA.

Done paying for CareCall?

Get your version built