How providers at $1.5M–$3M close the 3 revenue leaks that keep them stuck below scale
At $1.5M–$3M with 5+ SIL homes, you have crossed a threshold most NDIS providers never reach. The operation that got you here will not get you to $3M.
You are not losing money because the market is tough. You are losing money because your operation was designed for 3 homes and you are running 8. The manual processes that worked at $750k are now the primary source of margin leakage. The founder is still the bottleneck for incidents, referrals, and compliance — and the cost of that bottleneck is now measurable.
This blueprint identifies the 3 specific revenue leaks that consistently appear at this revenue band, quantifies their cost with real numbers, and maps the infrastructure sequence that closes them. It is based on operational patterns observed across providers running SIL homes in metropolitan and regional Australia.
The sector context reinforces the urgency. Nearly 50% of NDIS providers report a financial loss. 81% say current prices are unsustainable. 77% deliver unfunded supports averaging approximately $500,000 per year per provider. Workforce turnover sits at 24%. At $1.5M–$3M, you are large enough that these sector pressures compound — but also large enough that systematisation can create margin the sector average does not have. (Source: NDS State of the Disability Sector Report 2025)
The regulatory exposure is equally material. Fair Work penalties for SCHADS non-compliance reach up to $93,900 per breach per employee per pay period. The most common exposure at your size: weekend and holiday penalty rates (45% of all SCHADS claims), broken shift allowances, and minimum engagement periods.
These are not theoretical. They appear in the same pattern, at the same revenue band, with the same consequences. If you are running 5+ SIL homes and billing above $1.5M, at least two of these are active in your operation right now.
At 5+ SIL homes, incidents do not happen occasionally. They happen weekly. Falls, behavioural events, medication errors, property damage, participant distress. Each one requires documented intake, severity classification, and a defensible audit trail within 24 hours.
Without an automated intake and classification system, incident reports are logged late, logged incompletely, or not logged at all. The founder's mobile phone is the intake system. Messages arrive at 2am. Notes get written three days later from memory. Evidence packages are assembled retroactively when an auditor requests them.
The compounding effect: each undocumented incident degrades your audit posture. Two near-miss findings become a corrective action notice. A corrective action notice becomes a condition on registration. A condition on registration becomes a barrier to growth — coordinators will not refer to a provider with conditions.
Providers at this size almost always built their initial participant base through personal relationships. The founder knew coordinators by name. They answered calls on the first ring. They followed up within hours. That is how they grew from $500k to $1.5M.
Then they stopped. Not deliberately — they got pulled into operations. Rostering problems. Staff issues. Compliance deadlines. Nobody replaced them as the coordinator relationship manager. The pipeline now runs on reputation and inbound — which is not a pipeline at all.
The real number is worse. This calculation only captures lost capacity from exits and slow replacements. It does not account for the referrals you never received because no one was maintaining coordinator relationships in the first place. Providers who track coordinator conversations report that 73% of SIL referrals go to the provider who responds within 4 hours. If no one is monitoring the request, you are not in the running.
10–15% of NDIS claims are rejected on first submission. At $2M in annual billing, that is $200,000–$300,000 in first-submission rejections. Most rejections are for trivial reasons: missing documentation, unit discrepancies, incorrect support category codes. These are preventable with pre-submission validation. Most providers at this size do not know their rejection rate because they do not validate claims against participant plans before submission.
The hidden cost: plan expiry gaps. When a claim is rejected because a participant's plan has lapsed or changed, the resubmission window is often already closed. Services delivered during plan transitions are frequently unbillable. Providers who pre-validate claims against current plan data before submission report rejection rates below 0.5%.
For a provider billing $1.8M, that is 22%–36% of revenue consumed by operational gaps that do not require more staff to close. That is not a cost of doing business. That is the cost of not having systems.
A provider at $2M with closed revenue leaks does not operate with more people. It operates with agents handling the jobs that humans consistently fail to do at scale: real-time incident intake, proactive coordinator outreach, continuous compliance monitoring, and pre-submission claims validation.
24/7 incident intake via dedicated channel. Classifies severity (critical / elevated / routine). Timestamps and documents every report. Generates initial audit narrative. Routes critical incidents to on-call staff within 4 minutes.
Tracks all policy review dates, registration deadlines, and staff credential expiries. Consumes Triage audit trails to maintain live evidence packages. Generates evidence bundles on demand — no 3-day scramble when an auditor calls.
Monitors coordinator networks and referral channels. Sends proactive outreach to coordinators in your service areas. Routes warm inquiries to intake within 15 minutes. Tracks coordinator conversations and response times.
Pre-validates every claim against participant plan data before submission. Checks line items, plan dates, and funding allocations. Flags rejection risk. Produces cashflow forecasts from current claim pipeline.
The agents are not independent tools. They form an operational loop:
| Metric | What It Measures | Target |
|---|---|---|
| Referral response time | Minutes from coordinator inquiry to first response | < 4 hours |
| Incident documentation rate | % of incidents with complete audit trail within 24 hours | 100% |
| Claims pre-validation rate | % of claims checked against current plan before submission | > 95% |
| Coordinator conversations / month | Active outreach touchpoints with coordinators in service area | > 20 |
| Compliance evidence freshness | Days since last evidence package update | < 7 days |
| Claims rejection rate | % of submitted claims rejected by NDIA | < 0.5% |
| Bed vacancy duration | Average days between participant exit and replacement | < 21 days |
If you cannot produce these numbers today, you do not have an operations system. You have a collection of manual habits. That is the distinction between providers who stay at $1.8M and providers who reach $3M.
Answer each question honestly. A "no" to any of these indicates an active revenue leak at your current scale. Two or more "no" answers means the combined exposure is likely above $400k per year.
Most providers at this revenue band answer "no" to all three. That is not a criticism — it is the natural consequence of growing from a founder-led operation to a multi-site business. The processes that got you here cannot take you further. The question is whether you close these gaps with more staff (expensive, inconsistent, does not scale) or with systems that run 24/7 without error.
The sequence is not arbitrary. Each agent creates infrastructure that the next agent depends on. Installing them out of order wastes money and creates gaps. This is the deployment order that produces compound returns.
After-hours incident liability is the most dangerous leak because it compounds into regulatory risk. A single poorly documented critical incident during an audit period can trigger a corrective action notice. Install Triage first: 24/7 intake, automated severity classification, timestamped audit trails, on-call routing.
Why first: Regulatory risk is existential. Revenue leaks cost money. Compliance failures cost your registration.The Compliance Agent consumes the audit trails that Triage produces. It layers policy tracking, credential monitoring, and evidence package generation on top of an incident documentation system that already works. Without Triage running first, the Compliance Agent has incomplete data. With Triage in place, it has a live feed of documented operational events to build evidence from.
The deadline is concrete: from 1 July 2026, all SIL providers must hold certification-level registration. SIL is classified as high-risk — verification-level will not suffice. The audit requirements include incident management documentation, restrictive practice compliance, worker screening currency, and continuous compliance demonstration.
Why second: It depends on Triage data. Installing Compliance without Triage means building evidence packages from incomplete records. The July 2026 certification deadline makes this non-negotiable.Now you have documented incident management and audit-ready compliance. This is the foundation coordinators evaluate when deciding where to refer. The Referral Agent can now surface your compliance posture as a differentiator: "We produce evidence packages on demand. Our incident documentation rate is 100%. Our last audit had zero findings." That is not marketing. That is operational proof — and coordinators know the difference.
Why third: Generating referrals before fixing compliance is counterproductive. A coordinator who refers a participant to a provider with audit findings will not refer again.Total deployment timeline: 6 months. Total investment: $17,000 (Triage $9,000 + Compliance $4,500 + Referral $3,500). Against $400k–$650k in annual leakage, the payback period is under 30 days on the first agent alone.
At $1.5M–$3M with 5+ SIL homes, you are in the strongest position to capitalise on the navigator transition — if you prepare.
The NDIS Navigator model replaces Support Coordinators with government-funded Navigators. Testing mid-2026. Gradual rollout 2026–2028. Five-year implementation.
Navigators will select providers based on: specialisation depth, compliance track record, incident management quality, response speed, and capacity documentation. Personal relationships will not carry weight.
The three revenue leaks in this blueprint (after-hours liability, coordinator pipeline decay, claims leakage) are exactly what navigators will screen against. An undocumented incident = a risk flag. A slow response = an unreliable provider. Rejected claims = financial instability.
The agent stack described in this blueprint (Triage → Compliance → Referral) is not just about closing leaks. It builds the operational profile that navigators will use to rank providers:
The infrastructure sequence in this blueprint positions you for both worlds: maximum referrals from coordinators while the channel is open, AND maximum findability when navigators replace them.
Providers at your size who build this infrastructure in the next 12 months will absorb market share from providers who did not prepare. At $1.5M–$3M, you have the revenue to invest. Smaller providers do not.
This case study is illustrative, based on composite operational patterns observed across SIL providers in this revenue band. Names and identifying details have been changed.
Starting position: 8 SIL homes. 67 participants. $1.8M annual revenue. 34 support workers. 3 team leaders. 1 operations manager. Founder still involved in daily operations.
6-month referral drought. No new SIL placements. Two vacancies costing $18,000/month.
2 near-miss audit findings. One incident had no written record. Another had a 72-hour documentation delay.
Claims rejection rate: 12.4%. $223,200 in annual first-submission rejections.
Founder managing incidents at 1am. Writing notes from memory the following week.
$2.6M annual revenue. $800k growth in 14 months.
Zero audit findings. Evidence packages produced on demand.
Claims rejection rate: 0.3%. $218,000 in annual leakage closed.
Zero founder after-hours calls. 15 hours/week reclaimed.
Dedicated intake channel replaced the founder's mobile. All after-hours incidents routed through automated intake. Severity classification applied within 90 seconds. Audit narrative generated immediately. Founder's after-hours call volume dropped to zero within 2 weeks.
Layered on top of Triage audit trails. Policy review calendar automated. Staff credential tracking activated. Evidence packages available on demand. Mid-year audit result: zero findings.
Proactive coordinator outreach launched. 15 coordinators contacted in the first month. Referral response time reduced from 48+ hours to under 3 hours. First new SIL placement received within 3 weeks of activation.
Pre-submission validation against participant plans. First-submission rejection rate dropped from 12.4% to 0.3% within 6 weeks. $218,000 in annual leakage closed.
Revenue impact breakdown: $480,000 in new participant revenue from 4 SIL placements via coordinator referrals. $120,000 recovered from closed vacancy gaps. $218,000 saved from claims leakage reduction. $95,000 in avoided audit remediation costs. Founder reclaimed an estimated 15 hours per week previously spent on incident management, compliance preparation, and coordinator outreach.
You'll calculate the exposure. The number will be uncomfortable. Then Monday happens. An incident at 2am that gets handled by phone and never logged. A claim submitted without pre-validation because billing is behind. A coordinator inquiry that sits in the inbox for 3 days because everyone assumed someone else would respond.
The exposure you just measured keeps running because nobody has time to build the systems that stop it. Not because you don't know what to fix — because fixing it requires dedicated operational focus that competes with every other priority in a $1.5M–$3M operation.
The agent stack doesn't compete with your priorities. It runs alongside them. Triage handles incident documentation 24/7. Compliance tracks every policy date. The Referral Agent keeps 40–60 coordinators in an active relationship cycle every month. Total investment: $17,000 against $400k–$650k in annual leakage.
Provider at $1.8M with 8 SIL homes. Revenue reached $2.6M within 14 months of agent stack install. Zero audit findings. 12 new coordinator relationships. Incident documentation rate: 100%.
— NDIS Provider, Western Sydney · Stage 4The full diagnostic maps your specific leaks against the agent that closes each one. We use your numbers, your operation, your service areas. The session produces your Agent Recommendation Report — the specific agents your operation needs, in the order they should be installed, with guaranteed outcomes and timeframes.
Total investment: $17,000 against $400k–$650k in annual leakage.
30 minutes. Your numbers. Your recommendation. No obligations. Book Your Capacity Blueprint