I'm going to tell you about one of my favourite projects.

Not because the technology was flashy. It wasn't. Not because the budget was huge. It definitely wasn't.

I loved it because of what happened six months after we finished.

The charity's operations manager, the one who'd spent years manually copying data between spreadsheets, chasing approvals, and fighting with systems that didn't talk to each other, sent us a photo. She was at a community event, actually talking to people, something she used to never have time for. The caption said simply: "This is what you built."

That's the good stuff right there.

The Problem Nobody Could Fix

This charity supported vulnerable families in their local community. They ran food banks, advice sessions, youth programmes, the kind of work that actually changes lives.

But behind the scenes, they were drowning.

Every family they supported meant paperwork. Referral forms. Food voucher logs. Attendance records. Follow-up notes. All of it lived in different places. Some on paper. Some in spreadsheets. Some in email threads that nobody could find six months later.

When a family needed help, someone had to piece together their story from half a dozen sources. When funders asked for impact data, someone spent weeks pulling it together manually. When staff were off sick, nobody knew where to find the information they needed.

The team wasn't failing. They were working harder than anyone should have to. The systems were failing them.

Why Off-The-Shelf Wasn't Working

They'd tried commercial software. Bought a CRM that was supposed to solve everything. But it was designed for sales teams, not charities. It wanted them to track "opportunities" and "deals" when what they actually needed was to track whether a family had enough food for the week.

They'd tried free tools. Google Forms for intake. Spreadsheets for tracking. A shared calendar for appointments. Each tool worked in isolation. Together, they created more work, not less, because information had to be copied between them constantly.

This is the thing about off-the-shelf software. It's built for someone. Just not necessarily you.

What We Actually Built

When they came to us, we didn't start with technology. We started with a question: what's the one thing that, if it worked better, would change everything?

They didn't hesitate. "Knowing what's happening with a family without having to ask three people and check four systems."

So we built exactly that.

A simple dashboard that showed everything about a family in one place. When they first came. What support they'd received. Who'd spoken to them last. What was needed next. No more hunting through spreadsheets. No more asking colleagues to dig out old notes. Just one screen that told you everything you needed to know.

We built the forms they actually used, not generic templates. We connected the parts that needed connecting. We made it easy enough that everyone actually used it, not just the tech-savvy ones.

And we left the bits they didn't need on the cutting room floor.

What Happened Next

The numbers were nice. Admin time dropped by about fifteen hours a week across the team. Referral processing went from days to hours. Funders got reports in minutes instead of weeks.

But the numbers weren't the point.

The point was that the operations manager finally had time to actually be present with the families she was helping. The point was that new staff could get up and running in days instead of months. The point was that when a family in crisis reached out, someone could see their whole story immediately and respond properly.

One story sticks with me. A support worker was with a family when they realised they'd forgotten a key document. Before, that would have meant rescheduling, another trip, more stress for everyone. Instead, she pulled out her phone, accessed the system, and confirmed the information was already there. The appointment continued. The family got help that day.

That's the difference between technology that looks good on paper and technology that actually works.

What We Learned

This project taught me something I carry into every engagement since.

The best technology isn't the most sophisticated. It's the most useful. It's the thing that fades into the background so completely that people forget it's there. It's the thing that lets good people do good work without fighting their tools every step of the way.

We could have built something fancier. More features. More automation. More everything. But that wouldn't have helped. It would have added complexity to a team already drowning in it.

Instead, we built the thing they actually needed. Just that. And it changed everything.

Where You Come In

I'm telling you this story not because every organisation needs custom software. Most don't. Most can get by with off-the-shelf tools and a bit of discipline.

But some organisations hit a wall. Their processes are too specific. Their needs are too unique. Their team is too stretched to keep bending around tools built for someone else.

If that's you, if you're tired of fighting systems that weren't designed for the work you actually do, let's talk. Not about features or roadmaps or digital transformation strategies. Just about what's not working and whether there's a smarter way forward.

Because honestly? That conversation is where the good work starts.

Got a process that's driving your team crazy? [Talk to ALWAYS 49] about whether custom software could help.