The slides are polished. The screenshots are clean. The architecture diagram shows a system of elegant simplicity. The demo flows seamlessly from login to dashboard to export.
The product you will receive after signing the contract will resemble this presentation the way a restaurant meal resembles its photograph on the menu.
⸻
The Demo Environment
The demo runs on a curated environment. The data is clean. The edge cases are removed. The workflows are pre-configured. The load is zero.
The vendor did not build a realistic demo. They built an ideal one. The difference is significant. The realistic demo would show the three-second load time on the analytics page. It would show the error message when the CSV export exceeds 50,000 rows. It would show the settings panel that requires a support ticket to configure.
The demo is the vendor's aspiration. The product is the vendor's reality.
⸻
The Roadmap Slide
Somewhere in the deck, there is a roadmap. It shows the features that are "planned" and "coming soon." The buyer evaluates the product based on what it will become, not what it is.
This is the intended effect. The roadmap slide converts future intent into present value. The buyer signs the contract for a product that includes features that have not been built, may not be built, and are not contractually guaranteed.
If the feature appears on the roadmap slide but not in the contract, it does not exist. Treat it accordingly.
⸻
The Reference Game
The vendor provides references. Three customers who will say positive things. These customers were selected for a reason.
They are the customers who received the most attention, the most custom work, or the most favorable pricing. Their experience is genuine but not representative. The vendor did not provide the reference who experienced the six-week implementation delay. They did not provide the reference who discovered that the integration they were promised requires an additional module with an additional fee.
References are marketing materials delivered by a customer's voice. Ask the reference what surprised them. Ask what they would do differently. The answers to these questions are where the truth lives.
⸻
The Evaluation Discipline
Before the pitch, define your evaluation criteria. Write them down. Share them with the vendor.
During the pitch, score against your criteria, not the vendor's narrative. If the vendor spends twenty minutes on a feature you did not ask for, note what they avoided. If the demo skips a workflow you specified, ask to see it live.
The vendor controls the pitch. You control the evaluation. Do not let the performance replace the assessment.
End.