It is 8:40 on a Tuesday morning. A lottery file containing 12,000 rows arrives, but somebody has changed the columns again.
By 10:15, an agency has resent yesterday’s file with a request to ignore the first version. After lunch, somebody finds two supporters with the same name, postcode and direct debit. Nobody can say with confidence whether they are the same person.
At 4:30, the thank-you campaign misses its slot because the data still is not ready.
By the end of the day, nobody in the fundraising team has spoken to a donor.
This may be a fictional Tuesday, but the underlying problems are very real. Fundraisers join charities to build relationships and generate income. Too often, they spend their time moving, checking and correcting data instead.
Key takeaway
Charities do not need to automate every fundraising process at once. The most effective approach starts by establishing ownership, setting one data standard, agreeing how duplicate supporters will be identified and automating the source that creates the most work.
Why does fundraising data become so difficult to manage?
Most charities never deliberately create a complicated fundraising data process. It develops gradually.
A new campaign adds a supplier. Another channel introduces its own file. An agency creates a spreadsheet based on the requirements it received at the time. Somebody writes an import process to handle that individual format.
Each decision may appear reasonable on its own. The difficulty becomes apparent when the charity has to manage all of them together.
A large charity might receive data from more than 50 sources, including:
- Door-to-door fundraising
- Telephone fundraising
- Digital campaigns
- DRTV
- Lotteries
- Events
- Legacy giving
- Website donation platforms
- Payment processors
- External fundraising agencies
Each source can have its own format, schedule and interpretation of apparently simple information such as a date, campaign code or supporter address.
When a column changes, an established process can break without immediately alerting anyone. The fundraising team then has to work out what happened, correct the file and protect the next campaign deadline.
Nobody planned to create this level of complexity. Everyone involved was simply trying to do their job.
What does manual fundraising data processing cost a charity?
The clearest cost is staff time, but the wider consequences are often more important.
During one Sweet Potato Tec project with a national charity, the existing process involved more than 170 uploads. Over 200 hours a week were being spent handling files, equivalent to five full-time roles before including additional time from fundraisers.
The charity was also dealing with:
- One in seven records being duplicated
- Around 15 data errors disrupting campaigns each month
- Agency onboarding taking approximately four weeks
- Supporters sometimes being thanked or approached more than once
Those problems affected far more than administration.
A delayed file could postpone a campaign. A duplicate record could create an awkward supporter experience. Slow agency onboarding could consume a significant part of a seasonal fundraising window.
The charity had employed fundraisers, but a substantial amount of their working week was disappearing into spreadsheets.
“We hired fundraisers. They spent their week in spreadsheets.”
Head of Fundraising Operations
What should a charity decide before automating fundraising data?
The project began with conversations rather than technology.
Sweet Potato Tec asked the fundraising team three questions.
Which decision can you not make today?
The team could not confidently determine whether a supporter should receive a second ask.
That answer shaped the supporter-matching rules. The purpose of better data was to help fundraisers make a better decision, rather than simply creating cleaner records.
What would you do with an extra day each week?
The fundraisers wanted to spend more time calling major donors.
That made hours returned to the team a central measure of success.
Which supporter would notice if the process improved?
The answer was the supporter thanked twice for one gift.
That experience became the first test case for the new process.
These questions kept the project focused on fundraising outcomes. Salesforce, FinDock and the data engine were important, but they supported the objective rather than defining it.
The four foundations of fundraising data automation
Before development began, the charity and Sweet Potato Tec agreed four principles.
1. Give fundraising data a named owner
Somebody must have the authority to set the standard and reject unnecessary exceptions.
In this project, that owner sat within fundraising. They understood the operational consequences of each new file format and could judge whether a requested change created enough value to justify the additional complexity.
A committee can contribute to a standard, but it cannot easily protect one. Clear ownership matters.
2. Set one standard for incoming data
Every channel and agency should deliver information according to an agreed master data standard.
The standard needs to define the structure and meaning of information about supporters, pledges, gifts, major giving and corporate opportunities.
It should form part of agency contracts and renewals. Treating the format as a contractual requirement gives it more weight than sending another spreadsheet template by email.
3. Agree how duplicate supporters will be handled
A single supporter may donate through several channels, use different email addresses or appear under slightly different versions of their name.
Fundraising and data teams therefore need to agree the matching rules together. These rules should reflect how the charity understands its supporters, rather than relying on technical assumptions.
The organisation should review the rules periodically as its fundraising activities and data change.
4. Automate the repeatable work
Automation should begin with a high value source that causes the most disruption.
There is little benefit in automating a straightforward low value monthly file while staff continue spending several days repairing another source every week.
Start where automation can return meaningful time to the team or prevent a recurring supporter problem. Once that process works reliably, the charity can expand the approach.
What did the automated fundraising data process look like?
Sweet Potato Tec designed one data engine to replace more than 170 separate upload links and processes.
Fundraising channels and agencies delivered their information through one controlled route. The engine then completed four tasks:
- Collect the file, regardless of its original format or schedule.
- Validate the information and reject errors before they entered the charity’s core systems.
- Match the data to a single supporter using the agreed rules.
- Load and record the information, maintaining a traceable history of what happened.
The validated data passed into Salesforce, giving the charity a more complete view of each supporter.
FinDock handled the payment and reconciliation information so that fundraising and finance could work from consistent records.
Consent information travelled with each gift. If a channel did not provide the required consent data, the file did not load. The charity did not try to reconstruct permission later.
Agencies delivered data to the agreed standard without receiving direct access to Salesforce. This protected the CRM and created a clearer audit trail.
Why is governance harder than the technology?
The technical work only solves part of the problem.
Agreeing one data standard took longer than building the engine. Protecting that standard became an ongoing responsibility.
Every exception creates more work. If one agency receives permission to use a different format, that exception may remain in place for years. It requires its own logic, testing, monitoring and support.
During this project, the charity rejected a requested exception from a large agency. That decision protected the standard for every supplier that followed.
Poor-quality files also returned to the sender rather than joining an internal correction queue. This placed responsibility with the organisation producing the information and stopped the charity’s fundraising team becoming a permanent data clean-up service.
This does not mean every integration automatically deserves investment. Charities should consider the income or strategic importance of each agency against the long-term cost of building and maintaining the connection.
A small business case for each major integration can prevent unnecessary complexity later.
What changed after six months?
According to the project measures presented by Sweet Potato Tec, the new process produced a significant operational change:
- Weekly file-handling time fell from more than 200 hours to under 40
- The charity returned approximately 160 hours a week to its teams
- Data errors disrupting campaigns fell from around 15 per month to zero
- New agency onboarding fell from four weeks to one day
- The engine handled 15.73 million gifts a year without a person manually processing each file
The change that mattered most was simpler: the duplicate thank-you that helped start the project would no longer happen.
These results show why fundraising data automation should not be treated purely as an IT efficiency exercise. The real value comes from giving people time to speak to supporters, helping campaigns run when planned and creating a more consistent experience for donors.
Does this approach work for smaller charities?
The technology and level of automation will vary, but the same four principles apply.
For one person managing the process
Write down who owns the data process, even if that person is you.
Create one spreadsheet template with a consistent column order. Use simple matching rules, such as email address or postcode combined with surname, and begin with the source that creates the most problems.
For a small fundraising team
Name one person as the owner rather than assigning responsibility to the whole team.
Ask every channel to use the same template. Establish the matching rules within the CRM and automate the two sources that break most often.
For a national charity
Place a data steward inside fundraising.
Include the master data standard in supplier contracts. Use automated matching but review its performance regularly. Bring every fundraising source through one controlled data engine.
The size of the solution should reflect the organisation, but ownership and consistency matter at every scale.
Three fundraising data improvements you can make tomorrow
You do not need an approved technology budget to start improving the process.
Count the hours
Ask everyone involved how long they spent moving, checking or correcting fundraising data last week.
Include the fundraising time lost while people waited for files or investigated problems. The full number may be considerably higher than expected.
Name the owner
Choose one person who can maintain the standard and challenge the next requested exception.
Give them enough authority to protect the process.
Fix one file
Identify the data source that breaks most often or consumes the most staff time.
Improve or automate that source before tackling anything else.
What should you agree before investing in a larger data project?
Before commissioning technology, clarify three areas.
Understand the value of each integration
Assess the income and strategic value associated with each agency or channel.
Compare that value with the cost of building, monitoring and maintaining the integration. Not every connection requires the same level of investment.
Finalise the data standard
Bring together the people who understand fundraising operations, supporter data and Salesforce.
Agree how the charity will represent supporters, pledges, gifts, major giving and corporate opportunities before developers begin building integrations.
Create an internal agreement
Establish how the organisation will assess requests to expand or change the standard.
Agree that agencies will adopt the standard at the start of a relationship or when their contract comes up for renewal.
Without this internal discipline, technical automation can simply make an inconsistent process run faster.
Fundraising data should help people build relationships
Good fundraising data allows a charity to understand its supporters and communicate with them appropriately.
When people spend most of their week correcting files, that value remains locked inside the process.
The first step does not have to be a major technology project. Count the time, establish ownership and fix the most disruptive source. Those actions alone can start a useful internal conversation about what fundraising data should do for your charity.
If fragmented fundraising data is taking your team away from supporters, Sweet Potato Tec can help you understand the problem, define a workable standard and identify where automation will deliver the greatest value.
Talk to Sweet Potato Tec about your fundraising data
Frequently asked questions
What is fundraising data automation?
Fundraising data automation uses defined rules and integrations to collect, validate, match and load donation information into systems such as Salesforce. It reduces the amount of manual file handling required from fundraising and data teams.
Where should a charity begin with fundraising automation?
Start by measuring the time spent handling data and identifying the source that creates the most work. Name an owner, define the required file format and automate one problematic process before expanding further.
How can charities reduce duplicate supporter records?
Fundraising and data teams should agree clear matching rules based on the information they collect. These rules can then be applied within the CRM or a dedicated data process and reviewed regularly.
Should fundraising agencies have direct access to Salesforce?
Direct access is not always necessary. Agencies can submit data through a controlled route that validates the information before loading it into Salesforce. This supports least-privilege access and creates a clearer audit trail.
What is the role of FinDock in fundraising data automation?
FinDock can help manage payment data and reconciliation within Salesforce. This allows fundraising and finance teams to work from connected payment and supporter records.
Can a small charity automate fundraising data?
Yes. A smaller charity can begin with one standard spreadsheet, simple matching rules and automation for its most time-consuming source. The process does not need to begin with a large transformation programme.