If you do major-gift fundraising, you carry a particular kind of relationship memory. Not just names and amounts — the specific concern a donor raised in a 2024 site visit, the daughter who's a freshman at the same school you both went to, the ask the donor declined and the reason they gave, the program area they keep gravitating toward, the spouse who handles the family's giving decisions.
This context is the work. The institutions that lose donors usually aren't worse than the ones that keep them at the program level — they're worse at remembering what the donor said the last three times. This guide is about a calmer way to hold donor context across many relationships, where an AI agent reads the vault alongside you.
Why CRM alone isn't enough for major-gift work
Most fundraising teams use a CRM. Raiser's Edge, Bloomerang, DonorPerfect, Salesforce NPSP — pick your flavor. They're all reasonable at structured data: gift amounts, gift dates, soft credits, designations, contact owner.
What CRMs are not great at is the unstructured story. The texture of a donor relationship lives in places the CRM doesn't reach: handwritten notes from a coffee meeting, the email thread where a donor's spouse explained their giving philosophy, the recording of last spring's site visit, the briefing memo you wrote before the gala that got buried.
A workable system has the CRM doing what it's good at — structured tracking, reporting, board-facing rollups — and a vault doing what it's good at — holding the unstructured story in a form an AI agent can read. Not a replacement. A complement.
What we built Docapybara around is the second piece: a single vault, plain markdown notes, an AI agent that reads everything. The rest of this guide is how that maps to a fundraiser's actual workflow. Adjacent shapes — account-context tracking and the broader sales-day workflow — are in How Account Managers Keep Client Context From Slipping and How to Use AI in Sales (Without Falling for the Hype).
One donor, one branch of the vault
The shape that scales across a major-gift portfolio is dead simple: one top-level page per donor (or donor household), with sub-pages underneath for everything that pertains to them. Unlimited nesting, so the structure can grow with the relationship.
A typical donor page in your sidebar:
- The Carlyle Family
- Profile (giving history, family context, interests)
- Meetings
- 2024-09-12 — coffee with Margaret
- 2025-03-04 — site visit (both)
- 2025-11-18 — Christmas card and check-in
- Correspondence (emails, letters, thank-yous)
- Past asks and outcomes
- Stewardship plan
- Open follow-ups
When the next ask is approaching, you don't reassemble context from email and CRM. You ask the agent: "Read everything under the Carlyles. Give me a one-page brief covering giving history, the things they've consistently cared about, the last conversation we had, and any open follow-ups."
For couples or families with multiple decision-makers, the page can split into sub-pages per individual while still rolling up to the household. Margaret's interests, David's interests, the joint giving pattern.
Meeting notes that survive the year
A coffee meeting with a donor in March produces a few pages of useful context — what they're thinking about, what changed in their family or their giving philosophy, what they liked from the last update. By August, those pages have evaporated unless they were captured well.
For meetings you'd normally take notes in, the audio-and-transcript pattern helps a lot. With the donor's knowledge, record the conversation. Drop the audio onto the relevant meeting page in your vault. Transcription with speaker labels happens automatically. You're free during the meeting to be present — eye contact, real listening, picking up on the things between the words.
Afterward, ask the agent: "Read the transcript from the coffee with Margaret. Pull what she said about the program areas she's most drawn to, anything she mentioned about her family's giving plans, and any specific commitments either of us made." You get a structured note in seconds. The transcript is still there if you need to pull more later.
For phone calls — which fundraising involves a lot of — the same pattern. A short call with the donor relations chair becomes a transcript, becomes a searchable note, becomes part of the donor's record. Three months later when the donor references "what we talked about on the phone," the moment comes back.
Stewardship that doesn't go fuzzy
Stewardship is famously the easy thing to skip. There's always a more urgent ask. The donor who gave six months ago and hasn't been thanked properly in a personal way is the donor most likely to lapse.
A stewardship plan lives best as a sub-page on each major donor's page. What kind of touch they prefer, the cadence that's worked, the people internally who should also touch base, anniversaries to acknowledge, programs they've funded that should be reported on. Specifics, not generic stewardship calendars.
The agent helps with the cadence question. Ask once a month: "Read the stewardship plans for my top 30 donors. Tell me which ones haven't been touched in over 60 days, and which ones are coming up on a meaningful anniversary." You get a focused short list of who needs a real touch this month, not a guilty general feeling that you're behind.
For drafting the actual outreach, the agent works from the record. "Draft a stewardship email to the Carlyles. Reference the conversation Margaret and I had in March about the literacy program, and the gift they made in May. Make it warm but not gushy." You get a draft grounded in actual history, not a template-driven thank-you. The agent-acts-on-docs idea behind that is described in Claude Code for Documents.
Donor briefs that take 30 minutes, not three hours
Before any major donor meeting, the prep is the work. Most fundraisers do this in a Word doc the day before — pulling history from the CRM, scanning past meeting notes, googling for any recent mentions of the donor in the news.
In a vault, the prep happens by asking. "I'm meeting with the Carlyles on Tuesday. Read everything under their page. Draft me a briefing memo with: their giving history and pattern, the three things they care about most, the last time we talked and what they said, anything open since the last meeting, and one specific update about the program area they care about that I can lead with."
The agent gives you a draft. You spend twenty minutes refining it — adding nuance the agent missed, fixing wrong inferences from the transcripts, adding context that came up in conversation with a colleague. You walk into the meeting genuinely prepared, with a brief that's grounded in the actual history of the relationship.
For board-prep around major donors, the same pattern. The board chair wants a briefing on the top 10 prospects ahead of the next meeting; the agent drafts a one-paragraph summary of each, you refine, done. The consulting analogue of this prep rhythm is in AI Notes for Consultants.
Past asks, foundations, and the prospect-research pile
Most fundraising teams lose institutional memory at staff transitions. The new gift officer inherits a portfolio with names and amounts but not the texture: which ask did we make in 2022 that the donor declined and why, what was the program officer's read on the household dynamic. A "Past asks and outcomes" sub-page on every major-donor page captures it — date, amount, designation, outcome, what the donor said. A few lines per ask, accumulated over years, becomes the institutional memory a CRM can't hold. When a new gift officer takes over the portfolio, the agent summarizes everything for them in an afternoon.
For foundation work, each foundation gets a top-level page with sub-pages for giving guidelines (the PDF auto-converts to searchable text via docstrange), past proposals, correspondence, program officer relationship, and the next deadline. When a new RFP lands, drop the PDF in and ask: "Compare this RFP to the proposal we submitted last year. What's changed in their priorities, and which sections of last year's proposal can we reuse?" For drafting, the agent works from your library — reuse the budget structure from the Doe proposal, lead with the impact data updated last quarter — and you focus on the case-making.
For prospect research, the agent's web_search tool pulls live web pages with source URLs. "Find recent news about the Carlyle Foundation's giving in the literacy space. Save the findings as a sub-page under their profile with source URLs." The research lives next to the rest of the donor's record, sourced and ready to refine.
The weekly portfolio review
Once a week, scan the active portfolio. Anything that needs a follow-up email, a stewardship touch, or a meeting request goes on a single follow-ups list. Update statuses on anyone whose stage changed. Add anything that didn't get logged during the week.
Ask the agent: "Across my whole portfolio, what stewardship is overdue? Who hasn't been touched in over 30 days? What asks are pending and need a next-step decision?" Ten minutes — and the donors who would have quietly slipped get a touch this week instead of next quarter.
A calmer way to fundraise
Worth being explicit about boundaries. This isn't a CRM — keep your CRM for gift recording and team-shared visibility. It isn't a database of record for compliance. It isn't a shared workspace — the vault is single-user, scoped to your account. What it is: the place your own working context lives. The unstructured story. The transcripts. The strategy memos. The texture that makes you the gift officer who actually knows the donor.
Major-gift work is going to take a lot of relationship memory regardless of tooling. But the cost of holding that context — the searching, the reassembly, the night-before prep — is fixable. Move the unstructured context into a vault, let an agent read across it, and the meetings get easier to walk into.
Try Docapybara free. Pick one major donor, drop in the last meeting recording, the giving history, and your stewardship plan — and ask the agent for a briefing memo for your next conversation.