Lori Gatmaitan
Senior Consultant
A “Quick Data Ask” Late One Thursday
It’s 4:47pm Thursday afternoon when an email lands in your inbox. Subject line: “Quick ask for tomorrow.” Little does the sender know, the ask is anything but quick.
The VP of Development wants to know how many donors who gave in FY24 lapsed the following year, broken out by giving society, cross-referenced against the upcoming gala attendance list. The board committee meeting is at 9am Friday. Could you have it ready by 8am?
In this scenario, you have been in advancement services for almost a decade. You know this dance. You open the CRM, start building the query, and hit the first snag: giving society thresholds changed 18 months ago, and nobody backfilled the historical records. So “Cornerstone Society” means one thing for gifts before March 2025 and another thing after, and the system has no idea there’s a difference.
You work around it. Then you need event attendance. Event attendance isn’t tracked in the CRM. It’s in a spreadsheet an events coordinator maintains by hand, matched to constituent records by name, which means “Bob Sinclair” and “Robert Sinclair, Jr.” are, as far as the data is concerned, two different people who may or may not be the same donor.
By 7:45am, you have a number. You’re about 85% confident in it. You send it anyway, with three caveats in the email and a note to yourself to fix this properly when things calm down.
If this sounds familiar, you’re not alone. And more importantly, it’s not a you problem.
Why “Can You Pull That Number?” Is Really a Donor Database Question
Every advancement services team has some version of this story. A senior leader needs a number, needs it fast, and needs it to be right. The team pulls it off (because advancement services teams are good at pulling things off), but the process behind that number is held together with institutional knowledge, workarounds, and a fair amount of grit.
Here’s the thing: the ask itself was completely reasonable. Lapsed-donor analysis by giving society and event engagement is exactly the kind of question a board committee should be asking, and exactly the kind of question a modern advancement operation should be able to answer in minutes, not hours. The friction wasn’t in the question. It was in the system underneath it.
That’s the real story “can you pull that number?” tells. Not about whether your team is capable—they clearly are, or you wouldn’t have had a number ready by 8am. It’s about whether your database was built to answer questions, or just to record transactions.
What a Reporting-Ready Nonprofit CRM Actually Looks Like
A CRM that’s set up for ad hoc reporting has a few things in common, and none of them are exotic:
Giving societies and donor segments are tracked with effective dates, so “when did this designation apply” is a query, not a guessing game. Constituent records are deduplicated and merged on a rhythm, not just when someone notices Bob and Robert are the same person. Event attendance, volunteer activity, and other engagement data live inside the system of record (or are integrated into it) instead of orbiting it in spreadsheets that only one person knows how to update. And field usage is documented and enforced, so the same concept is coded the same way whether the gift entry happened in 2019 or 2026.
None of this is glamorous. It’s the unglamorous infrastructure work that makes the glamorous questions (the ones that inform strategy) answerable on demand.
What Bad Donor Data Actually Costs Your Advancement Team
When the database isn’t set up this way, the cost shows up in places that are easy to miss. It shows up as advancement services staff spending Thursday nights and early Friday mornings on reports instead of on the higher-value analysis they were hired to do. It shows up as leadership quietly losing confidence in the numbers, because every figure arrives with an asterisk. And it shows up as a kind of institutional caution—teams stop asking ambitious questions of their data because they already know the answer will take a week and come with caveats.
That caution is the real loss. The most valuable questions an advancement shop can ask—who’s ready for a next-ask conversation, which donors are showing early signs of lapsing, where the major gift pipeline is thinning—are exactly the questions that get asked less often when every data pull is a project.
How to Start Fixing Donor Data and CRM Issues
Knowing what a reporting-ready CRM looks like is one thing. Getting there is another. If any part of that Thursday-night scramble sounded familiar, here’s where to start:
Review your data before you review your software.
Before you assume the CRM is the problem, get honest about what’s living inside it. Pull a sample of records and look for the patterns above: giving societies coded inconsistently across years, duplicate constituents nobody’s merged, engagement data that lives in someone’s personal spreadsheet instead of the system of record. Most organizations are surprised by how much of the friction is data hygiene, not platform limitation. And once you recognize that, you can put a data cleanup plan in place.
Find a CRM that works with you, not against you.
Sometimes the diagnosis is a platform, not a records problem. If your system can’t track effective dates, can’t enforce field-level standards, or simply wasn’t built for the kind of reporting your leadership expects, no amount of cleanup will fully solve it. The question isn’t whether your CRM is the “best” one on the market—it’s whether it’s the right fit for how your team works and the questions your board and leadership ask.
Bring in a partner who’s done this before.
Data audits and CRM evaluations are the kind of project every advancement services team knows they need and rarely have the bandwidth to run themselves—not because they lack the skill, but because they’re too busy answering Thursday’s version of this email. An outside partner can assess what’s fixable, what’s not, and what order to tackle it in, so the work gets done without pulling your team off the reporting that still has to happen in the meantime.
None of this happens in a day. But each one is a concrete, findable next step to solve the problem.
A Different Thursday
Imagine your Thursday if the groundwork had already been laid. The VP’s email arrives at 4:47pm. You open a saved report template, adjust the filters, and have a clean, confident number back within the hour and caveat-free, because the system tracks history the way the organization works. You spend the rest of your evening (and the next morning) the way you’d planned to.
That version isn’t a fantasy. It’s what happens when a database is treated as a strategic asset instead of a filing cabinet, and when the people asking questions and the system holding the answers are built for each other.
The next time someone asks “can you pull that number?”, the real question worth asking back isn’t whether your team can do it. It’s whether your database is making that harder than it needs to be. Most of the time, the honest answer is yes and that’s genuinely good news, because unlike staffing or budget, it’s a fixable problem, and a well-understood one.
Curious what your own database would say if you asked it that question? We help advancement teams find and fix what’s in the way. Let’s talk.