The new cost of custom: maintenance, not typing

There is a version of the new cost of custom: maintenance, not typing that looks busy and a version that compounds. The difference is rarely a tool.

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

A purchased AI tool still needs an owner on-call for failure modes, data handling, and process fit.

Buy-versus-build debates should start from ownership. If nobody on your team can operate the failure mode, you did not buy a capability — you rented a demo.

Make-or-buy decisions should include the cost of undoing the choice. Soft lock-in is still lock-in.

Buy commodities. Build the harness that makes your team’s judgment visible: policy, evals, audit, and exit.

Sustainability shows up as fewer retries, right-sized environments, and CI that does not burn cycles for vanity. Efficiency is operational maturity.

On the new cost of custom: maintenance, not typing, the leadership move is to make the invisible visible: ownership, verification, and the path for the next person.

When agents join the loop, treat them like junior systems: limited privileges, explicit tools, budgets, and a human who owns the outcome. Autonomy without audit is just distributed risk.

I prefer written decisions over verbal ones. Memory is a poor archive, and AI tools make fluent improvisation cheap — which raises the value of durable context.

None of this requires a new framework brand. It requires attention, a short feedback loop, and the humility to change process when agents join the workflow.

Ask your team one question in standup this week: what did we make easier to own?