NDIS support services for people attending events · Brisbane, Sunshine Coast, Gold Coast and Byron Bay
The events out front. The rostering, the RSVPs and the registrations running themselves behind it.
Let's Go!, letsgosupportservice.com.au
Where they were
Let's Go! supports people to get to things: live music, sport, exhibitions and social events, with a support worker alongside them. Two separate businesses sit inside that one sentence. The public-facing one has to show what is on and persuade a family it is worth joining. The operational one has to register new participants, plan each event, collect and confirm RSVPs, and allocate a support worker to every person attending. Before this build, the second business ran on messages and memory. That is fine at ten people. It does not survive four regions and a calendar that turns over every month.
What they needed
- Show what is actually on, so nobody has to imagine what a supported day out looks like
- Recruit support workers from the same site, because the service cannot grow without them
- Turn a participant registration into a process that starts itself, rather than an email somebody has to notice
- Confirm RSVPs without a person chasing them one at a time
- Allocate a worker to every event and confirm it, so no one is left without support on the day
- Let the team publish a blog every month without booking a developer
- Work across Brisbane, the Sunshine Coast, the Gold Coast and Byron Bay at once
What it did for the business
The service sells itself by showing what is on.
Events are browsable by category: music, sport, art and culture, and social. Each carries its date and venue, so a family on the Sunshine Coast and one in Byron Bay each see what is near them. Instead of describing what support might feel like, the business shows someone a Saturday they could be at.
Picking a category filters the list down to the events on near you.
The same site recruits the people who make the service possible.
A support service is only as big as its roster. The site carries a Work page alongside the events: contact details, previous experience, how they heard about Let's Go!, and a CV upload. A support worker reading about Saturday's event is one short form away from asking to be the person who takes someone to it. No separate careers site to find, no second system to run.
A support worker applies from the same site a participant browses.
Registering as a participant starts a process, not an email.
Getting started runs as four visible steps: meet and greet, setup, choose events, go. The Join form collects NDIS plan type, goals and accessibility needs, and a submission triggers the automations that move that person through onboarding. The family sees the whole path before committing to a conversation, and nobody in the office re-keys anything.
A registration moves itself through the four onboarding steps.
RSVPs confirm themselves.
Every event needs a headcount before it can be planned, and the old version of that was someone chasing replies. Confirmations now go out and come back automatically. Delivery was tested on the live site rather than assumed, which matters more here than most places: a confirmation that does not arrive means a person waiting outside for a pickup nobody knew to make.
Each RSVP confirms back to the participant without anyone sending it.
Every person attending has a worker allocated, and both of them know it.
Event planning is a matching problem: people attending on one side, available workers on the other. The system allocates and then confirms the allocation with the worker, so a gap shows up days before the event rather than on the morning of it.
Workers are allocated to each event and confirm back.
The team publishes every month without asking anyone.
Blogging dies when it needs a developer. The publishing process was built so the Let's Go! team writes and uploads their own posts monthly. That is what keeps a community site looking alive between events, and it is the difference between a site people read once and one they check.
A post goes from draft to published by the team, every month.
Recognise any of this in your own business? Fifteen minutes is usually enough to say whether we can help.
How we know
Dreamy built the front end and the back end: the public events site, the support worker path, and the automations for participant registration, event planning, RSVP confirmation and worker allocation.
Scope of the engagement, confirmed by Rishav on 2026-09-19. The back end runs behind a login, so unlike the public site it cannot be verified by a reader, and this page does not imply it can.
The public site carries event categories, the four-step onboarding path, community testimonials, partner logos, FAQs and a newsletter signup.
Checked directly on letsgosupportservice.com.au on 2026-09-19. Anyone can open it and verify every item in this list right now.
Events are browsable by category (music, sport, art and culture, social) with a date and a venue on each.
Visible on the live site at the same check on 2026-09-19.
The site carries a dedicated Work page for people applying to become support workers, with a form covering contact details, previous experience, how they heard about Let's Go!, and a CV upload.
Checked directly on the live public site (the Work page) on 2026-09-19.
The participant registration form collects NDIS plan type, goals and accessibility needs, and states the same four-step path from application through to attending an event.
Checked directly on the live public site (the Join page) on 2026-09-19.
The team publishes their own blog posts on a monthly cadence through the process Dreamy set up.
Scope confirmed by Rishav on 2026-09-19. Published posts are visible on the live site, with an August recap live at the check on that date.
The rebuilt site went live on the new platform and new web address on 2026-08-19, with production email delivery verified the same day.
Recorded in Dreamy's engagement file. Delivery was proven by a live send test on the production site, not assumed to work.
Want one that does this for you?
Fifteen minutes, and you will see it working rather than described.
Book a 15-minute demo