Bigmind

Build your pipeline

A closer look at the cold call

Watch Cognism’s Rate My Cold Call with Morgan J Ingram and guest Brian LaManna, with practical takeaways for your next conversation.

Cold call takeaways

Editorial summary of Brian LaManna’s discussion with Morgan J Ingram. Timestamps link to the original episode.

1:02 — Establish context before asking permission

Confirm the recipient’s name, introduce yourself and your company, then ask permission to continue. Confident delivery matters more than a clever time limit.

5:01 — Avoid an interrogation

One relevance-checking question can help. Repeated technical questions before explaining why you called create confusion. Connect the problem to value, then invite a response.

7:32 — Bring a role-specific hypothesis

Without deep research, start with a likely priority for that buyer’s role and ask whether another priority matters more.

9:08 — Budget ownership is not the whole story

A relevant contact can still evaluate value. Explore previous evaluations and participants before redirecting immediately to the budget owner.

10:34 — Diagnose objections first

Acknowledge the concern, briefly reflect it back, and let the buyer explain. Adapt the meeting request after understanding the constraint.

13:09 — Recognize genuine disqualification

Persistence should account for concrete barriers, including incompatible technology or long contractual commitments.

14:22 — Learn by skill

Identify strong colleagues separately for discovery, prospecting, and negotiation; study each person’s strongest practice.

Practice: separate a brush-off from a real constraint

This is an original Bigmind exercise. A buyer says that they have no budget and already use another supplier. Write down three things you still do not know: whether the current approach meets their needs, who evaluates improvements, and when a change could reasonably be considered. You do not need to ask every question immediately. Choose one that fits the conversation and listen for whether the answer reveals an actual business issue or confirms that there is no useful opportunity.

Keep an objection log that improves judgment

Capture the objection in the buyer’s words, your response, and the information learned afterward. Avoid recording only whether you secured a meeting. Two calls can end without meetings for very different reasons: one buyer may have a binding contract and no unmet need, while another may need to involve an operations colleague before discussing a problem. Reviewing those differences helps a team improve qualification and avoid rewarding persistence when it adds no value.

Choose one experiment for the next call block

Select a narrow behavior you can observe, such as stating the relevant context before asking a question. Practice it with a teammate, then use it where appropriate in real conversations. Review a few examples together and ask whether the buyer understood the purpose of the call sooner. Keep the parts that worked and revise the rest. A small, specific experiment makes coaching more actionable than trying to rebuild the entire call at once.

Zet het in de library van je team, waar elke agent het vindt, en maak er je eigen kopie van.

Vorm
Video
Lengte
17 min watch
Status
Free
Thema
cold callingprospectingoutboundpermission based openervalue propositionobjection handlingbudget objections

Meer zoals dit