Skip to content
All insights
Tool · Sales

How to Automate Meeting Prep for a Sales Team

At one firm, meeting prep meant going through the calendars one at a time and making notes on a legal pad. The agent that replaced it is not clever. The hard part is agreeing what goes on the one page, and where that page has to land.

· 5 min read

Patrick Laughlin, Founder, Chief AI Officer

Naval Academy, class of 2011. Decorated naval aviator, 10+ years. President, 2023 Inc. 5000 company.

At a retirement planning firm, this is how a client meeting got prepared before an agent did it. Someone went through the advisors' calendars one at a time, made notes on a legal pad, and the notes were printed and left on a desk. The advisor read them in the few minutes before the client walked in.

The prep itself was good. It was also one person's morning, every morning.

To automate meeting prep, run one job early each morning that reads the next forty-eight hours of meetings out of the CRM, pulls each account's history, and writes a short brief into the calendar invite and onto the meeting record. Nobody has to open anything new. The prep arrives in the place they were already going to look.

That is the shape we have now built three times: for the retirement planning firm, for a licensed apparel company whose reps get briefs written into their calendar events, and as part of the advisor portal at a national wealth management firm with several hundred advisors.

What goes on the one page

The brief earns its place by being short enough to read standing up. Five things, in this order, and the order matters because the first two are what a person checks in the hallway.

  1. Who the account is and who is in the room. Everyone on the invite, their role, and which of them you have met before.
  2. What they have bought, this year and across the whole relationship. At the apparel company that is lifetime and year-to-date spend, pulled from the CRM rather than remembered.
  3. What is open right now. Orders in flight, anything that shipped late, anything they asked for that nobody has answered.
  4. The last conversation, in three lines. From the record, not from recollection, so it is right even when the person covering the meeting is not the person who had that call.
  5. One thing to confirm in the meeting. A single named next step beats a page of context, because context without a next step becomes reading rather than preparation.

Then leave out everything that cannot change what somebody says in the next hour. No sentiment score. No model commentary on the account. No summary of a summary. A brief is easy to overfill, and an overfilled one gets read in week one and skipped by week three. The test I use now is whether it fits on a phone screen, because that is where it gets read, in a parking lot, five minutes out.

Where the brief has to land

The brief goes where the meeting already lives. That is the whole design decision, and it is worth more than anything in the prompt.

At the retirement planning firm the agent sends each advisor one email early in the morning covering their next two days, and writes the same brief as a note on the meeting record in the CRM. Two destinations, on purpose. The email is what gets read. The note is what makes the prep part of the account history, so the next person who opens that record sees what was known going in.

At the apparel company the brief is written into the calendar event itself. A rep opens tomorrow's invite, which they were going to open anyway, and the brief is sitting inside it.

What we do not do is give it a screen of its own. A tool with its own login has to be visited, and that decision is where adoption dies. We learned that the expensive way, with the build at that same company nobody opened.

When it runs, and what happens when a meeting moves

Run it early, and look further ahead than you think you need to.

Forty-eight hours of lookahead rather than twenty-four, for two reasons. Meetings get booked late in the day, so a one-day window misses exactly the meeting that was added at five o'clock. And a brief that lands the night before gets read on the commute, which is free attention you do not otherwise get.

Three rules we build to, all of them because a calendar is a moving target.

Rewrite, never append. Calendars move constantly. If the job adds a brief instead of replacing the one it wrote yesterday, by Thursday the invite holds three of them and the rep reads the stalest one at the top.

Match on the meeting, not the time. A brief attached to a slot is wrong the moment the meeting slides an hour. A brief attached to the meeting record follows it.

Give the user a refresh. Something lands on an account at nine for a ten o'clock call, and the only thing worse than no brief is a confident one that predates what everybody is about to discuss. That is the same argument as picking a sync interval from the person waiting on the number.

What I have not measured, and the page to write this week

I do not have a timed before-and-after for a meeting-prep brief, and I am not going to borrow one.

At the wealth management firm, pre-meeting and post-meeting agents are part of the advisor portal that went to advisors as an MVP in mid-September, and the pilot asks each tester two questions about one real client meeting: how many minutes preparation took in the new portal against their normal route, and how many separate systems they avoided opening. That is the measurement that would settle it, and the pilot plan explains why those questions were written before anyone got access.

Until it reports, I can tell you exactly what a brief contains and where it lands, and not what it saves. A number like that has to come from the person who used to do the prep by hand, taken before the hand version stops happening, and that window closes faster than anyone expects.

So take your first external meeting tomorrow and spend ten minutes writing the brief you wish had arrived for it. One page, by hand, the five items above.

Then write down what you had to open to produce it. The CRM, an inbox, probably a spreadsheet somebody maintains. Two or three systems, and a person who knows where each of them hides the answer.

That list is the build. The page you just wrote is the specification, and it is a better one than you would have got from a requirements meeting, because you wrote it while you needed it.

Tell us what you want to get done.

A first conversation with a Chief AI Officer about your goals and what you need, whether that is a build, training, change management or expert advice. We shape the engagement around your answer.

A developer at work on a build