Insights from 16 nonprofits in the OpenAI Foundation's People-First AI Fund, and how much they turned out to have in common.
Read the paperSix nonprofits running five months of agentic fundraising in the open, with everything they learn published as they go.
Meet themEngage
Donor experiences
Outreach
Audience
Insights
Library & data
25 Aug 2026No supporter gets the same email twiceWhat personalized email actually runs on, what we capture, and what we're testing.
18 Aug 2026Your donor used AI to give to your causeA new Senate bill, a payments protocol, and what agentic giving means for consent.
12 Aug 2026Six nonprofits selected to pioneer agentic givingFive months of open experiments in agentic fundraising, published as we go.Whitelabel AI Bootcamp, one day
One day for nonprofit fundraising and technology teams. You bring one problem and your own donor data, you build it with an engineer beside you, and you leave with something running rather than a slide about the future.
The session
In June a foundation put nine of its grantees in one room in New York for a morning on benefits access, and we ran it. Nobody there wanted another talk about what AI might do. They wanted to see an eligibility check run on a real application, watch it get one wrong, and argue about why. That morning produced the only engagement we have ever won from a workshop, and it is the shape of this day.
The Bootcamp is one day, and it ends with something running on your own data. We spend the morning choosing the problem, the afternoon building it with one of our engineers at your table, and the last hour showing the room what works and where it fell over. There is no product demo, because a demo is what most of you have already sat through. If a sale ever follows, it follows weeks later, when someone asks what it would take to run this properly.
It is built for the two people who never sit in the same session, the fundraiser who knows the donors and whoever ends up owning the tools, and it works when both come. Eight to twelve nonprofits fill the room, two or three people each, and every one of them arrives with one problem it has been meaning to solve, the lapsed-donor list nobody has written to or the grant report that takes a week. By five o’clock we expect that problem to have a working answer, and the notes to keep it working on Monday.
The day
One day, doors at a quarter to nine, drinks at five. Open a session to see what happens in it and who is in front of the room.
Morning, framing and choosing
Coffee and a table for each organisation. The engineer who is yours for the day finds you, and you show them the export you brought.
What the day is for and what it is not, how the pairing works, and what we will ask of you by four o'clock. One rule holds all day, which is that nothing gets built that you could not run yourselves on Monday.
Someone who has put AI in front of their own donors, on what changed and what they would not do again. Twenty minutes, then questions.
The five themes further down the page, each shown working rather than described. A supporter finds a cause through an AI search, an agent answers a donor at eleven at night, a retention score runs on a real file, a CRM talks to a campaign, and a governance page comes out that a board would sign. Each gets ten minutes, including where it falls over.
Each organisation names the one problem it will build against this afternoon, out loud, to the room. It might be the lapsed-donor list nobody has written to, the grant report that takes a week, or the inbox that gets answered on Friday. We help you cut it down to something a day can hold.
Afternoon, the build
Two and a half hours on your own data, in your own accounts, with an engineer beside you. Short skills sessions run at the side of the room for anyone who wants them, on getting a clean export out of a CRM, reading a retention score without a statistician, and writing the one-page policy a board will ask for.
Each team has five minutes to show what works, what fell over, and what it would take to run it on Monday. The room asks questions and nobody pitches.
Twenty minutes from someone outside the room on where this goes next for the sector, and what the people who fund this work now expect from it.
We go for a drink nearby, and every organisation leaves with something running and the notes to keep it that way.
Donor-advised bots
Five themes, each shown as something working rather than a slide, in the hour before you choose your own problem.
How supporters discover your cause through AI search, recommendations and conversations.
We ask an AI search for a cause like yours and watch who it recommends, then look at what on your site decided it.
Specialist agents, intelligent websites and personalised donor journeys.
An agent answers a donor's question at eleven at night, takes the gift, and writes the thank-you. You see where it gets it wrong.
From giving propensity and retention risk to campaign planning.
A retention score runs on a real donor file in the room, and we read it together without a statistician.
Linking CRM, campaign and donor knowledge with automated action.
A CRM export becomes a campaign, the campaign writes back to the CRM, and a person approves each send.
Governance, adoption and scaling beyond isolated experiments.
The one-page policy a board will sign, written from the day's work, and what to do when the pilot's champion leaves.
Bring your own problem
The organisations in the room are the experts on their donors, and the afternoon is built on what they bring rather than what we show. Every nonprofit that has written to us this year asked for a version of the same handful of things, and any one of them fits in a day.
Organisations in the room
Eight to twelve nonprofits, named with the date.
Who is in the room
We host and our engineers pair with your team. Three guests join for the talks, and their names go to the sign-up list before they go anywhere else.
The practical part
Questions about the day go to hello@whitelabel.ai.
First session
The date, the city and the guests go to this list first. Tell us who you are and we will write when the first Bootcamp opens, with the problem list to think about before you come.
