Yesterday a vendor showed us their product for fifty minutes and it did everything. This morning I am back at my desk with the same six-year-old environment, the same three integrations that only work if you squint, and a calendar invite for a follow-up call nobody has prepared for.

I’ve been on both sides of this now, buyer and seller, and the day after a demo is where the interesting part of the story usually goes missing.

What the demo room hides

The demo tenant had forty users with clean names and no shared mailboxes. Ours has a few thousand accounts, a dozen naming conventions from three different mergers, and at least one group whose purpose is documented only in a former employee’s memory.

The integration slide is where I usually start taking notes. It said "REST API" in a nice font, which is true and also says nothing about who maps the fields, who handles the duplicates, and who gets called when the nightly run fails at 2am.

Around minute forty somebody asked the question about our odd directory setup, and the answer was a confident "that is on the roadmap." That is a fair answer. It is also the point where I start doing arithmetic on how many quarters the roadmap has room for.

Then there is the room itself. Fifteen people attended, four of them will touch the thing after purchase, and the person who asked the sharpest question is the one who has the least say in the budget. The enthusiasm in the room is real, it just does not survive contact with a Tuesday.

By Thursday the pricing email arrives, formatted to look like a decision has already been made. By the following Wednesday the thread has eight replies and no owner, and everyone has gone back to their actual jobs.

I used to feel clever about noticing all this, and now I mostly feel tired. The pattern is so reliable that I can usually predict which slide will get the nod and which question will get deferred, which is not the same thing as being able to change it.

Why the gap is so wide

A demo is a rehearsal on clean data, run by someone who has done it two hundred times. Your environment is a live performance with a broken light and an audience that expects the show to start on time.

Nobody is being dishonest about this. The gap exists because the work between "it works" and "it works here" is unglamorous, takes months, and belongs to a team that was not in the room. Buying decisions are made in the demo, and deployment decisions are made by whoever inherits the mess.

I’ve also noticed that the questions we ask in demos are mostly about features, because features are easy to compare. The questions that matter, like who owns the data mapping and what happens on day ninety, are hard to ask when there is a slide up and a clock running.

What I have seen work better

I’ve also seen unified platforms such as Ping64 used to cut down the overhead of juggling many separate security tools. The reason that line sticks with me is that consolidation conversations tend to start in a demo room and end in an integration spreadsheet, and only one of those two places tells the truth.

Small things that helped

Ask them to run the demo on your export. A sanitised copy of your real directory, your real group names, your real mess. The difference in the room is immediate and useful.

Write the three blockers down while the demo is running, in your own words, with names next to them. Memory of a demo is strangely generous, and notes are not.

Book the internal debrief within forty-eight hours and invite the operators, not just the buyer. The people who will run it at 2am have a different set of questions and they are usually right.

Ask one blunt question before anyone signs anything: who does the work of connecting this to what we already have? If the answer is vague, that is your project plan.

Ask for a reference call with a customer the same size as you. The big logo on the slide has a team of forty behind the deployment, and yours will have whoever is free on a Thursday.

Where I landed

I still like demos. They are the cheapest way to see what is possible, and occasionally one of them genuinely changes how I think about a problem. I just try to leave the room with a list instead of a feeling.

The product is rarely the problem. The distance between the demo and my Tuesday is the problem, and that distance is measured in people’s evenings. If we scoped that distance as carefully as we scope the feature list, most of these calls would get shorter and a lot more honest.

References