Every channel keeps its own list
Donations arrive through several platforms and only one of them syncs. The rest get downloaded, matched by hand and re-keyed.
CMS: Central Management System. Fundraising, donors, volunteers and project delivery on one shared record.
Stop moving data between the platforms you use. With everything in one place, built-in AI can answer questions in plain English, flag who to contact next and turn each answer into a call list or campaign — no spreadsheets, no report builder.
Donations arrive through several platforms and only one of them syncs. The rest get downloaded, matched by hand and re-keyed.
Field reports, volunteer hours and Gift Aid forms sit wherever they were last saved. Someone has to find them and attach them to the right supporter.
Your CRM tells you what a donor has already given. It never tells you who to call next.
Every CRM can tell you what happened. This one can be asked why, who, and what to do about it — in the words you’d use with a colleague.
Plain-English questions across donations, donors, volunteers, campaigns and project delivery. No query builder, no report designer, no waiting on someone technical.
Patterns nobody had time to look for. Lapsing segments, giving anniversaries, campaigns underperforming against their own history.
Every answer is a working segment, not a dead end. Turn it into a call list, an email audience or a campaign in one click.
Charities don’t have a software problem. They have a seams problem. Donations in one platform, supporters in a CRM, volunteers in a spreadsheet, Gift Aid in a finance export, field reports in a folder — and a person whose job is quietly to carry data between them.
CharityCMS puts one donor record at the centre and feeds it from every channel. Your CRM, volunteers, Gift Aid, beneficiaries and project delivery all run off that record, with AI working across all of it. Everything we add afterwards plugs into the same record, rather than becoming another thing to reconcile.
Solid modules are part of the system from the start. Outlined modules are on the roadmap, shaped by founding partners.
Keep the platforms you already raise through. CharityCMS syncs what comes in from each one, matches it to the right supporter and keeps the full history on a single record.
With everything in one place, the AI can see what no single platform can: who is lapsing, who gives across channels, and who to call next.
Link the platforms and channels you already raise through, and bring in your history.
Each gift is matched to the right supporter, so every person has one complete record.
AI looks across every channel to spot patterns and answer questions in plain English.
Turn each answer into a call list, a segment or an update to the donors who funded a project.
Already raising on other platforms? Keep them. We sync what comes in and give you one place for everything else.
Not three products with an integration between them. One database, one donor record, one login.
41 donors gave to Ramadan last year and haven’t given yet this year. Here they are.
Amina gave £500 in October three years running. October is in six weeks.
Your water appeal is converting at half the rate of your orphan appeal. The difference is the second email.
No chatbot bolted onto a settings menu. Prompts that arrive when they’re useful — and a place to ask your own questions when you have them.
Each product carries a feedback schedule: an update at the start, at the mid-point and on completion. The schedule is created when the donation arrives, from whichever channel it came through, so the obligation is visible from day one — with an owner and a due date.
Field offices upload reports, photographs and completion evidence against a project ID. Everyone who funded that project receives it, and it is logged on their record. No filenames matched to names by hand.
Modelled on workflows we’ve mapped with charity partners.
A fundraising officer downloads exports from three giving platforms on the first of the month and matches 380 donors by hand. Two working days, and duplicates creep in every time.
External donations sync on arrival, matched against existing records. The two days go back to the officer, who spends them on the top 50 donors.
A field office emails 60 annual child reports as a zip file. The UK team downloads, renames, finds each sponsor, attaches, emails. Three weeks, and four sponsors get the wrong child.
The field office uploads against child IDs. Every sponsor gets their report the same day, branded, logged to the donor record automatically.
A regional lead “just knows” Yusuf is one of the good ones. Nobody knows he raised £11,400 across two Ramadans and brought in 34 first-time donors.
Yusuf tops the regional leaderboard, gets recognised at the annual dinner, and his 34 donors are flagged as a distinct acquisition segment.
Ramadan planning starts with “let’s email everyone.”
Filter — gave Ramadan 2025, hasn’t given Ramadan 2026, average gift over £100. 41 people. A phone list, not an email blast.
Founding partners shape the roadmap directly with the build team and hold preferential terms for the life of the partnership. The group is deliberately small enough that your requirements actually get built.
Founding partners get every module we release at their founding rate, including the ones that don’t exist yet.
Start a conversationFortnightly sessions with the people writing the code, not an account manager.
Your operational requirements get prioritised while the product is still forming.
Founding commercials, held for the life of the partnership.
We do the data work alongside your team rather than handing you an import template.
Central Management System — not content management system. CharityCMS brings the donor data from every platform and channel you use into one shared record, then runs your CRM, volunteers, Gift Aid, beneficiary records and project delivery off it. Later additions, such as email marketing, are built on the same record rather than becoming another tool to reconcile.
The channels charities raise through most: crowdfunding and peer-to-peer platforms, payment processors and website donation forms, Direct Debit, bank feeds, and spreadsheet or CSV imports for everything else. Tell us what you use; if a channel isn’t covered yet, we’ll say so before you commit.
It runs on your data only and is never trained on it or shared with other charities. It is read-only by default, so it reports on your records but never edits them. Every answer shows the filters it used, and role-based access means country offices can only ask about their own records.
You do. Your charity is the data controller and CharityCMS is the processor, under a DPA signed before onboarding. Data is hosted in UK/EU regions, encrypted in transit and at rest, with role-based access and an audit trail on every donor record.
Yes. We have mapped migrations from spreadsheet-and-inbox setups as well as Salesforce NPSP, Donorfy, Beacon and N3O exports. Donors, giving history, funds, campaigns and recurring mandates are mapped, loaded into a staging environment for your team to check, then cut over on an agreed date.
Declarations are brought in from every channel and stored against the donor with date, type and source. Eligible donations are flagged automatically and claims come out as an HMRC-ready schedule, with claimed and unclaimed amounts reconciled back to the donor record.
You export everything — donors, giving history, notes, documents, volunteers — as CSV plus original files, at any time, without asking us. On termination we provide a full structured export and delete your data on a defined schedule, confirmed in writing.
A founding partner with straightforward data typically has their main channels connected and syncing in four to six weeks, with CRM migration and field-office reporting following in the same quarter. Multi-office setups take longer, and we will say so before you commit.
Tell us how you fundraise today and we’ll walk the system against your own campaigns. Founding partner conversations, not sales calls.