AI-generated code: Business impact and costs
Expanded web report · Related PDF snapshot: 22 October 2026 · PDF page 11
Research reviewed 22 October 2026 · Evidence and editorial planning guidance are distinguished below.
The business process at risk
Applications that expose customer records, documents, account actions or administrative functions.
A feature can work correctly for its intended user while exposing another customer’s records. The business consequence depends on the reachable data and actions, not the size of the code change or the speed at which it was written.
Build an estimate from your own operation
Estimate interruption, investigation, recovery and continuing control costs separately. Use a range and state the assumptions. Avoid adding overlapping losses twice: an order delayed and later fulfilled is different from an order permanently lost. The report does not assign a universal dollar loss or a probability of breach.
- Interruption: affected transactions or staff hours × your measured contribution or cost, adjusted for work recovered later.
- Response: internal hours, specialist support, clean capacity and supplier coordination actually required.
- Recovery: rebuilding, validation, transaction reconciliation and customer support during the transition.
- Continuing operation: ownership, maintenance, access review and recovery testing after normal service returns.
Decisions for the operating team
- Identify the records and actions that must remain separate between customers or teams.
- Include misuse and exception scenarios in acceptance discussions with engineering.
- Assign a human owner for security-sensitive releases.
A scenario to rehearse
Illustrative exercise, not an observed customer incident: An invoice feature displays only the signed-in customer’s invoices, but its download endpoint accepts another customer’s identifier. The exercise verifies server-side ownership rather than relying on the filtered user interface.
Evidence before accepting the cost
A release policy linking business sensitivity to required review and evidence.
Compare immediate continuity work with longer-term architecture changes. Migration can reduce specific maintenance responsibilities, but it cannot replace investigation of an active compromise. Evaluate the controls and retained responsibilities of the proposed operating model, including recovery and exit.
Decision checkpoint
Are delivery targets rewarding speed while leaving nobody time to challenge the design?