When a vendor becomes your process: the operable version

In an AI-accelerated world, When a vendor becomes your process is less about typing speed and more about maintenance, integration debt, and who owns outcomes.

If you cannot unwind it, you did not buy a tool — you adopted a dependency with a logo.

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

For When a vendor becomes your process, the inheritance test is blunt: after a week, can someone outside the original room explain what changed, who owns it, and how you will know if it breaks? If the answer depends on hallway memory, you still have a story — not a practice.

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.

What fails when you skip it

Teams already have scars. Naming the failure modes precisely is faster than inventing a framework brand.

No exit plan; switching costs discovered during an outage or a price hike.

Custom platforms that reinvent commodity chrome while underfunding the harness.

Building because pride, buying because fear — neither from ownership analysis.

Vendor success metrics replacing your product metrics.

Controls that answer those failures

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.

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

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.

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

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

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

Keep harnesses you control — evals, policy, audit — even when you buy commodity inference or platforms. That is how judgment stays portable.

A concrete scene

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.

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

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

Tradeoffs

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

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.

On When a vendor becomes your process, start from ownership of the failure mode and the exit path. Purchase price is the down payment; integration debt is the mortgage.

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.

What to do this month

• Every purchase: name the internal owner and the failure-mode runbook.
• Annual: run a tabletop exit for one critical vendor.
• Every build: name the commodity you refused to buy and why ownership differs.
• Track integration debt items on the same board as features until retired.

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

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.

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

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.

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

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.

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

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

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

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.

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

Close

Harnesses outlive vendors. Invest accordingly.

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