6 sales skills for better customer conversations
In my own outreach, the messages that tend to start conversations are the ones where I can point to a problem I might be able to help with. The tricky part comes after someone replies. I have an idea of what might be happening, but they know how their business actually works. A good conversation helps us figure out together whether the problem is real, what it costs them and whether it’s worth solving.
Here are six skills you can practise on a discovery call, in an outreach conversation or while handling an inbound enquiry. I’ll use the same example throughout so you can see how the conversation develops.
1. Prepare before the conversation
Spend some time learning what the business sells, who it serves and how customers reach it. Pick one observation that relates to a problem you can help solve. Then separate what you saw from what you think it might mean.
| What you observed | What might be happening | What to check |
|---|---|---|
| The business takes enquiries through WhatsApp, Instagram and a website form. | When a few people share replies, it might be hard to tell who’s following up. | How does the team know who’s taking the next action on an enquiry? |
The channels are visible. How the team manages them is something you need to learn. That distinction keeps you from opening with a claim about a problem they may already have solved.
Prepare on your side too. Know what you can deliver, what it costs, what setup requires and where your offer has limits. That makes it easier to recognise a good fit and give a straight answer when someone asks what’s involved.
Practise. Before your next call, write one observation, one possible problem and two questions that would help you check it.
2. Ask questions that help the customer see what’s worth solving
Build most of your questions from the preparation in section 1. Share the observation that prompted the question so the customer knows why you’re asking. Use their answer to decide where to go next.
“I noticed customers can reach you through WhatsApp, Instagram and your website. When several people are replying, how do you know who’s taking the next step?”
If they say everyone checks a shared inbox, you might ask them to walk you through a recent enquiry that needed a follow-up. If they mention that someone has to chase the team for updates, ask what happens when that person is busy. Once you’ve heard a concrete example, help them decide how much it matters.
“If everyone could see who owed the next reply, what would that change for your team on a busy day?”
That question gives them a chance to picture a better workflow and decide whether it’s worth the effort. Keep the pace conversational. Ask one question, listen, and share back what you’re hearing before asking another. If the team already has a reliable way to handle enquiries, accept the answer and move on.
Practise. Write an opening question based on one thing you observed. During the call, build your second question from a detail the customer actually mentions.
3. Listen and check your understanding
Listen for where the process breaks down and what people do to work around it. “Follow-up is messy” could mean nobody knows who owns it, people can’t find the conversation history, or reminders get buried. Each points to a different fix.
Play back the specific situation in plain language and ask whether you understood it.
“It sounds like the first reply is usually quick. The trouble starts when someone promises to send a quote and the rest of the team can’t tell whether it went out. Have I got that right?”
Leave room for a correction. If they say the quote always goes out but nobody checks back a few days later, use that detail to change what you show them.
Practise. Before you explain your offer, summarise the problem in one sentence. Include when it happens and what the customer has to do because of it.
4. Explain value in the customer’s terms
Start with the situation they just described. Show what their team would do differently, then connect that change to an outcome they care about.
“You said your team sends quotes on time but often has to search old messages to see which customers still need a check-in. Here’s how the rep could assign a follow-up when they send the quote. The owner would see it on their due list, and the manager could see which follow-ups are still open.”
Explain what has to happen for that to work. The team might need to agree who owns a follow-up and when it’s due. Then check whether the workflow fits how they operate. If you discuss time saved or revenue impact, start with numbers the customer can verify. Ask how many quotes they send and how much time they spend checking on them. Label any estimate.
Practise. Take one feature you often explain. Rehearse a 30-second explanation that starts with the customer’s problem, describes what the team would do differently and ends with the outcome they care about.
5. Understand concerns before responding
When a customer says “That’s expensive,” pause before defending the price. They could be telling you the budget is fixed, that they’re comparing you with a cheaper tool or that they’re unsure the team would use it enough to justify the cost.
A simple question can help you find out what they mean.
“Is the price above what you’ve budgeted, or are you still weighing up what the team would get out of it?”
If they mention a cheaper option, find out what it covers and compare the parts they care about. If the concern is adoption, walk through what a typical rep would actually have to do each day. If the budget is fixed or they decide to pause, respect that and be clear about what you can deliver within their constraints.
Practise. Pick the objection you hear most often. Write down two plausible reasons behind it and one question that would help you tell them apart.
6. Agree on the next step and deliver it
Before you finish, ask what would help the customer make their next decision. A generic demo might add another meeting to the calendar. A short walkthrough of how a rep follows up on a quote could answer the question they actually have.
“I’ll send you a short walkthrough of the quote follow-up workflow by Thursday. You can share it with the reps who would use it. Would it make sense to reconnect on Monday after they’ve had a chance to look at it?”
Record the action, owner and date, plus the decision it supports. If they want to pause, agree what would make it worth revisiting. Deliver what you promised by the agreed time. If the timing changes, let them know before they have to ask.
Practise. Look at the last follow-up you sent. Could the customer tell from your message what would happen next, who was doing it and when?
A two-minute review after each conversation
- What did I assume going in? Write down what the customer confirmed or corrected.
- What did I learn? Capture one concrete example of the problem and what it costs them in time, effort or missed work, if you know.
- What did we agree? Write down the next action, who owns it and when it’s due.
- What will I practise on my next call? Choose one behaviour you can actually observe. For example, summarise the problem and invite a correction before showing the product.
Further reading
The Mom Test by Rob Fitzpatrick is a useful companion if you’re a founder doing discovery while selling your own product. It explains how to ask about what people have actually done so you can learn more from their answers.
Qonvera is a conversational sales CRM built by Aether Solutions.