When a vendor becomes your process — note 172

If you lead engineers, you already know the temptation: solve the hard part yourself. That instinct fights when a vendor becomes your process — note 172.

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

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

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

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

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

Process should be light enough to change. If your AI workflow cannot be updated when a model, connector, or compliance rule changes, you do not have a workflow — you have a ritual.

On when a vendor becomes your process — note 172, 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.

Team literacy matters more than individual clever prompts. Shared harnesses beat private magic.

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.