This case study covers an anonymised NDIS provider that had good frontline staff, strong word-of-mouth referrals, and a website that was quietly getting in the way.
The site looked acceptable. It converted poorly. Referral partners struggled to find the right intake path, participants hit dense copy blocks, and the intake team spent too much time clarifying basic fit questions after enquiries arrived.
After the rebuild, referral enquiries increased by 41 percent and the intake process became materially cleaner.
The problem before the rebuild
The old site made three common NDIS mistakes:
- it used one contact form for every audience
- it described services in provider language instead of participant language
- it treated accessibility as a plugin setting rather than a design constraint
Support coordinators needed registration clarity, service-area coverage, and faster routing. Participants and families needed plain language, confidence, and a clear next step. The old site gave all of them the same generic pathway.
What we changed
1. Separated the key user journeys
The homepage and service pages were rebuilt around three clear audiences:
- participants
- families and carers
- support coordinators and referral partners
Instead of one generic contact CTA, each pathway had its own destination. Self-referrals stayed short and plain-language. Coordinator referrals captured the information intake teams actually needed.
2. Rewrote the service pages in plain English
Service descriptions were shortened, simplified, and structured around real questions:
- what support is offered
- who it is for
- where it is delivered
- what happens after an enquiry
Registration status and service-area clarity were moved higher on the page. That single change reduced irrelevant referral enquiries and made the provider easier to assess quickly.
3. Rebuilt the forms for accessibility and intake quality
The new forms used explicit labels, clearer error handling, better focus states, and helper text that told users what would happen next. The coordinator form captured plan-management type, support category, urgency, and key notes without becoming bloated.
The participant form stayed much shorter. That mattered because the old form was turning a support request into an admin task.
4. Added a trust layer that matched the buyer
Families and coordinators do not buy NDIS services the way they buy home services or retail products. They are looking for suitability, clarity, and responsiveness.
The rebuild added:
- visible registration messaging
- service-area confirmation
- straightforward staff and service explanations
- clear callback expectations
The site stopped sounding like internal provider documentation and started sounding like a real front door.
Results after launch
Measured over the first eight weeks after launch against the prior comparable period:
- referral enquiries increased by 41 percent
- self-referral completion rate improved because the participant form was shorter and easier to understand
- intake triage time dropped because coordinator submissions arrived with cleaner context
- page-level engagement improved on the core service pages, especially mobile
The qualitative result mattered too: the intake team spent less time clarifying basics and more time handling the actual support fit conversation.
Why it worked
The rebuild worked because it respected the reality of NDIS demand.
This was not a design-only project. It was a website, accessibility, and intake-operations project at the same time. The service pages, referral forms, and follow-up expectations all supported the same user outcome: help the right person enquire in the right way with the least friction possible.
That is why the lift showed up in both volume and quality.
What other NDIS providers should copy
If an NDIS site is underperforming, start here:
- Separate participant and coordinator journeys.
- Move registration and service-fit information higher on the page.
- Rewrite service copy in plain English.
- Treat accessibility as a core product requirement, not a late-stage checklist.
That combination tends to do more commercial work than cosmetic redesign alone.
FAQ
What changed first in the rebuild?
The journey structure. Once the audiences were separated properly, the copy and forms could become much clearer.
Did accessibility work really affect conversions?
Yes. Accessibility improvements reduce friction directly and also raise trust for users deciding whether the provider feels usable and credible.
What counted as a referral enquiry?
Coordinator or LAC referral submissions plus tracked calls from referral-focused pages. Self-referrals were measured separately.





