Software that empowers a small charity to punch above its weight
b:friend wanted to reach more lonely older people without its small team getting buried in admin, and to show funders with confidence the difference its work makes.
The Mission
b:friend wanted to reach more lonely older people without its small team getting buried in admin, and to show funders with confidence the difference its work makes.
The Outcome
A custom CRM that runs the charity's whole befriending journey: referrals and volunteer sign-ups, DBS checks, pairing, impact surveys and reporting. It was first built in 2018 and modernised in 2025–26, growing with the charity at every step.
The Impact
- Monthly reporting now builds itself, giving the team back an estimated 2–4 working days a month [TODO: confirm with Colette]
- Trello retired: every volunteer's journey now sits on one live status board
- 400+ duplicate records resolved, so the figures that go to funders are right [TODO: confirm count]
- Busy list pages went from 7–8 seconds to almost instant [TODO: confirm before/after]
- Grew with the charity from around 300 volunteers to around 5,000 [TODO: confirm figures]
- The annual telethon finally runs properly, with volunteer helpers updating records safely
A friend for every lonely older person
b:friend tackles loneliness among older people in South Yorkshire and North Derbyshire. Some of the people it supports live alone; others live with a partner but have little family nearby. The charity pairs each of them with a volunteer for regular visits or phone calls. Today a staff team of eight or nine supports around 5,000 older people and around 5,000 volunteers [TODO: confirm].
In 2018 all of that ran on Google Sheets and Trello. Founder Mike Niles [TODO: confirm OK to name] wanted to modernise, and had a clear idea: let would-be volunteers find an older neighbour near them on a map on the website, and sign up there and then. The charity had funding, and a quote of around £20,000 from a large London agency.
We met through a shared co-working space. After talking it through, I thought what they needed was more focused than that quote suggested, and scoped the build to it so their funding would go further. Choosing a freelancer over an agency was a real decision for a small charity, and the question in the room was a fair one: "What are we going to lose?" Seven weeks later the new CRM was live, and staff took to it straight away.
After launch I stepped back. For a few years the charity was supported by a volunteer developer [TODO: confirm]. That was possible because the system is built on widely used, well-documented tools, not on anything only I could maintain. When b:friend came back to me in 2025, it was by choice, not because they were locked in.
By then the charity had grown more than tenfold. The system had kept up, but it was showing its age: pages were slowing down, years of routine updates had built up, and the team had a growing list of everyday frustrations. They began asking a serious question: should they replace it with an off-the-shelf CRM?
Listening for the workaround
Our way of working is simple. The team sends me a list of what's getting in their way, we go through it together on a call, and I come back with a plan and a price. Some of the most useful things come up in passing.
On one of those calls, someone mentioned Trello. Years after launch, staff were still tracking the core volunteer journey (sign-up, DBS check, pairing) on a separate board alongside the CRM. Nobody had flagged it as a problem; it was just how things were done. But it meant keeping two systems up to date, and the board only showed what someone remembered to move.
I asked about it, and we designed a status board inside the CRM. Each coordinator sees every volunteer they're responsible for and where they are in the journey. Staff update a profile or a pairing, and the board updates itself. Colleagues can see each other's caseloads, so whoever is covering knows exactly what needs doing that day. The team stopped using Trello completely.
Finding the hidden hours
The team's own wish list showed where their time was going. Each staff member spent an hour or two pulling together their own figures, and the CEO then spent a day or two combining them into one spreadsheet. Unfamiliar postcodes were looked up one by one to work out which area a referral came from.
Now the CRM knows which area each postcode belongs to, suggests volunteers who live nearby, and produces the monthly figures itself, ready to export. One person on the team said the location matching alone saved "a hell of a lot" of time [TODO: confirm who said it, or keep unattributed].
Figures you can stand behind
Older people are often known to several organisations, and each might refer them. Over the years, some people ended up with three or four records, and more than 400 duplicates in total [TODO: confirm]. Nobody was contacted twice, but information was spread across records and the numbers reported to funders were off.
I built a tool that groups likely duplicates by name and postcode and lets staff compare them side by side, choose the main record, and review before anything is merged. The system does the searching; people make the decisions.
Putting the team in control
Changing a survey question or an automated email used to need a developer. Now staff edit the wording of their impact surveys, add help notes for whoever is filling them in, and update email text themselves. Clearer questions mean more accurate answers, and more accurate answers mean impact figures the charity can rely on in funding bids and reports.
Solid foundations
Some of the work was invisible but essential. Years of routine platform updates had built up, as they do, so I brought everything up to date. List pages that had slowed to 7–8 seconds as the records grew now load almost instantly. Every list now has filters, so staff can find an existing person in seconds. The public referral and volunteer sign-up forms moved off the website and into the CRM, with one set of rules instead of two.
The telethon
Every year, the team phones older people whose pairings have been going for a long time, to check in. It had never worked well from a spreadsheet, because the volunteers helping with the calls couldn't update the CRM. Now they get their own restricted login and a single screen with everything they need, and none of the sensitive information they don't need. Early feedback: it's easy to use, and everything is in one place.
Building on, not starting over
Replacing the system was a reasonable idea. Off-the-shelf CRMs suit plenty of charities, and the team had real frustrations. But switching would have meant moving years of records and fitting their way of working to someone else's software. Building on what they had meant trusting it could be brought up to date and made fit for the next stage of growth.
After a genuine internal debate, b:friend chose to invest in their own system. It's a decision I respect, partly because they made it freely: the charity had already shown it could work with another developer, and could have walked away.
They followed it with another good call. In 2026, of their own accord, they commissioned an independent security audit, simply as good practice for a charity holding sensitive information about vulnerable people. It found a number of older issues, including access left over from plans that never went ahead. All were fixed.
A small team, a big reach
The major update in November 2025 went live without disrupting the team's work, and the small follow-up fixes were handled within a week.
The result is a charity where 8–9 people support thousands of older people and volunteers, and spend their time on people rather than spreadsheets. Reporting that used to take days now builds itself. Every volunteer's journey is visible in one place. The numbers that go to funders are right. And when the team wants to change how something works, they can often do it themselves.
Asked what they would lose if the CRM disappeared tomorrow, the answer was simple: "Everything." [TODO: confirm who said this; turn it into a quote block if Colette is happy to be named]
“[TODO: testimonial from Colette]”
b:friend has always punched above its weight. Software is only part of that story; what matters is giving a dedicated team the tools to do their best work. Running a charity's day-to-day doesn't have to be a slog, and technology doesn't have to hold growth back. Done right, it drives it.
Is admin getting in the way of your work?
If your team is juggling spreadsheets, workarounds and reports that take days, let's talk about what could run itself.
Get in touch