Prepare your technical team for client meetings by setting the expectation that they’re going in to listen and learn from, and about their clients. Tell them they’re the ’empty vessel’ on all the things that matter most at this stage, and their only job is to fill up on all they can that’s relevant about the customer – why they wanted to talk, what’s going on, pains, pressures, frustrations, what opportunities they face, what their colleagues and boss think about the situation, what they want to happen, what risks they see and don’t yet see, what their number one buying driver is, and other buying drivers. Come back with that intel and you’ll have all you need. Get your questions written down and clear, and so that they feel good to ask. Most people don’t take the time to prepare. That’s way more than half the battle.
Key facts
- Most technical teams prepare for client meetings by loading up on product knowledge and slides. That’s the wrong direction. Preparation means understanding the buyer’s world deeply enough to ask the questions that switch on their buying drivers, not rehearsing your own pitch.
- 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. Good pre-meeting preparation is about designing the questions that get them to play those cards.
- A technical engineer at Vinci Energies (one of our clients) used a paint-by-numbers approach we taught them to prepare for their commercial conversations. One team turned a casual nuclear-sector account into a multi-million-pound strategic partner. Director Andrew Hunter called it ‘adding sales skills by stealth’. The engineers didn’t feel they were doing sales. They thought they were just having better conversations.
- Value is in the eye of the beholder. You cannot know what the buyer values before the meeting. So your job in preparation is not to build the case for your solution. It’s to build the questions that help the buyer articulate their own value in their own words.
- A free starting point is the HPB Sales Tool below, which helps you structure your thinking before a client meeting, qualify the opportunity clearly, and see your fastest path to technical sales growth.
What should my team actually do before a client meeting to prepare properly?
Start with the buyer, not your solution. Before the meeting, your team should research the client’s business, their market pressures, and any recent news that shapes their priorities. Then write down the specific questions they genuinely need answered to understand whether and how you can help. Not questions to fill a template. Questions they actually want the answers to. Send those questions to your manager or team lead before you walk in. Knowing you’ll be asked what you learned when you come out is one of the most powerful preparation tools there is. It sharpens focus before the meeting and sharpens listening during it. Preparation is not rehearsing your pitch. It’s getting ready to go in as the empty vessel, seeking to understand everything about the buyer’s situation, what’s important to them, what’s valuable to them, and how decisions get made.
How do we define what a good outcome for the meeting looks like before we walk in?
Agree it as a team before anyone leaves the office. A good meeting outcome is not ‘they liked us’. It’s a specific next step, owned by someone, with a date attached. Work backwards from that. What would the buyer need to tell you, feel, and believe for that next step to be natural? What questions get you there? What do you need to understand about their situation, their priorities, and their buying process to make the next step feel obvious to them? When your team walks into a meeting knowing the specific outcome they’re working towards, the whole dynamic changes. They stop performing and start listening. Discovery sharpens. The conversation has a direction. And when you get to the end of the meeting, you know whether you’ve done your job.
How do I stop my engineers going into meetings and immediately talking about the solution?
Build the habit of going in as the empty vessel. Two ears, one mouth comes to mind! The instinct to lead with the solution comes from a good place. Engineers are proud of what they do and they want to help. But switching straight into solution mode before you understand the buyer’s world is the single fastest way to lose their trust. They don’t feel heard. They feel processed. The preparation fix is structural. Before the meeting, ask your engineers to write down ten things they’d genuinely like to know about the client’s situation. Not facts to gather for a proposal. Genuine curiosity. When they arrive at the meeting with real questions they want answered, the conversation naturally starts in the right place. They ask. The buyer talks. Discovery begins. That’s how you listen your way to a sale, and it starts the night before, not in the meeting room.
Should we prepare differently depending on whether it’s a first meeting or a follow-up?
Yes, and the distinction matters. In a first meeting, your preparation is entirely about the buyer’s world. Who are they? What pressures are they under? What does a successful outcome look like to them? You have no right to present solutions yet. Your job is to earn the right to make intelligent suggestions by first understanding their situation fully. In a follow-up, you have intel. Use it. Review what they told you last time. What did they say they valued? What concerns did they raise? What was left unanswered? Your preparation should connect directly to what you learned before. When the buyer sees you’ve listened and remembered, trust builds fast. When they see you’re starting fresh as if the last conversation never happened, it destroys it. Every meeting builds on the last one if you’ve prepared to make it do so.
How do we make sure the whole team that attends the meeting is aligned before they walk in?
Run a short pre-meeting briefing, even ten minutes. Agree who leads the conversation, who asks which types of questions, and who listens and notes. Technical people in client meetings often talk over each other, or worse, undermine each other by contradicting a point mid-flow. That’s a trust killer. Agree the objectives for the meeting as a group. Agree the key questions you want answered. Agree how you’ll handle it if the conversation heads somewhere unexpected. The first rule of sales club is: everyone lifts. That applies in the meeting room too. Everyone in that room is contributing to the buyer’s experience, whether they’re speaking or not. A quiet person who’s clearly paying attention and taking notes sends a powerful signal. A distracted person on their phone sends another.
What’s the simplest structure or tool we can give our team to prepare consistently?
Give them a paint-by-numbers framework they can follow before every meeting. Not a script. A structure. What do we know about this buyer? What do we still need to find out? What are the three or four questions we must get answers to? What outcome are we aiming for by the end of this meeting? What’s the specific next step we’ll propose? That’s it. Five prompts. Ten minutes. Done consistently, it transforms how your team shows up. The HPB Sales Tool (free) linked below is a free starting point that helps you and your team think through exactly this kind of preparation before a client meeting, and it will show you your fastest path to technical sales growth. Most people don’t take the time to prepare. We know that’s way more than half the battle anyway.
Isn’t thorough product knowledge the best way to prepare for a client meeting?
This is the most common mistake technical teams make. They spend their preparation time loading up on product specs, case studies, and slide decks. Then they walk into the meeting, feel confident, and spend the first thirty minutes talking about their solution to a buyer who hasn’t yet told them what they actually need. Product knowledge matters. But it is not preparation for a client meeting. It’s background. Real preparation is about the buyer: their world, their pressures, their goals, the questions you need to ask, and the outcome you’re working towards. Go in as the empty vessel seeking to understand everything about the buyer’s situation. What’s important to them, what’s valuable to them, how decisions get made. Value is in the eye of the beholder, and you cannot know what that is until the buyer tells you. Preparing your solution before you’ve understood their problem is getting it exactly backwards.
Three signs your team isn’t preparing for client meetings properly
First, your team comes out of meetings with good feelings but vague next steps. If ‘they seemed interested’ is the debrief, the meeting had no clear objective going in and no agreed outcome coming out. Second, your engineers can tell you everything about the solution they presented but struggle to recall exactly what the buyer said their three biggest priorities were. That’s a sign they went in to talk, not to listen. Third, every client meeting follows roughly the same shape, regardless of what stage the relationship is at or what you already know about the buyer. If first meetings and follow-up meetings look identical, your team isn’t building on what they’ve learned. They’re starting from scratch each time, which means trust compounds slowly and deals take longer than they should.