Integration debt after the purchase

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

What follows stays on that claim: mechanisms, concrete scenes, and the failure modes that appear when the claim is ignored.

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.

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.

How it actually works

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

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

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

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.

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.

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.

Measure what you claim to care about. If Integration debt after the purchase only appears in kickoff slides and never in review, incident, or planning artifacts, it is branding. Put a verification signal where people already look.

Where this shows up

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.

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

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.

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

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.

Failure modes

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

• Vendor success metrics replacing your product metrics.
• Shadow purchases by teams that skip security and data review.
• No exit plan; switching costs discovered during an outage or a price hike.
• Custom platforms that reinvent commodity chrome while underfunding the harness.

What to do this month

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

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

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

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.

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

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

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

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.

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.

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.

Optimism without an owner is how demos become liabilities. Name the human before you name the tool.

Close

Harnesses outlive vendors. Invest accordingly.

If someone new cannot explain Integration debt after the purchase from your artifacts in fifteen minutes, the practice is still private.