Proof of Value
Get Started

Why Jordan Never Demos on Day One (and the Catastrophe of Max’s Misstep)

There’s a special kind of dread that washes over you when you realise you’ve walked straight into a technical sales disaster of your own making. I know this feeling intimately - it has the texture of cold sweat and tastes remarkably like over-brewed office coffee.

Jordan, my battle-scarred mentor with wisdom etched into every cynical smile, had one golden rule they’d repeat during our post-mortem sessions at the pub: “Never, under any circumstances, demo on day one.”

It wasn’t superstition. It was survival.

The Setup: Riley’s “Simple” Request

Last quarter at Proof of Value, I learned Jordan’s rule the hard way during the Tyrell Tech engagement. Even now, recalling the event makes me wince so hard my coffee mug seems to flinch in sympathy.

Riley bounced into my workspace, practically levitating with his trademark enthusiasm. “They’re practically ours,” he chirped, performing what I can only describe as an emotional tap dance. “Just needs a bit of technical fluff. Easy peasy.”

In my notebook, I scribbled: Easy peasy in Riley-speak = prepare for Armageddon.

“What exactly are they expecting?” I ventured, already feeling the familiar tightening in my chest.

“Just a peek at the platform. Their CTO’s a bit hands-on,” Riley grinned with an optimism so bright it should have come with a UV warning. “I’ve pencilled you in for tomorrow. Nothing bespoke, just run-of-the-mill stuff.”

That should have been my cue to fake a sudden bout of keyboard-induced repetitive strain injury. In the murky realm of technical demos, ‘run-of-the-mill’ is about as common as a unicorn in the server room.

“And who are we entertaining?” I probed, visions of late nights already dancing in my head.

“Just the key players,” replied Riley, which inevitably translated to everyone including the office cat and possibly several ghosts haunting their IT department.

The Night Before: Preparing for Battle

That night, I built what I believed was an invincible demo. Environments double-checked, sample data triple-loaded, and backup slides prepared for every conceivable tangent. I rehearsed until the technical jargon lost all meaning and became a strange technological lullaby.

I was a warrior ready for battle, armed with APIs and dashboards instead of sword and shield.

The Demo: When “Flawless” Meets “Futile”

The next morning, I logged into the Zoom call fifteen minutes early, exuding a caffeinated blend of professionalism and barely concealed terror. The Tyrell brigade arrived in dribs and drabs - first the CTO, Eldon, followed by a conga line of various titles and faces that blurred together in my anxiety-addled brain.

Once the pleasantries were dispensed with, I launched into my spiel. “I gather you’re keen to see our real-time data-processing capabilities across complex systems?”

Eldon nodded. “Particularly keen on the compliance module. It’s critical for our operations.”

My stomach performed an Olympic-level gymnastics routine. Riley had conveniently omitted any mention of ‘compliance’ in our prep talks.

“Absolutely,” I fibbed with a smile plastered on. “Let’s dive into that.”

Technically, the demo was flawless. The software performed its dance beautifully, dazzling with data visualisations and smooth transitions. I even landed a terrible joke about “SELECT * FROM problems WHERE solution = ‘our platform’” that somehow made the CTO chuckle.

Then disaster struck in the form of a seemingly innocent question.

The Sandra Factor: When Stakeholders Go AWOL

“This is splendid,” Eldon leaned in, visibly impressed. “Could you demonstrate the data residency controls? Sandra from Legal will need to give the nod.”

I kept my smile stitched firmly in place. “Of course. The platform boasts extensive data residency controls.” I navigated to the relevant screen. “Here, policies can be tailored at multiple levels.”

“Marvellous,” Eldon beamed. “Sandra will be thrilled. She’s particular about these things.”

“Is Sandra joining us today?” I ventured, hoping to directly address any potential concerns.

A pause swelled, filling the virtual room like an unwelcome system error. Then Eldon chuckled. “Oh, Sandra’s on a sabbatical. Scaling mountains in Nepal. Completely off-grid. She’ll be back next month.”

My smile fossilised. “And… she’s the sole signatory?”

“Indeed,” Eldon’s cheerfulness did nothing to ease the sinking feeling. “Nothing moves without Sandra’s stamp.”

There it was. The deal’s death knell. Sandra, Legal’s gatekeeper, was communing with the Himalayan gods, beyond the reach of mundane things like email or project timelines.

“Does she have a deputy?” I asked, a thread of hope in my voice.

Eldon laughed, a sound that echoed the death of our commission. “Sandra doesn’t do deputies.”

The Aftermath: Riley’s Parallel Universe

The rest of the call was a blur, a slow-motion trainwreck. Promises were made about sending over documents for Sandra’s eventual perusal - documents that would sit idly in a digital inbox, waiting for her royal stamp of approval sometime after the yaks had been properly appreciated.

As soon as the call ended, Riley pinged me: Nailed it! They loved us!

I stared at the screen. Had Riley been on the same call, or had he transcended into a parallel universe where Sandra was not an absentee monarch?

Riley, I typed, fighting the urge to scream into the void, we just demoed to a ghost. Sandra’s approval method? A literal stamp. She’s back next quarter.

His reply: So, we’re still in the game?

Jordan’s Wisdom: The Reconnaissance Rule

Later, Jordan found me nursing my coffee, my face a study in existential despair.

“How did Tyrell go?” they inquired, already reading the answer in my slumped shoulders.

“Ever tried selling a dream to a phantom?” I muttered.

Jordan nodded, the ghost of a smile playing on their lips. “Ah, the elusive stakeholder. Classic. Someone vital, unreachable?”

“Sandra’s off embracing her inner yeti in Nepal. No contact, just a desk waiting for her stamp.”

Jordan’s smirk was all-knowing. “That’s why day one is for reconnaissance, not show-and-tell. You find all the Sandras before they find you.”

I added a new note to my battered notebook: Rule #1 (reinforced): Never demo on day one. Sandras lurk everywhere, sometimes even in the Himalayas.

The Lesson: Stakeholder Mapping Before Demo Trapping

The next time Riley approached, buzzing about another “simple validation,” I simply smiled. “Who’s your Sandra this time?”

His confusion was palpable, but I had learned. There’s always a Sandra. And occasionally, she’s incommunicado, possibly consulting with mountain spirits about the finer points of data residency requirements.

In the world of technical sales, the most sophisticated demo means nothing if the person who needs to see it is unreachable. Stakeholder mapping isn’t just a box-ticking exercise - it’s the difference between a productive demo and shouting technical specifications into the void.

Jordan was right. Day one is for reconnaissance: identifying decision-makers, understanding approval chains, and most importantly, ensuring everyone who needs to be present actually exists in the same dimension as your sales timeline.

Because no matter how perfect your demo, how slick your transitions, or how compelling your value proposition, none of it matters if Sandra is off finding herself in Nepal while your quarter-end targets quietly weep in the corner.

Related Content

From our blog