Advisory boards are an unusual form of meeting. They're high-context — usually four to eight smart people who already know the company well. They're high-stakes — you're spending some of the most expensive hours your business has access to. And they're famously hard to follow through on, because by the time you've digested the discussion, three weeks have passed and the next set of operational fires is in front of you.
This guide is about a calmer setup for the advisory board cycle: how to prepare so the meeting is dense with useful discussion, how to capture so the advice survives the week, and how to follow through so it actually changes how the business runs.
What an advisory board meeting is for
Worth being honest about the shape. An advisory board meeting isn't a board meeting. There are no votes, no fiduciary obligations, no formal minutes for compliance. The job is different: bring a small group of people who understand your business well enough to challenge you, and use a few hours of their attention to surface the questions you've been avoiding and the decisions you've been delaying.
Which means the artifacts are different too. You're not producing minutes for the record — you're producing a record for you, the operator. The pre-read needs to set up real questions. The capture needs to preserve who said what so you can untangle it later. The follow-up needs to convert advice into specific decisions or changes.
A vault that holds the agenda, the pre-read, the recording, the transcript, and the follow-ups in one place is the calmer way to run that cycle. We built Docapybara around this kind of work — single-user, plain markdown, an AI agent that reads everything in your vault. The fiduciary cousin of this — formal corporate boards with minutes that have legal life — is in AI notes for board meetings.
The pre-read that earns the meeting
The biggest determinant of an advisory board meeting's quality is the pre-read. A weak pre-read produces a meeting where you spend the first hour on context. A good pre-read produces a meeting where you walk in and someone asks "Can we go straight to the question on slide four?"
Structure that works for most operating businesses:
- A one-page state-of-the-business — the numbers that matter, the trend, the surprises since the last meeting.
- The two or three open questions you most want input on, framed as decisions you're considering.
- Background only on the questions — context, what you've already tried, what your hypothesis is.
This page lives in the meeting page in your vault. The agent helps draft it. "Read the last advisory meeting transcript, the follow-ups page, and my Q1 review. Draft a state-of-the-business summary covering what's changed, what's working, and the two or three biggest open questions for the next advisory meeting." You get a draft to refine, grounded in the actual record of the quarter.
Send the pre-read 5–7 days before the meeting. Specifically ask each advisor to read it before the meeting. The advisors who don't will be obvious in the first ten minutes, and that's useful information about who's actually engaged.
During the meeting: stop being the human transcription machine
The single biggest improvement to advisory meetings is letting something else handle verbatim capture so you can be present in the conversation.
The pattern: with the advisors' knowledge, record the meeting. Drop the audio onto the meeting page in your vault as soon as the meeting ends. Transcription with speaker labels happens automatically. You don't have to babysit it.
The speaker labels matter more here than in most meetings. Advisory advice is attributable — you'll want to know whether the case for a price increase came from the advisor with twenty years of pricing experience or from the advisor who's mainly there for the network. Three months later when you're deciding whether to act on the advice, you'll want to remember whose conviction was behind it.
During the meeting itself, take light notes — only the things that don't make sense without context, like what was on the screen when something was said. Skip the verbatim. Be in the room as a participant who's actually listening. The deeper-dive on transcription mechanics is at AI meeting note taker with speaker labels, and the broader category landscape at AI meeting notes: what's actually worth using.
After the meeting: the synthesis that makes the meeting valuable
The hour after an advisory meeting is the most valuable hour. The discussion is fresh, your reactions are sharp, and the advice that mattered is still distinguishable from the advice that didn't.
Skim the transcript. The agent helps with the structural pass. "Read the advisory meeting transcript. For each of the three open questions in the pre-read, pull the substantive points the advisors made — who said what, what they were arguing for, and where the advisors disagreed." You get a structured note in minutes, with attribution, that you can edit and turn into something useful.
Then, the harder synthesis work — only you can do this part. For each open question, write down: what you heard, what convinced you, what didn't, what you're going to do, and by when. That synthesis goes on a "Synthesis" sub-page on the meeting page. It's the document you'll reread when you make the actual decision next month.
The advisors' job ended when they spoke. Your job starts now.
Where follow-ups should live (and not live)
The most common failure of advisory boards isn't bad advice — it's good advice that no one acts on. Three months later, the advisor mentions they thought you were going to try the pricing experiment, and you have to admit you forgot.
The fix is structural. Open follow-ups go on a single, persistent list, not in the meeting notes themselves. Meeting notes are read once and forgotten; a persistent list is something you actually look at.
In the vault, an inline database of follow-ups works well. Embedded directly in a markdown page via the :::database::: directive. One row per commitment. Columns for the commitment, the source meeting, the owner (you, your team, or an advisor), the due date, the status. Six column types are available — short text, long text, dates, single-select, number, checkbox — which is enough.
The agent can populate it for you. After the synthesis: "Pull every commitment I made in this meeting, and every recommendation I said I'd act on. Add them as new rows in my advisory follow-ups database, with the source meeting and a tentative due date." You confirm the dates, and the work is captured in the place you'll actually revisit. The deeper take on extracting and chasing those commitments is in how to capture action items so they actually get done.
The cadence that keeps advisory boards useful
Most advisory boards meet quarterly. Some meet every six weeks. The cadence matters less than the rhythm of work between meetings.
A workable quarterly cadence:
- Month 1, Week 1 (week of meeting): meeting itself, transcript, synthesis page, follow-ups added to the database.
- Month 1, Week 2: send each advisor a short personalized note thanking them for specific advice, mentioning what you took away. Five sentences each.
- Month 1, Week 3–4: act on the highest-priority follow-ups while the discussion is still fresh.
- Month 2: ongoing operational work; advisory follow-ups continue closing.
- Month 3, Week 1: midterm check on what's been done. The agent helps: "Read the advisory follow-ups database. What's been completed, what's overdue, what's still untouched?"
- Month 3, Week 2–3: pre-read for next meeting starts coming together. Last meeting's follow-ups become a section of the next pre-read — what we did with the advice and what we learned.
- Month 3, Week 4: send pre-read 5–7 days ahead of next meeting.
The agent helps at every step where the work is "read what's in the vault and assemble." The thinking — what to actually do, how to interpret the advice — stays yours.
Advisor pages and what compounds over a year
Beyond the meetings themselves, each advisor is a relationship. A page per advisor with their background, the topics they engage on, the specific advice they've given and what came of it, the date of your last one-on-one, and their preferences. Before a one-on-one, ask the agent: "Read everything under [advisor]'s page. What advice have they given recently, what came of it, and what's likely to come up?" Five minutes of prep, and the call has substance.
The vault is single-user, scoped to your account. Synthesis pages, operational follow-ups, and candid notes about which advice you're rejecting stay internal. What you share with advisors: the pre-read, a short post-meeting thank-you that mentions what you took away, and the next quarter's pre-read with a note on what you did with their advice from last time.
The compounding shows up around meeting three or four. By then you have a transcript history the agent can read across. "Across the last four meetings, what's the pattern of advice on pricing? Which advisors have changed their views, and on what?" That's pattern-finding that's hard to do from memory but easy from a vault. By the end of a year, the advisory archive is a real strategic asset — the decisions you made and didn't make, the advice that held up, the advisors whose track record on your specific business actually proved out.
A quieter way to run the cycle
Advisory boards are one of the cheapest sources of leverage a business has. The problem isn't getting the advice — it's converting it into action without the conversion drowning under operational work. A vault that holds the agenda, the recording, the synthesis, and the follow-ups makes that conversion routine instead of heroic.
Try Docapybara free — sign up, then run your next advisory meeting through the cycle: pre-read in a vault page, recording dropped in afterward, transcript, synthesis, follow-ups in a database. See whether the advice survives longer than usual.