The short answer
NDIS website design in Logan means building a provider site a referrer can use at speed: supports named the way funding names them, the suburbs you staff, a current intake position and an accessible referral form. AR Digital Solutions builds these from Pallara, minutes from the Logan boundary. We are not a provider.
More providers per street than anywhere else in Queensland
Logan holds the densest concentration of disability service providers in the state, and from the outside it barely looks like an industry. Support offices sit above shops in Logan Central and Woodridge, in units along Kingston Road at Slacks Creek, and in houses through Marsden and Crestmead where supported independent living runs.
What makes writing for this market different is the range of people reading the same pages. A coordinator working a caseload across Springwood and Underwood. A plan manager checking your invoicing arrangements. Discharge staff at Logan Hospital placing someone by Friday. A family member reading on a phone at 10pm, sometimes in a second language, since Logan is one of the most culturally diverse parts of Queensland.
None of them care about your values statement, and all of them are deciding whether to spend a phone call on you.
Nobody starts on your homepage
Open your analytics and look at the landing page report rather than the traffic total. On most provider sites the entries spread across deep pages, because a coordinator arrives from a search for a specific support in a specific suburb, or from a forwarded link. The homepage you spent the design money on is the one nobody loads.
So every service page has to work as though it is the only page, carrying its own answers rather than pointing at an about page three clicks away.
There are two ways to get this wrong. The first is a handsome homepage above service pages of three sentences and a stock photograph. The second is a page for every support crossed with every suburb, which produces forty near identical pages Google's systems are built to filter as a group.
Build a page for each support you deliver, coverage pages only for areas you can reach on a Tuesday morning, and get the capability statement out of its PDF, since a coordinator with six tabs open downloads nothing.
What a service page has to answer on its own
- The support named the way funding names it, in plain English a family can read at 10pm
- Who delivers it, with qualifications and worker screening stated
- Suburbs and travel, honest about the edges, since Beenleigh and Springwood are not one trip
- A dated intake line: taking referrals, waitlisted or full
- Plan management arrangements accepted, and your registration position stated exactly
- A named intake contact, and a form built for a referrer rather than a shopper
Accessible on day one, and the limit of our job
Part of your audience uses a screen reader, magnification, captions or a switch device. We build to WCAG 2.2 AA as the working target: heading order that makes sense read aloud, form fields with real labels, keyboard navigation that does not trap. Tested before launch, not audited after.
Say it plainly: we are the web team, not a provider. AR Digital Solutions holds no NDIS registration, delivers no supports, and has no view on your audit or registration application. Meeting the Practice Standards and the Commission's advertising expectations is your work. Ours is to write copy that does not make it harder, describing what a support involves and who delivers it rather than what it will do for a participant.
One registered address, several catchments
Your Google listing sits at one address, so the map pack works around it and stops. Everything past that gets won with pages about the supports you deliver where you deliver them, supported by local SEO.
Ours works the same way. The office is at 1 Cheshire Street, Pallara, ten minutes from Browns Plains, so Logan sits inside our own local results, which is unusual for an agency selling into it. It does nothing in Beenleigh, and there will be no second address to fix that.
Where else we build provider sites
Catchments ignore council boundaries, so there are pages for the areas Logan providers also staff: Underwood, Kuraby, Calamvale, Drewvale, Runcorn and Pallara, plus Brisbane and the Gold Coast. Full service areas list.
How a provider build runs
Your service list and registration position first
What you deliver, under what arrangements, in which suburbs, and who signs off.
The referral path gets mapped before anything is designed
Pages, intake fields and coverage, then the build.
Build, then test
Staging link, keyboard pass, screen reader pass, compliance review, launch.
Handover that sticks
Your intake team edits the capacity line, and managed support answers in 1 to 3 hours.
What providers get from working with us
The page that matters most stays current.
Capacity information rots in weeks, so your intake coordinator edits it in two clicks, without a ticket or an invoice.
Developers, not template assemblers.
Referral forms that feed your systems, and provider software when an off the shelf tool cannot do it.
No lock in contracts, and no pressure in the sale.
Fixed scope and fixed price on the build, month to month after.
"Our last agency wrote things we had to take down."
Common, usually because nobody involved had read the guidance. We write the constraints into the first draft and expect your compliance person to mark it up before anything goes live.