Volunteer platform / 2025
Running for Resilience
A roster app that signs people up to help at community runs, fills every role and texts reminders so people show up.
Read the case studyInternal tools
One proper tool for the way your team works.
When the problem is bigger than a report, I design and build a tool around the real sequence of work - intake, handoffs, approvals, service delivery and follow-up. Everyone works from the same screen, so it’s clear who has what.
How it works
How a team tool comes together.
The work lives in four places at once.
A shared spreadsheet, an inbox, a group chat and the one person who knows how it all fits together.
So the day goes on chasing.
Who has this? Has it been approved? Requests slip through the gaps between one person and the next.
We map how the work really moves.
From the first request to the last follow-up, worked out with the people who do it every day.
Then we build one tool around that path.
Every step has a place and every job has an owner, so it’s always clear what comes next.
Now everyone works from the same screen.
Requests come in, move along and get done - anyone can see where things are up to.
Team tools
Built around the people who use it.
Our guarantee
100% delivery and satisfaction guarantee.
If you are not happy with the work at any point during the project, you can request a refund. That option stays open until four weeks after the delivery date.
To request one, email hello@digitalnachos.com.au.
Before you get in touch
Questions about team tools.
What kind of tools do you build?
Tools that follow how work actually moves through a team - requests coming in, someone picking them up, approvals and the follow-up. The Running for Resilience roster app is one example - volunteers claim roles and get a text reminder before the event.
How do you work out what it should do?
By starting with the current process and the people who do it every day. We map where requests come from, who picks them up and where they get stuck - then agree the part worth changing first.
Do we have to replace the systems we already use?
The aim is to stop work falling between your systems, not to rip them out. The reporting work is an example - it runs alongside CIMS and SRS without replacing them.
Can you replace our shared spreadsheet with an app?
Often that’s where it starts. The Running for Resilience roster app replaced a spreadsheet and group chat - volunteers tap a role to sign up and coordinators see the roster fill as it happens.
Tell me how the work moves now.
Say what the work is and where it lives today. I’ll reply with a sensible next step.