Nonprofit fundraising CRM: what it does that a contact list cannot

A nonprofit fundraising CRM is a donor record with a fundraising process wrapped around it: appeals with sources attached, segments that update themselves, tasks against relationships, and reporting that ties income back to what caused it. Organisations usually go looking for one at the point where a spreadsheet stops being able to say which appeal paid for itself.

What a nonprofit fundraising CRM adds

• Attribution: every gift carries the appeal, channel and campaign that produced it, so cost per pound raised is calculable rather than felt.
• Segments that recalculate — lapsed, upgraded, first-time — instead of being rebuilt by filtering a sheet each month.
• Stewardship tasks with owners and dates against major relationships.
• Pipeline for asks in progress, which is the part that distinguishes fundraising from receipting.
• Communication history in one place, including what each person was sent and what they opened.
• Consent and preference handling at the record level, applied automatically when a list is built.

Where a general CRM is enough

Be honest about scale. Below a few thousand supporters and a handful of appeals a year, a general CRM plus your payment provider covers it: contacts with gift history, pipelines for major asks, tasks for stewardship, and lists for mailing. Ettex CRM does that part, and pairing it with a donor register in Ettex Records keeps the gift history and the relationship in the same place. The saving is real, and so is the ceiling.

Ettex is not a dedicated fundraising platform. There is no built-in donation page with payment processing, no tax-relief claim generation, no wealth screening and no legacy or grant pipeline module. If your operation depends on those, buy the sector product — the integration cost of bolting them onto a general CRM usually exceeds the licence you avoided.

Choosing, if you do buy one

1. Count your supporters and your appeals per year honestly — most sector software is priced on records and most quotes assume growth you have not had yet.
2. List the integrations you actually need: payment provider, email tool, accounting, website forms.
3. Ask how data comes out, not only how it goes in. Export format and completeness is what protects you at renewal.
4. Test a real import of your existing list before signing, including the messy duplicate rows.
5. Check who can change a consent flag and whether the change is logged.
6. Price the migration and the training, which together often exceed the first year of licence.

What to fix before buying anything

Software does not deduplicate a list that has never had a rule for what a duplicate is, and it does not create attribution for appeals that were never coded. Fix the record first: one row per supporter, gifts attached, sources recorded, consents dated. Organisations that do that discover either that the tooling problem was smaller than they thought, or exactly which module they are buying — and both outcomes are cheaper than a migration into software chosen on a demo.

The underlying habits do not change with the tooling: donor management is still about the second gift, and a membership database is still about the renewal date.