TheInquisitor Podcast with Marcus Cauchi

Andy Weins: How the Words Your Sales Team Uses Are Costing You Deals — and How to Fix It

Most sales leaders invest in process, technology, and training. Almost none of them invest in the one lever that silently controls all three: the language their people use — out loud and in their own heads. Andy Weins has spent 20+ years in the military as a mass resiliency trainer, built a business from scratch, and studied the neuroscience and psychology of how the words we choose wire our behaviour. In this episode, he and Marcus Cauchi go deep on the specific phrases that signal avoidance, underperformance, and self-sabotage, and the language patterns that drive ownership, execution, and results. If you lead a sales team or run a company, this is not a soft conversation about mindfulness. It is a diagnostic tool. By the end, you will recognise the exact words your team uses when they are not going to close the deal, and you will know what to replace them with. Why This Matters Every sales team has what looks like a pipeline problem, a skills problem, or a market problem. Often it is a language problem in disguise. When your salespeople say "I just wanted to follow up," they are signalling low value before they have even started. When they say "I should call that account," they are parking it indefinitely. When they say "we need more leads," they are frequently deflecting accountability for what they already have. The language your team uses in CRM notes, forecast calls, and customer conversations is data. It tells you who is owning their number and who is performing learned helplessness. This episode gives you the framework to hear that signal clearly. Key Themes and Takeaways 1. Blame, Excuse, and Denial: The Three Default Failure Modes Andy opens with a concept drawn from Brené Brown's work on shame: when there is a gap between what we want and what we have, the brain defaults to one of three responses — blame, excuse, or denial — because they require the least cognitive effort. In sales, this shows up as: Blame: "The prospect went dark." "Marketing isn't generating quality leads." "The economy is tough." Excuse: "I didn't have time to prep." "The deck wasn't ready." Denial: "I didn't really want that account anyway." The correction Andy offers is deceptively simple: ask "Where is my DNA in this?" Even if you are 1% responsible for a poor outcome, claiming that 1% shifts you from passenger to driver. For sales leaders running deal reviews, that question, where is your DNA in this?, is worth installing as a standard. 2. "Just" and "But": The Two Words That Kill Credibility Before You've Started Marcus flags two words that most people use dozens of times a day without realising their cost: "Just" — minimises what follows. "I'm just calling to check in" communicates low value, low confidence, and low intent. Andy's framing: just justifies the nonsense that's about to happen. Train your team to remove it entirely from outreach language. Not "I just wanted to reach out" — "I'm calling because..." "But" — cancels everything before it. "Great work on that proposal, but..." means the compliment is noise. Two conflicting ideas, only one of which is true: the one that comes after but . In coaching conversations with reps, this matters. In customer conversations, it is fatal. These are not stylistic preferences. They are trust and credibility signals that prospects and internal stakeholders pick up subconsciously. 3. The Difference Between a Desire and an Expectation — and Why It Determines Whether You Hit Target Andy draws a sharp distinction that has direct application to how sales leaders manage their teams and how salespeople manage their customers: An expectation is what you want from someone else. It sets you up for resentment, conflict, and passivity — because other people are not here to meet your expectations. A desire is what you want. It is owned. It creates agency, because the question that follows is what are you willing to do to get it? In sales management, the difference sounds like this: Expectation: "My reps should

Listen