What Two Decades in Enterprise Sales Taught Me About Plotting a Thriller

Every enterprise deal I've ever worked has the bones of a thriller in it, even if nobody in the room would call it that. There's a protagonist with something to lose. There are stakeholders who want different things and won't say so directly. There's a piece of information withheld until exactly the moment it does the most damage or the most good. It took me a long time — and a good deal of frustration writing my first drafts of The Alchemist Triangle — to notice that I already knew this structure cold. I'd just been calling it "the deal cycle" instead of "the plot."

The pitch is Act One

In enterprise technology, you don't get to open with the climax. You open with a problem the buyer has half-articulated to themselves — a cost they're absorbing, a risk they're carrying, a competitor pulling ahead — and your job in the first conversation is to sharpen that problem into something they can see clearly for the first time. That's Act One of any thriller: not the explosion, but the moment the ordinary world tilts and the protagonist realizes something is wrong. When I sat down to write, the instinct to delay the "explosion" and earn it through setup wasn't new to me. I'd been doing it in every discovery call for years.

A good GTM strategy and a good mystery novel fail for the exact same reason: they reveal too much, too early, and the reader — or the buyer — stops turning pages.

Objection handling is rising action

The middle of a deal cycle is where most technology sellers get uncomfortable, because it's where the resistance shows up — budget owners who weren't in the first call, a competing vendor with a cheaper number, a security team asking the question you hoped nobody would ask. I used to think of this stage as friction to be managed. Writing fiction taught me to think of it as fuel. A thriller with no resistance in its middle third is not a thriller, it's a pamphlet. The same is true of a transformation story: if there's no real obstacle, there's no real stake, and nobody — buyer or reader — believes the ending was earned.

Structuring The Alchemist Triangle around a scientific mystery meant I had to plant clues early that would only make sense later, the same discipline good enterprise architects use when they design for a future state three phases ahead of where the client currently sits. You're always writing two timelines at once: what the reader (or the client) understands right now, and what you know they'll understand by the end. The gap between those two things, held just long enough, is where tension lives.

The close is the resolution — but only if you've paid off what you promised

Closing an enterprise deal and closing a novel's plot have the same failure mode: an ending that arrives out of nowhere, unearned by what came before. In sales, that looks like a "yes" that isn't really understood by the buyer, and unravels in implementation. In fiction, it looks like a twist that technically surprises the reader but doesn't actually satisfy them, because it wasn't built from what they were shown. Two decades of watching deals either land cleanly or unravel in the fine print taught me to always ask, before I write a resolution: have I actually earned this, or am I just hoping the reader won't check my work?

I don't think storytelling makes anyone a better enterprise strategist, and I don't think enterprise strategy makes anyone a better novelist. But I do think both crafts reward the same underlying discipline — structuring information so the truth lands exactly when it's ready to be believed, not a moment before.