When a vendor becomes your process: evidence over enthusiasm

I care about “When a vendor becomes your process” for one practical reason: it either leaves clearer ownership next week, or it was theater.

Buy commodities. Build the harness that makes your judgment visible: policy, evals, audit, and exit.

The rest develops that one idea with controls you can install and failure modes you can recognize.

Write one page while the decision is still warm — context, options, choice, owner, revisit date. Verbal alignment on When a vendor becomes your process evaporates under ordinary calendar pressure, and Slack archaeology is a poor substitute for a decision record.

Measure what you claim to care about. If When a vendor becomes your process only appears in kickoff slides and never in review, incident, or planning artifacts, it is branding. Put a verification signal where people already look.

How it actually works

Install the smallest set of mechanisms that make success and failure legible. Skip the program name.

Make-or-buy with agents in the mix still requires you to define tool allow-lists and human override. Buying the runtime does not buy judgment.

When a vendor becomes your process, document the process in your words. Otherwise a price hike or outage becomes an identity crisis.

Evaluate AI vendors like critical-path systems: SLOs, incident communication, subprocessors, kill switches, and data boundaries.

Start from ownership. If nobody on your team can operate the failure mode, you did not buy a capability — you rented a demo with a support email.

Price integration debt explicitly: connectors, identity, logging, eval wiring, and the people who will babysit them. Purchase price is the down payment.

Write exit strategies for bought AI tooling before procurement: data export, prompt/eval portability, and a 90-day unwind drill. Soft lock-in is still lock-in.

If nobody on your team can operate the failure mode, you did not buy a capability — you rented a demo with a support email.

Where this shows up

A vendor’s success metrics replace product metrics in leadership reviews. That is lock-in of attention. Keep your north-star metrics in-house.

Integration debt after purchase: five half-connected identity paths and no single owner for authz bugs. Procurement celebrated; on-call paid.

A team builds a custom agent platform because it feels strategic. Six months later they maintain auth, quotas, and UI chrome instead of product differentiation. Commodity inference plus an in-house harness would have been enough.

Tradeoffs

Vendor features arrive fast. Your process still needs translation into owned runbooks.

Building custom feels like control and often buys maintenance. Buying feels like speed and often buys integration debt. Name the debt either way.

Keeping harnesses in-house costs engineering time and preserves exit. Worth it for anything on the critical path.

When pressure rises, teams drop the unowned practice first. Put When a vendor becomes your process in the path of work — templates, checklists, review norms — or admit it was optional applause.

Keep the unit of progress small enough to finish under a full calendar: one owner clarification, one verification signal, one reversible control. Grand programs without weekly evidence become status machines.

Failure modes

Each of these is a missing control, not a personality problem:

• Building because pride, buying because fear — neither from ownership analysis.
• Custom platforms that reinvent commodity chrome while underfunding the harness.
• No exit plan; switching costs discovered during an outage or a price hike.
• Vendor success metrics replacing your product metrics.

What to do this month

• Track integration debt items on the same board as features until retired.
• Require eval and audit ownership to stay in-house for AI tooling.
• Annual: run a tabletop exit for one critical vendor.

Keep eval suites and audit logs in systems you control even when inference is purchased. That is how you keep judgment portable.

Platforms you buy still need owners — for identity integration, data retention, incident comms, and process translation. Procurement does not create ownership.

Exit drills are cheap insurance. Export a sample, revoke a key, and time how long a degraded mode lasts before you need the vendor again.

Build less, own more of the outcome: prefer thin custom layers over reimplementing commodity models. Copilots make greenfield look cheap until on-call inherits it.

Integration debt belongs on the same board as features until retired. Otherwise procurement wins the quarter and on-call pays the year.

Build the harness, buy the commodity: keep eval suites, policy, and audit logs in systems you control even if inference is purchased.

The new cost of custom is maintenance, not typing. AI makes that easy to forget until the second quarter of on-call.

Evaluating vendors like critical-path systems includes asking how you pause them. No pause path means no operational maturity.

Build the harness, buy the commodity works until someone rebuilds the commodity “for flexibility.” Flexibility without differentiated ownership is usually nostalgia.

No exit plan. Price increases. Suddenly “switching costs” are discovered during budget season. A tabletop unwind once a year is cheaper than surprise.

A price hike arrives and nobody can list what data is trapped where. The exit sketch should have been written at purchase, not at panic.

One more practice worth installing: Every build: name the commodity you refused to buy and why ownership differs.

Close

If nobody can operate the failure mode, you rented a demo.

If someone new cannot explain When a vendor becomes your process from your artifacts in fifteen minutes, the practice is still private.