“It costs too much.” “We tried something like this.” “The team will not use another tool.” These sentences sound like closing arguments, but they may be the opening to a more useful conversation.
Before reaching for a response, find out what the customer is protecting: money, time, credibility, implementation effort, or attention. The right next question depends on that concern.
Give the concern room to become specific
Acknowledge what you heard and invite an example. If the buyer mentions a failed rollout, ask what happened in the daily workflow. If they question the investment, explore what they are comparing it with and what outcome would justify a change.
Stay neutral. A customer who says “the team will not use it” may be describing a real operational constraint. Treating the statement as resistance to overcome can hide the information you need to judge whether your product fits.
Separate price from value and priority
A price concern can mean several things: the funds are unavailable, the benefit is unclear, another project matters more, or the proposed scope is larger than the need. Those situations call for different next actions.
Work through the uncertainty with the buyer. If the outcome is unclear, return to the work they want to change. If the scope is too broad, consider a smaller test. If the timing does not fit, agree what would make the conversation relevant later.
Use approved information when explaining what the product does and what the pilot includes. A reassuring statement that cannot be supported creates a harder objection when the customer discovers the difference.
Explore the experience behind adoption concerns
Ask which part of using another tool feels difficult. Is it setup, training, attention during the call, or work afterwards? Understand who would need to change a habit and how that change would be supported.
A focused RevConvo demonstration can then answer a real question: how the seller prepares, when assistance starts, what written guidance looks like, and how suggested updates are reviewed. Show the relevant workflow instead of trying to cover every feature.
Practice the branch before the meeting
Build common concerns into a branching playbook. A budget question should lead to a different exploration from an implementation concern. Keep a path for discovering that the product is not the right next investment.
Use RevConvo practice to try a skeptical customer situation. Review whether the seller understood the concern and checked their interpretation. A polished rebuttal is less useful than a response that helps both people make a better decision.
Agree on evidence that would help
Ask what the customer would need to see before taking another step. It might be a workflow test with one seller, a review of a source document, or a conversation with the person who would own the rollout.
Record the action and the open concern together. RevConvo helps carry that context into reviewed notes and follow-up, so the next conversation starts with the question that mattered rather than a generic reminder to reconnect.
RevConvo