CRM Tips for Charities and Non-Profits

The 2024 NCVO Civil Society Almanac put UK voluntary sector income at GBP 71.6 billion, with around 165,000 registered charities sharing it. The bigger story sits in the long tail: more than 80 percent of those charities turn over less than GBP 100,000 a year, and most run on volunteer time and a single laptop. That is the reality this guide is written for, not the household-name charities with full development teams.

Charity CRMs get talked about as if they are a different species from business CRMs. They are not. Donors are clients with a different reason for buying. The mechanics, contact records, segmented campaigns, automated follow-ups, clean reporting, are the same. What changes is the regulatory frame, the language, and the fact that supporter trust is the entire product.

What a charity actually needs from a CRM

A charity CRM has to do three jobs reliably before anything else.

  1. Record every gift accurately, with date, amount, fund, campaign, and Gift Aid status.
  2. Track consent and contact preferences at a granular level, by channel and by purpose.
  3. Segment supporters so the right people get the right ask, and lapsed supporters do not get marketing aimed at active donors.

Everything else, event management, volunteer rotas, peer-to-peer fundraising, is a nice-to-have. Get the three above right and the rest can be bolted on later.

Custom fields that matter for charities

Out-of-the-box CRMs assume a sales cycle. Charities need a different set of fields. These are the ones that earn their keep.

FieldRecord TypePurpose
Supporter typeContactDonor, regular giver, volunteer, beneficiary, trustee, corporate
Lifetime givingContactCumulative donations across all years
First gift dateContactDrives anniversary thank-yous and tenure segmentation
Last gift dateContactIdentifies lapsed supporters before they go cold
Gift Aid declarationContactYes (enduring), Yes (single), No, Refused, Unknown
Declaration dateContactRequired for HMRC retention and audit
Consent: email, post, phone, SMSContactOne flag per channel, with date and source
Campaign sourceDonationFirst-touch attribution for every gift
Restricted fundDonationWhere the gift must be applied, by donor instruction
Legacy intentionContactConfirmed pledge, soft pledge, expressed interest

For a deeper look at structuring fields like these, see how to use CRM tags and custom fields effectively.

Donor segmentation: the single biggest lever

Most small charities send the same email to everyone on the list. That is the fastest way to burn through the goodwill of long-standing supporters and waste your acquisition spend on cold contacts. The Institute of Fundraising’s standing benchmark is that retaining a donor costs roughly a fifth of acquiring a new one, which makes segmentation the highest-return work most charities can do.

A workable segmentation model for a small charity looks like this.

Recency of last gift Annual value New donors First gift in last 90 days Welcome series, no second ask yet Active regulars Gift in last 12 months Standard appeal cadence Mid and major Cumulative GBP 1k+ or recent GBP 500+ Personal contact, no mass email Reactivated Returned after 18+ months Dedicated welcome-back stream Lapsed No gift in 18 to 36 months Reactivation appeal, then archive Cold archive No gift in 36+ months Suppressed from marketing Treat each segment differently. The CRM does the sorting; the team writes the messages.

The point of segmenting is not to send more mail. It is to send less, more precisely. A new donor who gave a fiver to a Christmas appeal does not need three Easter asks before April. They need a thank-you, a story about what their gift did, and one well-judged second invitation. For broader principles on segmenting your contacts, see how to segment your client database.

Gift Aid: the easiest 25 percent your charity will ever earn

UK charities can reclaim 25p for every GBP 1 of eligible donations from UK taxpayers under the Gift Aid scheme administered by HMRC. Most small charities leave money on the table because their CRM either does not store declarations correctly or cannot produce the schedule that HMRC’s Charities Online service expects.

Three things to get right.

  1. Store the wording the donor signed. A 2014 declaration uses different wording from a 2024 one, and HMRC can ask to see the exact text years later.
  2. Flag enduring vs single declarations. An enduring declaration covers all past four years and all future donations. A single covers one gift only. Mixing them up is the most common Gift Aid claim error.
  3. Reconcile claims to your accounts. Quarterly is sensible. Run a CRM report of eligible gifts in the period, compare to the schedule submitted, and chase declarations for any gap.

Official guidance lives on the HMRC Gift Aid claim page ↗ and the supporter-facing rules sit on the government’s donating to charity page ↗. Both are worth bookmarking inside your CRM as reference links for fundraisers who handle declarations.

Charities sit under three sets of rules: UK GDPR enforced by the Information Commissioner’s Office ↗, the Code of Fundraising Practice from the Fundraising Regulator ↗, and PECR for electronic marketing. A CRM that handles consent loosely is a regulatory risk and a reputational one.

Non-negotiables for a charity CRM:

  • Per-channel consent flags for email, post, phone, SMS, with date and source recorded against each
  • Per-purpose consent so a supporter can opt in to fundraising appeals but out of campaigning, or vice versa
  • Lawful basis recorded against every contact (consent, legitimate interest, contractual necessity)
  • Suppressions honoured across the database, not just within one mailing list
  • Audit trail showing who changed a consent flag and when
  • Retention rules so unused contacts are reviewed annually and archived if no engagement

The Fundraising Regulator runs the Fundraising Preference Service, which lets the public block fundraising contact from named charities. Your CRM must check the FPS suppression list before any campaign goes out. Missing that step is one of the fastest ways to land in front of the Regulator.

For a wider checklist that applies across small businesses including charities, see CRM and GDPR: a compliance checklist for UK small businesses.

Donor retention: the metric that runs the charity

The single number worth reading every month is your donor retention rate. UK sector benchmarks tracked by NCVO and others sit between 40 and 50 percent for first-year retention and 70 to 80 percent for second-year and beyond. If you are below those, your acquisition spend is leaking out of a bucket.

What actually moves retention:

  • Send a thank-you within 48 hours of every gift. Email is fine for under GBP 50, a personal letter for above. The CRM triggers the workflow; a human signs the over-GBP-50 letters.
  • Tell the donor what their gift did, specifically, within four to six weeks. “Your GBP 30 funded one home visit” beats “thanks to supporters like you” every time.
  • Anniversary a first gift with a short note, not an ask, on the one-year mark.
  • Catch failed direct debits within seven days. A failed DD that runs for three months is usually a lost regular giver.

For a fuller approach to keeping supporters engaged, see how to build a client loyalty programme with your CRM.

Automations worth setting up

Volunteer time is the most expensive resource a small charity has. Use the CRM to remove the admin that nobody enjoys.

TriggerAutomationOutcome
New gift receivedTagged thank-you email within an hourAcknowledgement, no manual queue
First gift from new donorThree-step welcome series over 14 daysSecond-gift conversion lift
Direct debit failureNotification to fundraiser plus supporter emailRetention of regular givers
Lapsed 18 monthsReactivation appeal, fall back to archiveClean active list, lower send costs
Event signupReminder sequence and post-event surveyBetter attendance, supporter feedback
Major gift receivedTask to executive director within one dayPersonal acknowledgement at speed

For broader patterns that work for small organisations, see email sequences every small business should set up.

What to leave out of the CRM

Two areas regularly get pulled into a CRM and shouldn’t.

  • Beneficiary case management for safeguarding-sensitive services. Use a dedicated case management tool with the right access controls. Mixing donor records with safeguarding notes in the same database is a problem waiting to happen.
  • Restricted-fund accounting. Track the campaign source and restricted instruction in the CRM; do the actual fund accounting in your finance system. The two need to reconcile, not duplicate.

Reporting that the trustees actually want

Trustees do not need 40 dashboards. They need four numbers, every quarter, with last quarter for comparison.

  • Income by source (regular giving, single gifts, major gifts, legacies, grants, trading)
  • Donor retention rate (first-year, multi-year)
  • Cost per pound raised (for each significant channel)
  • Gift Aid claimed vs eligible (a leakage indicator)

If your CRM cannot produce those four reliably, the configuration needs a rethink before the next campaign. For more on building reports that drive action, the same principles in the real cost of not having a CRM apply directly.

Start with one segment, one workflow

The temptation with a new charity CRM is to import every spreadsheet, set up every automation, and design the perfect supporter journey on day one. That is how CRM projects stall. A better approach: pick one segment (new donors), build one workflow (welcome series with a 30-day second-gift ask), measure the result for two months, then move to the next segment. The charities that get the most from CRM software are the ones that ship one tidy workflow at a time, not the ones with the longest implementation plan.

If you want the bigger picture on what good looks like across the sector, the NCVO Civil Society Almanac ↗ is the most useful single reference. For regulatory grounding, the Charity Commission for England and Wales ↗ covers governance and reporting duties for registered charities. Bookmark both inside your CRM and refer fundraisers to them whenever a question on consent, reporting, or compliance comes up.

Frequently asked questions

Do charities need a specialist non-profit CRM?

Not always. Specialist tools like Beacon, Donorfy, Salesforce NPSP, and Blackbaud Raiser's Edge are excellent once you process more than around 10,000 donations a year, run a regulated lottery, or need deep Gift Aid integration. Below that, a well-configured general CRM with custom fields for donation amount, Gift Aid status, and campaign source handles most small charity needs at a fraction of the cost. The deciding factor is usually Gift Aid claim volume and whether you accept legacies, not size of database.

How should a charity handle Gift Aid in its CRM?

Store the declaration text the donor signed, the date they signed it, the lawful basis for storing it, and an enduring or single-donation flag. HMRC can ask to see declarations for six years after the last claim, so retention matters. If your CRM does not produce an HMRC-format claim file, export a CSV that matches the Charities Online schedule and submit through the HMRC online service. Reconcile the claim against your accounts every quarter to catch missed declarations early.

What does GDPR require from a charity CRM?

Two things matter most. First, a clear lawful basis recorded against every contact: legitimate interest for existing supporters, consent for cold marketing, contract for service users, and explicit consent for any special category data. Second, separate consent flags for each channel (email, post, phone, SMS) and each purpose (fundraising, campaigning, service updates). The ICO and the Fundraising Regulator both expect granular, refreshable consent that the donor can change at any time.

How do we track legacies in a CRM without being insensitive?

Create a separate, restricted pipeline for legacy intentions and pledges. Only fundraisers with a clear need should see it. Use respectful field names (legacy intention confirmed, executor contact, pledge stage) rather than commercial deal language. Never automate marketing into this pipeline. Legacy giving is often the largest single income stream a small charity will ever receive, but trust evaporates the moment a bereaved family receives a templated supporter email.

How often should a charity run a database review?

Quarterly for active supporters, annually for the full database. Look for lapsed donors (no gift in 18 to 24 months), failed direct debits, expired Gift Aid declarations, deceased contacts, and supporters whose consent is older than two years. A database review is not just hygiene; it is a UK GDPR obligation. Most charities find that ten to fifteen percent of their list should be archived or refreshed at any one time, and acting on it usually lifts campaign response rates noticeably.

Enjoyed this article? Get more CRM tips straight to your inbox.

Comments

Join the conversation. Share your experience or ask a question below.

0/1000

No comments yet. Be the first to share your thoughts.