Your CRM Has the Data — So Why Can’t Your Team Act on It?
The question that comes up most often when fundraising teams start evaluating their CRM is not whether the data is there. It usually is. The question is why, if the data is there, the team still struggles to use it to make decisions at scale.
The answer is almost never a missing feature. It is a structural problem: data that was entered over years, across multiple staff members, into a system that was configured incrementally, ends up scattered in ways that make it hard to surface at the right moment.
How CRMs Get Disorganized Over Time
No one sets out to build a disorganized CRM. What happens is that organizations grow, needs change, and the system gets configured to meet each new need without a full view of how everything fits together.
A new object gets added to track event attendance. A workflow gets built to log giving history. A custom property gets created to capture a relationship type that did not exist in the original setup. Each of these decisions makes sense in isolation. Over time, they add up to a system where the information that matters is technically present but practically difficult to access.
For a fundraising team, this plays out in a specific way. A development officer looking at a contact record can see basic demographics and recent activity. To get a full picture — giving history, event attendance, family relationships, communication notes — they have to click through multiple associated records, cross-reference lists, and rely on memory for anything that was not entered consistently.
That process works when you are managing a handful of relationships. It does not work when you are trying to prioritize outreach across thousands of contacts. Why your fundraising team is spending more time on admin than donor relationships covers what that time cost actually looks like for a development team.
The Gap Between Data and Decisions
There is a meaningful difference between having data and being able to act on it. A CRM that stores information is useful. A CRM that surfaces the right information at the right moment is what actually changes how a team operates.
Most fundraising CRMs, including HubSpot when used without additional configuration, sit closer to the first category than the second. They are good at storing. They are not designed to synthesize. A contact record tells you what is true about a person. It does not tell you whether that person is worth calling today, or how they compare to the other 500 contacts your team could be reaching out to this week.
That synthesis has always been left to the fundraiser. And for teams managing large databases, it is simply too much to ask of any individual, no matter how experienced. The institutional knowledge that makes a senior development officer effective at spotting high-potential donors does not scale across 100,000 records.
This is where the problem sits for most organizations. It is not that the system is broken. It is that the system was never designed to do the thing the team actually needs it to do. Your donor database is full of answers — here is how to find them walks through what a system designed for that purpose actually looks like.
What It Means to Make Data Actionable
Making CRM data actionable for a fundraising team means two things: getting the right information into a single view, and producing an output that supports a clear decision.
The first part is a data structure problem. Information that lives across multiple objects needs to be pulled together in a way that a scoring or synthesis process can access. In HubSpot, this is where Data Studio comes in — it allows you to aggregate contact data alongside related record data, creating a unified view that includes giving history, event attendance, family relationships, and any other signals that are relevant to your scoring criteria.
The second part is where the data agent comes in. Once that aggregated view exists, the data agent allows you to write a prompt — a structured set of instructions — that tells the system what to look for and what to output. For donor scoring, that output is typically a simple high, medium, low designation that gets written back to the contact record as a property.
The result is that every contact in the system carries a current score, updated automatically, that reflects everything the CRM knows about them. A fundraiser opening their list in the morning does not need to do research to figure out who to call. The system has already done it. What is HubSpot’s data agent and what can it actually do? explains the mechanics of how this works inside HubSpot.
The Data Quality Question
Before building a scoring system, it is worth being honest about the state of the data. A prompt that synthesizes information from related records is only as good as the information those records contain.
This does not mean the data needs to be perfect before you start. It means you need to know what you have. Which fields are consistently populated? Where are the gaps? Is giving history stored in a way that the data agent can access, or is it locked in a format that requires cleanup first?
For most organizations, there are a few areas where data quality is strong and a few where it is not. The practical approach is to build the initial scoring logic around the data that is reliable, then expand as data quality improves over time. Starting with complete data for 80% of contacts and scoring those is more useful than waiting until the entire database is clean. Is your HubSpot data clean enough to use AI on? covers how to assess readiness before you build.
What Happens After You Fix the Problem
The operational change that comes from a well-configured donor prioritization system is not just efficiency. It is a shift in what the team is capable of.
When fundraisers are not spending time on research, they spend it on relationships. When management has a real-time view of prospect scores across the database, they can direct staff time with confidence. When the system surfaces contacts that would have been overlooked in a manual review process, the pipeline grows without adding headcount.
For a university fundraising team that worked with Fast Slow Motion on this problem, the implementation started with a database of over 100,000 records and no reliable way to identify who to prioritize. The data agent built inside HubSpot changed that by pulling together contact history, giving patterns, and engagement signals into a single score for every contact in the system. The AI in Action episode on turning donor data into decisions covers how that was built and what it changed for the team.
If your CRM has the data but your team still cannot act on it efficiently, the system is not the problem. The configuration is. And that is a solvable problem.
Listen to the full podcast episode here.