The new cost of custom: maintenance, not typing in practice

Good engineering leadership treats the new cost of custom: maintenance, not typing in practice as practice — repeated, observable, coachable.

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

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

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.

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

Cross-team collaboration gets easier when you publish interfaces: who consumes what, what “done” means, and how failures are communicated. Ambiguity is expensive; clarity is a kindness.

On the new cost of custom: maintenance, not typing in practice, 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.

Leaders should ask: what did the model change, what did a human verify, and where is that trail stored?

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.

The practical next step is small: pick one workflow, name an owner, and make the outcome observable next week.