html

The Vendor Who Outlasted the Buyer

A relationship between two people across two organizations. One leaves. The contract continues — but the implicit understanding that made it work is gone, and nobody notices until something needs renegotiating.

Summary: A relationship was built between two people across two organizations. One of them moves on. The contract continues. The work continues. But the implicit understanding that made the relationship work is gone, and nobody notices until something needs to be renegotiated.

Pattern

A vendor and a client have been working together for years. The relationship works because of two specific people who built a shared understanding over time. One of them leaves. The relationship continues on paper. In practice, the substrate that made it function is no longer there.


What tends to happen

The contract was signed in a context that no longer exists. The original client contact agreed to terms that worked because they trusted the vendor’s judgment on certain edges. The vendor, for their part, accommodated requests outside the literal contract because the relationship made it worthwhile.

The original contact moves to a different role, or a different company, or a different team. A new person takes over. They inherit the contract, not the relationship. They read what is written. They do not have access to what was not written.

The vendor continues operating on the prior understanding for some period of time. The new contact begins making requests, or pushing back on decisions, that do not match that understanding. The vendor experiences this as a sudden change in tone. The new contact experiences it as appropriate stewardship of a contract they are now responsible for.

Both interpretations are reasonable. Neither is the actual problem.


Why it fails

The relationship was load-bearing. Nobody acknowledged it as such, because acknowledging it would have meant admitting that the contract alone was not sufficient. The implicit understanding was a feature, not a bug, of the working arrangement.

When the carrier of that understanding leaves, the carrier is replaced but the understanding is not. The replacement is structural, not relational. The contract survives the personnel change. The relationship does not, because relationships do not transfer through paperwork.


Human layer

Long-term vendor relationships tend to drift toward a kind of personal trust that is more efficient than constant contractual reference. Both sides extend small accommodations. Both sides absorb small inconveniences. The arrangement is more functional than the contract describes.

This works until it does not. The function depends on continuity of context. Once the context breaks, both sides find themselves operating from a contract that was never meant to be the load-bearing document.


System layer

Contracts and relationships are tracked in different systems. The contract lives in a CRM, a document repository, a procurement record. The relationship lives in two people’s heads, in informal notes, in the texture of a hundred small conversations.

When personnel changes, the contract migrates cleanly. The relationship does not migrate at all. There is no protocol for handing off the unwritten parts of a working arrangement, because most organizations do not acknowledge that there are unwritten parts.


What it costs

The immediate cost is friction at the next contractual touchpoint — a renewal, an amendment, a change request. The new contact and the vendor discover, in real time, that their models of the relationship do not match.

The deeper cost is that the vendor now has to renegotiate the relationship under conditions that are less favorable than the ones that originally produced it. The original arrangement was the product of trust earned slowly. The new arrangement has to be negotiated quickly, in writing, by people who do not have that trust.


Reduction path

The first intervention is to acknowledge, on both sides, that long-running vendor relationships have an unwritten layer. Not to formalize it — formalizing it kills it — but to acknowledge that it exists, so that both sides know it is at risk during personnel changes.

The second is to introduce, as a matter of practice, a transitional overlap whenever a key contact changes. The departing contact spends a defined period briefing the incoming contact, and the vendor is part of that briefing. This costs time. It saves a renegotiation.

The third is to recognize that a contract is a record of decisions, not of understanding. The understanding has to be rebuilt with each new contact, regardless of what the contract says. Treating the contract as sufficient is the specific mistake that leads to relationships outlasting the people who built them and decaying in place.