Nonprofit board service is a real job done in narrow windows. The board packet lands four days before the meeting — sometimes 80 pages, sometimes 200 — and you have evenings around your day job to read it carefully enough to ask a useful question. The committee work between meetings is its own packet. The fiduciary duty doesn't pause when the calendar is full. And the consequence of skimming is real: you're either going to ratify something you didn't fully understand or stay quiet on something where the board needed your voice.
A vault of plain markdown notes with an integrated agent is a calmer way to carry the load. Not a replacement for actually reading — that's still your job — but a way to make the prep tractable in the time you have, hold the governance history across years of service, and walk into the room having actually thought about what's on the agenda. The same shape underwrites how angel investors handle deal screening and portfolio tracking and how startup advisors and board members hold context across many companies.
A vault shaped around the board calendar
The shape that holds up across years of service is roughly: one top-level page per organization you serve, with sub-pages for the board-meeting archive, the committee work (each committee its own sub-page), the governing documents, the strategic plan, and the per-meeting prep notes. Capy supports unlimited page nesting, so a long-tenured seat can fan out by year or by topic without forcing structure on a newer one.
The whole vault is plain markdown. That matters because when the next packet lands, you don't start from blank. You ask the agent to read across the prior meeting recap, the relevant committee notes, the strategic plan, and the new packet, and to draft a short pre-read brief: what's new, what continues a thread from last meeting, what looks inconsistent with prior decisions, what you should be asking about. The reading you still have to do, but the framing is already built.
Board packets that get read carefully in the time you have
The honest workflow most board members use is to skim the packet on the train and hope the conversation in the room covers the substance. The honest result is that important decisions get ratified without the depth of attention they deserve — not because the board doesn't care, but because the prep is structurally rushed.
Drop the packet on the per-meeting prep page. The PDFs auto-convert to markdown via docstrange, which means the agent can read every page and treat them as searchable text the same as any other note. Ask the agent to summarize the board packet in plain English with the financial section called out separately, the program updates compressed to one paragraph each, and the resolutions listed verbatim. Then ask: which items in the packet contradict something we decided in the last three meetings, and which items aren't backed by the data referenced in the financials.
You read the summary first, which takes ten minutes, and then you do targeted deep reads on the parts that warrant it. The total time is shorter than a careful skim and the depth on the parts that matter is much better. (The same packet-prep mechanic is the spine of how to run a board-of-directors meeting from notes — different audience, same compression.)
Governance documents that stop being filing-cabinet noise
Every nonprofit board operates under a stack of governing documents — bylaws, articles of incorporation, conflict-of-interest policy, whistleblower policy, gift-acceptance policy, document-retention policy. Most board members signed acknowledgments of these documents at orientation and have not opened them since.
Drop the governance stack on the org's top-level page. They auto-convert to markdown the same way. Now when a question comes up in committee — does the bylaw require a quorum of half plus one or two-thirds for this kind of vote, can the gift-acceptance policy be invoked to decline the proposed donation, what does the conflict-of-interest policy require me to disclose about my new business relationship — you ask the agent and get the relevant clause back with citation.
The agent isn't a substitute for legal counsel. It is a substitute for "let me get back to you" followed by never quite getting back to you, which is the typical pattern.
A decisions log across years of service
Boards make a lot of decisions and most of them get filed in minutes that nobody opens again. The decision to defer the executive director's compensation review for a quarter. The decision to accept the risk on a particular grant condition. The decision to wait on a strategic question until the next planning cycle. Each one made sense in the room. Two years later, when the question comes back, the rationale is gone and the new board reconstructs it from scratch, sometimes badly.
A working setup: an inline decisions database in the org's top-level page via the :::database::: directive — rows for date, decision, rationale, area affected, and what triggered it. After every board or committee meeting, ask the agent to read the recap and the minutes and propose entries. You confirm or edit; the rationale lands while it's still fresh.
Over years of service, you build a personal record of what the board has actually decided and why — separate from the official minutes, focused on the rationale rather than the resolution. When a new board member asks why the org doesn't take corporate sponsorship, you have the actual answer, not "I think we discussed this in 2023."
Committee work that doesn't restart from zero
Most board members serve on at least one committee — finance, audit, governance, development, executive. The committee meets less often than the board, usually with thinner support, and the prep cost is structurally similar. The packet, the document review, the question of what's continuing from last meeting and what's new.
Each committee gets its own sub-page in the org's vault, with the same shape: meeting archive, decisions log, open questions database, key documents. Before the committee meeting, ask the agent to read the prior recap, the open questions, and the new packet, and draft a brief in the same way. Open questions that have aged past their target close date surface automatically. The committee meeting becomes a working session against an actual list. (The open-questions discipline is the same one underwriting advisory board meetings — different room, same structural tightening.)
Multiple boards held in one vault
Many nonprofit board members serve on more than one board. The two boards rarely intersect substantively, but they do compete for the same evening hours and the same fiduciary attention. Holding each org's vault as a top-level page lets you keep them genuinely separate while still benefiting from a single search surface.
Ask the agent: across all my board work, when does my next major fiduciary deadline fall — annual audit signoff, 990 review, ED evaluation, strategic-plan update? You get a unified calendar of obligations across organizations without having to maintain a separate spreadsheet. The agent reads the vault on demand.
For the harder rooms — a contentious executive session, a strategic planning retreat, a leadership-transition conversation — record the session in Capy where the board's protocol allows. The transcript comes back with speaker diarization, labels like "Speaker 1: …" so you can tell who said what. Ask the agent to draft a personal recap focused on what was decided, what was raised but not resolved, and where the board's center of gravity actually is. The transcript matters for your own thinking next time the topic comes back; it isn't a substitute for the official minutes. (The recording-with-speaker-labels habit shows up in our writeup of coaching sessions and personal growth too — different setting, same loss pattern.)
What this isn't
Capy isn't board-management software. It doesn't host the official minutes, run a board portal, or manage director communications. The structured side of board work — the portal, the minutes archive, the official document repository — still lives in the tools the org uses. Capy is for the unstructured side, the personal connective tissue: your prep, your decision log across years, your private recaps, your questions queue. That's the part that's currently sprawled across email, Drive, and your memory.
It's also single-user by design. One board member, one vault. If your governance setup needs a multi-user shared workspace where the whole board edits the same artifacts with role-based permissions, that isn't this product. Capy doesn't claim regulatory certifications either — it's not a substitute for the org's compliance infrastructure. Pricing tiers are on the pricing page.
A small first test
Pick the next board meeting on your calendar. Drop the packet, the last meeting's recap, and one of your governing documents on a Capy page. Ask the agent to draft a one-page pre-read brief and a list of the three questions you should be ready to ask. If the brief surfaces a tension between the new packet and the last meeting's decisions, that's the agent doing for you what board service deserves and rarely gets.
Try Docapybara free. Load one packet and see what the agent does with it before the next meeting.