Premature Elaboration

A sales engineer I once worked with spent an entire weekend building a demo.

Eighteen distinct capabilities, each with its own polished walkthrough, presented in careful sequence. It was thorough, accurate, and genuinely impressive as a piece of preparation.

He ran the whole thing for a mid-sized logistics buyer, beginning to end, exactly as rehearsed.

Afterward, I asked the buyer's champion which part had landed hardest.

She paused. Then admitted she couldn't remember most of it. It had all blurred together somewhere around feature nine.

The one thing she did remember, unprompted, was a single throwaway screen shown for maybe ninety seconds near the very beginning, one that matched a specific reconciliation error her team dealt with every week.

Eighty minutes of careful, accurate material had simply evaporated.

What went wrong

Michael Bosworth, author of Solution Selling, had a name for what happened: premature elaboration.[^1]

It means presenting the complete, fully realized version of your product before the buyer has developed enough of a stake in the story to want it.

It doesn't look like a mistake while it's happening. It looks like thoroughness. Generosity, even. You've built something impressive and you want to show it. You've done the work and you want the buyer to see that you've done the work.

But completeness delivered too early doesn't build confidence. It buries the one or two things that actually matter under a dozen things that, at this stage, do not.

Three ways it backfires

It erases the recognition moment. The recognition moment is the instant a buyer sees their own problem reflected back at them clearly enough to think: that's us. That moment is fragile. It requires the buyer to be paying close attention when it arrives. Bury it in feature nine of eighteen and most buyers will have already started composing their follow-up email.

It converts a scene into an inventory. Buyers don't remember inventories. They remember the one moment that answered the one fear they walked in carrying. A demo that tries to cover everything gives the buyer nothing specific to hold onto. When they try to describe it to a colleague afterward, they can't. That's a problem, because your champion needs to be able to carry the argument into rooms you'll never enter.

It hands the room premature objections. Every feature you show that the buyer didn't ask about is now fair game to question, compare, or push back on. Features shown before the buyer has a reason to care about them don't build the case. They extend the conversation in directions you didn't intend and give skeptics something to work with.

Why improv and Aristotle both saw this coming

Premature elaboration isn't just a sales problem. It's a persuasion problem, and two very different traditions figured it out long before Bosworth named it.

Aristotle argued in Rhetoric that persuasion requires three elements working in sequence: ethos (credibility), pathos (emotional connection), and logos (logical argument). The order matters. You cannot lead with logos, meaning facts, features, and proof, until the audience has a reason to care. Aristotle understood that an argument delivered before the listener has an emotional stake in the outcome is not persuasion. It's noise.

Improv theater teaches the same lesson from the stage. The foundational rule of improv is "yes, and": you accept what your scene partner gives you and build on it. You never walk onstage with a fully formed script and bulldoze through it regardless of what the other person does. The scene only works when both parties are present, listening, and responding to what's actually happening in the room.

A sales demo is a scene, not a monologue. The moment you stop responding to the buyer and start executing a rehearsed sequence, you've left the conversation. You're performing for yourself.

Bosworth named the mistake. Aristotle explained why it fails. Improv shows you what to do instead: listen first, build from what you're given, and let the scene go where the buyer needs it to go.

The fix isn't a shorter demo

The fix is a more disciplined one.

Before you open a single screen, find out what the buyer is actually carrying into the room. What problem brought them here? What does it cost them weekly? What have they already tried? What would have to be true for this to be worth their time?

Then show only the part of your solution that speaks directly to that. Not because the rest doesn't matter, but because the rest doesn't matter yet.

The buyer needs to see themselves in the story before they can care about the rest of the story.

We rebuilt that demo around ninety seconds instead of eighty minutes. The next three buyers all remembered exactly what we wanted them to remember. More importantly, they could explain it to someone else.

Try this before your next demo

Before your next demonstration, write down the one problem this specific buyer is most likely carrying into the room.

Then find the single screen, moment, or capability in your product that speaks most directly to that problem.

Start there. Let the buyer respond. Build the rest of the demo around what they tell you next.

A demo that begins with recognition is far more likely to end with a decision.

---

[^1]: Michael T. Bosworth, Solution Selling: Creating Buyers in Difficult Selling Markets (McGraw-Hill, 1994). Bosworth uses "premature elaboration" to describe the common sales mistake of presenting a complete product solution before the buyer has articulated, or fully acknowledged, the pain it solves. The result is a solution in search of a problem the buyer hasn't yet owned.