Integration debt after the purchase: naming the owner

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.

On Integration debt after the purchase, start from ownership of the failure mode and the exit path. Purchase price is the down payment; integration debt is the mortgage.

When pressure rises, teams drop the unowned practice first. Put Integration debt after the purchase 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.

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

Shadow purchases by teams that skip security and data review.

Custom platforms that reinvent commodity chrome while underfunding the harness.

Vendor success metrics replacing your product metrics.

Controls that answer those failures

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

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.

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

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

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.

A concrete scene

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

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

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.

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

Write one page while the decision is still warm — context, options, choice, owner, revisit date. Verbal alignment on Integration debt after the purchase evaporates under ordinary calendar pressure, and Slack archaeology is a poor substitute for a decision record.

What to do this month

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

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.

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.

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 belongs on the same board as features until retired. Otherwise procurement wins the quarter and on-call pays the year.

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

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.

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

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

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

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

One more practice worth installing: Every purchase: name the internal owner and the failure-mode runbook.

Prefer reversible moves on Integration debt after the purchase. If you cannot say how you would unwind the decision, you are not done designing it.

Close

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

On Integration debt after the purchase, keep the loop short: write the decision, name the owner, verify the outcome.