If you run a small nonprofit, with a tiny staff, an active board, a volunteer corps, and a donor base you know by name, this is the toolkit. Eight AI co-founders handle development, grant writing, program delivery, volunteer leverage, communications, finance, legal, and the connective tissue that holds the org together, so Annie can stay close to the mission and the people.
Charity OS is for Annie. She is the executive director of a small community-serving nonprofit. Four staff. A $1.4M annual budget. 150 active volunteers. A nine-member board. A donor base she knows by name. Think community food bank, youth education nonprofit, free clinic, land trust, arts organization, animal rescue. Anywhere a tiny staff is asked to carry an enormous mission.
Eight AI co-founders handle the work that lives around the mission. Development and major donors. Grant writing. Program delivery and impact. Volunteers. Communications and storytelling. Finance and operations. Board and compliance. So Annie can stay close to the beneficiaries, the volunteers, and the donors who make the work possible.
This page shows what a finished Charity OS looks like. To build your own, follow the AI Agents 101 guide. It walks you through the setup in a weekend. No coding required. No engineering background assumed.
Development, grant writing, program delivery, volunteer coordination, board governance, communications, finance, compliance. A small charity needs every one of these done well, every week. One executive director cannot do all of it and still be present for the mission, the people, and the moments that actually matter.
So small-shop EDs make the same trade every week. Either Annie does the operating work (and the mission slips), or Annie stays close to the mission (and the operating work slips). Both options cost the org.
Charity OS gives Annie operating leverage equivalent to a twelve-person staff while she stays at four humans. The mission is the product. Beneficiary outcomes are the P&L. The donor is the customer. AI specialists handle the operating work around all three.
Donors are the customers. Volunteers are the leverage. Beneficiaries are the point.
Operating leverage: the org scales the mission without Annie becoming the bottleneck
No coding. No technical background. Annie gives a plain-English instruction. Alfred routes it. The right specialist does the work. Annie reviews. Here's how a typical week moves through the system.
Annie installs the eight agents using the AI Agents 101 guide. A weekend of work. She loads in the mission, the theory of change, the donor list, the grant calendar, the volunteer roster, the board cadence. Each agent gets the org context they need.
Each agent works with full org context: the mission, the theory of change, the donor base, the grant calendar, the volunteer roster, the board cadence. Helen does not start from scratch on a thank-you note; she knows the donor. David does not invent a grant narrative; he knows the program outcomes.
Everything routes back through Alfred. Annie approves, adjusts, or redirects. The voice gets sharper, the work gets faster, the org's institutional knowledge accumulates in writing for the first time.
The system gets better with use. Agents learn Annie's voice and the org's specific cadence. The next year-end campaign is faster than the last. The next grant report writes itself. The next board meeting takes 90 minutes of Annie's time, not eight hours.
Think of it less like software and more like an eight-person staff. Annie is the ED. The team handles everything that does not require Annie's judgment.
Eight co-founders with names and clear scopes. Alfred sits at the center and routes every request. Each specialist works with full org context: the mission, the theory of change, the donor base, the grant calendar, the volunteer roster, Annie's voice. Click any skill to see what it actually does.
The hub. Routes everything. Sees the full week: grant deadlines, board meeting, donor calls, program reviews, volunteer training, payroll. Holds the line between what Annie actually has to touch and what the team can absorb. Without Alfred, Annie ends up in her inbox at 11pm on a Sunday triaging instead of leading.
Every morning Alfred sends Annie the one-page "what needs you today, what doesn't." Three buckets: auto-handled, drafted for review, stop-and-ask. Annie reads it with coffee. The day starts in control.
Calm, organized, never alarmist. The opposite of frantic. Drawing room, not Wall Street.
"Alfred, what's on my plate this week that actually needs me versus what the team can run?"
Finance and operations in one. Equal-standing co-founder. The Jekyll to Annie's Hyde: equal but opposite, by design. Tracks the operating budget, updates the cash forecast, maintains restricted vs unrestricted tracking, assists audit prep, prepares the 990, assembles finance committee materials. The deliberate counterweight when mission pulls Annie toward a new program the org cannot yet fund.
Annie runs every meaningful financial decision past Margaret before acting. New program, new hire, new lease, new grant accepted, Margaret models it first. Her job is to slow Annie down just enough to think clearly.
Direct, warm, honest. She has the unpopular numbers and she shares them anyway.
"Margaret, the board wants me to launch a second site in [neighborhood]. Walk me through what it does to the budget, the cash, and our restricted-fund exposure."
Individual giving pipeline, donor research, gift acknowledgement within 48 hours, annual appeal, year-end campaign, capital campaign support. Donors are the customers. Helen treats donor stewardship as a real practice, not a thank-you note afterthought.
Helen runs the donor CRM, drafts every thank-you within 48 hours of a gift, prepares cultivation briefs before each major donor meeting, and reminds Annie when a top donor has gone quiet for 90 days.
Warm, gracious, specific. Never canned, never grateful-grateful.
"Helen, brief me on [donor] before my coffee with her on Thursday. Last gift, recent life events, what we last talked about, three options for the ask."
Grant prospecting, application writing, foundation relationship mapping, grant reporting compliance. Grant writing at a small charity can be 30 hours a week; David takes the first 25. Annie still adds the soul.
David maintains the grant calendar, scouts new prospects monthly against the mission, drafts LOIs and full proposals to 80 percent, and tracks every reporting deadline so nothing slips.
Specific, evidence-led, foundation-program-officer voice. Never generic nonprofit-ese.
"David, scout three foundations we haven't approached that fund [program area] under $100K. Give me a 90-day cultivation plan."
Program design, delivery oversight, beneficiary outcomes, theory of change, impact measurement, M&E. The actual mission work. Sarah holds the program team and the outcomes data; she answers to the theory of change, not the activity count.
Sarah maintains the program logic model, runs quarterly outcomes reviews with the program team, writes the impact section of every grant report, and brings beneficiary voice into board meetings so the board hears the work, not just the numbers.
Rigorous, humble, beneficiary-centered. Never paternalistic.
"Sarah, the board wants outcomes data for the Q3 meeting. Pull the cohort numbers, three beneficiary stories with consent, and the one finding that surprised us."
Volunteer recruitment, training, scheduling, retention, community partnership coordination. Operating charities run on volunteer leverage. Olivia treats the volunteer corps as a real workforce, not a nice-to-have.
Olivia maintains the volunteer database, runs the monthly onboarding cohort, schedules shifts, tracks retention, and runs a quarterly volunteer appreciation. When a community partner reaches out, Olivia is the first point of contact.
Welcoming, organized, human. The volunteer's first impression of the org.
"Olivia, retention check. Which volunteers have shown up zero times in the last 60 days, and what's our re-engagement play for each?"
Newsletter, social, beneficiary stories with consent, annual report narrative, annual appeal copy, donor stewardship comms. Mission-led marketing voice. Gratitude-led, not pipeline-led.
Catherine drafts the monthly newsletter, ships two social posts a week, writes the annual report and annual appeal copy, and pairs every beneficiary story with the signed consent. She voice-matches Annie's natural cadence.
Warm, specific, never grateful-grateful or development-ese. Beneficiary dignity is the floor.
"Catherine, draft the year-end appeal. Lead with the [program] story Sarah cleared. 350 words. My voice."
Board books, minutes, committee prep, 501c3 compliance, state filings, gift acceptance policy, conflict of interest, succession. Heavier in nonprofit than in any for-profit role. James does the board prep that would take Annie 8 hours a week without him.
James drafts the full board packet 14 days before each meeting, takes minutes during, files them after, runs the compliance calendar so nothing lapses, and flags any gift that triggers the acceptance policy.
Precise, formal-warm, board-fiduciary register.
"James, draft the board packet for the November meeting. Lead with the FY26 budget Margaret approved, Sarah's Q3 outcomes, my ED report, and the three governance items."
Hub and spoke. Alfred at the center, routing every request and orchestrating multi-agent work. Each specialist covers a clear domain and brings full org context. One team, no silos.
Four moments from a real season at a small charity. Each one shows how a question moves through the team.
It's October. Annie needs a year-end appeal that lands. Catherine drafts the copy. Sarah pulls the beneficiary story with consent. Helen segments the donor list and stages the asks. David checks if any year-end-deadline grants are in play. Alfred sequences the seven-week run. Annie adds the soul and approves.
Top donor hasn't responded to the last three touches. Helen surfaces the silence at 90 days. Catherine pulls the last three personal notes for context. Sarah identifies which program update would resonate. Annie reaches out by phone with a specific update, not an ask.
A program officer at [foundation] emails Annie about a new RFP, $250K over two years, due in three weeks. David pulls the foundation profile and prior grantee patterns. Sarah pulls the outcomes data that would map. Margaret checks fit with current restricted-fund mix. Catherine drafts the narrative. James handles the compliance attachments.
Board meets next Thursday. James drafts the full packet 14 days out: financials from Margaret, outcomes from Sarah, development update from Helen, the ED report from Annie. Annie does one pass and approves. James files minutes after. Total of Annie's time: 90 minutes.
Charity OS is a working artifact in the Consumer Safari Papers series. The publication is for the people who build things and run them. Charity OS lives at the intersection where the mission meets the donor, the volunteer, and the beneficiary, and the ED meets operating leverage.
The first generation of nonprofit leaders hired managers, fundraisers, and program staff to do the operating work. Most small charities never get that headcount. The next generation will run leaner orgs by routing the operating work to AI specialists who carry full org context. The EDs who thrive will be the ones who stay close to the mission, the donors, and the beneficiaries, because the team around them handles everything else.
Charity OS is a worked example. The structure is real, the agent roles are real, the prompts work. Take it, fork it, change the names, adjust the personalities, add or remove specialists based on the org. No coding required. No engineering background assumed.
The hand-held guide to building your own team of AI co-founders with Claude Code. Start here if you are new to this.
Entrepreneur OS, Designer OS, Investor OS, and Operator OS. Four worked examples for individuals and firms.
Foundation OS, and Institute OS. Two more worked examples in the nonprofit family.