[00:00:00]
Bram Lagrou: welcome back to yet another episode of the Commercial Leader podcast. My name is Bram Lagrou. Let's unpack today the idea of Psychological Bid Engineering. It's about winning the head as well as the gut. Now, let me ask you before we dive in. When you design a structure as an engineer, how many failure modes do you check against before you sign off on it?
Now, you don't test it against one lead case and call it done. You test it against every condition it'll actually face. Things like wind, fatigue, the edge case. That's just what rigorous engineering is about.
So here's the question that I actually want you sitting with today. How many failure modes does your last tender submission get checked against before it goes out the door? Now, for most technical bid teams, [00:01:00] the honest answer is one. Is it accurate? Is every spec right? Every number checked? Every claim defensible? That's it. One load case on a document that's failing consistently in ways your engineering never would because nobody ever designed it to carry the other loads it's actually going to face.
A fast-moving decision maker who wants the outcome, not the method, or an operations lead who's quietly terrified of what this does to their next quarter, or a relationship driven stakeholder who's never going to trust a document that reads like a specification sheet no matter how correct it is.
That's what we're getting into today. Not a critique of technical rigor. I'm about to spend the next 18 minutes or so telling you how good yours actually is. This is more about the other half of the [00:02:00] design brief nobody hands your bid team, and that is called the human one. Now a quick word on where this is coming from. 16 years working as a management consultant on sales and business development effectiveness in the room with commercial and technical teams across 25 countries to date and counting. A master's degree in psychology behind that. So what I'm about to talk you through isn't just a hunch, it's a methodology called Communication Mastery, or CM as I like to reference it, and I license it to corporate clients as consulting, training, and coaching, and we also have a network of licensed partners that helps to deliver it.
Now, a good chunk of that work has been inside engineering and technical organizations specifically, which is exactly where this episode comes from.
Here's the thing that I want you to say plainly before I go any further, because I know exactly who's listening [00:03:00] to this episode. Your technical rigor is not the problem. It's the reason your organization is in the room first of all. Nobody wins a tender with a beautiful document and a broken solution underneath it.
But what I'm about to show you isn't a replacement for that rigor. It's the other half of it. The half that decides whether that rigor you've already got actually gets seen, understood, and trusted by the people that will be signing the cheque.
Here's a concept that I would like to share with you. Every bid evaluation produces two kinds of yes, and you need both of them, not just one. There's the yes that comes from the spec sheet. It's called the logical yes. The numbers stack up, the methodology's sound, the risk's been managed, the technical evaluator can defend this choice to their own boss based on the facts.
That's the yes [00:04:00] engineering-led bid teams are extremely good at earning. It's what you were trained for. It's what you've been promoted for, and you should never, ever stop earning that.
Then there's also the yes that comes from the gut, the emotional yes. "This team gets it. I trust these people. I can already picture working with them for the next three years to come without dreading a single steering committee meeting." Now, that yes has nothing to do with the spec. It comes from whether the document and most importantly, the people behind it make the stakeholder feel understood.
Now, here's the uncomfortable bit. A buying committee doesn't actually split neatly into logical people and emotional people. The same procurement lead who needs the spec defensible on paper also needs to feel in their gut that this is the safe choice.
Every single [00:05:00] person on that panel is running both calculations whether they'd ever admit the second one out loud. Now, win only the logical yes, and you've built half a bridge. Technically flawless, and it doesn't reach the other side.
Now, if you caught the episode a few weeks ago on The Brain Elevator, this will land familiar. Floor three, that is where the neocortex lives, the rational floor, your logical yes. Now, floor two, just below it, was the limbic system where trust and rapport create. It's your gut yes. And in the same brain, same order, just applied here to a tender instead of a sales conversation.
You don't get to skip a floor in a bid document any more than you do in a sales call. I call the discipline of deliberately engineering for both of these, the logical and the resonance in the same document, [00:06:00] calibrated to the specific people reading it, Psychological Bid Engineering. It's the same communication mastery methodology that I use everywhere else in this show, applied specifically to how a technical organization writes, designs, and delivers a bid.
And like any other kind of engineering, it isn't guesswork. It's a process, and it starts with actually knowing who you're designing for.
Now, I'd like to make this concrete with something I saw firsthand working inside an international engineering and automation business with a global footprint, blue-chip industrial clients, and technically capable as anyone else in the industry. Now, I'm not going to name them, but the pattern I saw there is one I've now seen enough times that I'd put my money on you recognizing a piece of it in your own bid pack.
It showed up [00:07:00] from two directions all at once, and both teams were doing what felt completely reasonable to them. First of all was the marketing function, which built beautiful materials. Strong brand imagery, a polished style guide, generally appealing work. It landed well internally. Everyone in the room nodded.
What nobody had checked was who was actually sitting on the other side of the table. The buying committees this organization was pitching to skewed heavily toward exactly the profile you'd expect in industrial and technical procurement. Analytical, detail-driven evaluators, cautious operator stakeholders worried about disruption, and a decision-maker, often a CFO or a business owner, who wanted the bottom line, not the brand story.
The materials that felt most on brand in the internal review were, for a lot of that room, the least persuasive thing in the pack.
Now flip it. [00:08:00] The engineering side of that same bid process produced exactly what you'd expect from a team that takes rigor seriously. Comprehensive, accurate, dense technical content. Now, to the analytical evaluator, that content landed perfectly because that's their whole job, and they respected it. But to the operations stakeholder trying to picture what this actually does to their team's next six months, or the decision-maker who wanted the outcome upfront, it read as something to wade through before the actual point arrived.
Both halves of that bid pack were built with real skill. Neither half was built for the room it was walking into. Now, once that business stopped designing bid materials for the people writing them and started designing them for the specific psychology of the people evaluating them, something simple but significant [00:09:00] happened.
The same technical substance delivered through the right register for each stakeholder started landing as both the logical yes and the gut yes in the same room for the first time. Now, that's the whole exercise. Nothing about the underlying engineering changed. What changed was whether it actually reached the people it was meant to persuade.
So how do you actually do this on your next tender? This is where I want to borrow a bit of logic, not the label, just the logic, from how an intelligence agency maps an organized network. Things like who's actually in this? How do they connect? And the part that matters for us: What does each of them actually want?
Not to build a case against anyone, just to know precisely how to present value so it lands with every person on that buyer's board, not [00:10:00] just the one who signs the check. I call this a "Stakeholder Engagement Board", and it's built in four layers.
First, map the roles, not just the names. Who is the economic buyer? Who's the technical evaluator? Who's the end user who will actually live with this solution day to day? Who's procurement holding the process itself? And who's got informal influence that never shows up on the org chart for this decision, but matters anyway?
Second is map the likely DISC style of each one of them, even if it's just an educated working guess from how they've engaged with you so far. And in our Communication Mastery program, we get very deliberate and very specific as to how we read people, sometimes even without meeting them in the first place. Now, this is the layer that tells you what resonance [00:11:00] actually looks like for that specific human being, because it's different for every one of them.
Third one then is map the driver. What does a win actually look like for this person specifically? Not for the organization in the abstract. The CFO wants risk and cost defensibility they can stand behind. The operations lead wants a rollout that doesn't detonate their quarter. The technical evaluator wants to be able to defend this choice on the facts to their own boss.
Last but not least is the fourth one, which is map the angle. Which proof point, which framing actually speaks to that driver, and who on your side is the right person to deliver it?
Do that once properly, and you've got yourself a document that can earn the logical yes and the gut yes from four completely different people [00:12:00] at the same table without diluting a single technical fact to do it. That is Psychological Bid Engineering in practice. It's not softer, it's just more precise.
Here's the piece that turns "Know Your Audience" from a nice idea into something you can actually execute while you're drafting a section on a Tuesday afternoon. In Communication Mastery, I teach my students three things, and only three things. We're deliberately mirroring for whoever you're writing for.
First one is pace. That's fast or slow. Now, how quickly do you get to the point, and how dense a paragraph is allowed to be before it needs to breathe?
Two is priority. That is people or task. Is the stakeholder scanning for what happens to their team or scanning for what happens to the numbers?
Three then is language, and this one is the one that quietly wrecks more bid [00:13:00] documents than anything else on this list because it's invisible until someone points it out to you.
C language, for example, is factual, logical, and risk-averse. It's words like "audit, compliance, assessment, rigor, methodology, procedure, process, objective." It's the vocabulary of a document that wants to be defensible. Now, if your organization is engineering-led, this is very likely the only language or dialect your bid writers actually speak because it's the dialect that the work itself runs on.
I language is diagonally opposite because it's subjective, colorful, and emotional. It's words like "engaging, transformative, inspiring, uplifting, amazing." Words that describe how something feels, not just what it does. Now, here's why this matters more than [00:14:00] people think.
A bid document that's pure C language cover to cover doesn't just fail to excite an I stakeholder. It reads as cold, clinical, and sterile. Even a D or an S reading the same page can pick up the document with zero warmth in language as one written by people who don't actually care whether this project succeeds, only whether it's technically compliant.
Now, that's not the impression any of you are trying to leave. It's just what happens when one dialect or language runs the whole document unchecked. You don't need to rewrite your technical sections in glowing, inspirational prose either. That would be its own mismatch for exactly the same reason.
What you do need is the same document speaking C where the C ev- evaluator is reading, and finding a little more [00:15:00] warmth, a few more people first words in the sections built for the I and the S.
Pace, priority, language. Three levers, not 40. Pull them deliberately instead of defaulting to whichever one of your own team already speaks fluently.
Once you've mapped the board, here's the practical rule of thumb I use for actually structuring the document. The same three levers, which is pace, priority, and language, broken out section by section instead of paragraph by paragraph. This is the angle layer made concrete.
For your D, your fast bottom line decision-maker, open with an executive summary, which is dot points, bullet points, where the big picture is outlaid, the investment that is required, and the ROI they can expect right up front. Put it on the first page, [00:16:00] not buried on page 40 after the methodology. A D who has to go looking for the number has already mentally checked out.
For your I, relationship driven, story led people. This is where color actually earns its place. Imagery with real people in it, not generic stock photography. An inspiring story about the outcome, not just the output. A client video testimonial and the likes, if you can get them. A 30 second clip of a real client saying this changed how their team operates does more for an I than four pages of case study prose ever will.
For your S then, steady, process-oriented, quietly worried about disruption people: show the whole process. Every step, every milestone, who's actually doing the work at each stage, and the part that matters most for this style specifically, spend real space on how [00:17:00] the people side gets handled. It's kind of like what we call the change management side of things.
Now, who's their point of contact? What does support look like in week one versus month six? An S isn't really asking, "Will this work?" They're asking rather, "Will I and my team be looked after while we're bedding it in?" If the document doesn't answer that in a satisfying way, no amount of technical brilliance closes the gap for them.
And for your C, the style your own organization is probably built on, this is where the facts live. Full detail, stats, terms and conditions, pricing, pros and cons, everything required to make a defensible, logical decision. Now, don't dress this up. A C wants to feel like nothing was hidden and that the decisions hold up under their own scrutiny, not just yours
Here's the discipline part, and it's the bit people get wrong [00:18:00] even once they know all four languages. You don't need all four sections in every bid. You need the sections that match the committee you're actually mapped. So if your board reads C and S heavy with no D or I in sight, four pages of glossy imagery and inspirational stories and case studies aren't inclusive.
It's noise standing between the reader and the parts they actually came for. So skip what doesn't align with your specific committee. Precision beats completeness.
Here's a tactic worth building into your process wherever the tender rules allow it. Submit two responses. One that conforms tightly to the requirements as written, safe, compliant, keeps you inside the evaluation on their terms. A second one then presents what you'd actually recommend as the best solution as a trusted expert.
It [00:19:00] plays to your strengths. It reframes the problem the way your engineers actually see it, and it differentiates you from every other conforming submission in the pile. Whichever one wins, you win. And even when the non-conforming submission doesn't win outright, it does something valuable because it puts your actual thinking in front of the buyer, which is very often the first step toward being invited in earlier on the next one.
Which brings me now to the highest leverage move in the whole process, and it happens before the tender document exists at all. Get involved in shaping the requirements while they're still being written, and you're helping set the frame everyone else will be judged against. I'm thinking scope, evaluation criteria, technical standards.
Now, miss that window and you inherit a spec built by committee, standardized and engineered by procurement to be defensible [00:20:00] rather than being differentiated. I call that "The Sausage Factory". Every solution provider gets run through the same die, differentiation gets quietly designed out of the process, and the price ends up being the only lever anyone else got left to pull.
But getting in early is how you make sure your differentiation isn't one of the things that gets standardized away before you even get a chance to present it, because that's where your true value lives.
If the bid lands, the real test is the pitch. Do the document well and you get the outcome every bid team wants: an invitation to present to the buying committee in person. Here's the trap. A lot of teams treat that invitation as the finish line when it's actually the start of a second harder round of exactly the same work.
Everything you calibrated on paper now has to happen [00:21:00] live in real time, reading the room while you're standing in it. The D in the room still wants you to get to the point fast and still wants to feel in control of the decision. Resist the urge to walk them through your whole methodology before you give them the headline.
The I still needs warmth and story, not just data, delivered face-to-face this time. The S then is watching how you handle their questions about disruption and support as closely as they're listening to the answer itself.
And the C is quietly fact-checking everything you say against what the document already told them. So consistency matters more than charisma in that moment for them.
Now, this is worth saying plainly, because I've watched it happen more than once. A bid can be technically superior, land perfectly on paper, earn the invitation to pitch, and still be [00:22:00] lost in that room because one person on the committee walked out not feeling heard. Not out-argued, not unconvinced by the numbers. Just not resonated with.
Different people need different things, and it only takes one person feeling overlooked to cost you the room.
Starting Monday, Pull your last three lost bids, not the ones you know you lost on price. The ones where you generally thought you had them. Build a stakeholder engagement board for each one after the fact.
Map who was actually in the room, what style they were, what they needed to feel, not just what they needed to read.
I put money on at least one of those losses looking a lot less like a pricing problem and a lot more like a document or a pitch that only ever earned the logical yes from people who also needed the gut one.
[00:23:00] Technical brilliance gets you into the room. It's necessary, and nothing in this episode says otherwise. But on its own, it only ever earns half the yes you actually need. Human resonance, deliberately built in, calibrated to the specific people evaluating you, not bolted on as a decoration, is what earns the other half.
Put both into the same submission, engineered together the way you'd engineer redundancy into anything else that has to hold under real conditions, and you stop losing work you were genuinely the best-placed team to win. Get this right and it compounds. Organizations I've personally worked with on this have pushed bid-win rates beyond 40%, and in some rare cases, as high as 95%, once winning stopped being accidental and started being engineered right from the get-go.
[00:24:00] That's exactly the work I and licensed partners do with engineering and technical organizations through Communication Mastery, building psychological bid engineering into how your BD and technical teams actually put a submission together. So you're earning both kinds of yes deliberately every time you go to tender, and every time you're standing in front of the committee that invited you in.
If you've got a bid pack that reads beautifully to your own team and you're not entirely sure how it lands with the people evaluating it, let's talk. Book a free discovery call, link somewhere in the show notes, and we'll look at exactly where the gut yes might be quietly missing from your last few submissions.
See you next time. Thanks for tuning in. My name is Bram.
