AI for non-profits
AI workflows for non-profits
A small non-profit team spends a lot of its week keeping funders, partners and supporters up to date. We set up tested workflows around that work, give your team practical lessons to use them and keep people in charge of what goes out.
The repetitive work a non-profit carries
Tasks like these come back every week. They are good candidates for a tested workflow with a person checking the result.
Funder and donor records
Keeping notes on every funder and donor conversation, and the next follow-up on each, up to date in one place.
Partner and collaborator lists
Building and keeping current the lists of partners, collaborators and contacts the team works with.
Newsletters and impact stories
Turning the stories that come in from the work into a regular newsletter for supporters.
Approvals and expenses
Keeping the approvals and expenses sheet current, so reporting to funders and the board is not a scramble.
What we set up
A workspace for your business
Your context, your trusted sources and instructions for repeatable tasks, organised in one place your team can edit.
Starter workflows
Two agreed workflows to begin with, such as funder notes and follow-ups in your contact system, and a partner list kept current.
Self-guided lessons
Practical lessons inside the workspace, so your team can practise on real tasks, check the output and learn when to ask for help.
Human approval
Each workflow has a named person who checks the result before anything is sent or acted on.
Where we’ve done this
Client example · Non-profit foundation
Funder records and follow-ups, with the team in charge
A non-profit foundation that raises money for an impact fund asked for help with the work around its funders and partners. We are setting up a workspace that writes notes on investor and funder conversations into the foundation’s contact system, sets each follow-up as a dated task and keeps the investor and collaborator lists filled in.
Nothing goes to a funder without a person reading it first. The newsletter, the expenses sheet and a shared description of the foundation’s work are on the list for later workflows.
This describes work being set up now, not finished work or measured results.
How it works
A defined scope makes the result easier to assess and the handover easier to run.
- Map. Choose the workflow, authoritative inputs, responsible people and desired outcome.
- Define. Agree systems, access, approval points, exclusions and acceptance criteria.
- Build & check. Tailor the workspace and test normal work, missing information and the agreed failure cases.
- Hand over & adopt. Give a brief orientation, leave practical lessons and record acceptance. Adoption support stays within the agreed scope.
Setup options
Choose one option. Fees are confirmed after your discovery call, and your proposal confirms one total for the agreed package.
Foundation
Your first repository, set up and connected, with two agreed workflows operated by your team, practical lessons and a tested handover.
Connected
Four agreed workflows in total, connected to the supported systems, with input and output checks and approval steps.
Operations
Six agreed workflows in total, with scheduling, queues and human approvals where feasible. Feasibility is assessed first.
Questions
Will the workflows email funders or donors by themselves?
We are a small team. Is this worth it for us?
Is there a rate for non-profits?
How is donor and funder information handled?
Start with the work.
Email Don with a repeatable task that slows your team down. We’ll discuss a useful first workflow and a scope you can assess before you commit.