An objection is often a request for evidence. Before rehearsing, collect the product facts you can stand behind: current capability, price terms, implementation requirements and a customer-approved example, if one exists. Keep planned features and assumptions separate.

Build a three-branch response#

For “Your implementation sounds slow,” first ask what deadline matters. Then explain the actual implementation steps and a realistic timeline only if your team has verified one. Finally, agree on the evidence the buyer needs to proceed. If no dependable timeline exists, offer to confirm it rather than guessing.

For “We already use another tool,” ask which job that tool performs well and where the workflow still costs time. Demonstrate a specific difference using your approved facts; do not claim the competitor lacks a feature without checking.

Practice and inspect#

Run a discovery call roleplay, let the objection interrupt you and respond in two or three turns. Mark each claim as supported by the brief, needing verification or unnecessary. Rehearse the supported version again. The sales-call assistant can use a project and chosen sources as context; see the Pro terms for server coaching and practice. Never place confidential client material in a project without authority to use it.

An objection card you can reuse#

Write the buyer’s objection, your clarifying question, the approved fact you can answer with, the evidence you can show and the next step requiring agreement. For a timing objection, an unknown delivery date belongs in the next-step field, not in the answer. Repeat the roleplay after changing only the weak response.