Use case · AI sales meeting prep

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

AI sales meeting prep is a briefing that arrives before a customer meeting without anyone asking for it. It covers where the deal stands, who is in the room, what has already been said, and what the meeting needs to accomplish. Ollie is the AI sales co-worker that delivers it before every deal meeting. Minutes after the meeting ends, the follow-up work is already moving.

Karri Takki
by Karri Takki, Growth Marketing Lead @ Optivian
withOllie, AI Sales Co-Worker @ Optivian
Delivered inSlackMicrosoft Teams
Walk into every deal meeting prepared · Book a demo

The definition

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, 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.

The stakes

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, and reps remain the most important source at three 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.

Before the meeting

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.

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

Ollie delivers a meeting briefing in Slack the afternoon before an early call: where the deal stands, who is in the room including a CFO joining for the first time and what each person has said, what was agreed and is still owed, and what the meeting needs to accomplish Ollie  ·  Direct messageOllieAPP3:40 PMSarah, tomorrow’s 8:30 with Northwind is the CFO meeting.Daniel Okafor joins for the first time, and he signs the budget.Marcus has carried this internally since the demo. Tomorrow he needs Daniel’s backing to take the business case to the board.Meeting prep: Northwind Logistics, Thursday 8:30Where the deal standsProposal, €120k, close date Oct 31. Technical evaluation signed off Jun 27. Steering committee approval is the open milestoneand Marcus owns it. Nothing has moved in twelve days; Marcus is waiting for Daniel’s backing.Who is in the roomMarcus Webb, VP Operations, champion. His words: “we lose two days a month to manual reporting.” He has told his teama decision comes by September.Priya Sharma, IT. Security review complete. Asked twice about data residency; answered in writing on Aug 14, not yet acknowledged.first meetingDaniel Okafor, CFO. No contact with us yet. Per Marcus (Aug 12 call): signed off the last two platform purchaseson a twelve-month ROI. Expect the question: what happens if adoption stalls.Agreed last timeYou owed Marcus the integration timeline. Sent Tuesday; he replied it covers Priya’s concern. He also asked for helpwith the business case for the board.What this meeting needsOpen by asking Daniel what a good outcome looks like for him by year end; get his criteria in his words. Agree what the businesscase for the board has to show. Confirm the board date. Leave with a named owner for the commercial review.

After the meeting

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, 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 will send a reminder to the rep.

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, 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.

Minutes after a deal meeting, Ollie posts the notes to the deal and CRM, names who owes what, adds the new stakeholder to the deal, attaches three drafts (the business case, the follow-up email, and the intro to the new stakeholder), and asks whether to move the close date in HubSpot Ollie  ·  Direct messageOllieAPP9:21 AMSarah, notes from the Northwind 8:30 are on the deal and in HubSpot.Daniel’s line: he needs ROI inside twelve months, and the budget goes to the September board. He asked Marcus to bring thebusiness case to that board.The business case is drafted below, built around Daniel’s twelve-month ROI. Share it with Marcus.Marcus is confirming the board date. Priya is sending the integration checklist to Daniel’s team.Daniel named Lena Vogt, Head of Procurement, to run the commercial review. She’s on the deal now. Your intro to her is drafted below.Business case: Northwind Logistics, draft for your reviewPrepared for Daniel Okafor  ·  twelve-month ROI  ·  September boardFollow-up email: Northwind Logistics, draft for your review“Marcus, Daniel, Priya, thank you for this morning. Three things we agreed…”Intro to Lena Vogt, Head of Procurement, draft for your review“Hi Lena, Daniel mentioned you’ll be running the commercial review on…”One thing to change in HubSpot: the decision is at the September board, so the close date should move to Sep 26. Shall I update it?HubSpot suggestionsClose date   Oct 31 → Sep 26

From the first call

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, so 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.

The mechanism

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, 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.

Customer story · Supermetrics

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 hire, 96% of the team was active weekly, 48 of 50 sellers within 30 days of the global launch. That is adoption shelfware never gets.

What we really want is an assistant that works with the reps and prompts them on the right next steps, based on research, data, and actual results, rather than the reps having to prompt the AI engine. That is what is really attractive about what Optivian have done with Ollie.
Ed Barrett, Chief Sales Officer, Supermetrics

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

FAQ

Common questions about sales meeting prep

Four things: where the deal stands (stage, momentum, open commitments), who is in the room (each stakeholder’s role and what they have said so far), what was agreed last time, and what this meeting needs to accomplish, with the talking points to get there.
If no open deal matches the meeting, Ollie proposes one for the rep to confirm, with the company, the attendees as contacts, and the meeting attached, in the right pipeline and stage, with a close date read from the timing the buyer discussed. The summary is written to the new record, qualification is read from what the buyer said, the next steps are captured with owners, and the follow-up email is drafted. From the second meeting on, a briefing arrives before each one.
Within minutes of a recorded deal meeting ending: the summary is written to the deal and lands in your CRM as a note, every agreed next step is captured with an owner and a due date, and if the conversation moved the deal’s stage, amount, or close date, the deal owner gets the proposed changes to approve with one tap. The follow-up email is drafted from what was said, waiting for the rep to edit and send.
A note-taker such as Fireflies or Otter has done its job when the transcript and summary exist. That is where this starts. What was said in the meeting becomes part of what Ollie knows about the deal, and that becomes work: the next meeting’s prep, the updated deal record, the drafted follow-up. The recap is not the work. It is the raw material. More on that boundary: from recording to executing.
Yes, with one condition: the AI has to know the deal. A generalist AI can format an agenda from whatever you paste into it. Prep that changes the meeting comes from the deal’s own history, every conversation, every email, every commitment, which is exactly what Optivian keeps current and what Ollie’s briefings are drafted from. Everything Ollie knows about the deal is open to the AI your team already runs, so an assistant that knows the deal is possible too; a co-worker that brings the briefing before you ask is the difference.
Yes. If your transcripts sync to Salesforce or HubSpot, Optivian imports them and puts them through the same understanding as its own recordings: the summary, the qualification read from what the buyer said, the deal context. Optivian also records natively, so teams consolidating their stack can drop a separate recorder when they are ready, on their own schedule.
No. The draft goes to the rep who owns the deal, in Slack or Teams. The rep reviews, edits, and sends it as their own. The same rule holds everywhere: Ollie drafts the work, proposes the changes, and a human colleague makes the call. Nothing Ollie writes reaches your customer without a human colleague choosing to send it.

Watch Ollie work a deal

Book a 30-minute demo. The video shows how Ollie works with a rep through a whole deal. The demo shows what it looks like with Ollie working in your team: the prep before a meeting, the follow-up after it, how setup works, where the work shows up, and what gets written to your CRM.