Quiet friction: a nonprofit technology audit
By Ben Serunyigo, co-founder of Nimara · Updated October 2026
Most nonprofits and charities I talk to don't have a broken system. They have a dozen small things that take longer than they should. A gift comes in through the donation form, someone copies it into a spreadsheet, someone else types the receipt, and a third person adds the donor to the newsletter list, if they remember. Nothing is technically wrong, but everyone is double-checking, and the week fills up with work nobody planned for.
I call it quiet friction. It doesn't feel urgent enough to fix, so it never gets fixed, and it adds up.
A nonprofit technology audit is a plain, honest look at the tools your team uses, where your information lives and where it gets stuck. A useful one has five steps: list every tool, name an owner for each, follow one gift and one sign-up through your systems, check what donors experience, and pick one thing to fix first. Most nonprofits and charities don't need more software. They need fewer tools, better connected, with someone in charge of each.
- 1What quiet friction looks like
- 2What the research says
- 3How donors feel it
- 4What a tech stack should include
- 5The audit
- 6Do it once a year
- 7Questions people ask
What quiet friction looks like
When an executive director or chief executive tells me "our systems are messy," it usually means some mix of these:
- Donor details sit in the CRM, a spreadsheet and the email tool, and they don't agree. That's a data silo.
- Two tools do the same job because two people picked their favorite.
- The same details get copied and pasted from one spreadsheet into another every week.
- Receipts, reminders and thank-you emails go out by hand.
- Nobody owns the system. Everyone does a little bit, so nobody is responsible.
None of this is a lack of care. It's what happens when a small team grows its tools one urgent problem at a time.
What the research says about nonprofit data
Some of the most useful recent data comes from NTEN's 2025 Data Empowerment Report, a survey of 220 nonprofits. Almost 90% have staff who type data into their systems by hand. Staff time was the most common data challenge, named by more than 79%, and silos across departments ranked first by impact. Ownership is thin too, since 42% have nobody with "data" in their job title, 19% keep data on computers only one person can open, and more than half didn't answer who is responsible for data compliance.
Planning lags behind too, according to NTEN and Bridgespan's 2026 survey of 917 nonprofit staff and leaders in the US and around the world. Only three in ten leaders said they have a process to approve new AI tools and vendors, and only 8% reported having a one- to two-year AI roadmap.
So the problem usually isn't too few tools. It's tools run by one or two people, connected by retyping, and owned by nobody in particular.
Your donors feel it too
It's easy to think of systems as an internal headache, but supporters see the results.
Second gifts are where it shows. According to M+R's 2026 Benchmarks, a new online donor gives again only about 24% of the time, while a donor who has given before gives again about 66% of the time. That second gift often depends on a prompt, personal thank-you, and a thank-you that waits for someone to export a list tends to arrive late.
Receipts and records are another place where it shows. In the US, the IRS says a donor can't deduct a single gift of $250 or more without a written acknowledgment from your organization. In the UK, HMRC's Gift Aid guidance says charities need to keep their Gift Aid records, usually for six years. When receipts and records are typed by hand from a spreadsheet, mistakes are easy.
Then there's your email list. If someone unsubscribes in one tool and stays on the list in another, they'll notice, and it won't feel good.
Finally, there's the donation page, where M+R found that mobile brings 52% of donation-page traffic but only 28% of online revenue. If your form is hard to use on a phone, that friction costs you before anyone in the office sees it.
What should a nonprofit tech stack include?
The answer isn't another app. It's deciding where each kind of information lives, and connecting the rest so nobody retypes it. A simple way to think about it:
- People (donors, members, volunteers) live in one CRM or donor database. This is the system of record for supporters.
- Money lives in your accounting system, and gifts reconcile to it on a schedule, not at year end.
- Your front door is your website and forms, and they send information straight to the CRM, with email consent recorded.
- Email comes from one tool, with one opt-out list synced from the CRM.
- Files live in one shared drive the organization owns, never a personal account.
- Client or program records, if you have them, stay in their own system on purpose, for privacy.
That's one home for each kind of information, not one system for everything, and it's the heart of good nonprofit data management. If you're thinking about buying new donor management software, do this first. A new tool on top of messy data just moves the mess. Fewer tools are also safer because every extra tool is another set of accounts to manage and another login to remove when someone leaves.
How to do a nonprofit technology audit
Set aside time this week with the person who does the work and one colleague. You'll need a spreadsheet or a whiteboard.
- List every tool. Include spreadsheets, personal drives and free apps. For each one, write what personal information is in it and which company holds it.
- Name an owner. One person per tool, plus who has admin access, how many paid seats you have and when it renews. Flag any two tools doing the same job.
- Follow one gift and one sign-up. Trace a donation from the form to the thank-you and receipt, and a new contact from sign-up to the newsletter. Circle every place someone copies, pastes, exports or retypes.
- Run three donor checks. How many days from gift to thank-you, and to receipt? Does an unsubscribe in one tool reach all of them? Does any donor appear more than once?
- Decide what to fix first. Choose the home for each kind of information, pick the single worst manual handoff, and list any accounts to remove today.
Instead of starting with the biggest problem, start with the one that's annoying people every week and is easy to fix. Often that's sending form entries straight to your CRM, or making receipts go out on their own from the donor record, while the personal thank-you stays personal.
Do it once a year
Run the same audit every year, before any software renewal, and before you buy a new tool. It also gives you the list you need when someone leaves: every account they had, ready to remove. If you want a more detailed nonprofit technology assessment later, with security and a full plan, this audit is where it starts.
It isn't a passion problem
If things are falling through the cracks, it isn't because your team doesn't care. It's because the work depends on memory and willpower instead of a system. That works until someone is sick, on vacation or moves on, and then the organization finds out how much lived in one person's head.
A good system should feel like support, not stress. People know where to find things, there's less second-guessing, and fewer donors slip through the cracks.
To go deeper on one workflow, read how to map one workflow before you automate it. Our free Workflow Mapping Workbook helps you map, measure and fix it. If your files are part of the mess, start with the shared drive structure guide. And if you'd like help connecting the tools you already have, see Connected Systems or book a free assessment.
Questions people ask
What is a nonprofit technology audit?
It's a review of the tools your organization uses, the information in each one, who owns them and where work gets stuck. A simple audit covers the basics. A full technology assessment adds security, budget and a written plan.
How often should a nonprofit audit its technology?
Once a year is a good rhythm, plus before buying any new tool and whenever someone with admin access leaves.
What should a nonprofit tech stack include?
Most small and mid-sized nonprofits and charities need a CRM or donor database, an accounting system, a website with donation and sign-up forms, an email tool and one shared drive. Organizations that serve clients usually keep client records in a separate system for privacy.
What is a data silo in a nonprofit?
It's information that lives in one tool or one person's files and doesn't reach the others, like donors in a spreadsheet that never makes it to the email list. Silos mean people retype information and nobody sees the full picture.
Do we need a new CRM?
Often not, since many nonprofits get more from connecting and cleaning the CRM they already have. Run the audit first, then decide.
What should we automate first?
Start with steps that are the same every time, like sending form entries to your CRM and sending receipts from the donor record. Keep personal thank-yous and any decision about a person with a person.
Sources worth your time
- NTEN · 2025Data Empowerment Report →
How nonprofits collect, manage and use data, from a survey of 220 organizations.
- NTEN and Bridgespan · 2026State of Nonprofit AI Adoption and Governance →
How 917 nonprofit staff and leaders in the US and around the world use and govern AI.
- M+R · 2026Benchmarks: fundraising and websites →
Donor retention, monthly giving and donation-page results for online programs.
- IRSCompliance Guide for 501(c)(3) Public Charities →
Written acknowledgments for gifts of $250 or more, and which records to keep.
- HMRCChapter 3: Gift Aid →
How long UK charities need to keep their Gift Aid records.
Also used: The Bridgespan Group's press release on the 2026 survey.
Want help connecting the tools you already have?
We help nonprofits and charities decide where each kind of information lives, connect the tools they already use and automate the boring steps, with a person in charge of every decision about a person.
Book a free assessment →See Connected Systems
Starting on your own? Map one workflow with the free Workflow Mapping Workbook.
Your team isn't slow. Your information is just making too many stops.
Updated October 2026. This guide is general information, not legal or tax advice. Written with AI assistance. Reviewed by a person.
