Platforms you buy still need owners

I keep returning to a simple test: after a week of work on platforms you buy still need owners, can someone outside the room explain what changed and who owns it?

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.

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

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

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

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.

On platforms you buy still need owners, the leadership move is to make the invisible visible: ownership, verification, and the path for the next person.

In practice that means shorter cycles: decide, ship a thin slice, review what broke, coach the pattern into the next person. Long programs without those loops become status machines.

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?