The trigger was watching support workers spend fifteen-plus minutes per shift on paperwork — and then watching supervisors burn entire afternoons stitching those notes together into plan-review packs that the NDIA still wasn’t satisfied with. The data was being captured. It just wasn’t being captured meaningfully.
Every shift note lived in a different folder. Every incident report told a slightly different story. Every plan review started from scratch because no one had a single, longitudinal picture of the participant. Providers were drowning in evidence and producing none of it.
We’ve felt every one of these problems first-hand — on rosters, in back-office finance, sitting across from the NDIA at plan-review meetings. Caredly is the system the team wished they had: a single record per participant, structured data instead of free-text mush, and AI that earns its keep by doing the writing humans shouldn’t have to.
To make every NDIS participant the centre of their own data.
Person-centredness is the language the sector has used for two decades. In practice, almost every system on the market still organises information around the provider — sites, rosters, billing codes, compliance modules. The participant is a row in a table.
Caredly inverts that. Each participant has their own longitudinal record: their plan, their goals, their behaviours, their hospitalisations, their preferences, their wins. Shifts attach to the person, not the other way around. Reports are built from one source of truth rather than reconstructed from fragments.
That’s the mission, and it’s also the operating principle. When a design decision has two paths, we take the one that puts the person first — even when it’s harder to build.
We’re two co-founders. We’ve deliberately kept the team small while we get the foundations right.
A full-stack developer and AI solutions architect with a postgraduate background in artificial intelligence. Has spent years building software for the NDIS and broader healthcare sector — most recently inside aged care, where the daily realities of compliance, shift documentation, and stakeholder reporting shaped Caredly's data architecture.
Fifteen-plus years inside the NDIS sector — across SIL operations, regional management, and director roles at a leading provider. Built and validated, in the field, the data-driven reporting model that Caredly is now packaging into software so every Australian provider can run it.
Four commitments that shape every decision — from the data model right through to the colour of a button.
Software has to bend to the participant — never the other way around. Every workflow, every form, every report begins with a real person and works outward from there.
Funding decisions, plan reviews, and care outcomes all turn on data. We're not interested in claims you can't substantiate. Caredly is built to produce the evidence behind the story.
Designed alongside support workers, supervisors, and coordinators — not for them. Every feature has been pressure-tested by people who actually run shifts.
Built in Australia for Australian providers. Data lives in Sydney. Compliance, language, and funding logic all match the country we work in.
We ship slowly, but we ship. Here’s where Caredly is now and where it’s heading.
Public site, early-access pipeline, and direct conversations with the providers shaping our first release. We're talking to operators across NSW and VIC right now to validate the data model.
Core participant CRM with per-person record architecture, pre-built shift and incident forms, and the first generation of stakeholder-ready reports. The foundation everything else stands on.
Provider-defined forms without engineering tickets. Workflow automation for handovers, escalations, and plan-review cycles. Operational analytics that turn captured data into management decisions.
Per-participant AI assistants that read every shift note ever written. Voice-dictated documentation. AI-generated narrative reports for plan reviews. A live on-call dashboard for after-hours supervisors.
We’re a small team and we’re unapologetic about who we hire next. We’re looking for sector-experienced operators, senior engineers who care about people more than they care about stack debates, and designers who treat compliance as a feature.
If that sounds like you — or someone you know — we’d love to hear from you, even when there’s no advertised role.