One audit sticks with me because the gap between ambition and resources was wider than anything else I encountered across 55 businesses.
A charity wanted to build an app connecting surplus food from shops and restaurants with families in need. Not just a simple matching service. A suggestion algorithm that would learn what kinds of food different communities would actually use.
The concept
The idea was thoughtful. A pallet of coconuts donated to a food bank is a generous gesture. But if the families served by that food bank don't cook with coconuts, the food goes to waste twice: once by the business that couldn't sell it, and again by the families who can't use it.
The app would track what was available, what was needed and what was actually used. Over time it would learn. It would suggest redistribution routes that matched supply with demand in ways that reflected cultural preferences, dietary needs and practical constraints like storage and transport.
For a technology startup with venture funding, this would be a solid product concept. For a charity with about three staff and an income of around half a million, it was a different proposition entirely.
What the audit became
I couldn't audit a website that didn't exist yet. Instead, the audit became a scoping exercise. What could realistically be built in phases? What existing platforms might handle part of the problem without a custom build? Where could the charity find developers willing to work pro bono or at charity rates? How could the concept be proven with a simple version before committing to the full build?
The recommendation was to start small. A basic matching tool. Manual at first, maybe a structured spreadsheet or a simple web form. Test the concept with a handful of food donors and a handful of recipients. Prove the demand. Gather data. Then use that data to make the case for funding the full platform.
This is the approach I'd recommend to any organisation planning a technology project on a limited budget: don't build the finished product first. Build the smallest possible version that lets you test whether the idea works. Then grow from there.
Why this matters
This project is a reminder that digital isn't always about selling more products or getting more website traffic. Sometimes it's about getting surplus food to families who need it before it ends up in a skip.
The technology to solve problems like this exists. The APIs, the algorithms, the platforms. None of it is technically impossible. What makes it hard is the funding model. Charities can't raise venture capital. They can't run at a loss for three years while they build a user base. They need every penny accounted for and every project to demonstrate impact to funders.
If you work in tech and you've got time to give, organisations like this one exist in every region. They don't need your advice on their mission. They need your help building the tools.
This article is part of a series based on findings from 55 digital audits. Read the full case study for the complete picture, or get in touch if you'd like to discuss how digital can support social impact work.