The Vendor Stack That
Nobody Owns

By Scott Kendall
It didn’t happen all at once.
​
There was no single decision that created it. No executive stood up and said, “Let’s build something fragmented, expensive, and hard to manage!”
​
It accumulated:
- One contract to solve a problem.
- Another to move faster.
- A third because someone trusted a partner.
- A fourth because replacing the first three felt too risky.
And now - years later - you’re looking at a vendor stack that no one truly owns.
The Illusion of Control
​
On paper, everything looks accounted for.
-
Each vendor has a contract
-
Each contract has a business owner
-
Each owner has a justification
But when you zoom out, something doesn’t add up. Capabilities overlap. Costs don’t align with value.
Vendors operate in parallel.......... but not together.
​​
“Why do we have all of these?”
​
Ask who owns the vendor ecosystem, and you’ll get a list of names.
Procurement owns the contracts / IT owns the systems / Finance owns the spend / Business units own the outcomes.
​
Which means… no one owns the system.
Because ownership isn’t about pieces. It’s about the whole. And the whole is where the problem lives.
​
The Hidden Cost
​
The issue isn’t just spend. It’s what the stack does to the organization:
-
Decisions slow down because dependencies aren’t clear
-
Teams duplicate work because visibility is limited
-
Vendors optimize for their contract, not your outcome
-
Renewals happen out of convenience, not intent
Over time, the stack becomes self-preserving. Not because it’s working. But because it’s too complex to challenge.
​
Why It Doesn’t Get Fixed
​
Most organizations try to solve this the wrong way. They run an RFP. They renegotiate rates.
They swap one vendor for another. But the structure stays the same.
​
A vendor stack without clear ownership is not a sourcing issue. It’s organizational debt.
Because when no one owns the stack…
The stack owns you. Now check out real results..... ​​