Elegant Care Services
NDIS disability support: supported independent living and respite
An NDIS provider's site, with support models the team maintains.
What they would still have been doing by hand.
NDIS support types and their descriptions have to be exact, and they change with the scheme.
A participant or family reading the wrong description is a real problem, not a typo.
Feedback matters in care, and it needs somewhere to go that is not an inbox.
The part the public never sees.
Not a feature list. These are the jobs somebody at the client does in this system, on an ordinary day, without calling us.
Maintain support models
Its own section, because in this sector the support types are the product and they change.
Collect feedback
Feedback captured as records rather than as email, which matters when you are audited on it.
Work enquiries
Leads in one queue, routed to the care team as they arrive.
10 modules, read off the codebase.
Not a claim about what a site like this usually has. This is the list of sections and routes that exist in this project, which is the difference between a portfolio and an inventory.
Australia. Different regulator, same principle: the team controls what the public reads.
We don't build websites. We build the system your business runs on.
The site your customers see is the front of it. Behind it sits the part your team actually lives in: prices, bookings, orders, enquiries, stock, staff. Changed by you, on the day you decide, not by us on a support ticket.
That is the whole difference. A website tells people you exist. A system runs the business, and it keeps running when you are not looking at it.
What would your team stop doing by hand?
Tell us the job somebody in your business repeats every week: the rate change, the booking register, the enquiry that gets written on paper. A senior consultant will map what running it properly would take.