The honest reason board meetings consume so much founder time isn't the meeting itself. It's that every quarter you reassemble the same context from scratch — last quarter's deck, the metrics that matter, the open questions a board member raised in October that you promised to address in January, the strategic theme you said you were working on. The deck takes a week not because it's hard to write, but because the inputs to it are scattered across email, Drive, and your head.
A board cycle that holds up is one where the notes layer is doing the assembly work for you. Not "ask AI to write a board update." Ask the agent: read last quarter's deck, my running notes since then, the open items from the prior board, and this month's metrics, and draft this quarter's update in the same structure as last quarter's. The deck still needs your edit — the strategic framing is yours — but the assembly happens in a fraction of the time. The same vault feeds annual planning and goal setting — the year-in-review at the bottom of the planning cycle is the same source as the cumulative board update.
A board vault that holds the cycle
The shape that holds up is roughly: one top-level page per board cycle, with sub-pages for the deck, the pre-read, the open-items log carried forward from the prior board, and the meeting recap. One cross-cutting page for board notes per board member — running observations on what they care about, what kinds of questions they tend to ask, what frameworks they reach for. One inline database for board decisions across all cycles, with rows for date, decision, rationale, and owner.
Capy supports unlimited page nesting, so a heavy cycle with several committees can fan out into per-committee sub-pages. The decisions database lives directly in the cycle page via the :::database::: directive — you don't switch tabs to a separate tracker.
The board pages live in the same vault as the rest of your operating notes. That matters because the agent can read across both — the board materials and the underlying operating record — when it's drafting or prepping. The deck stops being a parallel narrative and starts being a synthesis of what the company actually did.
Drafting this quarter's deck from last quarter's
Most board decks are structurally similar to the deck before. The same five sections, the same metrics dashboard, the same "asks of the board" slide. The differences are the numbers and the strategic narrative, not the shape.
Drop the prior quarter's deck and your running operating notes since then on a fresh page. Tell the agent: read across these and draft this quarter's deck in the same structure. Pull the metrics from this month's dashboard. Update the asks slide to reflect what we actually need help with this quarter — the two intros that came out of the last board meeting are now closed and the new asks are these. Keep the candor level of last quarter's, including the parts that were uncomfortable to write.
The first draft is rarely perfect; it's usually a much better starting point than the empty page. The strategic framing is the part you spend real time on. The assembly — the metrics, the carried-forward asks, the structural consistency — is the part the agent does in minutes.
Pre-reads board members will actually read
The pre-read is where most boards lose value. It's either too long, in which case nobody reads it, or it's too short, in which case the meeting becomes a status update instead of a strategic conversation. The line between those two failure modes is a real craft.
A working pattern: ask the agent to draft a five-page pre-read from the deck, with an explicit instruction to summarize the metrics narrative in one paragraph and spend the bulk of the pages on the two or three strategic decisions you want input on. The agent has the deck and the operating notes; it can produce a pre-read that's actually weighted toward the parts that need board judgment, not the parts that need board acknowledgment. (For the more conversational board-style meeting, AI notes for advisory board meetings walks through the same prep loop with less formality.)
You edit. You push back on parts that feel off. The pre-read goes out the day before the meeting instead of the morning of. Board members walk in having already chewed on the actual questions.
Anticipating board questions, with the answers loaded
The most common board-meeting failure mode for founders isn't the deck. It's getting blindsided by a question whose answer is in your head somewhere but not at your fingertips. The board member asks about the gross-margin line and you spend two minutes flipping between tabs trying to remember which segment is dragging.
A working setup: a week before the board, ask the agent to read the deck, the open items from the prior board, the running notes per board member, and produce a one-page list of likely questions per board member based on what they've cared about historically. For each question, draft a one-paragraph answer with the supporting numbers from your operating data. The list is not a script — boards don't reward scripts — but it's the kind of preparation that lets you spend the meeting actually thinking instead of looking up.
The running notes per board member matter here. The board member who reaches for unit-economics framing is going to ask about CAC payback again. The board member who reaches for talent framing is going to ask about hiring velocity. You know this; the agent makes it explicit and helps you load the relevant data per question.
Recording the meeting with speaker labels
Board meetings produce two kinds of decay. The decisions decay because nobody writes them down with enough specificity. And the side-conversations decay because the action items mentioned in passing get lost in the recap.
Record the meeting inside Capy. The transcript comes back with speaker diarization — labels like "Speaker 1: …" so you can tell who said what, not just a wall of text. Park the recording on the cycle page. Ask the agent to draft a recap with three sections: decisions made, open items carried forward, action items per owner. Pull every numerical claim that came up so you can verify it later if needed.
The recap goes to the board within twenty-four hours. The decisions land in your decisions database. The open items carry forward into the next cycle's page automatically, which means next quarter's prep starts with the carried-forward list already populated.
The transcript also makes "what did the board actually agree to" a question with a definite answer, not a memory exercise.
PDFs board members send, finally readable
Board members send things. A market analysis from one of their other portfolio companies. An article they want you to read. A draft strategy memo they wrote between meetings. Most of those PDFs sit unread in your inbox.
Drop the PDF on a Capy page. It auto-converts to markdown via docstrange, which means the agent can read every line — not just keywords from the file name — and treat it as searchable text. Ask the agent to summarize the document in one paragraph, identify the parts that are likely relevant to your business, and propose a one-line response to the board member that's substantive but doesn't commit to anything you don't yet know.
The conversion runs once per upload. From then on, the document stays searchable in the same vault as the rest of your board materials.
What this isn't
Capy isn't a board portal. It doesn't manage board-member access permissions, host the board package for distribution, or handle director attestations. The compliance side of board operations still belongs in the tools that handle it. Capy is for the founder's working layer — the deck assembly, the prep, the running notes per board member, the recap and decisions log — which is the part of the cycle that actually consumes founder time.
It's also single-user by design. One founder, one vault. If you need a multi-user workspace where the corporate secretary, COO, and board chair share files with role-based access, that isn't this. The shape that fits is a personal vault that holds the founder's prep and synthesis, with the official package distributed through whatever channel your board prefers.
A small first test
Take the last quarter's deck, the recap from the last board meeting, and any running notes you've kept since then, and load them on a single page in Capy. Ask the agent to write a one-page summary of where the company stands going into this quarter's board and what the two strategic decisions are that most need board input. If the summary names a tension you'd been carrying around without saying out loud, you've got a sense of what the agent does once the board cycle is fully in the vault. The same draft-from-the-prior-deck pattern is detailed in AI for fundraising for the investor-update sibling artifact.
Try Docapybara free. Load last quarter's deck and see what this quarter's draft looks like.