Case Study

Case Study: Charity Donor CRM & Fundraising Automation

We built a connected set of automations for a small registered charity running community programmes with a handful of staff and many volunteers: every gift flowing into the donor CRM, acknowledgements and Gift Aid checks, one-step fundraising sign-up with automatic pages, volunteer onboarding and grant reporting packs. Staff now spend less time on data entry and more with supporters, and every decision on safeguarding, claims and funder reports stays with people.

Organisation type
Small registered charity with community programmes
Team involved
Chief executive, fundraising lead, finance officer, volunteer coordinator, trustees
Systems connected
Charity CRM, JustGiving, Stripe, Xero, Microsoft 365, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Gifts arrived through online giving, fundraising pages, events and bank transfers, and were typed into the CRM by hand. Supporters appeared more than once with different consent records.

Acknowledgements went out in batches when someone had time, and Gift Aid claims took days of checking declarations.

Supporters signing up for the annual challenge had to create their own fundraising page, and many never did.

Volunteer applications waited weeks for a reply, and grant reports were compiled from four spreadsheets the week they were due.

Goals

What the project had to change

  • Every gift and supporter in one clean CRM record with consent and Gift Aid status.
  • Prompt acknowledgements with the right details, and clean Gift Aid claim lists.
  • One-step challenge sign-up with a fundraising page created automatically.
  • Volunteers move from application to first shift without delays.
  • Grant reports drafted weeks before each deadline with sourced figures.

What we built

What we built, as one connected system.

01

Donor CRM feed

We connected online giving, fundraising pages, event sign-ups and bank imports to the CRM with duplicate matching, campaign coding, consent and Gift Aid fields, thank-you tasks and a monthly income view.

Service details
02

Receipts and Gift Aid

Acknowledgements now go out from approved templates for each gift type, Gift Aid declarations and benefit limits are checked before each claim, and sponsorship invoices are drafted in Xero.

Service details
03

Fundraising pages

One challenge sign-up form registers the supporter and creates their JustGiving page to claim, donations flow into the CRM, and fundraisers get milestone nudges.

Service details
04

Volunteer onboarding

Applications are acknowledged at once, references and checks are tracked as coordinator tasks, induction goes out in order and shifts are reminded with hours logged.

Service details
05

Grant reporting packs

Reporting dates sit on one calendar, and draft packs with activity, hours and spend by grant code arrive weeks ahead for leads to review.

Service details

Architecture

How the charity's workflows connect

Giving channels Online, pages, bank Sign-up forms Events, volunteers n8n Five workflows Charity CRM Supporters, gifts Xero Invoices, spend Receipts, nudges Email Staff Tasks, reviews Charity lead Claims, reports
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Giving channels and sign-up forms feed one n8n instance.
  2. 2 Five workflows update the CRM and Xero and send receipts, page links and nudges.
  3. 3 Staff work tasks, check exceptions and review draft reports.
  4. 4 The charity lead approves Gift Aid claims and funder reports before submission.

How it behaves

How the system behaves day to day

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

What supporters see

  • A prompt thank-you with the right receipt details
  • A ready fundraising page after one sign-up
  • Volunteer next steps the day they apply

What staff see

  • One record per supporter
  • Gift Aid exception lists before claims
  • Coordinator tasks for checks and induction
  • Grant drafts weeks before deadlines

What the automation does

  • Captures and matches gifts from every channel
  • Sends receipts, creates pages and sequences induction
  • Pulls report data by grant code and logs every step

Edge cases and fallbacks

An uncertain duplicate supporter
Sent to staff to confirm rather than merged.
A gift without a Gift Aid declaration
Excluded from the claim and the supporter invited to declare.
A volunteer applicant under 18
Routed to the coordinator under the youth volunteering policy.
A grant activity not coded
Listed for staff to code before figures are used.
n8n or a platform is down
Runs queue and retry; staff work from their tools as before and get an alert.

Integrations

What we connected

All integrations

JustGiving

Fundraising platform

Fundraising pages created for supporters and donations into the CRM.

JustGiving API, migrating to Blackbaud SKY API.

Stripe

Payments

Donation pages, event payments and webhooks into the CRM.

Stripe Payment Links, the Stripe API and webhooks.

Xero

Accounting

Sponsorship invoices and spend by grant for reports.

Xero Accounting API.

Microsoft 365

Workspace

Shared inbox, documents, calendars and Teams alerts.

Microsoft Graph API.

n8n

Automation platform

Runs every workflow, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We mapped giving channels, receipts, Gift Aid, the challenge sign-up, volunteer steps and active grants, agreed data flows and signed processor agreements.

  2. 02

    Design and access

    Week 2

    Matching rules, templates, page settings, induction steps, grant mapping and API access to the CRM, JustGiving, Stripe and Xero.

  3. 03

    Sprint 1: CRM feed

    Week 3

    Built and shadow-ran gift capture and matching beside manual entry; demo and sign-off.

  4. 04

    Sprint 2: receipts

    Week 4

    The CRM feed went live. Built acknowledgements, Gift Aid checks and invoice drafts.

  5. 05

    Sprint 3: fundraising pages

    Week 5

    Receipts went live after finance checked a parallel batch. Built one-step sign-up and page creation.

  6. 06

    Sprint 4: volunteers

    Week 6

    Sign-up went live for the challenge. Built volunteer onboarding and shift reminders.

  7. 07

    Sprint 5: grant reports

    Week 7

    Volunteer onboarding went live. Built the grant calendar and draft packs.

  8. 08

    UAT and handover

    Week 8

    Staff ran acceptance testing on every workflow, then we handed over the run book and briefed trustees.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures gifts from every channel and matches supporters
  • Sends acknowledgements and checks Gift Aid records
  • Creates fundraising pages and processes donations
  • Acknowledges volunteer applications and sequences induction
  • Pulls grant report data and drafts packs

The team does

  • Confirm uncertain matches and thank key supporters
  • Review receipt and claim exceptions
  • Support fundraisers and volunteers personally
  • Write grant narratives and check figures

Charity lead or trustees decide

  • Approves Gift Aid claims and tax filings
  • Makes every safeguarding and volunteer suitability decision
  • Signs off funder reports
  • Sets fundraising strategy and supporter approach

Compliance handled

Privacy, consent and safety, built in.

US acknowledgement rules

Templates for US gifts include the written acknowledgement details for gifts of $250 or more.

Source: www.irs.gov

Gift Aid records

Declarations and benefit limits are checked before claims, and only authorised staff submit them.

Source: www.gov.uk

Charity soft opt-in

Supporter emails rely on PECR regulation 22(3A) only where the conditions are met, with a refusal option in every message.

Source: www.legislation.gov.uk

Check results kept out of automation

Only check status is stored; criminal record data is not processed by the workflow.

Source: gdpr-info.eu

Processors under contract

Every vendor touching supporter data signed a processor agreement before go-live.

Source: gdpr-info.eu

Outcomes

What changed for the practice

  • Gifts from every channel now reach the CRM without retyping, on one record per supporter.
  • Donors receive acknowledgements promptly with the right details for their gift.
  • Gift Aid claims start from a checked list instead of days of manual review.
  • More challenge sign-ups end with a live fundraising page.
  • Volunteers hear back the day they apply and move to induction in order.
  • Grant reports start weeks before deadlines with figures that trace to records.

What we track

The measures the practice watches.

Data entry

Gifts entered automatically and duplicates caught.

Acknowledgements

Days from gift to acknowledgement.

Gift Aid

Exceptions per claim and time to prepare a claim.

Fundraising pages

Sign-ups that become active pages and average raised per page.

Volunteers

Days from application to first shift.

Grant reports

Reports submitted on time and staff hours per report.

Cost estimate

What a project like this costs

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

    Process mapping, data flows, templates and the backlog.

    $1,000 – $2,000

  • CRM feed module

    Capture, matching, coding, tasks and income view.

    $700 – $1,700

  • Receipts and Gift Aid module

    Acknowledgements, checks and invoice drafts.

    $700 – $1,700

  • Fundraising pages module

    Sign-up, page creation, webhooks and nudges.

    $700 – $1,700

  • Volunteer module

    Applications, tasks, induction and reminders.

    $600 – $1,500

  • Grant reporting module

    Calendar, data pulls and draft packs.

    $700 – $1,700

  • Integrations

    CRM, JustGiving, Stripe, Xero and Microsoft 365.

    $300 – $700

  • Testing, UAT and launch

    QA, acceptance testing, launch and training.

    $300 – $1,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every charity gets its own fixed quote after a free call.

Monthly running costs you pay directly

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

  • n8n: Self-hosted Community edition on the charity's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • CRM and platforms: The CRM, JustGiving and Xero plans, including any nonprofit pricing.
  • Payments: Stripe's own published processing fees.

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

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.

Free 20-minute call

Want this built 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