Your prep arrives before the meeting. The follow-up starts before you’re back at your desk.

What is AI sales meeting prep?

Sales meeting prep is the work of walking into a customer meeting knowing the deal: who you are meeting, what they care about, what was agreed last time, and what this conversation has to do to move forward. When done well, it takes into account everything that has happened earlier (the emails, the earlier calls, the CRM record, and the commitments both sides made).

That is exactly why it rarely happens. Doing prep well means rereading a deal’s whole history, and no rep has that time between back-to-back calls. So prep gets compressed into a few minutes of tab-switching, saved for the biggest meetings, or skipped. The meeting is where deals move, and reps routinely walk into it cold, then walk out of it into admin.

AI sales meeting prep is the same work, with the reading done for you. The briefing arrives before the meeting on its own, drafted from the deal’s history instead of whatever the rep had time to reread. How 50 sellers run Ollie in every meeting.

Buyers come to reps to validate. That happens in the meetings.

In Gartner’s 2026 survey of 645 B2B buyers, 45% used generative AI to research vendors and products, yet 69% still prefer to validate what the AI told them with a sales rep. Reps remain the most important source at 3 moments: when the buyer is working out the business problem, when they are securing internal support, and when they are finalizing the purchase.

Those moments are meetings, and every buyer knows the one where they had to repeat what they said last time. Gartner’s own conclusion for sales leaders is that sellers “need to show up differently.” Good preparation is how.

With Ollie, the briefing finds you, not the other way around

Before each deal meeting, Ollie delivers a briefing in Slack or Teams: where the deal stands, the stakeholders in the room and what each has said so far, the open next steps from earlier conversations, and talking points for what this meeting needs to accomplish. That is meeting prep with Ollie, on every deal meeting rather than only the biggest ones.

Ollie times the briefing so you can actually read it: it arrives during working hours and outside other meetings. If the meeting starts within 30 minutes, it comes regardless, because late preparation beats no preparation. And if tomorrow’s first meeting starts before 9, your prep arrives the afternoon before.

Example: the briefing the afternoon before an early call

An example of what arrives in Slack at 3:40 PM, for an 8:30 meeting the next morning:

1. The headline. Tomorrow’s 8:30 is the CFO meeting. The CFO joins for the first time and signs the budget. Your champion has carried the deal internally since the demo, and tomorrow needs the CFO’s backing to take the business case to the board.
2. Where the deal stands. Proposal, €120k, close date Oct 31. Technical evaluation signed off Jun 27. Steering committee approval is the open milestone, and your champion owns it. Nothing has moved in 12 days; your champion is waiting for the CFO’s backing.
3. Who is in the room. Your champion, VP Operations, in their words: “we lose two days a month to manual reporting.” They have told their team a decision comes by September. Your IT contact: security review complete, asked twice about data residency, answered in writing on Aug 14, not yet acknowledged. The CFO, first meeting: no contact with you yet, and according to your champion signed off the last 2 platform purchases on a 12-month ROI. Expect the question: what happens if adoption stalls.
4. Agreed last time. You owed your champion the integration timeline. Sent Tuesday; the reply says it covers your IT contact’s concern. Your champion also asked for help with the business case for the board.
5. What this meeting needs. Open by asking the CFO what a good outcome looks like by year end, and get their criteria in their words. Agree what the business case for the board has to show. Confirm the board date. Leave with a named owner for the commercial review.

The recap is not the work.

For a long time, the recap barely existed. A few lines the rep typed into the CRM at the end of the day, if at all. Then note-takers made it automatic, and every meeting produces a summary. That is what showed the summary was never the work. A note nobody reads is not follow-up; it is filing. What moves the deal is what the recap merely describes: the next steps someone owns, the deal record that tells the truth again, and the email the buyer is waiting for.

Minutes after a deal meeting ends, that work exists:

The summary lands where the deal lives

Ollie writes what was discussed and decided to the deal, and to your CRM, so the record reflects the meeting without anyone typing it up.

Every agreed next step is captured with an owner

The commitments made in the room come out of the room: each one on the rep’s list, linked to the deal, with who owns it and when it is due. When a next step gets done, it is ticked off automatically. When it doesn’t, Ollie sends the rep a reminder. That is sales follow-up tracking, running across every open deal at once.

The deal record catches up to the conversation

When the meeting moved the deal (a new close date, a changed amount, a stage that no longer matches reality), Ollie sends the deal owner a message in Slack or Teams listing each change, from and to, with the reason drawn from the conversation. One tap applies it to the CRM.

The follow-up email is already drafted

Ollie drafts it from the whole deal, not just from the meeting: what was said in the room, what was promised before it, and where the deal stands now. It covers the recap the buyer needs, the agreed next steps, and the answers still owed. The draft arrives alongside the summary, in Slack or Teams, without anyone asking for it. The rep edits and sends.

Example: minutes after the same meeting

An example of what Ollie posts at 9:21 AM, after the 8:30 with the CFO:

1. The notes. On the deal and in HubSpot. The CFO’s line: ROI inside 12 months, and the budget goes to the September board. The CFO asked your champion to bring the business case to that board.
2. Who owes what. Your champion is confirming the board date. Your IT contact is sending the integration checklist to the CFO’s team.
3. The new stakeholder. The CFO named the head of procurement to run the commercial review. They are on the deal now.
4. 3 drafts for your review. The business case, built around the CFO’s 12-month ROI, to share with your champion. The follow-up email: “Thank you for this morning. Three things we agreed…” And your intro to the head of procurement.
5. 1 change in HubSpot. The decision is at the September board, so the close date should move from Oct 31 to Sep 26. Ollie asks before updating it.

Every meeting after the first knows more

Each briefing is drafted from a longer history than the last, so the meetings that decide the deal, the ones Gartner’s buyers named, are the ones where prep is richest. It starts with the call that creates the deal.

The discovery call

When a first call with a new prospect ends, and no open deal matches it, Ollie proposes creating the deal (the company, the people who were in the room as contacts, the meeting attached) for the rep to confirm, in the right pipeline and stage, with a close date read from the timing the buyer discussed. Everything above then lands on the new deal.

The demo

The briefing carries the pains the buyer named, who in the room hasn’t seen the product yet, and the competitor they mentioned, with what has worked against them in deals like this one. The demo answers their questions instead of following a script, and the demo follow-up email answers what was asked.

The new stakeholder

Mid-deal, the rep meets someone who has only heard about them second-hand: an economic buyer, a technical evaluator, the executive sponsor. Here the briefing is about people: the stakeholder dynamics, who has said what and where the champion stands, and the decision criteria as the buyer stated them. And when a new name comes up in the meeting, they are on the deal with a role and researched before the rep has typed anything, and the intro to them is drafted in the rep’s own writing style.

The commercial meeting

Pricing, procurement, the paper process. The briefing carries what has already been agreed on terms, what the buyer’s process requires, the objections already answered, and the date the buyer is working to, so nothing already agreed gets renegotiated by a stakeholder who arrived late.

Where does the prep come from?

Ollie delivers the briefing. The understanding underneath it comes from Optivian, the deal intelligence layer Ollie is built on. Optivian reads every deal interaction (the emails, the calls, the meetings, and the CRM record) and keeps what it knows about each deal current. That is why the briefing reflects Tuesday’s email and not last month’s notes.

Meetings are read the same way. Optivian records and transcribes deal meetings natively. Teams already running Gong or Fireflies keep them; Optivian reads those transcripts too. Either way, what the buyer actually said becomes part of what Ollie knows about the deal, with qualification read from buyer-side statements, not from your team’s own optimism.

Every earlier answer to this problem assumed the rep would come and get the help. An assistant waits to be asked. A recap waits to be read. A co-worker notices what the meeting needs, and what it changed, before you ask.

That is what makes Ollie an AI sales co-worker, not an assistant: the meeting is covered on both sides without the rep requesting anything, in the places the rep already works.

How 50 sellers at Supermetrics work with Ollie

At Supermetrics, Ollie works across 50 sellers in EMEA, the Americas, and JAPAC, and the meeting rhythm runs as the case study describes it: a briefing in Slack with the deal context and stakeholder dynamics before the call, a summary with next steps already waiting after it, and the CRM updated. After the rollout, 96% of the team was active weekly, 48 of 50 sellers within 30 days of the global launch. That is adoption shelfware never gets.

The behavior Supermetrics’ CSO describes, prompting the rep instead of waiting to be prompted, is the difference between an assistant and a co-worker. Read the full Supermetrics case study.

Related: how Ollie notices the deals going quiet, how managers find where the pipeline stalls, and how the mutual action plan your champion carries gets drafted from what Ollie knows about the deal. To see the briefing and the follow-up on your own deals, explore meeting prep.