Software and digital products
A release is ready before the product team arrives. The tests pass. The unresolved decision is whether the change serves the customer.
- Cheaper to produce
- A tested, staged change, with its investigation, specification and rollback plan.
- Still scarce
- Distribution, customer relationships and engineers who have learned through real design, debugging and incident work. Demand decides whether faster delivery means better products or only more output.
- What the next attempt knows
- How this system fails in practice: which changes caused incidents and which fixes held.
- A person still answers for
- Whether this release serves the customer. Security and reliability teams can still stop it on their own authority.
- Public signal
- GitHub’s May 2025 coding-agent launch put issue-to-PR work inside a human-controlled review workflow. I1 · Human-reviewed coding workflow.
Source detail · building instead of buying
Among respondents whose organisations regularly used AI in at least one business function, 32% said they had decided against buying one or more additional software products or features in favour of building the functionality in-house with AI coding tools. E8
McKinsey, The state of AI in 2026, Exhibit 4, p.9 · fieldwork May–June 2026 · overall survey N 1,719; question-specific N not disclosed. A forgone addition is not the same as replaced software, displaced spending or a successfully maintained deployment.