His badge was turned around, so I couldn't tell where he was from.
He asked what we did. I asked what he did instead. Twenty minutes later I knew his bank's authentication platform was falling over, and three weeks after that we signed the contract — no demo, no proof of concept.
I've spent thirty years in pre-sales. This is the book I wish someone had handed me in February 1990.
Your technical knowledge is the price of admission. It gets you in the room. But it's not what keeps you there.
If you're a solutions engineer, a pre-sales architect, a solutions consultant, a technical account manager or a developer advocate, this is for you. So is it if you manage a team of them, or if you're sitting in engineering, DevRel or professional services wondering what the move across would actually be like.
You're good at what you do. You know your technology inside out. But you've noticed that the people in your company with the most influence and the most interesting work are the ones sitting between the technology and the customer — and from the outside that looks like a gift you were either born with or you weren't.
It isn't. It's a set of skills. They can be learned, practised and mastered like any language or methodology you've picked up already, and this book is my attempt to write them down in the order that makes them learnable.
The Influence Architecture
The Influence Architecture is the model I've been building for thirty years — a way to think about the skills that turn a technical expert into the person customers ring before they've finished writing their requirements.
Each stage sits on the one below it, like the floors of a building. Skip one and the structure is unstable. Build all four and you get something that lasts longer than any job you hold.
It works at two scales. Across the arc of a career, and inside a single meeting: a ten-minute conversation at a trade show runs through all four stages the same way a year-long enterprise campaign does.
Sometimes a win. More often a failure I'd rather not have on paper. Then it gets practical: how to explain what your product does in thirty seconds without jargon, the Carrot and Stick framework for talking about business outcomes, the seven questions I ask in discovery, how to map stakeholders by influence and favourability, the five principles of demo delivery, and what to do when the demo breaks in front of forty people.
If any of those made you pause, you're the reason I wrote this. Every chapter ends with a handful more like them.
Print it, fill it in, and keep it next to the deal.
It's about the trusted advisor: the trade show, the bank, and the sales rep at IBM who told me to stop talking about Unix. Read it and decide for yourself whether the rest is worth your time.
The book ships in February 2027. If you'd like to know when it does, leave your email.
I'll email you when the book ships, and not about anything else. Privacy policy.
I run half-day and full-day workshops built around the four stages, in person or remote, and I give keynotes at conferences and sales kickoffs. Bulk copies for a team are straightforward to arrange once the book is out.
Email me at [email protected] and tell me what you're trying to fix.
You don't have to become an extrovert to excel in pre-sales. You have to become yourself — and learn to bring that into the room.