DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

The Friendly Partner Who Keeps Getting the Work

By Deepak Kumar, CISSP

The problem: For six years, the company has used the same integrator (an outside firm that connects and sets up systems) for its security projects. The people are pleasant and quick to answer the phone. Three projects in a row have finished about six weeks late. Nobody has kept a record. The head of IT offers them the fourth project, which has an audit date attached.

Words used here: an integrator is an outside firm that sets up and connects systems. A performance score is a short written grade of how a supplier did. Competing a job means asking several suppliers to bid for it. Incumbent means the supplier already doing the work.

Think of the plumber who is always friendly

A homeowner has used the same plumber for years. He is kind, turns up with biscuits, and is always sorry. The kitchen sink has leaked after his repairs three times. Each time, the homeowner says, “He means well,” and calls him again. Nobody has asked, “Is there someone else who gets it right the first time?”

The plumber is the integrator. The leak is the delay.

The plumber and the leaking sink
A kitchen sink that has leaked three times
So sorry. I will fix it again.
Plumber
He means well. Call him again.
Homeowner
Nobody asked if someone else gets it right first time.

What it looks like at work

The integrator knows the company’s systems well, which is a real advantage. Switching would cost time to explain everything again. The head of IT has a good working relationship with the account manager. The first project was six weeks late because of a delayed delivery. The second was late for a different reason. These are example numbers.

Procurement has no scorecard, so each delay looks like a one-off. The fourth project is offered without other bids, and the audit date is now at risk. When the CISO asks why, nobody can show a pattern because nobody wrote one down.

How a friendly partner keeps winning work
  1. 11. Six good yearsKnows our systems, easy to work with
  2. 22. Late, onceSix weeks over, for a good reason
  3. 33. Late againA different reason, no record kept
  4. 44. Offered job fourNo other bids, an audit date attached
  5. 55. Date at riskNobody can show the pattern
Loyalty is fine. It needs a record behind it.

Both sides have a fair point. The head of IT is right that knowing the systems saves time and that trust is worth something. Procurement is right that a supplier who is never compared has no reason to improve. Loyalty is not wrong. It just needs a record behind it.

You will notice it when:

  • The same supplier wins without a bid for the third time.
  • Late finishes are explained one at a time, never as a pattern.
  • Nobody can say how the supplier did on the last project.
  • The reason to use them is “we know them”.
  • A project with a hard date goes to a supplier with a history of delay.

What exactly needs fixing

The fix is not to drop a good partner. It is a short score after every job, a fair comparison now and then, and results shared with both the partner and your own leaders. This card shows the whole problem on one page:

A partner who is never compared
WHAT IS BROKEN

The same integrator has been late on three projects in a row, with no record, and is offered the fourth.

MEDIUM
WHERE IT IS

Supplier selection for security projects, and procurement’s records.

WHAT COULD GO WRONG

A key project misses a legal or audit date.

WHAT IT COSTS US
  • Repeated delays
  • Higher prices
  • Missed audit date
  • Lost trust
THE FIX, IN THREE MOVES
  1. 1
    1. Score each jobA one-page sheet: on time, budget, quality, handover
  2. 2
    2. Compare fairlyTwo other bids on the next job, including the partner
  3. 3
    3. Share resultsShow the partner and your leaders, and agree what better looks like
WHO FIXES IT

Who fixes it: procurement and the head of IT

BY WHEN

By when: scores for the last three jobs in 2 weeks

A blank copy of this card is in the Tools section.

Why it happens

  • Familiarity feels safe. A known supplier looks like less risk.
  • Nobody scores the job. So there is no evidence either way.
  • Switching has a visible cost. Staying has a hidden one.
  • Each delay has its own reason. The pattern is only clear in a list.
  • Nobody owns supplier performance. Each project manager sees one job.

What happens if you ignore it

The company pays more and waits longer than it needs to, and does not know it.

  • Deadlines tied to audits and laws are missed.
  • The partner has no reason to improve, because nothing happens when they are late.
  • Price rises go unchallenged, because there is no other bid.
  • Project managers stop trusting the process, and warn each other privately.

At a glance

QuestionAnswer
How likely is it to hurt us?Likely, wherever a supplier is used out of habit.
Worst case?A key project misses a legal or audit date.
What does it cost?Repeated delays, higher prices, and lost trust.
What if we wait?The pattern continues, and the supplier relies on it.
What does the fix cost?A one-page score sheet and one extra quote per job.

How to fix it, step by step

Score every job, compare fairly, then share the results.

  1. Make a one-page score sheet. On time, on budget, quality, handover, and how they handled problems.
  2. Score the last three jobs now. Even roughly. A rough record beats none.
  3. Show the partner. Say, “Here is how we saw the last three. What happened?” Listen first.
  4. Agree what better looks like. For example, no more than two weeks late.
  5. Ask for two other bids on the next job. Include the current partner. Say why.
  6. Put a delay clause in the contract. A small, fair penalty or a fixed review point.
  7. Review the scores every six months. Keep the strong partners and replace the rest.
Score, compare, share
1. ScoreEvery job gets a short written score.
2. CompareTwo other bids on the next job.
3. ShareShow the partner and agree what better is.
Sharing often turns a loyal supplier into a better one.

The picture shows the order: score every job, compare fairly, then share the results. Sharing with the partner is what often turns a loyal supplier into a better one.

Who to bring in: Procurement (keeps the scores and runs the comparison), the head of IT (the main sponsor), the project managers who ran the jobs, and the partner’s account manager.

Tools and templates

Partner score sheet

JobOn time (days late)On budgetQuality (1 to 5)Handover (1 to 5)Notes
Project 1Yes / No
Project 2Yes / No
Project 3Yes / No

Blank finding card

FieldWrite here
What is brokenOne line, in plain words
Where it isThe system, team, or process
What could go wrongIn one sentence
What it costs usMoney, time, a failed audit, lost trust
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to the partner

Subject: Looking back at our last three projects together

Hi. We have worked together for six years and I value it. I would like us to look at our last three projects together. All three finished later than planned, and the next one has an audit date. Could we agree what “on time” means, and could I also ask two other firms to quote so we can compare? You would be welcome to quote too. Can we meet for 30 minutes this week?

Field tip

Before you offer the next job to the same partner, ask: “Can I show how they did on the last three?” If not, start with the score sheet.

Words used in this chapter

  • Integrator: an outside firm that sets up and connects systems.
  • Performance score: a short written grade of how a supplier did.
  • Competing a job: asking several suppliers to bid for it.
  • Incumbent: the supplier already doing the work.
  • Delay clause: a contract term that deals with late delivery.
  • Account manager: the supplier’s main contact for your company.