When the tools you built to know your donors stop you from knowing them at all...
Most nonprofits have more data on their donors than they have ever had. Many of them are less connected to those donors than they were before the data arrived. That is not a coincidence.
Your CRM captures transactional data well. Who gave. How much. When. Through which channel. It does this automatically, because that is what it was built to do. The integrated part of the system takes care of it without anyone having to think about it.
Everything else requires someone to stop and manually enter it. Why a donor gives. What they care about. How they talked about your cause at a dinner party. What they are hoping your work will eventually make possible. None of that flows in automatically. Someone has to type it.
And let's be honest: we are all busy. Entering qualitative notes into a CRM is one of the first things to drop off the list. There is always something more urgent. So those things do not get recorded. And over time, they disappear entirely, because staff move on, spreadsheets get lost, and the person who remembered that particular donor's story has left the building.
Before long, you can end up with a donor database that is very good at telling you what people have done, but much less good at telling you why they did it. It is more quantitative than qualitative. More transactional than relational. And it feels complete, because the fields are full, even if what is in them only tells half the story.
This is how a system can start to shape thinking without anyone deciding it should. The fields available to you can start to become the questions you think to ask. The categories built into your database - regular giver, event attendee, lapsed donor, major gift prospect - become part of the way you see people. Not because you chose that framework, but because it was already there when you opened the software.
The problem isn't that your CRM captures this information. That's exactly what it is supposed to do. The problem comes when we start treating the information it captures as the complete picture of our donors.
The donor becomes a record. The relationship becomes a contact history. The question "who is this person?" gets quietly replaced by "what does their profile say?"
Here is where it compounds. Because the data was never captured or set up in a way to tell you what you actually need to know, it is never quite right. There are duplicates. Missing fields. Contacts that have not been updated in three years. Giving histories that do not reconcile with what finance has on file.
So the team spends time fixing it. Cleaning it. Debating the right way to tag something. Waiting until the migration is complete, the new system is bedded in, the data audit is finished - and then they will be ready to really know the donors.
Meanwhile, the donors are right there.
The data is not the relationship. It is supposed to point you toward one. When maintaining the data becomes the focus, something has gone quietly wrong.
Most organisations have built their communications around segments and journeys. A donor falls into a category, and the category determines what they receive. New donor sequence. Lapsed donor reactivation. Event attendee follow-up. Regular giver upgrade pathway. Each one a tidy, linear flow designed around a type of person rather than an actual person.
The problem is that donors do not stay neatly inside a single category. Someone might attend an event, become a regular giver, volunteer occasionally, and have a deep personal connection to the cause, all at the same time. But if the system sees them primarily as an event attendee, that is the journey they get. The rest of who they are sits in a notes field nobody opens, or exists only in the memory of someone who no longer works there.
And donors feel it. They get messages that don’t quite make sense, are asked for things they’ve already done, or receive generic communications that ignore the relationship they’ve built with the organisation. They feel confused. Underappreciated. Eventually, they go elsewhere.
These are not data problems. They are relationship problems that got dressed up as data problems.
This does not require a new system. It usually requires a clearer sense of what you actually need to know about your donors, and then designing your data practices around that, rather than inheriting them from the software defaults.
A practical place to start is to export your data and look at it with fresh eyes. Not for errors to fix, but for patterns you might be missing. Who has given consistently over many years? Who has given significantly across different channels or campaigns? A donor who has gifted $5,000 is a mid-level donor, regardless of whether that giving came through an event, a campaign, or a direct appeal. If your system has never surfaced them that way, it is worth asking why, and who else might be hiding in the wrong category.
From there, look honestly at your communications. If most of what goes out is channel-triggered or campaign-driven, consider what a more relational programme might look like. Celebrating milestones is a simple but meaningful shift: acknowledging how long someone has been with you, or the cumulative impact of their giving over time, says something very different to "thank you for your recent gift." One is transactional. The other is relational. Donors notice the difference, even if they never say so.
Good data should make relationships easier to build and sustain. It should free up time and mental space for the human work. When it does the opposite, when it consumes the time, narrows the thinking, and becomes an obstacle between you and the people who care about your cause, you are not using your data. It is using you.
Start with the question: what would we need to know about this person to have a genuinely useful conversation with them? Then ask whether your system captures any of it. That gap is where the work begins.
Want help working out what your donor data should actually be doing for you? Get in touch with Empower Fundraising at enquiries@empowerfundraising.co.nz