The short versionAutomate the preparation, never the relationship. Summarising a donor's history before a call is help; sending the call is not.
The thing that is actually scarce
A small development team runs donors, volunteers, events, programmes, vendors and impact reporting, usually with fewer people than any one of those would justify on its own. So the case for automation lands easily — and the first things automated tend to be whatever looks most repetitive, which is frequently the points of contact the relationship is made of.
The distinction worth holding onto is between preparation and contact. Reading six years of a supporter's history before a conversation is preparation: it takes twenty minutes, and nobody will ever notice it was done by software. Having the conversation is contact, and everybody notices.
A supporter can tell the difference between being remembered and being retargeted.
Where the intelligence belongs
INSAIT's Non-Profit CRM is built on Salesforce, so the record stays the system of record. The assistive part sits deliberately on the preparation side of that line.
- Summarising a supporter's history before a call, so whoever makes it arrives informed.
- Identifying who is plausibly interested in a specific campaign, as a shortlist for a person to accept or reject.
- Surfacing lapsed engagement as something to look at, without a re-engagement sequence firing on its own.
- Joining volunteer, event and donation activity into one view, because they are usually the same person recorded in three places.
Why the authority stays put
Outreach strategy and execution stay with the nonprofit team in every one of those. Not because the software could not draft the email, but because the moment a supporter suspects the warmth was generated, the organisation has traded a durable asset for a quarter's worth of saved time.
This is one of the rare product decisions where the cautious option is also the commercially correct one.
Written about Non-Profit CRM
