How to prepare for a customer meeting using your CRM

Short answer

Preparing for a customer meeting starts with reading the last three records in your CRM and writing a single goal sentence. Check who makes the decision, whether budget has been discussed, and what you promised last time. Ten minutes of this keeps the meeting from being spent repeating what both sides already know.

What is customer meeting preparation?

Customer meeting preparation means pulling the customer's history, decision structure and open promises out of your CRM or ERP before the call, then tying all of it to one goal. It is not reading a file. It is deciding in advance what you will ask the meeting to produce.

The frame is simple: what you have (the existing record), what you give (the ten minutes you spend), what you get back (a meeting that ends with a clear next step). A rep who skips preparation saves ten minutes and loses the whole meeting.

An unprepared meeting looks the same every time. The first ten minutes go to "where did we leave off". The customer repeats what they already explained. The call ends without a next step.

Which CRM fields should you check before a meeting?

Five fields are enough. More than that turns preparation into reading, and reading into postponing.

The last two activities: what was discussed, what was sent. If your call notes are written properly, those two lines give you the whole context.
Open promises: what you committed to, what the customer committed to. An unkept promise belongs in the first sentence of the meeting.
The decision maker: is the person on the call deciding, or defending your case internally? Those are two different meetings.
Budget and timing: has a price range been discussed, and what is the customer's own calendar? If both are missing, the purpose of this meeting is to learn them.
Objection history: which concern did they raise before? Getting caught twice by the same concern costs trust.

How do you prepare in 10 minutes?

Preparation does not take long. It takes long when it has no order. This order works:

2 minutes: read the last two notes and the last email on the record.
2 minutes: write down open promises and unclosed items.
2 minutes: write the single goal of this meeting as one sentence.
3 minutes: prepare the three questions that get you to that goal.
1 minute: decide the concrete step you will ask for at the end: a second meeting, a technical review, approval on the quote.

How do you write the goal sentence?

A good goal sentence is measurable and has one part. "I will meet the customer" is not a goal. "I will find out who signs off and get one person from their technical team into the next meeting" is a goal.

Write the goal into the CRM before the meeting. Add the outcome to the same line afterwards. Over a few months this habit shows you, on its own, which kind of meeting actually moves work forward.

Which questions should you prepare?

Three questions are enough, and all three should be questions you do not already have the answer to:

What makes you look at this now? (timing)
Who else is part of this decision? (decision structure)
How do you handle this today? (the current alternative)

Asking a question whose answer is already written in the CRM is a sign of no preparation. Customers notice.

What if there is no data in the CRM?

If the record is empty you cannot prepare. That is not a discipline problem, it is a data production problem. In the short term, read the customer's recent announcements, headcount and branch structure, then write three lines yourself:

what the customer does about this today
the titles of the people joining the meeting
why this meeting is happening now

A preparation routine only holds in a team when the records are trustworthy. A CRM full of empty fields means starting research from zero before every single call.

What does an unprepared meeting cost?

Run the numbers with your own figures. Say a rep holds 8 customer meetings a week. If the first 10 minutes of each one goes to the "where were we" round, that is 80 minutes a week. Across 46 working weeks it adds up to roughly 61 hours, about 7 to 8 full working days.

In a team of five the same calculation passes 300 hours a year. That time goes to remembering meetings, not holding new ones. The gap is not laziness. It is the imbalance between what preparation costs and what it returns.

How do you make the routine stick in a team?

Left to personal discipline, the routine disappears within weeks. Three things keep it standing:

One field: add a single "meeting goal" field to the CRM. A meeting without it does not go on the calendar.
Meeting order: in the weekly sales review, discuss the goals of upcoming meetings, not just open deals.
Close the loop: write the outcome under the goal line. If a follow-up system is in place, that line triggers the next step by itself.

FAQ

How long should customer meeting preparation take?

Ten minutes is enough for a routine follow-up call. Allow 20 to 30 minutes for a first meeting or a proposal presentation, where the customer's industry and decision structure also come into play.

Do you need a CRM to prepare for meetings?

Not strictly, but the alternative is human memory. Memory leaves with the rep; records stay. The record can live in your CRM or your ERP — what matters is that it all lives in one place.

Is a meeting goal the same as a sales target?

No. A sales target is a quarterly number. A meeting goal is the step this one conversation moves the deal to. If meeting goals keep missing, the sales target will miss too.

Should the rep prepare, or an assistant?

Collecting the data can be automated; setting the goal is the rep's job. If someone else writes the goal, nobody follows it in the room.

How do you measure whether preparation works?

Watch one number: how many meetings end with a concrete next step. If that share is rising, preparation is working.

Closync AI is an AI layer that turns sales conversations into high-quality CRM/ERP data and that data into sales decisions. When the note writes itself after a call, preparing for the next one takes ten minutes.

Last updated: 21 October 2026