Fixed quote after a free call

CRM automation for charities that keeps every supporter in one place

Gifts arrive through online giving pages, peer-to-peer platforms, events, bank transfers and the post, and supporters get lost between them. We connect every source to your donor management software, such as Salesforce Nonprofit Cloud, Bloomerang or Beacon, merge duplicates, record consent and Gift Aid status on the right record, create thank-you tasks for major and first-time donors, and send a monthly income view by source and campaign. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why charity supporter data splits across systems

Most charities run several giving channels at once, and each keeps its own list. A supporter who gives online, runs a sponsored event and signs up to volunteer can appear three times, with different consent records on each.

Without one clean record, thank-yous are missed, the same person gets two appeals, marketing consent is unclear and the monthly income figure takes a day of spreadsheet work. Small teams spend hours on data entry that should go to supporters.

What we build

What our CRM automation for charities includes

Every channel into the CRM

Online giving, peer-to-peer pages, event registrations, forms and bank imports create or update supporters and gifts.

Duplicate matching

Supporters matched by email, address and name rules you agree, with uncertain matches sent to staff.

Consent on the record

Marketing consent, channel preferences and Gift Aid declarations stored on the supporter record, with their source and date.

Thank-you tasks

Tasks for first-time, major and lapsed-returning donors so a person thanks them personally.

Campaign and source coding

Gifts coded to campaign, appeal and fund so reports add up.

Monthly income view

Income by source, campaign and fund emailed to the finance lead and trustees.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Gift or sign-up arrives

    A donation, registration or form creates or updates a supporter.

  2. 02 Automated

    Record matched

    Duplicates are matched by agreed rules and consent is recorded.

  3. 03 Automated

    Tasks created

    Thank-you and follow-up tasks go to the right staff member.

  4. 04 Staff review

    Staff review

    Staff check uncertain matches and thank key supporters personally.

  5. 05 Charity lead or trustees decide

    Supporter strategy

    Appeal strategy and how supporters are approached are decided by the charity lead.

How it behaves

How the charity CRM behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What supporters see

  • A prompt thank-you after their gift
  • One appeal, not two, because they appear once
  • Messages that respect their preferences

What staff see

  • One record per supporter with gifts, consent and Gift Aid
  • Thank-you tasks for key donors
  • A monthly income view by source and fund

What the automation does

  • Captures gifts and sign-ups from every channel
  • Matches duplicates and codes gifts
  • Sends uncertain matches to staff

Edge cases and fallbacks

Couple gives from a joint account
Linked to a household with both names, following your rules.
Uncertain duplicate match
Sent to staff to confirm rather than merged automatically.
Gift arrives without consent information
Recorded with no marketing consent until the supporter opts in.
CRM API limit or outage
Gifts are queued and retried, and the data lead gets an alert.

Architecture

A charity CRM fed by every channel at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Online giving Donation pages Fundraising pages Peer-to-peer Forms and events Sign-ups, bank n8n Match and code Charity CRM Supporters, gifts Thank-you tasks For staff Income view Monthly
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 Gifts and sign-ups arrive from donation pages, fundraising platforms, events, forms and bank imports.
  2. 2 n8n matches each one to an existing supporter or creates a new one, and codes the gift to campaign and fund.
  3. 3 Consent and Gift Aid status are stored, and thank-you tasks go to staff.
  4. 4 A monthly income view goes to the finance lead and trustees.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Charity CRM & donor management automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Giving channels, current CRM setup, coding structure, consent records and reporting needs.

  2. 02

    Design

    2 to 3 days

    Matching rules, field mapping, consent and Gift Aid fields, task rules and report layout.

  3. 03

    Build

    1 to 2 weeks

    Channel connections, matching, coding, tasks and the income view.

  4. 04

    Shadow run

    About 1 week

    Gifts flow into a sandbox or flagged records while staff compare with manual entry.

  5. 05

    Launch

    1 to 2 days

    Switch over and walk the team through tasks and reports.

  6. 06

    Support

    Ongoing

    New channels, campaign codes and reporting tweaks.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Salesforce Nonprofit Cloud (Fundraising APIs) Bloomerang REST API Beacon API Donorbox API and webhooks JustGiving through Blackbaud SKY API

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Channels, matching rules, coding and reporting.

    $200 – $400

  • Build

    Capture, matching, coding, tasks and reports.

    $500 – $1,300

  • Integrations

    CRM, giving platforms and bank imports.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with manual entry.

    $100 – $250

  • Launch and training

    Switch-over and team walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM, giving platform and n8n subscriptions are billed to you directly. A large historic data clean-up is quoted separately.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • CRM subscription: Your CRM vendor's own plan, including any nonprofit pricing.
  • n8n: Self-hosted Community edition on your own server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

UK: charity soft opt-in under PECR

Since 5 February 2026, PECR regulation 22(3A) lets charities email supporters who expressed interest in or supported their purposes without fresh consent, if they were offered a simple way to refuse at collection and in every message. The CRM records how and when each contact was collected.

Source: www.legislation.gov.uk

EU and UK: processors under contract

Supporter data is personal data, so the CRM and automation host work under written processor contracts under GDPR Article 28.

Source: gdpr-info.eu

US: commercial email opt-outs

Where messages are commercial, CAN-SPAM requires opt-outs honoured within 10 business days and a valid postal address; we apply one shared opt-out list across tools.

Source: www.ftc.gov

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

CRM for charities questions questions, answered.

It depends on size and budget. Salesforce Nonprofit Cloud suits larger charities with in-house admins, Bloomerang and Beacon are built for small and mid-sized nonprofits, and Raiser's Edge NXT is common in established fundraising teams. We can work with the CRM you already have.

Some general CRMs have free tiers and some vendors offer nonprofit discounts, but the cost that matters most is staff time on data entry. We focus on getting every gift into whichever CRM you choose automatically.

It keeps supporters, gifts, consent and communications in one place. Our automation feeds it from every giving channel so the data is complete without manual entry.

Yes. Small charities often gain the most, because one or two people handle every channel. We keep the build small and use the tools you already have.

It stores the declaration, its date and source on the supporter record so claims can be prepared accurately. The claim itself is submitted by authorised staff.

Gifts entered automatically, duplicates caught, time to thank first-time donors, consent coverage and how long the monthly income report takes.

Free 20-minute call

Want this for your charity?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call