The problem: The head of IT has dinner with a salesperson he has known for years. The salesperson describes a new email security gateway, and the price is good. The head of IT decides to buy it that quarter. The security operations team (the SOC), which will run it every day, is told after the contract is signed. It cannot send its logs to the SOC’s main tool.
Words used here: an email security gateway is a tool that scans email for scams and malicious files before it reaches staff. A vendor is a company that sells a product. Logs are the records a tool keeps of what it did. The run team is the team that uses the tool every day.
Think of a van bought for the drivers
A boss buys a delivery van from a friend, at a good price, without asking his drivers. The van is too tall for the loading bay. The drivers now unload it in the car park, in the rain, every morning. The boss is not careless. He saw a bargain and he trusted his friend. He just did not ask the people who drive the van.
The head of IT is the boss. The SOC is the drivers.
What it looks like at work
The vendor contact is honest and helpful. The product is good, and many companies use it. The head of IT, who has a tight budget, sees a saving of about 30 percent on his current tool. These are example numbers. He signs a three-year contract.
Weeks later, the SOC tries to connect the gateway to its alert tool and finds there is no log export in the version they bought. The higher version costs more. Until then, an analyst opens the gateway’s own screen every morning and copies suspicious events by hand.
- 11. DinnerA trusted salesperson and a good price
- 22. Contract signedThree years, one vendor looked at
- 33. SOC told afterThe run team hears once it is signed
- 44. No log exportThe bought version cannot connect
- 55. Manual workAn analyst copies events by hand daily
Both sides have a fair point. The head of IT has to manage costs and cannot run a full tender for every purchase. His friend gave him real knowledge. The SOC is right that it knows what the tool must do each day. Neither is wrong about their own part. The gap is that the people who run the tool were never asked.
You will notice it when:
- A tool appears with no list of what it was meant to do.
- The people who run it say “we heard about it after.”
- Integration is discovered after the contract is signed.
- Only one vendor was ever looked at.
- The reason for the choice is “they are good people.”
What exactly needs fixing
The fix is not to ban friendships with vendors. It is a short list of must-haves from the run team, a trial against that list, and a written reason. This card shows the whole problem on one page:
An email gateway was bought on a friend’s pitch, and the SOC that runs it was told after signing.
The purchase decision, the contract, and the SOC’s daily work.
A tool is bought that does not do the one thing it was needed for.
- Three-year contract
- Daily manual work
- Gaps in alerts
- Lost goodwill
- 11. Ask the run teamOne page: what the tool must do and connect to
- 22. Trial the optionsSame checks for every option, including the friend’s
- 33. Write the reasonWho decided, what was weighed, any tie declared, an exit clause
Who fixes it: head of IT and SOC lead
By when: before the next purchase
A blank copy of this card is in the Tools section.
Why it happens
- Trust is quicker than a tender. A known person feels safer than a spreadsheet.
- The buyer is not the user. The person who signs is rarely the one who logs in.
- There is no must-have list. So nothing can be checked against it.
- Budgets close at quarter end. Speed beats fit.
- Nobody records why. Later, no one can see what was weighed.
What happens if you ignore it
The company owns a tool nobody wanted and pays for it for years.
- Manual work replaces automation, and the analysts carry it.
- Gaps appear because the tool does not connect to anything.
- The run team stops trusting how decisions are made.
- The vendor knows the buyer is loyal, and the next renewal is harder to negotiate.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Likely, wherever tools are bought on a relationship. |
| Worst case? | A tool is bought that does not do the one thing it was needed for. |
| What does it cost? | A multi-year contract, daily manual work, and lost goodwill. |
| What if we wait? | The next purchase is made the same way. |
| What does the fix cost? | One page of must-haves and a two-week trial. |
How to fix it, step by step
Ask who runs it, test every option the same way, then write the reason.
- Ask the run team first. A one-page list: what must this tool do for us, and what must it connect to.
- Mark the must-haves. Separate them from the nice-to-haves.
- Look at at least two options. Including the one the friend recommended.
- Trial each one on the same checks. Same test emails, same log export, same reports.
- Declare any tie to a vendor. A one-line note: “I know this person.” It is not an accusation, it is clean practice.
- Write down why you chose it. Who decided, what was weighed, and what was left out.
- Ask the vendor for a trial period or exit clause. So a wrong choice is not locked in for three years.
The picture shows the order: ask who runs it, test every option the same way, then write the reason. The first step is the one that costs nothing and saves the most.
Who to bring in: The head of IT (owns the choice), the SOC lead (owns the need list), procurement (checks the contract terms), and the vendor contact (answers the trial questions in writing).
Tools and templates
One-page need list
| Must the tool… | Must have / nice to have | Checked in trial |
|---|---|---|
| Send logs to the SOC alert tool | Must have | Yes / No |
| Block known bad links | Must have | Yes / No |
| Report on blocked mail each week | Nice to have | Yes / No |
| Work with our current mail system | Must have | 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 start the talk
Subject: What our team needs from the new email gateway
Hi. Before we go further on the gateway, could we write one page of what it must do for the team that runs it? The SOC has two or three things it cannot do without, such as sending logs to our alert tool. I would also like us to trial one other option on the same checks. I know the vendor contact is trusted and that is useful, but I would like a written reason we can stand behind. Can we meet for 30 minutes this week?
Field tip
Before any meeting with a vendor, ask the people who will use the tool: “What is the one thing it must do?” Take the answer into the room.
Words used in this chapter
- Email security gateway: a tool that scans email for scams and malicious files.
- Vendor: a company that sells a product.
- Run team: the team that uses the tool every day.
- Must-have: something the tool has to do, or it is not usable.
- Trial: a short test of a tool before buying.
- Exit clause: a contract term that lets you leave early.