The problem: A vendor shows the security team a smooth demo. Alerts from the monitoring tool open tickets in the help desk system on their own, and the head of security calculates it will save two analysts. The tool is bought. When the partner starts setting it up, the feature turns out to need a paid add-on and several weeks of custom work. The SOC (the security operations team) is still opening tickets by hand.
Words used here: a demo is a live show of a product. An add-on is an extra paid part. Custom work means building something special for one customer. A ticket is a logged job in the help desk system.
Think of the show home
A buyer walks through a show home. The kitchen has a lovely island, soft lighting and new appliances. She buys a flat in the same building. When she moves in, the flat has no island. The seller says, “The island was an option, in the show home only.” Nobody lied in the room. She just never saw it written down, and she did not check her own flat.
The demo is the show home. Your own network is the flat.
What it looks like at work
The vendor’s sales engineer is skilled and the demo is accurate for the vendor’s own test setup. The head of security asks, “Does it create tickets automatically?” and is told yes. The budget is approved on the saving of two analysts. These are example numbers.
Two months into setup, the partner engineer explains that automatic tickets need an add-on module and work to match the company’s help desk fields. The extra cost is about 40 percent of the purchase. The saving the board was promised does not appear.
- 11. Smooth demoAlerts open tickets on their own
- 22. “Yes”Said aloud, not written in the quote
- 33. BoughtThe saving of two analysts is approved
- 44. SetupIt needs an add-on and custom work
- 55. No savingAbout 40 percent more cost, still by hand
Both sides have a fair point. Vendors must show their product at its best, and the demo was not false. The buyer is right that a feature shown should be a feature delivered. The gap is that nobody asked, “Is this in the box we are buying, and does it work on our systems?”
You will notice it when:
- A key feature is described in the demo but is not in the quote.
- The demo used the vendor’s data, not yours.
- The word “integration” appears without a price.
- The partner says “that depends on your setup” after the contract is signed.
- The saving in the business case never shows in the real numbers.
What exactly needs fixing
The fix is not to distrust demos. It is to test the claim on your own data, write each shown feature into the contract, and hold back part of the payment until it works. This card shows the whole problem on one page:
Automatic ticket creation was shown in the demo but needs an add-on and custom work that was not in the price.
The purchase, the quote, and the business case for the saving.
A tool bought for a feature it cannot deliver without major extra cost.
- Extra spend
- Lost savings
- Work still by hand
- Lost credibility
- 11. Test on our dataThe vendor runs the three key features on your own alerts and help desk
- 22. Write it downEach feature is a plain-words contract clause, with add-ons priced
- 33. Pay on delivery15 to 20 percent is held until the feature works for you
Who fixes it: head of security with procurement
By when: before the next purchase
A blank copy of this card is in the Tools section.
Why it happens
- A demo is built to impress. It uses clean data and a perfect setup.
- Nobody tests the claim. The buyer takes the sales engineer’s word.
- Features, add-ons and services are priced apart. The headline price hides them.
- The business case is written before the details are known. So it rests on the promise.
- The promise is verbal. There is nothing in the contract to point at.
What happens if you ignore it
The company pays for a tool that does less than it was sold for.
- The budget is overspent, and the saving does not appear.
- The SOC keeps working by hand, which was the problem to begin with.
- The head of security loses credibility with the board.
- The vendor has no duty to fix it, because it was never written down.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Likely, in any purchase decided by a demo. |
| Worst case? | A tool bought for a feature it cannot deliver without major extra cost. |
| What does it cost? | Extra spend, lost savings, and lost trust. |
| What if we wait? | The next purchase repeats the pattern. |
| What does the fix cost? | A day of testing and a few contract lines. |
How to fix it, step by step
Demo on your own data, write the promise into the contract, then pay on delivery.
- List the three features you are buying it for. Everything else is a bonus.
- Ask the vendor to run those on your data. A short test, using your own alerts and your own help desk.
- Ask in writing: is it in the quote? Features, add-ons, and services, each with a price.
- Put each feature into the contract as a clause. Described in plain words.
- Hold back part of the payment. For example 15 to 20 percent, released when the feature works for you.
- Ask for one reference customer. Someone using the same feature in the same way.
- Write the saving into the business case as a range. Not a single number.
The picture shows the order: demo on your own data, write the promise into the contract, then pay on delivery. The second step is the one a vendor will take seriously, because it is now a promise.
Who to bring in: The head of security (owns the claim), the SOC lead (checks it in the test), procurement (writes the clause), and the vendor’s sales engineer (answers in writing).
Tools and templates
Demo checklist
| Feature we are buying it for | Shown in demo | Tested on our data | In the quote | In the contract |
|---|---|---|---|---|
| Alerts open tickets on their own | Yes / No | Yes / No | Yes / No | Yes / No |
| Works with our help desk | Yes / No | Yes / No | Yes / No | Yes / No |
| Reports needed for audit | Yes / No | Yes / No | Yes / No | Yes / No |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a failed audit, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the vendor
Subject: Confirming the features from the demo
Hi. Thank you for the demo. Before we sign, could you confirm in writing which of these are included in the quoted price: automatic ticket creation, the help desk link, and the audit reports? Please mark anything that needs an add-on or custom work, with a price. I would also like to run a short test on our own alerts. I am not doubting the product. I want to make sure what we buy is what we saw. Can we meet for 30 minutes this week?
Field tip
After any demo, ask: “Which part of what I just saw is not in the price?” The answer is often a surprise.
Words used in this chapter
- Demo: a live show of a product.
- Add-on: an extra paid part.
- Custom work: building something special for one customer.
- Ticket: a logged job in the help desk system.
- Business case: the written reason to spend the money.
- Reference customer: an existing customer who can say how it works for them.