Getting your board on board: earning trustee sign-off for a new charity CRM

Trustees look at proposals through a slightly different lens ... governance. Their role is to protect the charity's assets, reputation and long-term sustainability, so the questions they ask about a new CRM are the questions they're supposed to ask, and a proposal that answers them well tends to sail through.

Those questions cluster around four themes:

• Cost: "Is this the best use of restricted funds?"
• Risk: "What if the migration goes wrong?"
• Distraction: "Will this pull staff away from frontline work?"
• Necessity: "We've managed fine so far, so why now?"

All four are fair, and each has a good answer. By give trustees the answers, you're not so much overcoming the board, but equipping them to make the best decision.

Trustees find it easier to say yes when the benefit has a figure on it and the risk has a shape. These three things can help get you there.

1. What a yes frees up

Your current system already has a price, even if nobody has written it down: the licence fees for something the team works around, plus every staff hour going into manual processes.

The encouraging part is how much of that comes straight back when you switch. For example, Snow Camp moved from eTapestry to Donorfy, and calculated their efficiency gains as the equivalent of a full-time role, which is a remarkable thing to hand back to a team.

So, work out your own version. How many hours a week go on data entry, duplicate-checking, manual Gift Aid claims, or pulling reports a CRM would produce on its own? Multiply by your average hourly staff cost, and you've got the size of the prize.

Jenny Slater, now part of the Donorfy team, pitched for a CRM twice during her fundraising career, and her advice comes from experience: track a week of your own manual admin, then translate the hours a database would save into extra funding applications per month. That's the framing boards love, because it turns a software cost into fundraising capacity.

2. The income waiting in your data

Your supporter base almost certainly holds more potential than your current system lets you see.

Decent segmentation means the £500 donor gets a different ask from the £10 donor. Lapsed-donor flagging means supporters who've drifted get a well-timed reason to come back. Campaign tracking means every appeal teaches you something you can use in the next one.

Acorns Children's Hospice needs to raise more than £13 million a year, and used Donorfy's segmentation tools to deliver a campaign that brought in 109% more income than projected. The data was theirs all along; the system let them act on it.

3. A plan trustees can say yes to

Boards don't necessarily approve products ... they approve great plans. A named project lead, a phased timeline that steers clear of your biggest appeal, and a structured implementation programme with the effort spelled out up front will do more for you than any feature list.

A typical Donorfy implementation (FlightPath) asks for 32 to 50 hours from your team in total, and you know that figure before you start.

For trustees thinking about staff capacity, a clear ceiling on the commitment is exactly the reassurance they're looking for.

It's worth bounding the cost the same way. Set out what the system will cost over the next three to five years, allowing for growth in contacts or income, and put forecast returns alongside. When trustees can see the whole trajectory, this year's price becomes an investment with a visible return, rather than an open question.

Read our guide: How to build a competent charity CRM business case

The strongest business cases don't necessarily open with "we need a new CRM", but with the environment the charity is operating in.

The CAF UK Giving Report 2026 found six million fewer donors in the UK than a decade ago, with total giving falling from £15.4bn in 2024 to £14bn in 2025, and around 2.8 million people cancelling a regular donation in 2025 alone.

Meanwhile SORP 2026, the biggest update to charity accounting and reporting in years, is now in effect, bringing new income recognition rules, a three-tier reporting framework, and refreshed Trustees' Annual Report requirements including mandatory outcome reporting.

Read one way, that's a tough climate. Read another, it's a clear brief: the charities thriving in it are the ones that know their supporters well, steward every relationship, and can evidence their impact without heroic effort at year end.

A CRM that automates Gift Aid claims, keeps your segmentation sharp and gives the whole team the same view of your supporters is how a charity your size does all three. It's useful to frame it that way!

Every board asks questions, and the proposals that land are the ones where the questions have clearly been thought about in advance.

Here are the four you're likely to hear, and answers that work.

"We can't afford it right now."

The full picture usually says otherwise.

Work out what the current system costs in staff time, and check whether you're leaving Gift Aid unclaimed or paying for modules you don't use! Brake recovered £5,000 in backdated Gift Aid within months of switching, and Snow Camp's efficiency gains came out at a full-time role. For many charities, the system funds a meaningful part of itself.

"What happens if the migration doesn't go as expected?" 

A fair question with a reassuring answer: this is a well-trodden path.

Reputable providers offer structured implementation packages; Donorfy's go-live timeline is typically 4 to 10 weeks with expert-led support, with the 32 to 50 hours of team effort published up front. Ask any provider you're considering for a clear migration plan and reference customers you can speak to. Good ones will be glad you asked!

"Our staff won't use it."

Often this really means "our last system failed because nobody adopted it." 

Adoption is exactly where modern CRMs have improved most. Ask what training is included and what onboarding looks like. Brake found that a system their staff wanted to use changed everything: where their old CRM was so underused that teams were unknowingly approaching the same corporate donors, the new one became the place everyone worked.

"Now isn't the right time."

There's rarely a perfect time, but there's a strong case that now is a good one.

SORP 2026 makes robust supporter data more valuable than it's ever been, and a CRM handles the things trustees are accountable for, like consent preferences, secure storage and deletion requests, by design. The charities best placed in three years' time will be the ones investing in their data infrastructure now, and there's no reason yours can't be among them.

• Send the business case in advance: Trustees who've had time to read and digest arrive ready to engage rather than react.
• Lead with mission over technology: Start with what the CRM helps you do for beneficiaries and donors, and save the features and integrations for the appendix.
• Bring a one-page summary: Not everyone will read the full business case document, so a single-page board briefing with the headline numbers is helpful.
• Put names and dates on everything: Project lead: [Name]. Go-live target: [Month]. Board review: [Month]. Specific plans are more likely to get approved.
• Name a decision date: Ask the board to decide by a specific meeting, and you turn an open-ended discussion into a milestone.

The trustees who ask the hardest questions are often the ones who've seen an implementation go badly elsewhere, which makes them worth winning over properly.

Once they're satisfied the case stacks up, the risks have been thought through and the effort has a limit, they tend to become the project's strongest backers. Prepare well, and you're not just getting a system signed off, you're starting it with the whole board behind it.

Or as Jenny puts it:

"Stick to your guns. It will be worth it!"

Looking for a structured template to take to your board? Download the free Charity CRM Board Business Case Template: a practical, trustee-ready document covering financials, migration planning, objection responses and 2026 sector context.