"Updating one event used to take a volunteer half a day. Sometimes it was just easier not to."
I still think about that line. Because it's not unusual — we’ve heard variations of it from dozens of not-for-profit teams across WA.
The issue isn’t capability. It’s infrastructure. Most older not-for-profit websites were built for launch — not for ongoing life. And definitely not for a team juggling drives, volunteers, and compliance.
It’s usually fine at first. But then it slowly becomes a drag:
- Events go out late (or not at all)
- Donation campaigns stall
- Old content lingers for months
- And your team ends up duct-taping together outside tools just to make something work
This isn't sustainable — and it’s not fair.
What's actually needed?
Not-for-profit websites in Perth need to be as nimble as the teams behind them. That means:
- Being able to post an event in five minutes flat
- Auto-expiring past content so the site stays fresh
- Updating without needing a developer (or a manual)
- Keeping things internal so volunteers can hand things over without chaos
What better looks like
We rebuilt Trillion Trees’ site with exactly that in mind. Their old platform required staff to jump between systems just to run a campaign. Now? They can launch and update events, drives, and bequests all from one place — no extra logins, no technical gymnastics.
They’re not alone.
Because here's the thing:
If your team is spending energy wrestling with the system, that's energy not going toward your mission. And that’s the real cost.
The right web infrastructure doesn’t just look good — it gives your team back time, control, and confidence. And honestly, that should be the baseline.
