What questions should engineers ask in a sales conversation?

Key facts

• Most engineers go into sales conversations ready to talk. The ones who win go in as the empty vessel, genuinely seeking to understand everything about the buyer’s situation, and what’s most likely to move that client forwards, before they say a word about their solution.
• You listen your way to a sale. The buyer is constantly revealing cards about what they value, what they fear, who else matters in the decision, and where the budget sits. Your questions are how you get them to play those cards. Ask the right questions, and your buyers will reveal to you what will enable a ‘yes’.
• Discovery is not just the salesperson finding out facts about the buyer. Discovery is also about the buyer discovering compelling reasons to buy from you. That changes every question you plan to ask.
• Value is in the eye of the beholder. Until the buyer has articulated in their own words where they see the value, you have not established value at all. The right questions get you there. A pitch never does.
• A free 3-minute starting point is the Revenue Generator Score – link below, which reveals where your sales approach is breaking down and the single area to fix first.

What is the purpose of questions in a sales conversation for an engineer?

The purpose is not to gather information so you can build a better proposal. That is only part of it. The deeper purpose is to switch on the buying drivers in the customer and create buying tension at the right moments. You are probing for what matters to this specific buyer, what a good outcome looks like to them personally, and what it costs them to do nothing. When you ask the right questions in the right sequence, the buyer starts to feel the gap between where they are and where they want to be. That feeling is what moves them forward. You are not selling to your buyer. You are selling with your buyer, and questions are the mechanism that makes that possible.

What types of questions should engineers actually ask?

Start with situation questions that map the buyer’s current world. Not a checklist, genuine curiosity about their context. Then move to questions that expose the problem and its consequences. What happens if this does not get resolved? What has it already cost? Then go deeper into what good looks like. What would success mean to this person, not just the project? Then ask questions about the decision. Who else is involved? What needs to be true for them to move forward? These are not scripts. They are categories. Go in as the empty vessel seeking to understand everything about your prospective buyer’s situation, what is important to them, what is valuable to them, how decisions get made. Your questions should reflect that intent honestly.

How do engineers prepare the right questions before a meeting?

Most people do not take the time to prepare. We know that is way more than half the battle. Before the meeting, write down ten things you genuinely want or need to know about this buyer’s situation in order to understand whether and how you can help them. Not ten things about your solution. Ten things about their world. Commit to getting answers to all ten. After the meeting, ask yourself whether you could answer each one clearly. If you cannot, you did not listen hard enough or ask the right questions. This exercise alone sharpens both the questions and the listening. It also stops engineers walking in with a pitch already loaded. What questions would reveal information that tells you if this buyer is in a strong position to buy?

How do engineers ask difficult or challenging questions without damaging the relationship?

With some learnable ‘conversational jiu-jitsu’ you can pretty much say anything, comfortably. Even something awkward, frank, or challenging, It’s about framing it correctly, once you have rapport and trust. Buyers then respect you even more for it. Lead with your intent to understand fully and help them make the best decision. Then ask the hard question from that place. Buyers respond well to engineers who ask direct questions about budget, timeline, risk, and decision-making because most people in front of them avoid those questions entirely. When you ask them respectfully, you signal that you are a trusted advisor, not a vendor tiptoeing around the truth. Engineers who learn this move find that the conversations they dreaded become the ones that close deals.

What questions help engineers understand what the buyer actually values?

Value is in the eye of the beholder. You cannot assume you know what this buyer values based on what the last buyer valued, or based on what you think is impressive about your solution. The questions that surface real value sound like these: What does a successful outcome look like for you personally? What would change inside the business if this problem were solved? What has already been tried and why did it fall short? What would make you confident you had chosen the right partner? When you ask these questions and listen hard, the buyer tells you exactly where the value sits for them. Then your job is to align everything you say and propose to those specific words. Not to your brochure or the way you do things – to their words, and the way they do things.

What is the difference between asking questions to qualify and asking questions to help the buyer buy?

Qualification questions are about you. Can we win this? Is there budget? Is it worth our time? Are they right for us? Those are legitimate internal questions, but if the buyer hears that agenda, trust drops. Questions that help the buyer buy are about them. They help the buyer determine if you are right for them. They are structured so that the buyer, in answering them honestly, starts to clarify their own thinking, feel the weight of the problem, and see the path forward. Discovery is about the buyer discovering compelling reasons to buy from you. That is a completely different orientation from running a qualification checklist. Both matter. But the sequence and the spirit are everything. Lead with genuine curiosity about the buyer’s world, and the qualification intelligence follows naturally from what they reveal.

Do better questions mean asking more of them?

No. The engineers who struggle most in sales conversations often ask too many questions in a row, turning the meeting into an interrogation. The misconception is that more questions equals more information equals better outcomes. What actually matters is the quality and sequence of the questions, and what you do with the answers. Most engineers go into a meeting preparing what they want to say. Flip it. Prepare what you want to learn. Then ask one question, listen properly, summarise back what you heard in the buyer’s own words, and ask a follow-up that shows you understood. That is how you listen your way to a sale. Three good questions asked with genuine curiosity and sharp listening will do more commercial work than twenty questions fired off a list. The buyer does not want to be interviewed. They want to feel understood.

Is your team asking the right questions in client conversations?

Three signals worth checking. First, after a client meeting, can your engineer tell you in the buyer’s own words what the buyer said they valued, feared, and needed? If the answer is vague or technical rather than commercial and personal, the questions were not deep enough. Second, do your proposals reflect the specific language the buyer used in the meeting, or do they read like a standard capability document? Proposals that echo the buyer’s words back to them come from engineers who asked and listened well. Third, does your team end every client conversation with a specific next step owned by both sides? If meetings regularly end with a friendly handshake and a vague follow-up, the questions that create buying tension were never asked. These three checks reveal more about question quality than any post-meeting debrief.