Give the buyer a clear reason for the call
A sales call pitch should explain who you are, why the conversation may be relevant and what you want to establish. Use the buyer’s response to decide whether to continue. A call structure helps preparation; it does not guarantee interest or a next meeting.
Distinguish a first introduction from a call the buyer has already agreed to. In an arranged meeting, confirm the purpose and available time. In an unexpected call, identify yourself and give the person room to decline.
Prepare a reason, not an assumed problem
Review relevant account information and decide what you need to ask. A public announcement can provide context, but it does not establish how the company operates or which problems it wants to solve.
For example, a new office announcement may justify asking how requests are coordinated across locations. It does not justify claiming that the company has lost control of approvals.
Keep preparation proportionate. You need enough context to explain relevance and avoid obvious mistakes, not a speculative account of the buyer’s motives.
A fictional opening
“I’m Alex from a workflow software company. We provide a shared queue for tracking approval requests. I saw your announcement about the new office and wondered whether coordinating requests across locations is something your team handles. Is this relevant to your role?”
This is fictional wording for an imaginary offer, not a claim about The Sales Arc’s products or a real customer. Adapt the details to facts you can support.
If the person says the subject is irrelevant, acknowledge that. If it is relevant but the timing is poor, ask whether they want another way to review the information. Do not treat politeness as permission for repeated contact.
Ask about the situation before proposing a change
When the buyer chooses to continue, ask a question that helps assess fit. “How do you track requests today?” allows an answer that may differ from your expectations.
Follow the answer. Ask which part is difficult, what effect it has and whether the team wants to change it. Avoid supplying a cost or consequence the buyer has not confirmed.
A process that differs from your preferred approach is not automatically a problem. The buyer may already have a suitable system or another priority.
Explain only the relevant capability
Connect the offer to what the buyer described. In the fictional workflow example, a shared queue might make ownership visible. Explain what information it needs and what work the customer would still perform.
Do not promise numerical savings or a return on investment without a basis. If a benefit depends on the customer’s workload or systems, identify what needs checking.
A short explanation followed by a relevant question is often enough to establish whether a deeper discussion would be useful. You do not need to present every feature on the first call.
Answer price questions directly
If a buyer asks about price, provide the confirmed price or range you are authorised to share, with its scope and assumptions. If pricing requires further information, explain what is missing and why it matters.
Do not withhold an available price simply to force a longer discovery conversation. An early affordability check can prevent both sides investing time in an unsuitable option.
A quoted range is not a final proposal. Make any differences in term, quantity, setup or optional services clear enough for the buyer to interpret it.
Clarify concerns without treating them as buying signals
An objection may indicate interest, a genuine mismatch or a wish to end the conversation. Ask for clarification when appropriate rather than assuming it proves engagement.
If the buyer already uses another product, ask what prompted them to consider a discussion, if anything. Do not invent shortcomings in the existing system. If there is no reason to change, record that outcome accurately.
Tone or hesitation can prompt a check, but neither reliably reveals hidden motives. Give the person space to explain in their own words.
Agree a next step only when it has a purpose
A further meeting should resolve something specific: a requirement, a technical question or a comparison of options. Explain that purpose and ask whether it would be useful.
If the buyer agrees, confirm participants, timing and any preparation. If they request information instead, send the relevant material rather than assuming they accepted a demo.
Summarise open questions and commitments in your notes. Keep a suggested action separate from one the customer actually agreed to take.
Review the call for learning
Afterwards, ask whether the reason for calling was relevant, which assumptions changed and whether the next action matches the conversation. Use approved records or practice exercises when discussing the call with a manager.
The coaching guide explains how to work on a specific behaviour. Avoid judging a call only by whether it produced another meeting.
Keep the pitch accurate and responsive
Use a structure that helps you explain the offer and listen to the answer. Revise the conversation when new information changes its relevance.
A useful call may lead to a next step, reveal missing information or establish that the offer is not a fit. Record the outcome honestly and follow through on what was agreed.
