Software Comparison
Teiro vs Lumary: an honest comparison for NDIS providers
This page is written for operations managers and coordinators evaluating both platforms. Lumary is a genuine enterprise product with real capability. We have tried to represent it accurately, including where it is the stronger choice.
Lumary is built on Salesforce and is designed for large NDIS providers running multiple service streams -- direct support, plan management, and support coordination -- where the depth of billing and case management configuration justifies months of implementation work and enterprise-tier pricing. For that market, it is a serious tool.
Teiro is built for providers whose primary challenge is modern, compliant rostering and carer management -- without a six-month implementation project to get there. The platforms serve different needs. The right choice depends on the size and complexity of your operation, not on which product has more features.
Feature comparison
The table below covers the dimensions that matter most to coordinators and operations managers evaluating NDIS workforce management platforms.
| Feature | Lumary | Teiro |
|---|---|---|
| NDIS rostering | Configurable via Salesforce and handles complex multi-service workflows, but requires specialist configuration before the rostering layer is tuned to your operation. The depth is real; so is the setup overhead. | NDIS-specific rostering out of the box: SCHADS enforcement, qualification blocking at point of assignment, participant continuity preferences, and line item mapping with no prior configuration required. |
| SCHADS Award compliance | SCHADS support exists within the platform, but accuracy depends on how the implementation was configured. Edge cases -- broken shifts, sleepover disturbance pay, casual public holiday rates -- are only as right as the configuration that models them. | SCHADS rates are calculated at the rostering layer by default for every shift type: weekday day and evening, active nights, sleepovers, broken shifts, Saturday, Sunday, and public holidays including the correct casual rate. |
| Mobile carer app | A carer-facing mobile app is available. Because Lumary runs on Salesforce infrastructure, the mobile experience carries the interface conventions of that platform -- functional for administrators, less natural for support workers using a phone in the field. | Purpose-built mobile app for support workers: GPS check-in and check-out, shift details, incident reporting, and document capture. Designed for daily field use, not platform administration. |
| Implementation time | Typically months, with an implementation project managed by specialist Lumary consultants. This is not a criticism -- the platform is genuinely complex to configure correctly -- but it is a real cost in time and money before you are operational. | Most providers are running live rosters within a week. Participant records, worker credentials, SCHADS calculations, and qualification enforcement are configured at setup, not in a separate implementation project. |
| Pricing model | Quote-only enterprise pricing, negotiated per organisation. No publicly listed rates. Implementation consulting is an additional cost on top of the licence. The total cost of ownership is higher than most mid-size providers expect going in. | Transparent per-user pricing on the website. Free for 5 or fewer active users -- the full platform, no trial expiry, no credit card required. No implementation project cost. |
| NDIS billing | Deep billing capability including plan management, support coordination, and PRODA/PACE submission. Lumary's billing depth is a genuine strength for large providers running complex funding arrangements across multiple service streams. | NDIS billing included: SCHADS rate automation, line item mapping, service agreement tracking, claim management from draft to paid, and budget dashboards. Suited to direct support providers. Not the right fit for large-scale plan management operations. |
| Best suited to | Large NDIS providers (typically 100+ staff) running multiple service streams -- direct support, plan management, and support coordination -- where the depth of billing and case management configuration justifies the implementation investment. | Mid-size providers (20--200 staff) whose primary challenge is modern rostering, SCHADS accuracy, qualification enforcement, and carer app adoption. Providers who need to be operational quickly without an enterprise implementation project. |
Information based on publicly available product documentation and coordinator feedback as of June 2026. Features change; verify directly with each vendor.
Where Lumary is strong
Lumary is a serious platform with genuine strengths. If you are evaluating it honestly, these are the areas where it has real advantages over a mid-market competitor like Teiro:
Plan management and support coordination depth
Lumary's billing stack is built for organisations running plan management and support coordination alongside direct service delivery. The depth of funding model configuration -- multiple funding types, complex participant plan structures, and PRODA/PACE submission -- is a genuine advantage for providers operating at that scale.
Multi-service stream coverage
For a large provider managing NDIS direct support, plan management, support coordination, and possibly CHSP or HCP programs from a single platform, Lumary's Salesforce-based configurability lets the platform be shaped to match the service structure. Most mid-market platforms are not designed for that breadth.
Salesforce ecosystem integration
Organisations already running other operations on Salesforce -- CRM, fundraising, HR -- can integrate Lumary into that ecosystem. For large organisations with established Salesforce infrastructure, that interoperability has genuine value.
Configurable reporting for complex compliance
Providers with reporting obligations across multiple funding bodies -- state-funded programs, CHSP outcomes, NDIS audit evidence -- benefit from Lumary's configurable reporting capability. Larger organisations with dedicated data and compliance teams can build the reports they need.
Where Teiro is different
Teiro is narrower in scope than Lumary. That is a deliberate choice. The platform is built specifically for the operational core that coordinators at mid-size NDIS providers spend most of their time in.
Operational from day one, not month three
Lumary implementations are typically measured in months. Configuration, data migration, consultant time, and staff training are all part of the project before you are rostering live shifts. Teiro is designed to be functional within a week for a standard NDIS direct support provider: participant records, worker credentials, SCHADS calculations, and qualification enforcement are built in, not configured in. You do not need a Salesforce specialist to get started.
SCHADS at the rostering layer, not the billing layer
In Teiro, SCHADS penalty rates are calculated at the point of rostering -- before a shift is confirmed. The loaded cost of a broken shift, sleepover, or Sunday shift is visible to the coordinator before assignment. In platforms where SCHADS is handled at billing or payroll export, coordinators find out about rate errors after the work is done. Teiro surfaces the cost at the decision point.
A mobile app built for support workers, not Salesforce users
The Teiro carer app is designed for a support worker picking up a shift on their phone before their morning commute, not for a platform administrator. The daily workflow -- view shifts, check in, check out, report incidents, capture documentation -- is simple by design. Lumary's mobile experience inherits the conventions of Salesforce, which works for the right users and creates friction for others. Carer app adoption matters: if workers are not checking in and out consistently, the compliance benefit of any platform is reduced.
Pricing you can evaluate without a sales call
Lumary's pricing is negotiated per organisation. Getting to a number requires a discovery process. Teiro lists pricing publicly. Free for 5 or fewer active users. Per-user pricing above that, with no implementation project cost. For a provider evaluating whether to move off spreadsheets or a legacy tool, knowing the cost structure before you start the conversation matters.
Who each platform suits
Lumary may suit you if:
- --You have 100+ staff and operate across direct support, plan management, and support coordination from a single platform
- --You are running plan management at scale and need deep PRODA/PACE billing capability
- --Your organisation already has Salesforce infrastructure and can leverage the ecosystem
- --You have the internal resources and timeline for an enterprise implementation project
- --You need configurable compliance reporting across multiple funding bodies
Teiro may suit you if:
- --You have 20--200 staff and your primary operation is NDIS direct support workforce management
- --You want to be running live rosters within a week without an implementation project
- --SCHADS accuracy at the rostering layer and qualification enforcement at point of assignment matter to your compliance team
- --Carer app adoption and field-based shift verification are operational priorities
- --You want transparent pricing before you start a vendor conversation
Common questions
Is Lumary more powerful than Teiro?
In terms of raw configurability and billing depth -- particularly for plan management and support coordination -- yes. Lumary is designed for a wider and more complex operational surface area than Teiro. Whether that power is relevant to your organisation depends on whether you actually run plan management or support coordination at scale. Many direct support providers operating on Lumary are paying for and managing configuration complexity that their operation does not use.
What is Lumary's pricing?
Lumary does not publicly list pricing. Rates are negotiated per organisation and vary based on the modules licensed, headcount, and service type. Implementation consulting is an additional cost on top of the licence. If pricing transparency matters to your evaluation process, this is worth noting. Teiro lists pricing at teiro.com.au/pricing and is free for 5 or fewer active users.
Can Teiro handle plan management like Lumary?
No. Teiro is built for direct support providers. Its billing covers NDIS claim management for direct support delivery -- SCHADS rate automation, service agreement tracking, and claim submission. It is not designed for plan management operations at scale. If running a plan management division is a core part of your business, Lumary or FlowLogic are worth evaluating for that specific requirement.
How long does it take to switch from Lumary to Teiro?
The transition timeline depends on the complexity of your current Lumary configuration and how much historical data you need to migrate. Most organisations moving to Teiro are rostering live shifts within a week of setup. Full data migration -- participant records, worker credentials, historical documentation -- is a separate workstream that runs alongside active operations rather than blocking them. We work with you on migration before go-live.
We are evaluating Lumary but have not committed yet. How does Teiro compare on cost?
The total cost of ownership comparison between the two platforms is significant. Teiro is free for up to 5 active users and per-user priced above that. There is no implementation project cost -- setup is handled internally or with onboarding support at no extra charge. Lumary involves licence negotiation, implementation consulting fees, and ongoing configuration work. For providers with under 100 staff who primarily deliver direct support, the cost-benefit calculation usually favours Teiro substantially. Book a demo and we can give you a direct comparison for your headcount.
See how Teiro compares in a live demo
Book a 30-minute walkthrough. We will show you the rostering workflow, SCHADS calculations, qualification enforcement, and carer app in a live environment. If Teiro is not the right fit for your organisation, we will tell you.
Free for 5 or fewer active users. No credit card required.