Vendor governance and the discipline to not switch

The strategic question

Vendor decisions get treated as one-off negotiations, but the ones that matter are governance decisions: what commercial structure can this business actually operate well under, right now — and who bears the cost when a change is made for reasons that don't hold up under scrutiny? Two vendor situations, arriving from different directions, turned out to be the same question.

The constraint

The first: a key frontend delivery vendor was engaged on a time-and-materials basis across the platform. T&M gives flexibility, but everything about the operating context pulled the other way — the nature of the market, the business's risk-acceptance level, and its audit constraints all require a committed scope and a committed timeline. Continuing as-is meant flexibility we couldn't fully use, at a governance cost we could.

The second: marketing requested switching the content-operations vendor to one they had an existing personal familiarity with. The pitch was reasonable on its face — a vendor the team already trusted and knew how to work with.

The decision I owned

For the delivery vendor, I led the transition from time-and-materials to fixed-scope delivery, coordinating legal review through the contract restructuring. The trade was explicit: less flexibility in exchange for the predictability and accountability that a committed scope and timeline provide — which is what the operating environment actually required, not a preference.

For the content-operations vendor, I ran a value test before agreeing to anything: who benefits, and who pays? The familiarity benefit was real, but it accrued to one team. The switching costs — platform knowledge lost, a new ramp-up cycle, migration risk — would land on the whole platform, not just marketing. And the incumbent vendor had no SLA gap and no cost gap to justify the change. I recommended against switching.

Same method both times: separate the real benefit from who's asking for it, and weigh it against who absorbs the cost of change. Once that pointed toward changing the commercial model. Once it pointed toward keeping the vendor exactly as is. The method doesn't promise a consistent answer — it promises the right one for the situation in front of it.

The outcome

The delivery vendor now delivers against fixed scope and committed timelines, with accountability the business can actually audit and govern. On the content-operations side, marketing accepted the recommendation to keep the incumbent vendor, and the relationship — with marketing and with the vendor — stayed intact.

What I'd tell another product leader

Pushback isn't a personality trait, it's a method applied consistently. If you only ever say yes to convenient requests and no to inconvenient ones, you're not doing governance, you're doing politics. Run the same test every time — real benefit versus who pays for change — and let the answer land where it lands, even when it means changing your own vendor's contract structure just as readily as it means telling another team no.