Lumary vs Tendaroo: An Honest Comparison

You're a large or multi-vertical operation. Lumary is built for organisations managing 50+ participants across multiple sites, often with complex multi-vertical delivery — NDIS + aged care + allied health on the same platform. Tendaroo is NDIS-only. If you operate across all three, Lumary lets you keep one tool.

Deep customisation matters. Lumary is built on Salesforce. Everything is customisable — workflows, fields, integrations, reporting — to a degree no non-Salesforce platform can match. Tendaroo is more opinionated; we ship workflows that work and resist building configuration knobs for the sake of it.

You have or can fund Salesforce admin capability. Customisation power comes with admin cost. Lumary deployments either need an internal Salesforce admin or an external Salesforce consultancy on retainer. Tendaroo doesn't have a "Tendaroo admin role" — the software does what the software does.

You're optimising for enterprise scale. Lumary's reporting depth, multi-site cross-tenant visibility, complex rostering scenarios, AI-driven worker-to-participant matching — these matter when you're scheduling thousands of shifts a fortnight across multiple regions. At 30 shifts a fortnight, they're overhead.

You can spare a 3–6 month implementation window. Enterprise software comes with enterprise rollout. Lumary's implementation typically spans requirements gathering, data migration, configuration, testing, and training. If your operation can absorb that timeline, fine. If you need software running this fortnight, look elsewhere.

You're a small-to-mid NDIS provider. Lumary's profile fit starts at ~50 participants. Tendaroo's covers 10–300+ participants. Below 50, Lumary is overspec'd. At 50–150 it's a question of philosophy: configurability (Lumary) vs opinionated defaults (Tendaroo).

You want to be running the software this week, not in Q4. Tendaroo's "import a participant in 15 minutes" path is the opposite end of the time-to-value spectrum from Lumary's 3–6 month implementation. If your buying motion is "we'll evaluate over the next 2 months and decide," Tendaroo will be live in your operation before Lumary's discovery call ends.

You don't have or want Salesforce overhead. Lumary's Salesforce foundation is its biggest strength and its biggest cost. Salesforce admin time, licensing layers, customisation cycles, ongoing maintenance. Tendaroo is built on a standalone Laravel + Postgres stack — no admin role to fill, no recurring consultancy spend, no platform you also have to learn alongside the application.

Pricing transparency. Tendaroo's pricing is on the website. Lumary's requires a sales call. For organisations evaluating multiple vendors against a budget, the transparency itself is a feature.

NDIS-only focus. Tendaroo is built around the NDIS Pricing Arrangements, PACE, Practice Standards. Lumary's NDIS support is part of a broader multi-vertical platform. If your operation is NDIS-only, the depth-vs-breadth trade-off matters: configurable-everything vs purpose-built workflows.

Neither vendor's pricing strategy is "fill out a form and we'll call you to negotiate." Lumary's pricing strategy is exactly that.

Lumary: custom enterprise pricing, no published rates

Lumary doesn't publish prices. Quotes are based on organisation size, participant count, complexity, and required modules. Implementation costs are additional, often substantial, and run for 3–6 months for complex organisations. You're typically buying not just software but a delivery project.

Third-party reviewers describe Lumary's pricing as "enterprise tier, higher than alternatives such as ShiftCare or SupportAbility." Expect total first-year cost (software + implementation + Salesforce admin overhead) to land in the tens of thousands of dollars range for a mid-sized provider, materially more at scale.

Tendaroo: published pricing, transparent, no implementation phase

Tendaroo publishes pricing on tendaroo.com/pricing:

No implementation project. No Salesforce admin overhead. No setup fee on Starter or Growth ($1,500 onboarding included free on Scale).

What the pricing actually means

For most small-to-mid NDIS providers, Lumary and Tendaroo don't really compete — they're priced for different markets. Lumary is for organisations with budget for an enterprise software implementation. Tendaroo is for operations where the monthly software cost is a line item, not a project.

If you're seriously evaluating Lumary, you probably also have:

• A dedicated IT team or external Salesforce consultancy budget
• An operations director who can champion a 3–6 month rollout
• Multi-site operations or complex multi-vertical delivery (NDIS + aged care + allied health)
• Annual software budgets sized in the tens of thousands

If you don't have those, Lumary is probably the wrong shape — not because it's bad, but because it's optimised for a different operation size.

Pricing claims about Lumary reflect third-party reviewer summaries as of April 2026. Request a current quote from lumary.com before deciding.

• You're a mid-to-large NDIS organisation (50+ participants, often multi-site)
• You operate across multiple verticals (NDIS + aged care + allied health)
• You have IT or Salesforce admin capability in-house or budgeted
• You can absorb a 3–6 month implementation timeline
• Your buying process expects detailed quotes, custom configuration, and an implementation partner
• Annual software budget in the tens of thousands or more

• You're a small-to-mid NDIS provider (5–50 workers, 20–300 participants)
• You want to evaluate and adopt without a 3–6 month project
• You're NDIS-only or NDIS-primary
• You don't have Salesforce administration capacity (and don't want to acquire any)
• Pricing transparency and predictability are important
• You want to be running the software this week, not in Q4