When a vendor becomes your process: a shorter feedback loop

“When a vendor becomes your process” stops being abstract the moment you ask who gets paged when it fails.

AI compresses the typing cost of building. It does not compress the ownership cost of running what you built.

I will stay on this thesis — no adjacent manifesto, no tour of every neighboring discipline.

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.

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.

What fails when you skip it

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

Vendor success metrics replacing your product metrics.

Custom platforms that reinvent commodity chrome while underfunding the harness.

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

Shadow purchases by teams that skip security and data review.

Controls that answer those failures

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

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.

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.

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

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

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.

A concrete scene

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 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

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

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

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

Resist the urge to expand scope into neighboring slogans. If a control does not make When a vendor becomes your process more operable for the next person, leave it for another note. Dilution is how coherent essays become stitched scrapbooks.

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

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.
• Every purchase: name the internal owner and the failure-mode runbook.

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

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

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

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.

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

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

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.

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.

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.

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.

On When a vendor becomes your process, keep the loop short: write the decision, name the owner, verify the outcome.