Train on common objection patterns

Do not write objections from memory. Pull them from three places:

• Call recordings and transcripts from tools such as Gong, Chorus or Fireflies.ai. Search for phrases like "too expensive", "not right now" and "we already use".
• The lost reason field on deals in your CRM, such as HubSpot.
• Your reps. Ask each one for the two objections that annoy them most.

How to find good calls is covered in Review call recordings monthly. Aim for 30 to 50 examples before you group anything.

Sort the examples into a handful of themes. These five cover most B2B situations:

1. Price: "That is more than we planned."
2. Timing: "Come back next quarter."
3. Authority: "I need to check with my boss."
4. Risk and trust: "How do I know this works for us?"
5. Status quo and competitors: "We already have something."

Add a sixth if your data demands it, such as "we can build this ourselves". Count how often each theme appears. Start your training with the top two.

Use the same format every time, so reps can find answers quickly:

• The objection as customers actually say it, word for word.
• What it usually means, such as "I do not see the value yet" behind a price objection.
• A clarifying question to ask first.
• A short response, in plain language the rep can say out loud.
• A proof point, such as a customer story or number you can share.
• The next step to propose.

Keep entries short. If a response takes longer than thirty seconds to say, it is a speech, and no one will use it. The principles for answering on a call are in Handle objections in discovery, so keep this library to patterns and wording.

Put the library in a shared document in Notion or Google Docs, with a page per theme. Link it from your CRM and your team chat. If a rep needs more than two clicks during prep, they will not use it.

Hold a thirty minute session at the same time every week. A simple format:

1. Pick one theme and read two real examples from recordings.
2. Split into pairs. One plays the buyer, using the exact wording from the example. The other responds.
3. Swap roles and use a second example.
4. Come back together. Ask each pair what worked and what felt awkward.
5. Update the library entry with the improved wording.

Keep the tone light. The goal is practice, not a test. Rotate who goes first, and let the most senior person play the buyer sometimes.

After each role play, the buyer rates three points: did the rep ask a clarifying question before answering, did they address the real concern, and did they propose a next step? Yes or no for each. Tracking this for a month shows where the team is consistently weak.

Every month, add new objections from the latest calls and retire entries nobody has heard in a quarter. Mark the responses that worked in real calls, based on deals that moved forward. Remove those that were followed by dead conversations.

• Building the library from what you think buyers say instead of real calls.
• Writing long, polished scripts that sound unnatural.
• Practising once, then never again.
• Giving only the best rep a voice in the answers.
• Treating objections as attacks instead of information about what the buyer needs.

New reps can answer the top five objections within their first month. Calls where an objection is raised still move to a next step more often than before. In your recordings, you hear reps ask a clarifying question first. The library is updated every month and people actually open it.