The donor sheet
Built by whoever was there first. Two people have edit access, one of them left, and the version in the shared drive is four months behind the one on a laptop.
For nonprofits and NGOs
What you are working with now
None of these are mistakes. They are what happens when a growing organisation solves each problem the day it appears.
Built by whoever was there first. Two people have edit access, one of them left, and the version in the shared drive is four months behind the one on a laptop.
A separate sheet, a group chat for cancellations, and a paper sign-in book at the site. Hours get totalled in the last week of the financial year.
Downloaded monthly, matched to names by hand, and reconciled against receipts. Failed mandates look identical to donors who stopped caring.
Board meeting on Thursday, so someone spends Tuesday and Wednesday turning three of the above into one narrative that will be rebuilt from scratch next quarter.
What changes
The person who gives on the twelfth and volunteers on Saturdays is one record, not two rows in two files. Whoever picks up the relationship next inherits the whole history.
You cannot personally steward four thousand supporters. You can call the six whose engagement fell this fortnight, if somebody tells you which six and why.
Shift matching, reminders and hours logging run against the same record as giving, so coordination stops depending on one person's availability on a Friday evening.
Board packs, donor updates and grant interims are drafted from the giving and programme data your team already enters. You edit and approve rather than reconcile and retype.
Getting started
No implementation consultant, no six-month project plan. This is a small-team product and the onboarding is built for a team that is also running programmes.
Week 1
Bring in your donor sheet and volunteer roster with column mapping. Duplicates and unmatched rows come back as a fixable list. Most teams finish this in an afternoon and spend a day reviewing merges.
Week 2
Import gateway or donation-platform history so gifts, fees and failed mandates attach to the right records. This is what makes the difference between a lapse and a bank failure visible.
Week 3
Scores appear across the file. Read them against people you know well, and adjust the signal weights where your organisation's rhythm differs from the default. This step matters more than any other.
Week 4
Work the ranked list rather than the whole file. Log what you tried. The record of what worked is what makes the next month's suggestions better than this month's.
Where HOPEAQUE is the wrong choice
If your entire supporter base is under a hundred people and you know every one of them personally, a well-kept spreadsheet is genuinely better than any CRM, including this one. HOPEAQUE starts earning its place at roughly the point where you can no longer hold the file in your head, which for most organisations is somewhere between three and eight hundred supporters.
Six names with a reason attached beats four thousand names with none.