Sales skills need to show up in the work
Sales skills help a salesperson understand a buyer’s problem, assess whether an offer fits and work through a purchase decision. A useful development plan identifies what the seller needs to do differently in a real conversation or task.
Start with an observed gap. Perhaps discovery notes contain product requests but no explanation of the customer’s problem. Or proposals omit a dependency that implementation later has to resolve. Those examples give a manager and seller something specific to practise.
Research enough to ask a relevant question
Before contacting someone, identify a plausible connection between their work and your offer. Check the facts you intend to reference. Separate public information from assumptions about the person’s priorities, budget or purchasing authority.
For practice, ask a seller to prepare one opening question from an account’s public information. Have them explain what supports the question and what they still need to learn. The exercise should reveal whether the outreach has a reason beyond the person’s job title.
Listen and confirm the problem
Discovery requires more than a list of questions. Follow the customer’s answer, ask for an example and check your understanding before moving on. Avoid treating a hesitation or facial expression as proof of an objection.
In a fictional practice conversation, a buyer says reporting takes too long. A useful follow-up is to ask which report they mean and how it is produced today. That is more informative than immediately offering a dashboard.
After the exercise, compare the seller’s notes with what the buyer actually said. Look for missing details, assumptions presented as facts and questions the seller left unanswered.
Explain the offer in terms the buyer can check
Connect a product capability to the task the customer described. Show how it would work, what it requires and where its limits are. If the requirement cannot be met, say so.
When discussing expected benefits, distinguish measured results from estimates. Ask the customer to review any assumptions used in a business case. A result from another organisation does not establish what this customer will achieve.
A practical exercise is to explain one capability using the customer’s example, then answer a question about a limitation. Review accuracy and clarity rather than rewarding the most confident delivery.
Work through concerns without arguing
A concern may expose a missing requirement, a budget limit or a poor fit. Ask what the customer means before preparing a response. A price concern, for example, could relate to affordability, competing options or uncertainty about the proposed scope.
Respond to the specific issue and check whether the answer addresses it. When the answer depends on someone else, name the question you will take away and agree when to return with a response.
Use a realistic concern in practice. The seller should be able to clarify it, answer honestly and recognise when the offer cannot resolve it. Turning every refusal into another persuasion attempt is not a useful assessment standard.
Understand who needs to be involved
Ask the customer how the purchase will be evaluated and approved. Different people may own implementation, budget or day-to-day use. Do not assume their requirements are identical.
Record which requirements are confirmed and which conversations remain outstanding. Agree introductions with the customer. Adding contacts to an opportunity does not itself establish agreement or shorten the decision process.
For a review exercise, ask the seller to explain the next decision and the evidence needed for it. Gaps in that explanation identify questions to investigate.
Follow through on commitments
Write down what was agreed, who owns each action and when an update is due. Keep customer commitments separate from internal hopes about closing dates. Update the record when circumstances change.
After the sale, hand over the agreed scope, open questions and relevant context to the receiving team. Check that someone has accepted responsibility for unresolved work.
Practise by asking a colleague to take over a fictional account using only the handover notes. The questions they still need to ask show where the record needs improvement.
Choose one skill to develop next
Use recent work to select a skill, agree an observable standard and practise it with feedback. Then review an appropriate sample of subsequent work to see whether the behaviour changed.
A seller who asks better follow-up questions may still face a delayed or lost deal. Assess the quality of the work alongside commercial outcomes, and check other explanations before attributing a result to training. Keep the next development step specific enough that the seller knows what to practise.
