How to Assess a Sole-Source Vendor Without Leverage
Engineers often select a sole-source product out of personal confidence in it, rather than genuine clarity that it suits the system it is being selected into. These are different things, and conflating them is how sole-source dependency gets created in the first place.
A product an engineer trusts, because they have used it before, has succeeded elsewhere, or simply feels familiar, is not automatically the product that genuinely suits this particular system’s actual requirements. These are different things. An engineer’s confidence in a product is a statement about their own experience. A system’s suitability for that product is a statement about the system. Conflating the two is one of the quiet, common ways an organisation ends up sole-sourced without ever having deliberately chosen to be.
The pressures behind the conflation
This substitution rarely happens through carelessness. It happens under real pressure, time availability that leaves no room for a genuinely independent technical comparison, project pressure pushing toward whatever decision closes the gap fastest, a quiet desire to validate a choice that has effectively already been made, or deference to a suggestion from a superior that feels easier to accept than to properly test. None of these are due diligence. All of them can look like it, right up until the moment the dependency they created becomes permanent.
Why the responsibility increases exponentially
Once a vendor genuinely is sole-source, due diligence does not simply become more important. It becomes exponentially more important, because every risk that a competitive alternative would normally absorb has nowhere else to go. There is no second supplier to fall back on if the first one falters, no alternative product to switch to if a design flaw surfaces. Obsolescence sits at the sharpest edge of this exposure, and it applies to the product itself and to its spares. A sole-source relationship that goes obsolete does not just lose its best option. It loses its only one.
A weighted analysis across five dimensions
What a sole-source assessment actually needs is a weighted analysis spread across five distinct dimensions, not a single confidence judgement dressed up as rigour. Technicality asks whether the product genuinely fits the system it is being selected into, tested against the system’s real requirements rather than the engineer’s familiarity with the product. Availability asks whether the product can actually be sourced reliably over the system’s full service life, not just at the moment of purchase.
Replaceability asks what genuinely exists if this product, or this vendor, fails. Predictability asks how stable and forecastable the vendor’s own behaviour and performance actually are, not just today, but across the years this dependency will need to hold. Company net worth asks a question too many assessments skip entirely, whether the vendor itself is financially durable enough to still exist, and still support this product, for as long as the system depends on it.
Checking certifications and test validations before purchase
None of these five dimensions can be properly assessed on the vendor’s word alone. Certifications and test validations need to be genuinely checked before purchase, verified against what they actually claim to demonstrate, not assumed to be sound simply because the vendor has presented them confidently. This is what anchors the entire assessment in verifiable evidence rather than reputation, confidence, or a well-produced data sheet.
Why false leverage is worse than none
An assessment that quietly scores a sole-source vendor as though competitive pressure still exists, as though the vendor has some reason to compete for the business, produces a dangerous kind of comfort. It looks rigorous. It reads as though due diligence was genuinely done. Underneath it, the real exposure, no alternative, no leverage, no second option if any one of the five dimensions above turns out to be wrong, remains exactly as large as it always was, now simply hidden behind a document that says otherwise.
What this protects against
The actual failure this discipline exists to prevent is not a bad vendor. It is an organisation becoming sole-sourced by accident, through an engineer’s confidence substituting for the system’s clarity, under pressures that felt reasonable at the time, with nobody ever running the weighted analysis that would have surfaced the real exposure before the dependency became permanent and the time to choose differently had already passed.