A customer says, “Getting the team to use it is the hard part.” You could explain your onboarding, list features, or move to the next qualification question. A more useful response starts with the experience behind that sentence.
Discovery becomes valuable when the seller and customer build a clearer account of what is happening, why it matters, and what would make a change worthwhile. A question is useful because of the understanding it creates.
Begin with a piece of real work
Invite the customer to describe a recent example. Ask how the process works today, who takes part, and where the work becomes difficult. A specific situation is easier to explore than a broad statement such as “we need better productivity.”
Suppose a team prepares each meeting by searching old notes and checking a product document. Ask the customer to walk through the last time they did it. You can then distinguish the search problem from unclear ownership, missing information, or a process the team does not trust.
Use what you already know to make the opening relevant. A short reference to the last conversation is usually more useful than making the customer repeat their entire background.
Follow one detail before opening another topic
Choose a phrase the customer used and explore it. In the adoption example, you might ask what made the previous rollout difficult. Let the answer determine whether to discuss setup, relevance, manager support, or daily effort.
Keep your question neutral. “Which part became difficult?” leaves room for a surprising answer. A question that contains your preferred diagnosis can produce agreement without giving you much understanding.
You can keep a simple note in three parts: the customer’s example, your current interpretation, and the question still open. Keeping those separate makes it easier to correct an assumption later.
Find the consequence together
A difficult process matters because it changes something. Explore who is affected, how often it happens, what gets delayed, or which alternative the team uses. Let the buyer describe the significance in their own terms.
For an occasional inconvenience, a large rollout may be an unreasonable next step. For repeated missed handoffs, the buyer may want a more focused test. The purpose of the question is to find that difference.
Summarize your understanding and invite a correction. For example: the team can find the information, but checking it during the meeting disrupts the conversation. That is a more precise starting point than “your knowledge is scattered.”
Turn understanding into a next step
Ask what would help the customer decide what to do. It may be a demonstration of one workflow, a conversation with another stakeholder, or a small pilot with a clear question to answer.
Agree on an action, an owner, and a time. Make the next meeting depend on something useful happening between now and then. That gives the follow-up a reason to exist beyond another calendar invitation.
Keep the direction close with RevConvo
Build the opening and its useful branches into a RevConvo playbook. A concern about setup should lead to different questions from a concern about trust or cost. Keep an approved product answer connected to the moment where it becomes relevant.
Practice the uncertain turn before a customer call. During the meeting, use the written guidance as a direction while keeping your attention on the person. Afterwards, review the notes and follow-up so the customer’s actual concern carries into the next conversation.
RevConvo