Meeting prep for a small firm: a one-page brief where every line has a source

Good meeting prep for a client call is a one-page brief of seven lines: the goal, who is in the room, the last contact, what was decided and what is still open in both directions, the documents either side sent, the deal status and up to three questions. Each line needs a named source. A line with no source stays empty. Microsoft's own Copilot feature for this, Prepare for this meeting, only appears for meetings with at least three participants and related content to summarize, so a two-person client call may never get it.
If you own a firm of 10 to 40 people and take several outside calls a week, you rarely skip meeting prep on purpose. The context sits in five places: the invite, the last email thread, the CRM, a shared document and whatever was promised on the last call. Building the brief by hand from five tabs takes long enough that it gets dropped on the busy days, and you walk in without last time's promise. The payoff of the method below is a brief that is waiting in Slack the afternoon before, with a source on every line you can check in seconds.
What goes in meeting prep for a client call?
Seven lines, in this order, with an owner and a source for each. The table shows where each line comes from and what to do when it comes back empty.
| Line | Where it comes from | Who writes it | What an empty line means |
|---|---|---|---|
| 1. Goal of the call | Your own sentence, plus the agenda the guest wrote in the invite, if any | You | You have not decided what you want. Prepare by hand. |
| 2. Who is in the room, and their role | Calendar event guests and description; the contact and company record in the CRM | Agent drafts from the sources | The role is unknown. Ask on the call; do not guess a title. |
| 3. Last contact, with date and link | The latest Gmail thread with each guest | Agent drafts | No email found. Check Slack and your own notes before you say there was no contact. |
| 4. Decided and still open, in both directions | The transcript of the last call if one exists, the last email thread, CRM notes | Agent drafts, you confirm | Nobody recorded it. Ask the guest to confirm it in the first minute. |
| 5. Documents either side sent | Files attached to the event, a linked Drive file, email attachments | Agent drafts | Nothing was shared. Normal for a first call. |
| 6. Deal or ticket status | The deal or ticket in HubSpot or Pipedrive | Agent drafts | No record, or the CRM is not connected. A record last touched months ago deserves a question. |
| 7. Up to three questions | A fact or a gap in lines 2 to 6 | Agent proposes, you pick | A question for each empty line above. |
The shape is not new. Supernormal's prep sheet lists the goal, the desired outcome, the top two questions, attendees and roles, the last decision with a link and the risks, and suggests sending a pre-read about 24 hours ahead. What it leaves open is the gathering: it tells you to search your email, calendar notes, Slack or project docs, and does not say who does that or what to do when the search finds nothing.
Try Kipwise Agent free in Slack: mention it once in a thread and it does the repetitive work, with your permissions.
Why does every line need a source?
A brief without sources is a confident summary you cannot check, so a wrong line goes straight into what you tell the client. Danetsoft's one-page account brief is written for a sales call, but its rule travels: an empty source cell means the claim stays out of the brief, and any responsibility the page does not state goes into the brief as a question.
Give every line of the brief a named source and let a line with no source stay empty, because an empty line is a question to ask on the call and never a fact to state. This is a recommendation, not an industry standard, and it changes what you do on the call. A brief that says "Dana owns the budget" with no source makes you say it out loud. A brief that shows line 2 empty for Dana makes you ask, "Which part of this do you oversee?" The first is a risk and the second reads as interest.
An empty line also shows what to fix. If line 4 comes back empty for three calls in a row, nobody is writing down what was decided, and no brief can find a decision that was never recorded.
Why do most meeting prep checklists fail a small firm?
They describe the steps and skip the gathering. YouCanBookMe's guide lists client history and previous meeting notes among the materials to collect and tells first meetings to start 24 to 48 hours ahead, but not how a person with no assistant gets that history in front of them. Scribbl's eight-step checklist spends its steps on the decision, the invite list, the agenda and the technology, and says nothing about pulling context from email or a CRM.
Two reasons explain the gap. The checklist author does not know where your context lives. Yours is a Google Calendar, a Gmail inbox, HubSpot or Pipedrive and a Drive folder, and the first job is mapping each field to one of them, which is what the table above does. And gathering is the slow part. A Hacker News thread asking why the industry builds transcript tools when the real problem is bad meeting prep includes a commenter who says people excuse skipped pre-reads by saying their schedule is too full of meetings. That is one commenter's report, but it fits the pattern: prep that depends on free time fails when the calendar is full.
The usual fix is to hire a coordinator or a virtual assistant to build the brief. That works, and for a firm with a dozen calls a day it may be the right answer. For four to eight calls a week, the question is whether the gathering can be done for you in the tools you already have, with you keeping the two lines only you can write.
How do you get the brief in Slack the afternoon before?
Each person who takes outside calls sets up their own brief once, in a Slack thread, with the Kipwise agent. The steps:
- Connect your own accounts. Connect your Google Calendar and Gmail, and if the firm uses them, Google Drive and HubSpot or Pipedrive. Each service uses your own access, so the agent can read only what you can open.
- Ask once, in a channel thread or a direct chat. For example: "Every weekday at 4 pm, list tomorrow's meetings on my calendar that have guests from outside our domain, and post a draft brief for each in this thread. Use seven lines: goal (leave blank for me), who is in the room, last contact with date and link, decided and still open in both directions, documents, deal status, up to three questions. If you could not source a line, leave it empty and tell me what you did not read."
- Approve once. Creating a scheduled request needs one Approve on the card in the thread. Later runs do not ask again.
- Read the brief the afternoon before. For each meeting the agent reads the event with its guests, description and attachments, searches your Gmail for the latest thread with each guest, opens the attached or linked file in Drive, looks up the guest and any open deal in the CRM, and reads the last call's transcript when one exists.
- Reply in the same thread. Write the one-sentence goal yourself, then ask follow-ups such as "what did we promise on pricing?". Plain replies in the thread continue the work without another mention.
- Keep the client out of it. The brief goes to you. A CRM note, a draft email or a calendar change after the call is a separate request with its own Approve card, and the agent does not invite other people to an event unless you explicitly ask.
Here is a made-up example of what lands in the thread for a call with a fictional client, Harbor Lane Studio. Every name and date is invented.
Tomorrow 10:00, Harbor Lane Studio (2 guests)
1. Goal: [yours to write]
2. In the room: Priya Nair, operations lead (CRM contact record); Tom Eddy, role not found
3. Last contact: 11 Nov, thread "Revised scope" (link)
4. Decided: ship the phase-two plan by 28 Nov. Open: they owe us access to the analytics account; we owe them the revised quote. Source: 11 Nov thread, CRM note
5. Documents: scope-v3.pdf attached to the invite
6. Deal: "Phase two", stage proposal sent (CRM)
7. Questions: Who signs off on phase two? What should Tom's role be on this project?
Not read: no transcript found for the 4 Nov call.Tom's role came back empty. The agent is built to say when it has not read something rather than guess, so line 2 turns into question 7.
Set the brief up per person, not per firm
Set the brief up per person and not per firm, because the agent reads only the calendar of the person who connected it. An owner who has an assistant cannot have that assistant run the owner's brief through the assistant's own account: the calendar the agent reads is the one that was connected. Each person who takes calls connects their own Calendar and Gmail and asks for their own brief. For a 10 to 40 person firm that is a few minutes per person, and it keeps one person's inbox out of another person's brief.
What about a call booked at the last minute or on nobody's calendar?
A call booked yesterday through a booking page can start its own brief. Ask in a thread: "Whenever someone books a meeting with me, send me a brief here." The agent then posts the title, time, guests and what the booker wrote each time a new meeting with a guest lands on your calendar, including a booking on your Google appointment page. Calendly and Cal.com have the same kind of trigger. That is a lighter brief than the seven lines, built from the booking alone. Ask for the full seven lines in the same thread when you have a minute.
Limits to plan around: a change to a meeting, a cancellation, or a meeting made days ago starts nothing. A call that is on nobody's calendar can still be asked for by the guest's name in the thread, for example "brief me on Priya Nair before our call at 3." It will use whatever mail, files and CRM records exist for her.
On timing, YouCanBookMe suggests at least 15 to 20 minutes for a same-day meeting. A brief that is waiting when the meeting lands on the calendar turns that time into reading.
Which meetings should you still prepare by hand?
Prepare by hand the call where you cannot state the outcome you want in one sentence that matches last time's, and let the brief cover the rest. The test comes from hirekai.ai's guide to AI meeting prep, a vendor's blog: if you can describe the outcome in one sentence and it is the same sentence as last time, a brief covers you; if you would struggle to write that sentence, block real time and think. Treat it here as a recommendation, not a measured rule.
For a small firm the hand-prepared calls are the ones with money or a decision on the line: a renewal, a scope change, an awkward conversation about a missed deadline. The brief can still hand you the thread, the promise and the numbers, so your hour goes to the strategy and not the searching. Line 1 stays yours in every case, because the goal is the one line no source can supply.
What can go wrong, and how do you know the brief is right?
Four things can go wrong, and each has a check.
- No transcript. Line 4 depends on a transcript only if the host turned transcription on before the call. Google's Meet help says transcripts need a Workspace edition that supports them, such as Business Standard, and are saved in the meeting organizer's Drive. In Zoom, the host has to turn on the transcript before the meeting. If none exists, the agent says so and the brief falls back to the last email thread and CRM notes. For the after-call side, see Google Meet notes for a small team.
- A stale CRM. Line 6 is only as current as the last person who updated the deal. Check the "last updated" date and treat anything older than the last email thread as a question.
- The wrong thread. A guest with two projects has two threads. The brief links the thread it used; open it once on your first week to confirm it is the right one.
- Permissions. The agent reads only what your own account can open. A file a colleague owns and has not shared shows up as not read, not as a guess.
To verify the setup, run a one-week pilot. For each outside call that week, open the sources behind lines 3, 4 and 6 and check them against the brief. Count how many lines came back empty and why. If the same line is empty every time, fix the habit behind it: write the decision into the CRM, or turn on transcription. After the call, a "did anything surprise me that the brief should have caught?" note tells you which source is missing.
If a client review is on the calendar, the longer pre-read is a different job, covered in the quarterly business review for a small firm. For your own team's meetings, see the weekly meeting agenda for a small team.
What to do next
Pick tomorrow's first outside call and fill in the seven lines by hand once, writing the source beside each. The lines you cannot source are the ones a brief would have left empty, and the ones that cost you the most time are the ones to automate first. If the gathering is the slow part, connect your own Google Calendar and Gmail to the Kipwise agent and ask for tomorrow's brief in a thread. Pricing is $10 per user per month with a minimum of 3 users, and the install trial is $2 for 7 days, or $10 for 14 days with a saved card or a paid Slack plan, enough to test it on a week of calls.



