Sales pain points are problems the customer wants to address. They may involve cost, delays, missed work or an experience that is difficult for staff or customers. Your job in discovery is to understand the problem and its importance, then check whether your offer can help.
A complaint is a starting point. It does not establish the cause, the cost or a commitment to change. Ask for a recent example before turning it into a business case.
Start with the customer’s account
Ask what happened, who was involved and what the customer had to do as a result. A question such as “Can you walk me through the last time this happened?” often produces more useful detail than asking whether a process is inefficient.
Next, check how often it happens and whether the example is typical. Find out who experiences the problem and who is responsible for deciding what to do about it. Those may be different people.
Avoid supplying the answer in the question. “How much revenue are you losing?” assumes a loss before the customer has established one. Start by asking about the consequences, then examine any numbers they provide.
Use other evidence to investigate sales pain points
Read feedback in context
Surveys, reviews and support requests can reveal recurring questions. Read the explanation behind a rating, and check when the feedback was collected. A low score may concern one interaction rather than the whole service.
Public reviews of a competitor can suggest something to ask about. They are not proof that your prospect has the same problem.
Ask colleagues what they have observed
Sales, support and delivery teams may hold different parts of the story. Ask for specific cases and separate what the customer said from a colleague’s interpretation.
If several people report the same issue, check whether they are describing independent cases or repeating one customer’s account.
Observe the work
Where the customer agrees, ask them to show the current process. Look for repeated entry, unclear ownership and steps that require someone to chase information.
Usage data can show where an activity stops, but it may not explain why. Ask the customer to interpret the pattern before recommending a change.
Work through a concrete example
Consider a fictional sales team that says quote preparation is too slow. In discovery, the manager explains that a representative waits for approval whenever a non-standard discount is requested.
The delay could come from unclear discount rules, missing information or an approver who is unavailable. Buying a quoting tool would not necessarily resolve all three.
The salesperson asks for a recent quote, maps the approval steps with the manager and checks how long each took. They also ask which delays affected a customer decision. That evidence helps define the problem before discussing a solution.
Agree what makes the problem worth solving
Ask how the customer handles the issue today and what happens if they make no change. A workaround may be adequate, even if it is inconvenient. Other priorities may also take precedence.
When estimating an impact, record the source and assumptions. For a time-saving estimate, distinguish elapsed waiting time from staff time spent working. Do not present hours saved as cash savings unless the customer can explain how the saving would occur.
Then agree what a useful improvement would look like and how it could be checked. Keep the customer’s desired outcome separate from what your product has demonstrated.
Record the problem without exaggerating it
In the customer record, note the example, the people affected and the evidence still needed. Preserve uncertainty. “The manager estimates a weekly delay” is different from “the process causes a weekly delay.”
Link this work to your pipeline review. A problem statement should help the team decide what to investigate next, whether the offer fits and whether the customer wants to proceed.
