How to choose a charity CRM: capability versus complexity

Most charities start by asking which CRM is best. They ask around, read a few articles, and come away with contradictory answers and less confidence than they started with.

The problem isn’t the answers. It’s the question. “Which CRM is best?” has no useful answer, because the right system for a tiny fundraising team is often the wrong one for a ten-person charity running structured programmes, and the other way round.

I’ve run this process twice in the last few months. Both times the shape was the same: a simpler, well-liked system like Beacon on one side, something more powerful like Salesforce on the other, and a hard question about which they’d regret. Salesforce can do almost anything. It can also intimidate, and I’ve watched charities take it on and struggle to get value out of it. The right answer was different each time, and neither time was it about which system was ‘better’. It was about what each charity needed, and what each could take on.

So there’s a better way to ask the question: best for what, and best for whom? Put that way, the choice stops being a vague popularity contest and becomes something you can reason about. This post is about how you do that.

Start with the trade-off itself. Capability is what a system can do: how much you can track, shape, and automate to fit how your charity actually works. Complexity is what it takes to get there: the setup, the configuration, the expertise to build it well. The two tend to rise together, because all that flexibility has to be shaped into something that works for you. More capability usually means more complexity, and the right choice depends on how much of each you need.

One word in that trade-off can cause confusion. When I say a system is complex, people sometimes hear “complex for my team to use.” But complex to set up doesn’t necessarily mean complex to use. The complexity is in the building, and how the system feels day to day depends on how well it was built, not on how customisable it is. A well-configured Salesforce can present your team with a clean, simple screen that shows them only what they need. The power sits underneath; it doesn’t have to surface. When you weigh complexity, you’re not asking whether the system will be hard for your team to use. You’re asking whether you can resource the work of setting it up well.

A kitchen is a good way to picture it. Most of us cook fine in an ordinary domestic kitchen. It came more or less ready to use, and it handles almost everything a household needs. A professional kitchen - for example, in a Michelin-star restaurant - can do far more, but it has to be designed and fitted around the menu, and that takes time, money, and someone who knows what they’re doing. The difference is all in the building. Once either is set up, cooking a simple meal in the professional one isn’t harder; far more work just went in before the first pan was lifted. And the person eating never sees the fit-out, unless they’re the kind of guest who opens your cupboards. They only taste the result.

The powerful option isn’t harder to live with, then. What matters is whether you need what it can do, and whether you can resource the building. Four questions can help you judge these things.

What do you need it to do?

Start with scope, because it sets everything else. What do you want the system to handle?

For some charities the answer is contained: tracking supporters and donations, sending appeals, keeping good records. That’s a well-understood job, and plenty of systems do it well without much customisation. For others it’s broader: running programmes, managing cohorts, recording outcomes for funders, coordinating volunteers, maybe three of those at once. The more you’re asking the system to hold, and the further it sits from standard fundraising, the more it has to be customised for you, and customising is where the complexity lives.

There’s a second part to the question, and it’s easy to miss: how much will this change? A charity doing the same well-understood work in five years’ time can buy for today and be fine. A charity whose programmes shift each year, or that expects to grow into new kinds of work, is buying for a moving target. A simpler system can be quicker to start with and then become the thing you’ve outgrown. That risk doesn’t show up on day one, which is exactly why it’s worth thinking about explicitly when deciding.

Scope, then, has two axes: how broad your needs are now, and how much they’ll move. Broad or moving needs point toward capability, and the complexity that comes with it. Contained, stable needs point the other way. It’s tempting to buy for the charity you imagine becoming; it’s usually wiser to buy for the one you can actually see, with enough room to grow that you’re not boxed in.

What can you resource?

Notice the question isn’t “what’s your budget?” It’s what you can resource, which is a larger and more honest thing.

Start with money, but not the way it’s usually counted. The common mistake is to ask what budget you already have. Almost no charity has a CRM budget sitting ready; investing in one nearly always means finding money that isn’t currently allocated. So the better question is what you could free up or raise if you decided this mattered. That shift, from “what’s spare” to “what’s this worth,” is often what unlocks the right decision.

And count the whole cost, not just the licence. Underneath the subscription sits setup, configuration, training, and support, the work that turns a tool into something that fits you. Charities routinely budget the licence, skip the rest, and then conclude the CRM failed, when really it was never resourced to succeed. The more capable the system, the larger that underneath cost.

Then there’s the resource people forget entirely: time. A CRM project takes internal hours, during setup, during migration, and in the ongoing care afterwards. Even with outside help carrying the technical load, someone inside has to make decisions, answer questions, and keep it healthy. A charity with no slack to give it is taking on more risk with a complex system than the budget alone suggests.

Put money and time together and where you stand is clear. Thin resource, in either, points toward the simpler system you can stand up quickly and maintain lightly. Real resource makes the capable system a sound investment rather than a gamble. What sinks CRM projects is rarely the tool. It’s taking one on without the means to see it through.

Who’s going to own it?

Every system needs someone inside the charity who owns it. Not just for setup, but for the life of the thing: the person who understands how it’s put together, makes the calls when something needs to change, and keeps it from quietly drifting out of date.

Sometimes a charity has someone with real appetite for this, curious about the tech, willing to learn, glad to be asked. That person makes a great deal possible. With the right support around them, they can take on a good deal of the configuration themselves, and grow into the long-term owner the system needs. Appetite matters more than existing skill: someone keen who’s given time to learn will outrun someone skilled who’s been handed it on top of a full job and told to cope.

This points to a constraint that really matters - time and permission. A capable, willing person with no protected hours to give the system is in almost the same position as having no one. If you want someone to own the CRM, someone has to decide that owning it is part of their job, not an extra balanced on top.

This is where capability and complexity bite hardest. A simpler system asks less of its owner; it survives lighter attention and a less technical hand. A more capable system rewards a strong, committed owner and punishes the absence of one, because there’s more to maintain and more to drift. So the question is this: do you have someone who can own this, and will you give them the time to? A confident yes opens the door to the capable system. A no, or a maybe, points firmly toward the simpler one, whatever the budget could stretch to.

Who’s already doing this well?

The other three questions look inward. This one sends you outward, to charities a step ahead of you, because the fastest way to get a sense of where you really sit is to see how someone like you fared.

Be careful what “like you” means, though. The instinct is to look at charities with the same cause: another homelessness charity, another arts organisation. But cause is the wrong axis. Two homelessness charities can have completely different systems, because one runs structured programmes and the other does straightforward fundraising. An arts charity and a youth charity that both run cohort-based programmes might need almost the same setup. What makes a charity comparable is the shape of its operations, what it does day to day, not the field it works in.

There’s a trap on the way, too. Ask around widely and you’ll hear flatly contradictory things: the same system praised and damned in the same afternoon. That’s not because people are wrong; it’s because a CRM that was right for one charity’s operations was wrong for another’s, and they’re each reporting honestly from where they stand. Wide crowdsourcing feels like research, but it rarely settles anything.

What does help is going narrow and deep. Find two or three charities whose operations resemble yours, with a CRM that’s working, and talk to them properly. Not “do you like it?” but much more specific questions: how long did setup take, what did it really cost once everything was counted, who looks after it now, what would they do differently. A couple of honest conversations like that teach you more than a dozen quick opinions.

This question doesn’t point you one way so much as reinforce the other three. They tell you where you sit; the right comparators tell you whether you’ve read yourself correctly, and show you in advance what the choice you’re leaning towards will actually feel like to own.

Four questions, then. What do you need it to do? What can you resource? Who’s going to own it? Who’s already doing this well? None of them is about which CRM is best, because that is not the right question. They’re about you: your needs, your resources, your people, your situation assessed honestly.

That’s the better way to think about it. Choosing a CRM feels like a technical decision, the kind you need to be technical to make. It isn’t. The hard part isn’t knowing the systems; it’s knowing your organisation well enough to see which one fits. Answer these four honestly and you’ve got a good foundation for doing that. The shortlist tends to follow from the answers, and a conversation with anyone technical becomes far easier, because you arrive knowing what you need rather than hoping to be told.

Beacon or Salesforce, simple or capable, the right answer depends on who’s asking.