When a vendor becomes your process: what fails first

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

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

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.

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.

Practices with enough detail to copy

Cadence beats intensity. These hold when they fit inside weeks people already live.

1

Track integration debt items on the same board as features until retired.

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.

2

Every purchase: name the internal owner and the failure-mode runbook.

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

3

Every build: name the commodity you refused to buy and why ownership differs.

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

4

Require eval and audit ownership to stay in-house for AI tooling.

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.

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

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.

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.

Scenes

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

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

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.

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.

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

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.

Failure modes

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

• Vendor success metrics replacing your product metrics.
• Custom platforms that reinvent commodity chrome while underfunding the harness.
• Building because pride, buying because fear — neither from ownership analysis.
• Shadow purchases by teams that skip security and data review.

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

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 the harness, buy the commodity: keep eval suites, policy, and audit logs in systems you control even if inference is purchased.

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.

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

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.

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

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.

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.

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

Close

Own the outcome. Buy time on commodities; keep judgment and exit under your roof.

Carry the claim as a habit, not a brand: When a vendor becomes your process either compounds ownership or it was applause.