code, coding, computer, data, developing, development, ethernet, html, programmer, programming, screen, software, technology, work, code, code, coding, coding, coding, coding, coding, computer, computer, computer, computer, data, programming, programming, programming, software, software, technology, technology, technology, technology. Testing donor retention tools: a step-by-step buyer trial
Photo by Pexels on Pixabay

Rules

Part of Donor retention: the parts worth your attention

Testing donor retention tools: a step-by-step buyer trial

How to compare donor retention tools in a trial: donor file import, renewal-by-cohort reporting, failed payment handling and the labor each adds.

What to take away

  • Shortlist at least three donor retention tools, then give every candidate the same donor file, the same renewal report and the same export request before you compare prices.
  • Price the labor to reach an accepted result, not the subscription. Setup, correction and exit work usually outlast the license.
  • Test one normal gift path and one failed payment path, then write down what broke.
  • Keep the tested edition, plan and date in the decision file, because vendors change tiers quietly.
  • Treat privacy and security guidance as management aids, not as clearance for your fundraising use.

Start with the donor file, not the demo

A retention tool is only as good as the record it inherits. Ask each vendor to import the same anonymized slice of your donor file, including duplicate records, deceased donors and gifts with missing appeal codes.

Then ask for the report your board actually reads: renewal rate by cohort, with reason codes for attrition. A platform that cannot produce it from your own data will not produce it after you sign.

Candidates do not all come from the same shelf. Spreadsheets and in-house databases are the baseline; dedicated nonprofit CRMs such as Bloomerang, DonorPerfect, Little Green Light, Neon CRM and Blackbaud sit in the middle; enterprise fundraising platforms sit above them. Put one tool from each category you would honestly run into the trial, and write the shortlist down before the first demo.

Run the same trial for every candidate

Give each candidate one task, one dataset, one role and one failure case. Record what the person doing the work had to fix by hand.

Run the same tests on every candidate, in the same order, and keep the raw output. Import the same anonymized donor file and count the duplicates, deceased records and missing appeal codes you had to fix by hand. Build a renewal-by-cohort report and check that it states the cohort definition, the measurement window, the renewal rate, the retained-donor count and the reason codes for attrition. Send one test gift down the normal path and one down a failed-payment and recovery path. Export the full donor record to CSV and confirm that gifts, designations, contact history and consent flags survive the trip. Then ask for the current price sheet, the setup or migration fee and the minimum term in writing.

Review fieldWhat to recordAcceptance test
Core taskRenewal reporting by cohortCompleted by the intended staff role
DataImport, field definitions, export, deletionPortable and readable outside the tool
ControlAccess, logging, correction, recoveryObserved response to a failed payment
CostSetup, recurring labor, support, change, exitYour own total-cost estimate

The CISA software acquisition fact sheet covers supply-chain exposure and vulnerability management for bought software. Add those checks to the purchase record. They inform the decision; they do not approve the vendor.

The GAO evaluation design guide links evaluation questions to evidence needs and design choices. Use that discipline on your own trial. Its federal-program context does not transfer to a charity's donor file, so avoid causal claims your sample cannot carry.

Where the operating boundary sits

Keep donor intent, consent records, fundraising cost and stewardship visible through the review. Your working file should name the approved scope, the exclusions, the version, the owner and the decision date.

The GOV.UK technology selection guidance argues for adaptable choices, data control and attention to ownership cost. Those questions fit a trial. They do not endorse a provider.

The NIST Privacy Framework starting guide describes a voluntary process for identifying privacy risk and assigning owners. It is a management aid. For a US charity the binding requirements sit in IRS substantiation and disclosure rules for charitable contributions, state charitable solicitation registration where you ask for gifts, and the FTC's guidance on protecting donor data. If you also have Canadian donors, the CRA, PIPEDA, BC PIPA and Quebec Law 25 bear on receipting and storage, and consent rules for donor email govern what you may mail. Confirm the specifics with a qualified nonprofit lawyer.

Do the arithmetic on your own numbers

FieldTestRecorded result
CaseOne cohort of lapsed donors, one renewal appealPopulation, date, reviewer
MethodSame task, data, role, failure case and export for each candidate; price the labor to reach an accepted resultInputs, observations, unresolved limits
OutcomeRenewal rate and reason-coded attrition against cost and qualityEffect on the cohort, with the arithmetic shown
EscalationStop if the tool pushes message volume instead of better stewardshipCorrection owner, next review date

Work the arithmetic in your own variables: cohort size times renewal rate gives retained donors; subtract platform cost, staff hours and correction time to get cost per retained donor. Compare that figure to your current one. If you do not have a current figure, your donor retention baseline is the first thing to build.

Common questions

These are the questions that come up in almost every trial, whatever tool is on the shortlist.

What is the first decision?

Name the owner, the cohort, the outcome you want and the evidence that would stop the purchase. Without a baseline renewal rate, no demo can tell you whether a tool helped.

How should the review be run?

Score cohort renewal and reason-coded attrition alongside cost, quality, exclusions and observed failures. Date every record, because a vendor's tier and terms move.

What should a team avoid?

Avoid buying message volume in place of stewardship. If a trial shows the tool mainly increases send frequency, preserve the finding and correct the plan before renewal.

More in Rules

Latest from Review Desk