What a custom agent looks like inside a small or mid-size nonprofit — the ten roles in your language, and what each plugs into in an organization running Bloomerang, Salesforce NPSP, Little Green Light or DonorPerfect.
last reviewed
A nonprofit runs two operations at once: the program it exists to deliver, and the fundraising and reporting that funds it. The second consumes people who were hired for the first. Grant reports, donor acknowledgments, volunteer coordination, board packets and outcome measurement all arrive on fixed calendars, all require assembling information from several places, and all compete directly with mission delivery for the same small staff.
The honest version of "does it integrate with my software." These are the systems this industry actually runs on, and what each one means for a build.
The systems of record for donors, gifts, campaigns and engagement in small and mid-size organizations, with accessible interfaces.
Where larger or more complex organizations track constituents, programs and grants, with extensive integration capability and correspondingly more configuration.
Applications, reporting deadlines and restricted fund tracking, frequently maintained in a spreadsheet against portals that each work differently.
Online giving pages, recurring gifts, peer-to-peer and event platforms, each depositing and reporting separately.
Scheduling, hours tracking and background checks for a workforce that turns over constantly and is not paid.
Whatever holds who was served and what happened, which funders increasingly require and which is often the least structured data in the organization.
QuickBooks or a fund accounting system, needing restricted and unrestricted funds tracked separately.
Mass email and newsletters, usually segmented far less than the donor data would allow.
Each of these is a real build, not a feature of a product you already pay for. Follow one through to see how it works in general.
Nothing you are owed gets dropped.
Whatever arrives, in whatever format, becomes a clean record.
Writes the recurring document from your own past work.
Knows what expires, renews or comes due — and says so first.
Answers from your own records, not from the internet.
The conversation becomes the record, without anyone typing it up.
Assembles the recurring report from systems that do not talk.
Matches two sets of records and queues only the exceptions.
Two systems that do not talk, now talking.
Applies your rules, escalates only what needs judgment.
If that is a job in your business, the next step is half an hour on a call. Bring whatever you know about the volume — how many a month, who owns it now, which systems it touches. That is enough to scope it properly and quote it flat before anything starts.
Everything in this library is built to order rather than bought off a shelf — and whatever I build, I host and maintain. The rest of the library is here.