Field Guide 1:3 Chapter 16 Objection Handling and Conflict Resolution

Transcript

SPEAKER_00 0:00

Chapter sixteen Objection Handling and Conflict Resolution As we wrap up chapter fifteen, you've now seen how technical close plans, proof structures, and post demo conversations all work together to drive a deal toward the finish line. You've been introduced to real world examples, actual frameworks, actual conversations, actual momentum. But as you probably know by now, momentum alone doesn't always guarantee a smooth path to closing. Sometimes even the best laid plans hit a wall. That's where we're headed next. In chapter 16, we shift focus from planning and execution to one of the most vital, yet often underdeveloped skill sets in our profession. Objection handling and conflict resolution. Now I know what you might be thinking, objections. Uh but hang with me, because the truth is, objections aren't the enemy. They're a sign of engagement, a signal that your buyer is thinking critically and how you respond, not just what you say, but how you listen, empathize, and navigate through the tension can be the difference between a stalled deal and a breakthrough moment. In this next chapter, I'll walk you through what it really means to handle objections like a professional. Not just with clever phrasing, but with intention, emotional intelligence, and a framework that actually works, because you're not just managing resistance, you're earning trust. Let's dive in. Objections are a natural part of the sales process. For many, they create stress or even frustration, but they don't have to. The best sales professionals and solution engineers recognize objections for what they are, opportunities to strengthen relationships, showcase expertise, and ultimately build trust. But let's be clear, handling objections well requires more than a set of tactics. It demands emotional intelligence, curiosity, and a genuine intent to help both sides reach common ground. One of the first things I emphasize when training teams on objection handling is that intent matters more than technique. You can use the slickest phrasing or ask all the right questions, but if your intent isn't genuine, if it doesn't serve both parties, people will see through it. On the flip side, if your intent is clear and honest, even a rough delivery can still work. You can't fake sincerity. That's why this guide will focus not just on the how, but also on the why of objection handling, drawing from real examples, personal stories, and practical frameworks like the match, understand, resolve MUR process I've trained on for years. The emotional and psychological landscape of objections. Objections don't exist in a vacuum. They're tied to emotions, experiences, and attitudes. People aren't just challenging you because they're difficult or want to waste your time. Often they're reacting to underlying fears or doubts. Will this work for me? What happens if it doesn't? Do I trust you? When you handle objections, you're not just addressing logic or data. You're addressing people's need for trust and safety. This is where understanding emotional drivers becomes critical. I've always been fascinated by how the brain processes objections. Think about it. The fight or flight response kicks in when people feel backed into a corner. Your job is to diffuse that tension, creating an environment where collaboration feels safe. The word intent comes up a lot in these conversations, and for good reason. If people perceive your intent as self-serving, their defenses will go up. But if they see that you're genuinely trying to help them solve a problem or make their life easier, they're more likely to open up. This is why empathy, not agreement, is such a critical tool. You don't have to agree with their objection, but you do need to show them that you understand it and that their concerns matter to you. Two core approaches to objections. Agree to diffuse. The simplest way to disarm an objection is to agree, not with the objection itself, but with the validity of the concern. This isn't about saying, you know, of course you're right, we're wrong. It's about acknowledging that their perspective is reasonable. When someone feels heard, they're less likely to stay defensive and the conversation becomes a lot more productive. For example, if someone says, this solution is too expensive, you might respond with, I understand why you might feel that way. Let's explore it together. That's a fair concern, and I appreciate you being honest about it. Notice how none of these responses contradict the objection. Instead, they validate it, opening the door for a more collaborative discussion. Drill down and pivot. While agreeing diffuses tension, it's not enough on its own. You need to dig deeper to uncover the root cause of the objection. This is where directional questioning comes into play. Imagine the objection is a central point, and your questions help explore it from multiple angles. To the right, you might explore goals. What could this solution help you achieve? To the left, you explore pain. What challenges are driving this concern? Moving up, you explore strategic purpose. What's the bigger picture for solving this issue? Moving down, you get into specifics. What exactly do you need to see in order to feel comfortable? This process helps you identify the real issue behind the objection, which often isn't what the person said at first. Once you have clarity, you can pivot to new information or perspectives they may not have considered. The Match Understand Resolve Framework. The Match Understand Resolve MUR process is a structured way to approach objections. It's something I've trained on extensively, and it has helped countless teams navigate difficult conversations. Match, start with empathy. Matching doesn't mean agreeing, it means showing that you understand where the other person is coming from. This is crucial because people want to feel heard, not dismissed. Imagine driving through an intersection with a yellow light. You don't speed up, you slow down to proceed cautiously. That's what matching does in a conversation. Instead of responding with logic or counterarguments right away, take a moment to empathize. That's a tough question. Let's talk it through. I hear your concern. Can you share more about that? This approach not only diffuses tension but also sets the stage for deeper exploration. Understand. Dig into the root cause. Once you've matched the objection, it's time to understand it fully. This means asking thoughtful questions to uncover the real issue. Sometimes what people say isn't the full story. For example, when someone says, We're not ready for this, they might actually mean, I'm worried I'll look bad if this doesn't work. Understanding involves both curiosity and patience. You're not just solving a problem, you're showing the other person that you care about their perspective. Resolve, collaborate on solutions. Resolution isn't about proving someone wrong, it's about finding a solution that aligns with their goals and alleviates their concerns. This often involves reframing the objection to highlight its importance or demonstrating how your solution addresses it directly. For example, let's say a sales rep insists on scheduling a demo without a discovery call. Instead of saying, how, no, that's a bad idea, you might say, I appreciate your urgency and I want to make sure we're fully prepared. Can we take a quick step back to ensure we're aligned on their needs first? This approach resolves the objection without creating conflict, keeping the focus on what's best for everyone involved. Negotiating the sales cycle, a critical skill for closing deals. Negotiating the sales cycle is a crucial phase where the technical and business sides of a deal come together. During this stage, sales engineers, SEs, and account executives, EAEs, must collaborate closely to ensure they meet the client's needs, navigate objections, and seal the deal. However, it's also a period that can make or break a deal depending on how well the teams handle the negotiation and objections raised by the client. A major part of negotiation in the sales cycle involves value-based selling and objection handling. When negotiating, you're not just pushing a product, you're positioning a solution that solves specific business problems for the client. The importance of value-based techniques lies in aligning the client's pain points and goals with the solution, ensuring that it's not just about price, but about delivering long-term value. As an SE, your job is to help the AE make sure that what's on the table isn't just the solution, but also how it ties into the client's business objectives, creating value beyond the transaction. A good negotiation strategy also means addressing objections early in the cycle. This could be related to price, fit, or even the urgency of the purchase. The typical response is to match, understand, and resolve, a framework that allows you to acknowledge concerns, understand the underlying causes, and then work towards a resolution. For example, if a customer raises an objection about the timeline for a demo, instead of immediately accepting it, ask insightful questions to understand the urgency and see if there's a way to speed up the process without compromising the quality of the solution being presented. In the book you'll find a table that breaks down common objections during the sales cycle, and more importantly, how both the sales engineer and the account executive might handle those objections in real time. Now, I want to walk you through that table because even if you're just listening, this framework can help you visualize the difference in tone, role, and responsibility between the SE and AE when navigating tough moments in a deal. Let's dive into a few examples. Objection. We need to see a demo first, but can we skip discovery? Sales engineer's response. I understand your desire for a demo. But before we present, let's ensure it's tailored to your needs. Could we spend 15 minutes discussing your most pressing requirements? Account executives response. We definitely want to show the solution in the best light. Can I ask if you've seen demos from other vendors? What did you find most valuable from those? Here, the SE focuses on customization and technical alignment, while the AE opens up a comparative value conversation. Objection This solution is too expensive. ESE, I see how the price could be a concern. What budget constraints are you working with? Let's explore how this solution can deliver ROI and impact your bottom line. AE, let's focus on the business value and outcomes this solution will bring. I'm happy to explain how we can create more value over time and reduce costs in the long run. Notice that the SE leans into cost justification and ROI while the AE pivots towards strategic positioning and long term value. Objection We're already working with another vendor. SE It's great that you found a solution that works for you. What challenges or limitations have you encountered with your current provider? AE, can you tell me what your current vendor isn't addressing that could help improve your workflows or save time? I think we can offer a better fit for your evolving needs. Both responses acknowledge the existing relationship, but the SE probes for technical gaps, while the AE explores business opportunity and differentiation. Objection We need approval from higher ups before moving forward. ESE. Of course, can we get a better understanding of what specific concerns or information would help your executives make a decision? AE, let's schedule a meeting with your decision makers. We'll prepare a tailored presentation so it's easier for them to approve this solution. The SE looks to clarify requirements while the AE works to facilitate executive alignment. Objection We're not sure if this solution fits our long-term needs. SE, can you share more about where you see your organization in two to three years? I'd love to make sure our solution can scale to meet your future requirements. AE, that's a valid point. We can adjust our implementation plan based on your evolving needs. Let's talk about your roadmap to see how we can align with that. Here, both roles are future focused, but again, the SE zooms in on technical scalability while the AE keeps the lens on strategic alignment. Objection. We don't want to waste our executives' time with a demo. ESE. I understand the concern. How about we start with a brief 30-minute overview focused on the most important areas for them and they can decide if they want to go deeper? AE. What's important is making sure your executives see how this fits into their strategy. Can we schedule a brief session with them so they can evaluate if it's worth their time? This final one shows the SE offering a lightweight, low risk option, while the AE repositions the meeting as a strategic enabler. This table exists in the book as a quick reference during workshops or team role playing exercises, but whether you're reading or just listening, the key takeaway is this. Objections are a team sport. The SE and AE don't duplicate each other, they complement each other. And the more intentional you are about your role, your tone, and your strategy in these moments, the more trust you'll build and the more deals you'll win. Key takeaways. Mastering negotiation and objection handling. Understanding client needs. Before diving into a demo or discussing pricing, always ensure that the solution is a fit for the client's business goals. Ask questions to uncover their underlying needs. Value over price. When clients raise objections about price, always focus on value-based selling. Highlight the long-term impact your solution will have on their business, not just the upfront cost. Collaboration is key. SEs and AEs need to work together closely. SEs bring technical depth, while AEs focus on the bigger picture and deal closure. Working in unison strengthens the overall sales strategy. Practice makes perfect. Role-playing scenarios like these with the AE can help SEs refine their objection handling techniques and build the confidence to handle real-world objections smoothly. Stay solution focused. Even when facing resistance, stay focused on the solution and how it benefits the client. Offer tailored solutions based on the client's specific needs, and always stay aligned with their broader business strategy. By practicing these role play scenarios, SEs and AEs can improve their ability to handle objections during the sales cycle, increasing the likelihood of successful negotiations and deal closures. The key to overcoming objections is active listening, empathy, and always working toward a win-win resolution. Workshop practicing objection handling. Objection handling is a skill best learned through practice. Here's a workshop structure you can use with your team. One, divide into groups, assign roles, sales rep, customer, and observer. Two, use real scenarios, provide objection cards, e.g., the cost is too high, and let participants role play using MUR. Third debrief, discuss what worked, what didn't, and how the process can be improved. This workshop isn't just about skill building. It's a chance to laugh, learn, and build camaraderie. Trust me, some of the objections people come up with will have you in stitches. Final thoughts. Objection handling isn't about outsmarting the other person. It's about creating a shared path forward. When you approach objections with empathy, curiosity, and a genuine desire to help, you're not just overcoming resistance, you're building relationships that last. And sometimes those relationships start with a last-minute demo request on a Monday morning. Recommended books on objection handling, negotiation, and relationship building. Here's a curated list of books that every SEAC plus T S should consider reading to deepen their understanding of objection handling, negotiation, and building trust. These books range from tactical negotiation strategies to emotional intelligence and relationship building techniques, providing a well-rounded perspective. 1. Never split the difference by Chris Voss. Summary. Voss breaks down the art of tactical empathy, active listening, and calibrated questioning, offering actionable strategies for both personal and professional negotiations. Why it's valuable. The audiobook includes real recordings of negotiations such as the Chase Manhattan Bank robbery, which add incredible depth and realism to the lessons. Voss emphasizes how small behavioral shifts can lead to outsized results, making it an essential read for anyone who deals with objections or negotiations. 2. The Challenger Sale by Matthew Dixon and Brent Adamson. Summary. This book redefines the traditional approach to sales, suggesting that the best performers are those who challenge their clients' assumptions and teach them something new. The authors provide frameworks for identifying and nurturing challenger reps who thrive by delivering insights, not just solutions. Why it's valuable. For SEAC plus T S roles, this book is particularly useful because it focuses on how to lead customers toward new ways of thinking, perfect for objection handling and reframing resistance. 3. Getting to Yes by Roger Fisher, William Urey, and Bruce Patton. Summary, this classic on negotiation introduces the concept of principal negotiation. It advocates for focusing on interests, not positions, and finding solutions that meet mutual needs. Why it's valuable? It offers practical advice on separating people from the problem, generating creative options, and focusing on objective criteria, skills essential for resolving objections collaboratively. 5. Thinking fast and slow by Daniel Kahneman. Summary, Kahneman, a Nobel Prize-winning psychologist, explores the two systems of thought. The fast, intuitive system, and the slow, deliberate one. Understanding these systems can help you better predict how people will react in objection scenarios. Why it's valuable. Objection handling often involves navigating cognitive biases and emotional responses. This book provides a deep understanding of the psychological drivers behind decision making. 5. Emotional Intelligence to Toronto by Travis Bradbury and Gene Greaves. Summary. This book provides a practical guide to understanding and improving emotional intelligence, EQ. It focuses on self-awareness, self-regulation, empathy, and relationship management. Why it's valuable. For objection handling, EQ is a superpower. Being able to read emotional cues and respond appropriately can make or break a negotiation. Drilling into never split the difference. Voss's Never Split the Difference is a standout recommendation, particularly for the SEAC plus TS audience. It provides actionable strategies that align well with objection handling, such as tactical empathy, learning to understand and validate emotions without agreeing with them. Calibrated questions, asking open-ended questions like how do you see this working? Or what's driving this concern to uncover underlying issues? The power of silence, using pauses effectively to encourage the other party to reveal more information. Mirroring and labeling, repeating keywords and summarizing emotions to build trust and draw out insights. Pro tip, listen to the audiobook. Hearing the real negotiation tapes, such as the Chase Manhattan Bank robbery, adds an immersive layer to Voss's teachings, making them even more impactful. Humorous story, the Monday Demo Request, Bank of New York Edition. This story has become a bit of folklore for those of us who were there at the time, and for good reason. It started with the now infamous Monday morning call from Mark, the sales rep I was working with on the Bank of New York account, B O N Y. For those of you who know the story, Mark calls me bright and early on Monday with his trademark energy and enthusiasm. Hey, we need to do a demo for Boney tomorrow at 3 p.m. He says, No context, no discovery call, just a straight up mandate. I pause, because in this line of work you learn to expect curveballs, but this one felt more like a fastball to the head. Now, let me just say, I loved working with Mark. He was a good guy, funny, personable, and great with clients, but Mark also had a knack for pushing the limits of what we could pull off. This was one of those moments. I started with the usual match, understand, resolve approach. First, I matched his urgency to keep things collaborative. Mark, it sounds like you're making some solid progress with Boney if they're asking for a demo already. Then I moved to understand what was really driving this request. What's pushing this timeline? Is the customer up against a decision deadline, or is this more about keeping momentum? And this is where things took a turn. Mark, bless his heart, admitted that no one at Boney had actually requested a demo. It was his idea. Tactic to get in front of them and make an impression. I remember pinching the bridge of my nose and asking, so you promised a demo to a customer who doesn't even know it's happening? Mark, ever the optimist, laughed and said, Exactly. At the time it wasn't funny, it was infuriating. We were being set up to demo a solution with no context, no discovery, and no clue what Boney even cared about. But here's the thing Mark wasn't trying to make my life harder. He genuinely believed that if we got in front of the customer, we could win them over. To resolve, I laid out a compromise. Mark, I get it. You want to make an impression, but if we do this demo blind, we're more likely to miss the mark than hit it. Let's get a quick discovery call on the calendar today. That way we can tailor the demo and actually make it meaningful. We managed to pull it off. The discovery call happened, the demo went well, and Boney became a win for us. But what makes this story stick isn't just the chaos of that Monday morning. It's the memory of Mark. Mark was one of those people who could drive you nuts one minute and have you laughing the next. Tragically, he passed away a few years ago. His LinkedIn profile is still active, a bittersweet reminder of someone who left a big impact on those of us who knew him. Our families were close. His daughter and my kids played together often, and those connections made moments like the Bony demo feel even more meaningful. Looking back, the Boney story is funny now, though it certainly wasn't at the time. It's a reminder of the human side of this work, the personalities, the relationships, and the chaos that comes with trying to make things happen. For me, it's also a tribute to Mark, a guy who believed in making things happen, even if it meant calling for a Monday morning demo. What not to do, avoiding common pitfalls in objection handling. Objection handling is as much about avoiding mistakes as it is about executing strategies. Even the most skilled SEs can fall into traps that derail conversations or sour relationships. These mistakes usually come from a place of good intentions, trying too hard to prove your expertise, rushing to defend your product, or simply being unprepared for the unexpected. Over the years I've seen, and, let's be honest, made these mistakes firsthand and the lessons learned have stuck with me. Let's dive into a few of the most common missteps and how to steer clear of them. 1. Over explaining when you should be listening. It's easy to fall into the trap of over-explaining when faced with an objection. SEs often have a wealth of technical knowledge, and when someone questions the product or raises a concern, the instinct is to explain every detail that might address it. The problem? Most objections aren't resolved with a flood of information. I'll never forget one specific meeting with a client who raised concerns about our platform's scalability. Instead of digging into the root of their concern, I jumped in with a technical deep dive on how our solution handled scaling under high workloads. I spent 10 minutes laying it out only to realize I hadn't actually addressed their underlying issue. They weren't worried about scalability itself. They were worried about whether their IT team could handle implementing the solution. I had completely missed the point because I was too focused on explaining rather than understanding. The lesson? Take the time to listen. Ask questions to uncover the true concern instead of assuming you know the answer. Most of the time, objections aren't about the technical details. They're about trust, confidence, or something personal to the customer's experience. 2. Being defensive instead of curious. Nothing shuts down a conversation faster than defensiveness. When a customer raises an objection, it's not an attack, it's an opportunity to learn. However, it's easy to take objections personally, especially if they challenge something you've worked hard to build or believe in deeply. I once sat in a meeting where a customer said, I've heard your product isn't very user friendly. Instead of acknowledging their concern, the SE in the room immediately fired back with, That's not true. Our product has a great user experience. The tone was sharp and you could see the customer bristle. The objection wasn't addressed, it was dismissed. The conversation got tense and we spent the rest of the meeting trying to recover. The right approach would have been to stay curious. I hear you. Can you share more about what you've heard or experienced? I'd like to understand your perspective. That small shift, acknowledging the concern and inviting them to elaborate, could have turned the objection into a productive dialogue rather than a standoff. Three, failing to prepare or asking for help too late. As SEs, we're often pulled into situations at the last minute. While that's unavoidable at times, failing to prepare, whether it's researching the client, aligning with the account rep, or clarifying expectations, can set you up for failure. One example that's burned into my memory comes from a last-minute demo request. The sales rep told me we'd be presenting to a key decision maker, but they hadn't shared any details about the person or their role. I showed up prepared to discuss high-level strategy, only to find out the person was a hands-on technical lead who wanted to see code samples and architecture diagrams. The meeting was a disaster. Not only was I unprepared, but the disconnect made us look uncoordinated and unprofessional. The takeaway? Always carve out time for preparation, even if it's just 15 minutes. If you don't have the information you need, push back or ask for help early. It's better to delay a demo than to show up unprepared and risk your credibility. 4. Dismissing the importance of relationships. One of the biggest mistakes SEs make is focusing too much on the technical solution and not enough on the relationship with the customer. It's easy to fall into the mindset of if the product speaks for itself, I don't need to worry about anything else. But in reality, people don't just buy solutions, they buy trust. I remember a situation with a client who had been burned by a previous vendor. They were cautious, hesitant, and frankly skeptical of everyone they worked with. Instead of acknowledging their concerns, one of my colleagues focused entirely on the technical details of our platform, trying to impress them with features and capabilities. The customer wasn't impressed. They wanted someone to listen, empathize, and rebuild their confidence in vendors. We eventually won them over, but it took months to repair the initial damage caused by dismissing the relationship piece. 5. Avoiding tough conversations. Sometimes objections require you to deliver hard truths. It's tempting to sugarcoat things or avoid certain conversations altogether, but that can lead to bigger problems down the road. Customers appreciate honesty even if it's uncomfortable in the moment. For example, I once worked with a rep who had promised a timeline that wasn't realistic. When the client asked me directly, I had a choice go along with the promise or tell the truth. I chose the latter. I want to make sure we set the right expectations. Based on our current workload, I don't believe we can meet that timeline without sacrificing quality. Let's discuss what's possible and how we can get you what you need as soon as we can. It wasn't an easy conversation, but the client appreciated the honesty. They knew we were putting their success first and that built trust in the long run. 6. Telegraphing your frustration. Objection handling requires emotional control. It's not just about what you say, but how you say it. Your body language, tone, and expressions all communicate as much as your words. If you're frustrated, impatient, or dismissive, it will come through loud and clear. I've seen SES sit through meetings with their arms crossed, rolling their eyes, every time the client brought up a concern. Even though they answered the questions, their demeanor made it clear they didn't want to be there. Unsurprisingly, the client walked away feeling disrespected. It's okay to feel frustrated, especially in chaotic situations, but don't let it show. Take a breath, reset your mindset, and focus on staying calm and collaborative. Final thought. Turning mistakes into learning opportunities. The truth is, everyone makes mistakes in objection handling. What separates great SEs from the rest is their ability to learn from those moments. The best way to avoid these pitfalls is to stay curious, empathetic, and prepared. And when you do stumble, take a step back, reflect on what went wrong, and use it to refine your approach. After all, this work isn't just about handling objections. It's about building trust and creating partnerships that last. The role of body language in objection handling. When it comes to objection handling, what you say matters, but how you say it matters even more. Body language, tone of voice, and facial expressions are silent players in every interaction. They shape how your words are received and can make the difference between building trust or creating tension. As an SE, you're often in high-stakes conversations where every subtle cue counts, so understanding and mastering body language is a critical part of your toolkit. Why body language matters? Research shows that nonverbal communication makes up a significant portion of how people interpret meaning in conversations. Customers aren't just listening to your words, they're reading your posture, gestures, and facial expressions to gauge your intent. Are you confident or uncertain? Open or defensive, engaged or bored? These unspoken signals can amplify your message or undermine it entirely. For SEs, body language is especially important because objection handling is inherently emotional. Clients may feel frustrated, skeptical, or defensive, and your ability to project calm confidence and empathy can help diffuse those emotions. Likewise, poor body language, crossed arms, fidgeting, or avoiding eye contact can unintentionally escalate the situation. Mastering positive body language. First, open posture. One of the simplest ways to convey confidence and approachability is through open body language. Keep your arms uncrossed, hands visible, and posture upright but relaxed. Avoid slouching or leaning too far back as this can signal disinterest. In one memorable meeting, a colleague of mine unintentionally crossed his arms and leaned back in his chair as the customer voiced a concern. The customer reading his posture as defensive and dismissive became visibly more agitated. After the meeting, my colleague admitted he wasn't annoyed. He was just cold, but the damage had been done. The lesson? Even unintentional body language can send the wrong message, so stay mindful of your posture. Two, eye contact. Maintaining steady eye contact shows that you're engaged and paying attention. However, there's a balance to strike. You don't want to stare someone down. Use natural breaks to shift your gaze and ensure that you're connecting with everyone in the room, not just one person. During a client workshop, I noticed that one of our team members kept looking down at their laptop during the Q and A portion. Even though they were taking notes, it gave the impression that they weren't fully present. The client later mentioned that they felt ignored, highlighting how crucial eye contact is for building trust. 3. Gestures and movement. Use gestures purposefully to emphasize key points, but avoid overdoing it. Wild hand movements can be distracting while keeping your hands in your pockets or folded can come across as stiff or disinterested. Aim for natural measured gestures that align with your tone and message. One trick I've found helpful is to mirror the client's body language subtly. If they lean forward, lean forward slightly to show engagement. If they're more reserved, dial back your gestures to match their energy. Mirroring creates a sense of connection and makes the interaction feel more collaborative. 4. Smile, but don't overdo it. A genuine smile can go a long way in making you seem approachable and confident. However, forced or excessive smiling can feel insincere, especially during serious discussions. Use your smile strategically to put people at ease without undermining the gravity of the conversation. What to avoid? 1. Fidgeting. Tapping your pen, shifting in your seat, or playing with your phone can signal nervousness or disinterest. Even small movements like clicking a pen repeatedly can distract from your message and annoy your audience. During one particularly tense negotiation, I caught myself adjusting my watch band repeatedly, and it became obvious that it was distracting the client. I quickly stopped, but it was a good reminder to stay still and focused. Second defensive posture. Crossed arms leaning away or turning your body slightly away from the client can all signal that you're closed off. Even if you're just trying to get comfortable, it can come across as unwillingness to engage. Instead, aim for a posture that's open and oriented toward the person speaking. 3. Avoiding eye contact. While you don't want to stare, avoiding eye contact entirely sends a message of discomfort or even dishonesty. If you're addressing an objection and your eyes keep darting away, the customer may feel like you're unsure of your position, or worse, hiding something. Using body language to navigate objections. When handling objections, your body language can help diffuse tension and reinforce your intent. For example, when empathizing, lean in slightly to show interest and nod to signal that you're actively listening. A subtle tilt of the head can also indicate curiosity and engagement. When clarifying, use open hand gestures to invite dialogue and create a sense of collaboration. Avoid pointing as it can come across as accusatory. When resolving, stand or sit tall to project confidence. If you're presenting a solution, use deliberate gestures to emphasize key points but keep your movements controlled. Using body language to navigate objections, the Sal at Prudential example. One of the most memorable lessons I've learned about body language came during a high stakes pitch to Sal, a key decision maker at Prudential Securities. This was a big opportunity for us, and we had spent weeks preparing the presentation. Everything was lined up, the messaging, the visuals, the technical demonstrations, but as the conversation progressed, Sal raised some concerns about the budget. At that moment, one of the SEs on our team, who was incredibly sharp and technically brilliant, leaned back in his chair, clasped his hands behind his head, and adopted a posture that could only be described as overly casual, bordering on smug. It was meant to be relaxed, but it sent the wrong message entirely. Sal stopped mid sentence, visibly taken aback. His body language shifted instantly. He leaned back in his own chair, folded his arms, and gave us a look that screamed really? It wasn't just the words that were said or unsaid, it was the unspoken cue that we weren't taking his concerns seriously. The SE's posture unintentionally communicated, we're not worried about your concerns. We've already won this deal. The meeting took a noticeable turn after that moment. Sal became less engaged, more guarded, and far less interested in collaborating. While we eventually salvaged the opportunity by revisiting his concerns in a follow-up meeting, it was clear we damaged the trust in that initial interaction. This experience has stayed with me as a reminder of how body language can shape a conversation. Even when your words are perfect, your nonverbal cues can send an entirely different message. With Sal, it wasn't arrogance or disinterest. It was a moment of unintentional miscommunication, but to him, it felt dismissive, and that was enough to derail the momentum we'd built. What we learned from Sal. After that meeting, we made a point to discuss body language as a team. The takeaway was simple. Even if you're confident or comfortable, always remain mindful of how your posture might come across. Sitting forward with an open posture, maintaining eye contact, and using deliberate but natural gestures can make all the difference. Sal, at Prudential Securities, taught us a hard lesson about trust. His concerns about budget weren't just a challenge to overcome, they were a chance to build a deeper connection. And as I've learned time and again, connection happens as much through body language as it does through words. Objection handling for software clients. Objection. Why they're saying it, how to respond. The cost is too high. They don't see the ROI yet or are comparing against cheaper solutions. I hear you. Let's break down how this aligns with your goals. What's most important to you in this investment? Would it help to see how other clients in your industry achieved ROI with this solution? We already use Competitor X. They're comfortable with their current tool or afraid of the migration process. That's great. What do you like most about Competitor X? Where do you see gaps or opportunities to improve? Sometimes we can complement existing systems or solve gaps they can't. We don't have the resources to implement this right now. They're overwhelmed or need internal buy-in for resources. I get it. Timing is everything. What would need to happen internally for this to be realistic in the future? Would it help if we shared how other teams like yours phase their implementation to avoid overwhelming their resources? This doesn't align with our priorities. They don't see how it fits into their current strategy. I understand, can you share more about your current priorities? I want to make sure this aligns with where you're headed. Are there areas where this could help free up resources for other critical priorities? I need to run this by team boss. They don't want to commit or lack decision-making authority. Of course, can we set up a quick session with them so I can address any questions directly? What's the most important thing they'll need to see to feel confident in this decision? We've tried something similar and it didn't work. They're skeptical or burned by a past implementation. I can see why that would make you cautious. What challenges did you face with the previous solution? Would it help to walk through how we've addressed similar challenges for other clients? Can we get a custom feature for X? They want something specific to their environment. That's a great idea. Let me dig into what's possible. In the meantime, how critical is this to moving forward? If we can't provide that exact feature, are there other ways we can meet the same goal? Cheat sheet. Dealing with account rep behaviors. This next section is in the book. I will review each type of rep, their behavior, and how to address that behavior. What it looks like, how to respond. The last minute hero. We need a demo tomorrow at 3 PM for a major client. No, I haven't done a discovery call yet. Match. Sounds like you've made great progress. Understand, what's driving this urgency? Resolve. Let's schedule a quick prep call today so we're fully aligned for tomorrow. The overpromiser promises features that don't exist or timelines that aren't realistic. I hear you. It's great that you want to deliver for the client. Let's align on what's truly possible so we set the right expectations. The ghost disappears after passing a deal to you, leaving you with unanswered questions and no context. Hey, I'm missing some details on this. Let's sync quickly so we can set the client up for success. When's your next availability? The lone wolf goes rogue, bypassing processes, and involves you too late. I get why you took the lead here, but let's loop in the team so we can all be aligned going forward. It'll help us cover any blind spots. The enthusiastic newbie brings boundless energy but lacks experience, resulting in unrealistic asks or confusion. I love your energy. It's great for the team. Let's walk through how we typically approach this to make sure it lands well with the client. The overly defensive representative reacts poorly to feedback or suggestions, making collaboration difficult. I respect the effort you've put into this. Can we discuss some ideas to make sure we're all set up for success? The relationship builder, to a fault, prioritizes being liked by the client over addressing tough issues, leading to unproductive cycles. You've clearly built great rapport here. Let's channel that trust into having an honest conversation about their biggest challenges, will bring even more value that way. The opportunistic salesperson jumps on trends or buzzwords even if they don't align with the client's actual needs. I see where you're going, but let's make sure this aligns with what the client is focused on right now. What's their biggest challenge and how does this tie in? We've covered a lot from real-world objection handling, technical close plans, and QBR prep to how you should think about allocating your time and adapting your approach globally. These aren't just tips, they're real tools, drawn from the field, tested across roles, teams, and territories. Whether you're an early career SEAC or a seasoned pro, the goal is the same. Become someone who can influence deals, drive clarity, and operate with precision, no matter who's in the room or what part of the world you're working in. Remember, excellence in this role isn't just about knowing your product, it's about knowing your customer, your team, your data, and yourself. So take these frameworks, print out the tables if you're following along in the book, and make them your own. Practice the objection responses. Rethink your time management. And if you find yourself selling into a new region, flip back to the global mindset section and refresh before your next call. Because mastery comes not from reading once, but from applying repeatedly. Onward to the next chapter.