Skip to content
Back to blog
Meetings4 min read

A meeting brief isn't something you write 20 minutes before the call

A useful brief doesn't summarise the account. It answers why the meeting exists, which threads are open and what happens next. Prep with context, not five tabs.

By lapersona team

Twenty minutes before a 9am call

The rep opens the CRM, the inbox, LinkedIn, the proposal folder and the Slack thread. They look for what was said last time, who was in the room, what's still pending and why this account agreed to meet. They have twenty minutes. They find half of it and rebuild the other half from memory.

The meeting happens. It doesn't necessarily go badly. It goes with a question that wasn't asked, a promise nobody remembered, and a next step decided at the end, in a hurry, by two people already thinking about their next appointment.

The problem isn't a lack of information. The information exists, it's scattered, and it arrives late. A brief written twenty minutes before the call isn't a brief. It's a search with a deadline.

What a rep needs to know before walking in

They don't need a summary of everything that has happened at the account. They need three things, and they need them together.

  • Why there's a meeting now. What changed, what pain has been identified, what led this person to accept the conversation.
  • What's still open. What was promised, which objection went unanswered, who's missing from the table, what was said about the competition.
  • What comes next. Which next step makes sense to propose, and who should take it.

Everything else is useful context, but it isn't the brief. The brief is the part that changes what happens in the meeting.

How to prepare a sales meeting with account context

Walk in knowing three things: why this account is meeting now, which threads were left open in the last interaction, and which next step you're going to propose. That brief is built from the account's history and signals, not from the last twenty minutes of memory.

Last-minute prep fails for reasons discipline can't fix

Three things break, and none of them is solved by trying harder.

Memory is the first. When you prep at the last minute, you remember the most recent and the most striking, not the most important. The objection from three weeks ago disappears. Yesterday's email takes up all the space.

Scattered information is the second. It lives in the CRM, in email, on LinkedIn, in the recording of the last call and in the head of whoever used to own the account. Opening five tabs isn't preparing. It's searching.

The third is that the brief gets written for the meeting, not for after it. When the meeting ends, nobody turns it into the starting point for the next one. Preparation becomes a heroic act repeated every time, instead of a process that accumulates.

Three questions behind a useful brief

Why

The why is what triggered the meeting. It isn't "we want to sell them X". It's the specific reason this account decided to talk now: a stated need, a change in their business, a signal the team picked up. Without that why, the meeting turns into a presentation and the rep turns into one more vendor.

What's open

Open threads are the commitments, objections and people still in play. They include what the customer asked and didn't get answered, what the rep promised and didn't deliver, and what changed in the decision map. A brief that ignores this forces you to improvise on ground you've already covered.

What's next

The next step isn't "follow up". It's a concrete action with an owner and a reason: send the value case, talk to the technical lead, propose a trial, agree on scope. The brief should arrive at the meeting with a proposed next step, not wait for one to appear.

Preparing without opening five tabs

Preparation can be executed. The system connects the CRM, email, LinkedIn, Slack and the enrichment tools the team already uses. It reads the account's history, identifies what's still open and builds the brief with the why, the threads and the next step. The rep gets it before walking in, reviews it and corrects it.

That's what the lapersona meeting brief does: not a summary of the account, but the prep work done before the meeting. The source is verifiable at https://lapersona.ai/en: the brief builds the why, the open threads and the next step. The rep still decides. The system stops asking them to rebuild the story from zero.

The practical difference looks small and isn't: you walk in knowing what to ask, what not to promise again, and what to propose at the end.

The brief feeds the next play

The brief shouldn't end when the meeting starts. What's discussed, agreed and avoided has to go back into the system. When it does, the next prep starts where the last one ended: the why gets updated, threads close or open, the next step changes hands.

The CRM stores the history. The tools supply the context. lapersona runs the prep and logs the outcome so the next meeting doesn't start from a blank page.

The 9am meeting starts the same way for everyone. What differs is whether the rep walks in knowing what to ask, or finds out during the call.

See how it works → https://lapersona.ai/en#how

Create account → https://app.lapersona.ai/register

Next step

Want to see it on your CRM?

Tell us how your team works and we will show you what lapersona would execute in the first conversation.

Create account

Book a demo

Let's talk.

Leave your email and we'll write to you to find a time.

By sending, you accept our privacy policy.