Buyers arrive with their minds already made up

The most successful demo I ever sat through had nothing to do with the product. The prospect had already decided. I could see it in the way they nodded, the way they asked questions designed to confirm rather than interrogate, the way they steered the conversation toward implementation timelines before we had finished the second slide. The demo was not a test. It was a ceremony.

And we performed it beautifully. Because that is what you do when the room has already chosen you. You give them the evidence they need to tell their procurement team, their CFO, their board that they did their due diligence.

But here is the thing most product teams never confront: that demo was not where the deal was won. It was won weeks earlier, in conversations we were never part of, in peer recommendations we never saw, in a decision made quietly before anyone on our side picked up the phone.

The post-rationalisation window

TrustRadius data paints a picture that should unsettle every product and go-to-market team in B2B. Shortlists have shrunk. Not from ten products to five. From four or five down to one to three. And 71% of buyers go with their first-choice product after creating that shortlist. The research phase, the part where teams assume persuasion happens, is not where the decision lives. It is where the decision gets dressed up.

I call this the post-rationalisation window. The period between a buyer deciding and a buyer appearing to decide. It looks like evaluation. It feels like evaluation. Your analytics might even track it as evaluation. But the buyer is not weighing options. They are collecting evidence to support a conclusion they have already reached.

This is not cynicism. It is human psychology. People decide with instinct, pattern recognition, and social proof. Then they build a rational case after the fact. Buying a B2B product is no different from buying a house or choosing a restaurant. The gut moves first. The spreadsheet follows.

But most product teams build their entire go-to-market around that spreadsheet.

At Freshworks, I watched this play out in enterprise deal after enterprise deal. The prospects who were genuinely undecided looked different from the ones who had already made up their minds. The undecided ones interrogated. They pushed back on claims. They asked uncomfortable questions about edge cases and integrations. The decided ones asked easy questions. They smiled. They wanted to know about onboarding.

The demo, for the decided buyer, was a performance for the procurement team. Not a genuine evaluation. The sales team knew this instinctively but never said it out loud, because saying it would raise an awkward question: if the decision is already made before the demo, what exactly is the demo for?

The phantom evaluation

I have a name for what happens when a product team invests heavily in a stage the buyer has already passed through. I call it the phantom evaluation. Your team prepares for weeks. You rehearse the demo. You build custom slides. You assemble your best people in a conference room. And the buyer sits through it politely, because they need to demonstrate process compliance to their internal stakeholders.

The demo is theatre for an audience that has already chosen the ending.

But the phantom evaluation is not harmless. It consumes enormous resources. Product teams build features to win evaluations that were never genuine competitions. Sales engineers spend days on proof-of-concept environments that exist to satisfy a checkbox, not to change a mind. Marketing produces comparison content for a decision that was made over coffee two weeks earlier, when a buyer's former colleague mentioned your competitor's name.

The waste is invisible because it looks like work. It looks like rigour. But it is rigour applied to a process that has already concluded.

I saw the mirror image of this at Nike, in a completely different context. Retail. Consumer. Physical stores. But the pattern was identical. Consumers were arriving at the store having already decided what they wanted to buy. They had seen it on a friend. They had read about it. They had scrolled past it fourteen times on their phone. The in-store experience was not conversion. It was confirmation.

The store associates who understood this were brilliant. They did not try to sell. They reinforced the choice the customer had already made. "Great choice, that colourway has been moving fast." The associates who tried to redirect, who pitched alternatives, who treated the interaction as a fresh sales opportunity, consistently underperformed. They were trying to influence a decision that had already been made by the time the customer walked through the door.

Which is exactly the same mistake most B2B product teams make with their demos.

Where influence actually lives

If the decision is made before the formal evaluation, the question product teams need to ask is not how to win the demo. It is how to win the conversation that happens before the demo is ever scheduled.

But this is harder. Because that conversation is invisible. It happens in Slack channels you are not in. It happens when a VP asks a peer at another company what they use. It happens when a product manager reads a thread on LinkedIn where someone recommends a tool for a problem they recognise. It happens in the dark, outside your funnel, beyond your analytics, in spaces your marketing team does not control.

The implication is uncomfortable. You are not selling. You are helping the buyer justify what they have already decided. And if that is true, then the real product work is not building a better demo. It is building a product that people talk about before the buying process starts.

Peer influence. Word of mouth. The quality of the experience your existing users have. The things those users say about you when nobody from your company is in the room. That is your real sales motion. Everything else is post-production.

But most go-to-market strategies still treat the formal evaluation as the main event. They invest in demo environments, sales decks, competitive battle cards, and objection-handling playbooks. All of which matter. But all of which arrive after the verdict.

Think of a jury that has decided the case before the closing arguments begin. The lawyers still argue. The judge still instructs. The process still runs. But the outcome was settled in the jury room hours ago, based on evidence presented days earlier. The closing arguments exist for the record, not for the decision.

Building for the moment before the moment

The product teams that understand this do not stop investing in demos and evaluations. But they invest differently. They put more into what the product feels like in the first five minutes of a free trial, because that is where the real evaluation happens, alone, without a sales engineer narrating the experience. They put more into making existing customers successful, because those customers are the ones generating the recommendations that create the shortlist. They put more into public product quality, the kind a buyer encounters before anyone from the company knows they exist.

But this requires a kind of humility that most product organisations struggle with. It requires accepting that the moment of maximum influence is not the moment you control. It is the moment you never see.

The best product work happens long before the buyer raises their hand. It happens in the experience you built for someone else, someone who liked it enough to mention your name when a colleague asked what they should use. That quiet recommendation carries more weight than any demo you will ever build.

And you will never see it happen.