Fundraising runs on trust, and the CRM is where that trust is either kept or quietly broken: a duplicate record, a thank-you that never went, an appeal to someone who asked not to be contacted.
Fundraising AI for donor operations is a set of checks and drafts that run inside your donor CRM: merging duplicates, verifying consent and Gift Aid declarations, noticing supporters who are drifting away, and drafting personal thank-yous for a fundraiser to approve. It makes the database trustworthy; it does not decide who to ask for money.
The constraint that shapes it is data protection. Supporter records are personal data under GDPR, and in the UK fundraising also sits under the Code of Fundraising Practice and the direct-marketing rules. The ICO has fined charities for profiling and wealth-screening donors without telling them. So nothing here builds a hidden profile, and every drafted contact is checked against the consent recorded for that person and channel before a human sees it.
Merge suggestions are tested against a sample your data team has already resolved by hand, and the threshold is set so that the system proposes rather than merges: two different people at the same address is a worse error than a duplicate left in place.
Consent checks are tested the other way round. The test set is built from records that must not be contacted, and a single draft reaching one of them stops the release. Thank-you drafts are sampled by the supporter care team for tone, because a warm letter with the wrong gift amount is worse than a late one.
Most safely in the operational work around the ask: cleaning supporter records, checking consent and Gift Aid, noticing lapsing regular givers, drafting thank-you letters and appeal variations for a fundraiser to edit. Less safely in profiling donors, which in the UK and EU needs transparency and a lawful basis decided by the charity. The relationship itself, and the decision of whom to ask for what, stays with people.
It can make sure fewer supporters slip away unnoticed. Signals such as a cancelled direct debit, a missed regular gift or a long gap after a first donation are surfaced to a fundraiser with a drafted, personal response. Whether that improves retention depends on what the team does next, so we measure it against your own history rather than quoting an industry figure.
We build on the CRM you already run, through its API or exports: Raiser’s Edge NXT, Salesforce Nonprofit Cloud, Dynamics 365, Beacon, Donorfy and similar. The CRM stays the system of record; the AI proposes changes and drafts, and a person applies them. Integration is usually the larger part of the work.
What we built, what stage it is at, and a link to the live thing wherever there is one.
yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.
Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.
Start with a look at your CRM and how consent is recorded. The quickest wins are usually in the data, not the model.
30-minute technical call · no deck