If you run a small foundation, with an endowment, a family board, a grantmaking calendar, and a fiduciary duty that doesn't sleep, this is the toolkit. Eight AI co-founders handle the investment office, grantmaking, program strategy, family engagement, external affairs, finance, legal, and the connective tissue that holds the foundation together, so Laurence can stay close to the family, the trustees, and the grantees who matter most.
Foundation OS is for the executive director of a small family foundation. A $25M endowment. A $200M endowment. A foundation with three staff, or seven, or twelve. A foundation where the board is the family and the family is the board. A corporate foundation tucked inside a parent company. Anywhere a small team carries the same fiduciary, programmatic, and family-stewardship duties as a billion-dollar institution, this is your team.
Eight AI co-founders handle the work that lives around the mission. The investment office. The grantmaking pipeline. Program strategy. Family and trustee engagement. External affairs. Finance and compliance. Legal. The board materials and family communications cadence. So the ED can stay close to the trustees, the grantees, and the decisions that compound across generations.
This page shows what a finished Foundation 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.
A $35M family foundation carries the same fiduciary, programmatic, and family-stewardship duties as a $5B foundation. The same payout rule. The same 990-PF. The same investment policy statement. The same expectations from grantees, peer foundations, and the IRS. The same need to honor the founders while serving the present.
Large foundations meet those duties with a hundred-person team: an investment office, a program staff, a communications shop, a CFO, general counsel, a board liaison. Small foundations meet them with four people and a lot of nights and weekends.
Eight AI co-founders give Laurence operating leverage equivalent to a fourteen-person staff while he stays at four humans. The corpus must outlast the founding generation. The grants must reflect the family's values. The board must be informed without being overwhelmed.
The corpus must outlast the founders. The grants must reflect the values. The board must trust the team.
Operating leverage: the foundation does the work of a much larger institution without the headcount
No coding. No technical background. Laurence gives a plain-English instruction. Alfred routes it. The right specialist does the work. Laurence reviews. Here is how the foundation moves through the year.
Laurence installs the eight agents using the AI Agents 101 guide. One weekend. He feeds the system the foundation's mission, focus areas, payout rule, IPS, grantee portfolio, and the family history. The team is now context-aware.
Each agent works with full foundation context: mission, focus areas, payout rule, investment policy statement, grantee portfolio, family history. Henry knows the IPS. David knows every grantee. Eleanor knows which trustees are which generation. Margaret knows what the corpus can sustain.
The system gets better with use. Agents learn the family's philosophy, the foundation's cadence, the trustees' preferences, the grantees' rhythms. The board packet that took two weeks to draft now takes two days. The annual report cycle compounds year over year.
Think of it less like software and more like an eight-person staff. Laurence is the executive director. The team handles everything that does not require his judgment.
Eight co-founders with names and clear scopes. Alfred sits at the center and routes every request. Each specialist works with full foundation context: the mission, the focus areas, the payout rule, the grantee portfolio, the family. Click any skill to see what it actually does.
The hub. Routes everything. Sees the full quarter: board meeting, grant cycle deadlines, investment committee, site visits, grantee reports, family gatherings. Holds the line between what Laurence actually has to touch and what the team can absorb. Without Alfred, Laurence ends up rewriting board memos at midnight instead of thinking strategically.
Every morning Alfred sends Laurence the one-page "what needs you today, what doesn't." Three buckets: auto-handled, drafted for review, stop-and-ask. He also runs the board prep and family communication cadence.
Calm, organized, never alarmist. Discreet about family dynamics.
"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 Laurence's Hyde: equal but opposite, by design. Tracks the operating budget, applies the payout rule, prepares the 990-PF, assists the audit, assembles the finance committee materials. The deliberate counterweight when board enthusiasm pulls toward a new grant program the corpus cannot sustain at the current payout rule.
Laurence runs every meaningful financial decision past Margaret before acting. New initiative, multi-year pledge, staff hire: Margaret models it first against the payout rule and the long-term corpus model. Her job is to slow Laurence down just enough to think clearly.
Direct, warm, honest. Fiduciary register without being legalistic.
"Margaret, the board wants me to add a $500K-per-year initiative in [focus area] for five years. Walk me through what it does to the payout, the corpus trajectory, and our flexibility if returns soften."
Manages the endowment. Investment Policy Statement, asset allocation, manager selection, performance reporting, investment committee materials. A small foundation cannot afford a Chief Investment Officer; Henry is the next best thing, and he is honest about what he is not (a discretionary asset manager).
Henry drafts the quarterly investment committee pack, runs initial manager due diligence (Laurence and the IC chair approve any change), tracks performance against benchmarks, and flags when the asset allocation drifts outside the IPS bands.
Sober, evidence-led, allergic to manager-sales-deck language.
"Henry, draft the Q3 IC pack. Performance against benchmark, two rebalances to propose, and the public-equities manager review we deferred last quarter."
Grant scouting, grantee due diligence, grant agreements, grantee reporting tracking. The operational engine of the foundation. David runs the grant lifecycle from sourcing through final report, so Laurence and the program team can focus on judgment and relationships.
He maintains the grantee pipeline, drafts the due diligence memo for every prospective grant, prepares Laurence and the trustees for site visits, and tracks every grantee's reporting compliance so nothing slips through.
Specific, fair, respectful of grantee burden. Never bureaucratic.
"David, build the due diligence memo on [prospective grantee]. Org health, financial sustainability, program fit with our focus area, and the one risk the IC will ask about."
Program strategy, focus areas, theory of change, learning agenda, evaluation. Charlotte is the foundation's program brain. She does not run the programs (the grantees do) but she shapes where the foundation puts its money and how the foundation learns from what it funds.
Charlotte drafts the annual strategy update, runs the learning agenda across grantees, and prepares the focus-area review for the board every two years. When a new field opportunity appears, Charlotte writes the strategy memo first.
Rigorous, intellectually humble, never academic-jargon.
"Charlotte, the board wants to know if our [focus area] strategy is still right. Pull a field scan, three peer foundations' approaches, and a sharper articulation of where our money is differentiated."
Board books, family member onboarding, next-gen programming, succession planning, family meeting prep. Family foundations live or die on trustee engagement and generational handoff. Eleanor runs that program quietly and well.
Eleanor drafts the board packet 14 days before each meeting, runs the next-gen onboarding curriculum for any family member coming onto the board, prepares Laurence for sensitive family conversations, and tracks each trustee's level of engagement.
Discreet, warm, family-system-aware. She knows where the family fault lines are and never names them out loud.
"Eleanor, [next-gen family member] joins the board next quarter. Build the six-month onboarding plan: readings, site visits, one-on-ones with current trustees."
Annual report, grantmaking transparency, sector positioning, peer-foundation relationships, occasional press. Small foundations rarely need a comms director; they always need a thoughtful external voice. Beatrice is that voice.
Beatrice drafts the annual report each spring, maintains the foundation's public-facing materials, prepares Laurence for conference panels, and runs the relationships with peer-foundation EDs that matter.
Quiet, considered, slightly understated. The foundation does not market itself; it accounts for itself.
"Beatrice, draft the FY26 annual report. Lead with the [focus area] learning, three grantee profiles, the financials Margaret approved, and Laurence's letter."
501c3 compliance, 990-PF, state filings, self-dealing rules, excess business holdings, gift acceptance, grant agreements legal review. Foundation compliance is dense. Theodore makes it boring on purpose.
Theodore runs the compliance calendar so nothing lapses, reviews every grant agreement above $50K, flags any transaction that triggers self-dealing review, and prepares the audit firm before the engagement starts.
Precise, calm, fiduciary. Never alarmist, never sloppy.
"Theodore, run the compliance calendar for the next 90 days. What's coming due, what I need to approve, and what needs a board vote."
Hub and spoke. Alfred at the center, routing every request and orchestrating multi-agent work. Each specialist covers a clear domain and brings full foundation context. One team, no silos.
Four moments from a real year at a small family foundation. Each one shows how a question moves through the team.
It's January. The spring grant cycle opens. David scouts new prospects in the focus area. Charlotte updates the field scan and refreshes the strategy lens. David drafts due diligence memos. Margaret checks payout-rule fit. Eleanor preps the board packet. Laurence makes the final calls with the trustees.
The public-equities manager has trailed the benchmark for six quarters. Henry runs the manager review and surfaces two replacement candidates. Margaret models the transition cash flow. Theodore reviews the new advisor agreement. Eleanor preps the investment committee. Laurence and the IC chair make the call.
A second-generation family member joins the board next quarter. Eleanor builds the six-month onboarding curriculum: readings, site visits with three grantees, one-on-ones with each current trustee, a foundation history primer. Charlotte assigns the field-scan reading. Laurence holds the welcome conversation.
It's March. The board wants the FY annual report by the June meeting. Beatrice drafts the narrative. Margaret signs off the financials. David pulls grantmaking summary and three grantee profiles. Charlotte writes the learning section. Eleanor adds the trustee letter. Laurence writes his letter last.
Foundation OS is a working artifact in the Consumer Safari Papers series. The publication is for the people who build things and run them. Foundation OS lives at the intersection where fiduciary duty meets family stewardship and the executive director meets operating leverage.
The first generation of foundation EDs hired program officers and finance staff to do the operating work. The next generation will run leaner foundations by routing the operating work to AI specialists who carry full institutional context. The EDs who thrive will be the ones who stay close to the family, the trustees, and the grantees, because the team around them handles everything else.
Foundation 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 foundation. 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.
Charity OS, and Institute OS. Two more worked examples in the nonprofit family.