Tendaroo
How it works Pricing Why switch Trust & Security Integrations About Contact
Our story

We built Tendaroo because we lived the problem.

Before Tendaroo was a line of code, it was a year spent running the operations of an NDIS provider — rostering the shifts, chasing the claims, and watching a reportable-incident clock tick while the right screen was three menus away.

We knew the software could be calmer, safer and honest about its terms. So we built the one we wished we'd had.

A support professional smiling warmly outdoors — the people this work is really about
What we lived

Three things kept going wrong. None of them had to.

A year inside a provider taught us where the day actually breaks. Not in a demo — in a car park with no signal, on the worst morning of the week, in a claim batch that bounced without explanation.

Compliance risk you carry alone

A reportable incident lands, and it's on you to remember the 24-hour clock is running. Miss it and it isn't a bad UX day — it's your registration. We wanted the deadline to run itself.

So we built the statutory clock.

Admin drowning the actual work

Roster in one place, claim in another, reconcile the remittance by hand in a spreadsheet. The tool made more admin than it removed. We wanted the numbers to line up on screen, the first time.

So we check every claim before it leaves.

Workers losing the app in the field

Out in the community and in group homes — full of dead spots — the app just went blank. No plan, no meds, no clock-in, no note, and no message saying why. That's unsafe care and lost billing, every day.

So we made it work offline.

A note from the founder

I didn't set out to build software.

I set out to run good supports. For a year I ran the operations of a small NDIS provider — the rosters, the timesheets, the claims, the incidents, the audits. I learned exactly how much of a provider's week goes to fighting the tools instead of doing the work.

The pattern was always the same: the software looked fine in a sales call, then quietly let you down at the moment that mattered. A signature pad that accepted a blank signature. A claim file that bounced over one empty field. An app that went dark the second a worker drove out of range.

Tendaroo is my answer to that year. It's opinionated where the stakes are high — it won't let a reportable incident slip, or a claim leave with a mistake in it — and it's calm everywhere else. No lock-in, no setup invoice, no fine print. If it isn't for you, you can walk away with your data and owe us nothing.

We're a small, Australian team, and we intend to stay close to the people who actually use this every day. If that's you, I'd genuinely like to hear from you.

Tendaroo's founder

Former NDIS provider operations lead · Australia

Hands gesturing over a laptop during a planning session
Built from the operator's chair, not the boardroom.
What we believe

Three values, and you can hold us to them.

These aren't posters on a wall. Each one shows up as something concrete in the product.

Calm

Care work is stressful enough. The product is quiet by design — plain words, no shouty alerts, one clear next step. It should lower your heart rate, not raise it.

Shows up as: statutory clocks that count down calmly, errors that name the fix, no dark patterns.

Honest

Every price is on the pricing page — GST-inc and GST-ex, both shown. Month-to-month, no exit fees, your data is yours. Nothing hidden behind "contact sales".

Shows up as: public pricing, a plain-English data whitepaper, export anytime.

Provider-first

We build for the person doing the work, not the person signing the deal. Real NDIS vocabulary, real field conditions, and onboarding that's included — never sold as a service.

Shows up as: an offline-first field app, free migration, a knowledge base that is the onboarding.

Australian-built, Australian-hosted

Your participants' data never leaves the country.

Tendaroo is founded and run in Australia, for Australian providers, and hosted in Google Cloud Sydney (australia-southeast1). We know the sector because we work in it — the vocabulary, the price guide, the Commission's timeframes, the PACE claim file. It isn't localised from somewhere else; it's from here.

100%

AU data residency

$0

Setup & migration

M2M

No lock-in

Why no lock-in

If we have to trap you, we haven't earned you.

Annual contracts and exit fees exist to keep customers who'd otherwise leave. We'd rather build a product good enough that you stay because it works. So: month-to-month, cancel anytime, full export whenever you want it, and a 90-day hold on your data after you go — in case you need it.

  • Month-to-month, no minimum term, no exit fee.
  • Your data exports any time — JSON plus a readable PDF pack.
  • Stop paying and you drop to read-only — never deleted.
A product that teaches itself

Onboarding is built in, not billed.

We're a small team, and we couldn't staff an army of account managers even if we wanted to. That constraint became a principle: if the software needs a paid consultant to be usable, the software is wrong. So the guidance lives inside the product — a checklist that deep-links to the next step, plain empty states that tell you what to do, and a public knowledge base that is the onboarding.

  • Guided setup checklist with free CSV importers.
  • Short video per real flow — intake, shift-to-pay, audit pull.
  • In-app help that lands on the answer, never a dead end.
Open the Knowledge Base

Come build the calmer way with us.

Start a free trial with your own data, or just send us a note. We read every one.