About Digital Nachos
Small by design. Clear about who does the work.
I’m George, the founder of Digital Nachos. I work with organisations whose teams spend too much time getting data out of systems, rebuilding reports or working around software that does not quite fit.
Background
How you do one thing is how you do everything.
I’m a software engineer and data scientist based in Sydney, and I care about design as much as the data underneath it. The same standard runs all the way through: the infrastructure nobody sees, the checks behind every number, the screen your team opens on a Monday morning and how you’re kept in the loop along the way.
Work I’ve led:
- Women’s Community Shelters: CIMS reporting that used to take about two weeks each cycle and now runs on its own.
- Lou’s Place: SRS and feedback survey data brought together in one checked, repeatable report.
- Department of Defence: natural language processing to find themes in unstructured feedback, run in an air-gapped environment and delivered through an analytics partner.
- JLL Australia: national property data analysis and interactive reporting for a federal government bid.
- Blocksolve: methane emissions monitoring from satellite imagery across Australian landfills.
- JobLink: a booking and deposit platform for tradies, designed and built end to end.
- Yakka Finance: a loan repayment calculator brokers use to quote their clients.
- GovHack 2023 winner (Quantium): Bloom, an AI hotline prototype that reconnects older people with community events, built in under 24 hours.
The work
Start with what people actually do.
I map the current workflow with the people responsible for it, including the awkward exceptions and reporting definitions. Then we decide whether a process change, integration, dashboard or new tool is the smallest useful fix.
The team
You work with me, start to finish.
I’m the person on the first call, and the one who maps, builds, checks and hands over the work. No account managers and no hand-offs to someone you’ve never met.
When a project needs more hands, like a specialist designer or engineer, I’ll introduce them and agree their role with you before they start. Bigger programmes get a plan for cover too, so the work doesn’t stall if someone is away.
The standard
Useful after the demo.
A good result is not a clever prototype. It is a workflow people can use, data they can trace, and clear ownership when something changes. That means defining the checks, handover and support arrangement for each engagement.
If an existing product or a simpler process is enough, I will say so.