AI Meeting Preparation: What a Pre-Meeting Brief Can and Can't Do

Every tool in this category says it will prep you for your next meeting. Most of them will not prep you for yours, and the restrictions are written plainly in their own documentation (Granola, Read AI, Jump, Gong).

Granola builds a genuine pre-meeting brief, and restricts it to "Business and Enterprise users with Google Calendar connected", with meetings that "only include people from your own company" excluded outright (Granola docs). Read AI sends pre-reads with your open action items, and only for recurring meetings (Read AI support), so the first call with a new person gets nothing. Jump does the most thorough relationship prep we found anywhere and sells to financial advisors (Jump). Gong's prep summary generates "only when there's prior tracked activity with the account" (Gong help).

The feature is not missing. Getting to one is the hard part.

And underneath that, a second problem: the briefs that do reach you are built for the routine call. For the meeting that genuinely needs preparing, our own experience is that no generated brief replaces the thinking, and none of these vendors claims it does.

Here's what's worth knowing before you buy anything:

• what a real brief contains, and the four criteria to judge one by
• which tools build one, and exactly what gates each of them
• the meetings no assistant will ever prep, and why that's fine
• a workflow that survives a Tuesday afternoon

What AI meeting preparation actually means in 2026

AI meeting preparation is using AI to assemble the context, history and open commitments for an upcoming meeting before it starts, rather than summarizing it afterwards.

That makes it the inverse of a note-taker. Notes are a record of what happened. A brief is a forecast of the next thirty minutes: who's on the call, what you last discussed, what's still open, what you owe them.

The reason most people don't have this isn't a lack of interest. Context is scattered across the calendar, the mailbox, the CRM, the last transcript and a doc someone dropped in Slack. Assembling it by hand costs more than the meeting saves, so it gets skipped, and it gets skipped exactly when the week is busiest.

Microsoft's Work Trend Index caught what that looks like in behaviour rather than in survey answers. Across its Microsoft 365 telemetry, "in the final 10 minutes before a meeting, PowerPoint edits spike 122%, the digital equivalent of cramming before an exam" (Microsoft Work Trend Index). The source sells Copilot and Teams and the telemetry comes from its own install base, so it isn't neutral. It does measure what people did rather than what they estimated, which puts it above most numbers in this space.

The four things a real pre-meeting brief requires

These are the criteria the rest of this guide judges against.

1. Attendee context, not attendee names. Who is this person, when did you last speak, what did you promise. A name and a job title is a business card.

2. Open threads stitched across conversations. If this is meeting four in a sequence, you need what was decided in one, two and three, and what quietly got dropped. Most tools archive each meeting in isolation.

3. Commitments in both directions. The fastest way to lose credibility is to arrive without the thing you said you'd send. The brief needs an explicit line for what you owe them and what they owe you.

4. Delivery before you open the call. This is the criterion that changed in 2026, and the one most people still get wrong. A brief you have to request is a brief you skip on a busy Tuesday. It has to be written and waiting when you open the meeting.

We used to end this list differently. The old version of this article told you to block ten minutes of prep time on the calendar before every important call, because a brief with no time to read it is useless. That advice made sense when the brief didn't exist yet and assembling one was the work. It doesn't survive contact with a brief that's already written when you open the meeting. We're retiring it.

Relationship prep exists. Most people can't get it

Search "ai meeting preparation" and the results sort tools by CRM depth, promise an account brief in two minutes, and describe prep as company research: firmographics, funding news, LinkedIn, likely priorities. All of that is purchasable, and it's identical whichever vendor sells it to you.

The more useful half is what happened between you and this specific person. That isn't for sale anywhere, because it only exists in your own mailbox and your own past calls.

Several tools do build it. Here's the honest state of each, and what stops it reaching you.

Granola generates briefs overnight from "your previous Granola notes with the same people or company", your calendar, the wider web including LinkedIn, and Gmail if you connect it. It's restrained by design: "we'd rather show nothing than pad the brief with filler." Two gates. It requires a Business or Enterprise plan with Google Calendar connected, with no Microsoft Calendar path documented, and internal meetings get nothing (Granola docs). Business runs $14 per user per month and Enterprise $35, against a free Basic tier that has no briefs at all. Our fuller take on the product is in the Granola review and the Fathom vs Granola breakdown.

Granola pricing verified 2026-08-03 against granola.ai/pricing.

Read AI sends a pre-read about an hour before the call, containing the previous meeting's notes with "your action items and open questions". That's genuine commitment recall. The gate is that pre-reads are keyed to the calendar series, not to the people: they're "available for recurring meetings" only, and the panel shows reports "if it's part of a recurring series" (Read AI support). A first meeting with someone new produces nothing, and neither does a call with a familiar person under a new invite. It's also a sub-setting that's off by default. Read's documentation scopes the pre-read to the prior meeting instance and documents no email input, though you can query Ask Read manually and reach email context that way. More in our Read AI review and the piece on Read AI meeting notes.

Jump produces the most relationship-shaped brief in the category: client goals, household structure, past concerns, recent meetings with dates, and upcoming life events. It also works with no CRM at all, falling back to past meeting notes (Jump help). The gate is the market. Jump sells to financial advisors. Worth reading its two pages side by side, too: the marketing page lists email threads among its sources, the help doc's data-source list doesn't mention email at all.

Gong structures prep as objectives, key topics, suggested questions and reminders, with prior discussion highlights nested inside. But the summary generates "only when there's prior tracked activity with the account" (Gong help), and the Ask-anything panel is framed around "the Account or Deal". Per-person history exists if you drill into an individual's activity timeline. The unit is the account.

Oliv splits the two halves openly on a single page. For known deals it sends stage, close date, next steps and stakeholders. For a contact with no history, a separate agent "builds the pre-call brief: company news, LinkedIn context, funding, and likely priorities" (Oliv). When it holds relationship data it uses it, and when it doesn't it reaches for firmographics. That's the category's actual shape, stated by a vendor.

And then the constraint that applies to nearly all of them at once. Microsoft's telemetry puts 57% of meetings as "ad hoc calls without a calendar invite", with one in ten scheduled meetings booked at the last minute (Microsoft Work Trend Index). Granola, Read AI, Jump and Oliv all trigger off the calendar event. For the majority of meetings, there's no invite for the brief to fire on.

The meetings no assistant will prep for you

This is the part the category doesn't advertise, and it's the most useful thing to get straight before you change your workflow.

Automated prep is excellent for the recurring call and for the meeting where nothing enormous is riding on the outcome. What happened since last time, who these people are, which commitments are still open. That describes a large share of most calendars, and having it handled is a real gain.

It is not preparation for the meeting that needed preparing. When we record an episode of How We Grow, no brief covers the work: the angle, the questions worth asking, what we actually want the listener to leave with. No tool in this category touches that, and none of them claims to in the small print.

The failure mode is subtle. The brief isn't wrong. It's that a good brief feels like preparation, so you read it, feel ready, and walk into a high-stakes call having done none of the thinking.

A rough sort that holds up in practice: if you could describe the desired outcome in one sentence and it's the same sentence as last time, the brief covers you. If you'd struggle to write that sentence, block real time and do the work yourself.

A workflow that survives a busy week

Assume any step taking more than thirty seconds of manual effort gets skipped on a Tuesday afternoon. Each step below either runs on its own or takes less time than refilling a coffee.

Step 1: decide which meetings earn a brief

Not every meeting needs one. A standing sync with someone you speak to daily doesn't. A first call with a prospect does.

Pick a rule and keep it. A reasonable default: any external meeting with someone you've talked to fewer than five times, any meeting longer than 45 minutes, anything with money or a decision on the line. Everything else gets a sixty-second glance at the invite.

In practice this ends up informal rather than systematic. We read the brief when we're short on context or want the history with that person, and skip it entirely when we already know what the call is about. That's the honest version, and it works better than a rule nobody follows.

One useful side effect: if an internal weekly sync genuinely needs a brief to be intelligible, the meeting probably shouldn't exist in that form. Our guide on how to run a meeting covers what to do about that.

Step 2: pull the context automatically or not at all

For each meeting that earns a brief, you want the last email thread with the attendee, the most recent prior meeting summary, any tasks where they're the assignee or the source, and anything they sent recently.

By hand that's five to ten minutes per meeting, which is why it's the single most-skipped step in real life. There are two honest options: glue it together with a workflow tool, or use an assistant that already holds your calendar, mail and tasks in one place. There isn't a third option where you reliably do it by hand.

Whatever produces it, a brief should be structured and short. Three sections beat a two-thousand-word context dump. You're reading this in ninety seconds, not nine minutes.

Step 3: capture during the meeting so the next brief is half-written

This is the step that makes step 2 cheap forever. During the call, capture the decisions, the action items and the open questions, and land them somewhere your prep workflow can actually read later.

This is where note-takers earn their place. Otter, Fathom, Granola and Read AI are all good at it. Just make sure the output lands somewhere queryable rather than in a transcript graveyard. Our guide on taking meeting notes goes into what to capture, and if the problem is that meetings arrive without structure in the first place, the free meeting agenda generator handles the other end.

Where the popular note-takers actually land

Worth being precise here, because this category moved in 2026 and a lot of published advice hasn't caught up.

Otter does nothing before a meeting. Its feature page lists 26 named features and none is a brief, a prep document or an attendee dossier (Otter). The calendar connection is a join trigger, not a context source, and no CRM or mailbox integration appears. Everything operates on a recording that already exists. Details in our Otter AI review, its pricing breakdown, and the Otter alternatives roundup.

Fathom is retrospective by design. Its Ask Fathom documentation sits under "Using Fathom After a Call" and describes finding information from meetings that already happened. Exactly one prompt in the whole documented set looks forward, "help me create an agenda for my next call", and it's something you type rather than something you receive (Fathom help). Cross-meeting history is retrievable when you go and ask for it.

Granola and Read AI both genuinely ship pre-meeting briefs now, with the gates described above. Any advice telling you Granola only records meetings is out of date.

That manual-versus-automatic distinction runs through the whole note-taker category. The context is usually retrievable. Somebody has to remember to retrieve it, at the exact moment they're least likely to.

One structural note about that discussion, which ran to 386 comments on AI note-takers: across the entire thread, nobody raises pre-meeting preparation as a use case. Every comment is about recaps, transcripts and whether the meeting should have been an email. The practitioner conversation was still framed entirely around capture.

How Kai handles pre-meeting prep

Kai is an AI executive assistant rather than a note-taker, and it sits on your calendar, your mailbox and your tasks at once. That's the structural reason it can assemble a brief from more than a transcript archive.

In practice, we opened a meeting scheduled for the next day and the brief was already written. No request, no button to click. It carried a one-line purpose for the call, a Meetings section citing a prior call by name and date ("recorded We Grow Episode 10 during How we grow on July 31, 2026"), the unresolved action items still running between the two of us, and an Emails section citing a specific thread by subject and date. Underneath, an attendees block with a per-person profile.

Two details matter against the gates above. That meeting was internal, the case Granola explicitly excludes. And a separate meeting with no email history didn't come back blank, it returned "No open email threads found" and still produced the rest. Showing nothing rather than padding is the right instinct.

The per-person profile covers the company half: role, organisation, a couple of lines of context, and links out.

The meetings overview covers the underlying capability, and the action items workflow covers how commitments get from one call into the next brief. If you'd rather the prep came to you than sat waiting in the calendar entry, meeting prep dossiers is one of the scheduled workflows you can set up, delivered the evening before or the morning of, whichever you ask for. You can also just ask, through Ask Kai, which is the manual path when you want something the brief didn't include.

Honest limitations. The attendee profile sometimes resolves to the wrong person: give it a common name and it will occasionally return the LinkedIn of someone else entirely with the same name. Funny once, annoying when you're skimming before a call. It's known and being worked on, and it's a live example of why the company half of prep is the easy half to automate and the easy half to get wrong. Kai is also in open beta and newer than the established note-takers, so if you need a proven free recorder for tomorrow's call, Fathom or Granola get you there faster. And Kai does not block prep time on your calendar for you. Nothing here does that.

When this is overkill

Three to five meetings a week, mostly internal, mostly people you know well? You don't need any of this. A glance at the invite is enough, and a system on top creates more friction than it removes.

Mostly recurring one-to-ones with the same five people? Same answer. The context lives in your head.

The break-even sits somewhere around ten to fifteen external meetings a week with a rotating cast. We should be straight that this figure comes from reading practitioner threads and talking to users rather than from our own calendar, and that nobody has measured it properly. No source in this space quantifies time spent preparing for meetings as opposed to time spent in them. The Microsoft telemetry on last-minute cramming is the closest anyone gets, and it's a proxy.

FAQs