Instead of Lookout
Paying Lookout for a platform you cannot price ahead? Own your home care system.
We build your version around your funding mix, your service types and the way your rosterers really work, move your Lookout Members, Helpers and visit history across, and keep it running for you. One setup fee, then a monthly retainer.
Lookout publishes no price. Its pricing page offers a demo, a sales contact and a phone number, so every provider's bill is quoted privately.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
Where a Lookout bill comes from
Modules, two apps and a set of agents, priced in a conversation
Under the platform are records any home care provider keeps: who receives care, what funds it, which Helper is rostered, what happened at the visit and what got claimed. Lookout spreads those across care management, rostering, finance, reporting and its Assist agents, then quotes each provider on its own.
Pricing starts with a sales call
The pricing page has no plans or figures, only a demo booking, a contact form and a 1300 number. You cannot compare Lookout against another option until sales has seen you.
Care, rostering, finance and reporting as separate modules
Each is presented as its own part of the platform, from care plans and risk alerts through rostering margins to budgets, claiming and statements.
Lookout Assist agents for routine chores
Agents handle repeatable admin under human oversight, inside Lookout.
The Support at Home changeover inside their tools
Remapping visits to the new service types, building price lists and testing draft budgets all happen inside Lookout's tools.
Ask what a quote leaves out
Ask which modules and extras a quote leaves out.
Your history comes out one export template at a time
Getting records out means ready-made reports or building templates in the Data exporter, with financial reports visible only to staff holding the Finance Admin permission.
What you hold instead
One record of who you support, who visits and what was claimed, in your name
People and funding
Every client, the money behind their care, and how fast it is being used
The funding view that usually needs a budget screen and a spreadsheet becomes something you simply ask about.
- check Each client's agreement tracked from start date to end date, with spend compared against where it ought to sit today
- check Budgets drifting under or over are flagged weeks before the next review
- check Who manages the funds is recorded on every client, so each claim goes to the right place
- check No per-seat pricing as your roster grows
Roster
Bookings that check themselves before a worker is sent
The questions a rosterer asks in their head get asked by the system every time a visit is booked.
- check A worker whose screening clearance has expired cannot be booked
- check No visit is booked outside a current, signed agreement, and nobody is rostered to two homes at once
- check A visit stays open until its note is written
- check Short-notice cancellations keep their notice period and are claimed by the rule
Claims and incidents
Delivered visits turned into claims, serious events closed off properly
Finance asks a plain question and gets the list back, with no export template to build first.
- check Every visit with a note and no claim yet, oldest at the top
- check Bulk claim files prepared at the agreed rate, ready to lodge
- check A reportable incident stays open until the regulator's notification is recorded
- check Rejected claims keep their reason on file until they are sent again
Yours to change
Rules, fields and paperwork you can rewrite by asking
An open licence, records in your own database, and documents that carry your own logo.
- check New service types, fields or checks added by describing them
- check Worker files, incident reports and client statements printed under your brand
- check Nothing is ever deleted, so seven years of history stays on hand
- check Payroll and accounting connected where agreed
Make it yours
Design your own Lookout replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Lookout. 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 Lookout data across and run it for you.
Switching
How to switch from Lookout
A move involves exporting the records you need, mapping Lookout’s columns to the new database, checking the import, and running both systems together before you switch.
- 1
Export your records
Use Lookout’s Data exporter to build CSV or JSON templates with the columns you need. Export the records you plan to bring across, such as clients, workers, funding, visits, notes and claims. Lookout also has reports for Members, Helpers, tickets and visits. Check what your account allows you to export, and ask Lookout about any records you cannot find.
- 2
Load the records
Load the exported records into Home Care for Claude Code through its import process. Have the import run as a test first if that option is available, before relying on the imported data. Lookout’s columns differ from the fields the new system expects, so they need to be matched. If Enterprise DNA is running the move for you, they handle that mapping.
- 3
Review import issues
Check every issue the import reports before using the new records for day-to-day work. For example, the import can flag a shift with no covering service agreement or a client whose funding type is missing. Fix the source record or field mapping, then check the affected data again. Pay particular attention to funding details and any service types remapped in Lookout.
- 4
Run both systems together
Keep Lookout running while you check the new system against it for a short period. Compare the records and operational details you rely on, including clients, funding, visits and claims. Resolve differences before you make the new database your working record. If you have just moved to Support at Home in Lookout, include the remapped service types and visit history in those checks.
- 5
Switch off Lookout
Switch off Lookout only when the two systems agree on the records you have chosen to bring across. Before then, keep using Lookout as your reference while you resolve any remaining differences. Once your checks are complete, make Home Care for Claude Code the working record and stop relying on Lookout for day-to-day operations.
Where the real effort goes
The main work is usually matching your own Lookout fields to the new database, setting the rules for your funding streams, and deciding how much history to bring across. Support at Home, Home Care Packages and CHSP may need specific setup. If you have Enterprise DNA run the move, they build the templates, map the fields and check the records side by side with you.
Not ready for a call?
Get your Lookout switch plan by email
We will send you the step-by-step plan for moving your business off Lookout, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Lookout switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways off Lookout
Run the free version yourself, or have us build and run yours
Open source
Do it yourself
Free
- 1 Clone the repo from GitHub and run npm run demo
- 2 Open the folder in Claude Code and type /attention
- 3 Use Lookout's Data exporter to build CSV templates for Members, Helpers and visits
- 4 Ask Claude Code to map those Lookout columns to the import, then load your records
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a monthly retainer
- check We build the Lookout export templates, map every column across and check the result against Lookout before you switch
- check We set it up for how you are funded: Support at Home, Home Care Packages, CHSP, NDIS or private fees
- check We add a care worker phone app or web screens where your team needs them
- check It runs inside Omni, our managed Command Centre, beside the rest of your business
Questions
Instead of Lookout, answered
Lookout is built for Australian aged care. Is this? expand_more
The free version is built around the NDIS rules. Support at Home, Home Care Packages and CHSP, with their service types, contributions and claiming, are what Enterprise DNA writes into your version, so one record covers every client whatever funds their care. We will be plain on the call about how much of that work your mix needs.
How do we get our records out of Lookout? expand_more
Lookout has ready-made reports for Members, Helpers and visits, and a Data exporter that builds CSV or JSON templates with the columns you choose. Those columns differ from what the free version expects, so they need mapping. When we do the move, building the templates, mapping and checking side by side are our job.
Our workers and clients use the Lookout apps. What happens to that? expand_more
The free version has no phone app today. If Helpers need their roster and notes on the road, Enterprise DNA builds that into your version, working from the same database your office uses.
We have just moved to Support at Home inside Lookout. Is now the wrong time to switch? expand_more
Your visit history and the remapped service types come out through the exporter like any other records. Keep Lookout running while we check the new system against it, and switch off only when the two agree.
Is it compliant? expand_more
It keeps the record-keeping shape the rules describe: clearances checked before a booking, a note before a claim, rates held at the agreement, notification before an incident closes, and nothing deleted. Each rule cites its source. Deciding whether an event is reportable stays with you, and none of this is legal advice.
Find out what Lookout really costs you before the next renewal
Bring your Lookout quote or invoice and a list of the modules your coordinators and finance team open each week. In 30 minutes with Sam we work through what you pay for, what your team depends on, and how your own system would look with your funding mix and service types built in. If it fits, we build and run it for you. If it does not, the free version is yours to keep.
Home Care for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Lookout?
Get your version built