Blog / Builds & people / FIG. 98
Jev for Nonprofits: Triage on a Zero Budget
AI for nonprofits on a tight budget: donor email triage and volunteer routing for cents, as reported, with humans on every gift decision.
Nonprofits have the same inbox problem as a startup and none of the budget. A shared info@ address collecting donor questions, volunteer sign-ups, grant notices, press requests, and the occasional scam, read by whoever has an hour on Friday. Most AI for nonprofits pitches are enterprise software with a discount code. This one is about something cheaper: using a decision model to sort what comes in so the few staff hours go where they matter.
Jev, TypeSafe AI's decision model, answers closed questions (which category, urgent or not, needs a human or not) and doesn't write anything. For a team that mostly needs to know what to read first, that's the right shape and, per builder receipts, close to the right price.
AI for nonprofits: the cost is the headline
Budget is the first objection, so start there. One builder classified 500 emails in a few seconds for 3.5 cents (build, as reported). Another sorted about 1,500 emails by what each one needed in a single run (build, as reported). Across the cost table, per-verdict costs land at fractions of a cent.
Napkin math for a small organization: 100 inbound emails a day, three questions each, is 300 verdicts a day. At the rates builders report, a year of that costs less than a single printed mailing. Access terms and any free tier are TypeSafe's to set; check whether Jev is free and the official docs for today's answer.
The real cost is setup time. Someone has to write the questions and wire the inbox, and on a volunteer-run team that's the scarce resource. Budget an afternoon, not a quarter.
Donor email triage
Donor mail is the highest-value stream and the easiest to neglect. A triage battery sorts it into lanes:
- Gift question (receipt, tax letter, recurring gift change)
- Complaint or concern that needs a staff reply today
- Offer to give more, volunteer, or connect (the one you never want to miss)
- Event or RSVP logistics
- Unsubscribe or contact-preference request
- Vendor pitch or scam
The architecture is ordinary email classification: rules first for the obvious, verdicts for the rest, a human for anything unclear.
The rules for donor mail are stricter than for a support inbox. Anything touching money (refunds, gift changes, pledges) goes to a person, labeled, never processed automatically. Contact-preference changes run through your CRM's own unsubscribe mechanism, not a model's guess. Nothing gets deleted on a lone verdict. The model's job is to make sure the right person sees the message on Monday, not to act on it.
Volunteer routing
Volunteer inquiries are a matching problem wearing a triage costume. Is this person asking about a one-off event or ongoing work? Do they mention a skill you need (translation, accounting, driving)? Are they asking about something that requires a background check before anyone replies? Each answer routes the message to the coordinator who handles that lane.
Keep the final call human. A verdict can say "mentions working with children" and route to the coordinator who handles screening; it never approves or rejects a volunteer.
Donor data deserves the careful version
Donor records are personal data, and your supporters trusted you with them, not your vendors. Before any of this:
- Send the minimum. The email body and subject are usually enough; donation history, addresses, and payment details never need to leave your CRM for a triage question. The PII guide covers the patterns.
- Read the vendor terms at docs.typesafe.ai on retention and data use, and tell your board what you're doing.
- Log verdicts so when a donor asks why their email took a week, you can see what happened.
Data-protection rules for charities vary by country and by who you serve. This is not legal advice, and it's worth an hour with whoever handles compliance for you.
Frequently asked questions
How can a small nonprofit use AI without a budget?
Start with inbox triage on a decision model, where builder-reported costs run to cents per hundreds of emails. The main investment is an afternoon of setup, not a subscription.
What is donor email triage?
Sorting incoming donor mail into lanes (gift questions, complaints, offers to help, unsubscribes) so staff read the urgent and valuable messages first. The model sorts; people reply and handle anything involving money.
Can AI decide which volunteers to accept?
No. It can route an inquiry to the right coordinator and flag when screening is needed; accepting or rejecting a volunteer stays a human decision.
Is it safe to send donor emails to an AI service?
Send only what the question needs, keep financial and address data in your CRM, and check the vendor's retention terms. Local data-protection rules apply; get proper advice.
Where should we start?
Take last month's info@ inbox, write five triage questions, and compare the labels to what your team would have done. The getting-started guide walks through it.
Numbers throughout are as reported by the build authors, not verified by shipwithjev. Code-shaped examples are pseudocode; the official docs live at docs.typesafe.ai.