Legacy Modernisation #
- Case Study: Achieving 50% Faster Legacy Modernisation with AI-Driven Engineering (Codurance, 2026) — Published case study: 50% faster legacy modernisation through structured AI-driven engineering. Key methodology elements: human engineers retain architectural oversight; AI handles the mechanical transformation work under spec-driven constraints. Codurance (engineering consultancy) framing situates this in the “agentic engineering” paradigm: supervision not abdication.
- Legacy System Modernization with AI: A Complete 2026 Guide (Stromasys, 2026) — Market sizing: global legacy modernisation market at $29.39B in 2026, growing at 17.64% CAGR. The structural driver: enterprises spend 72% of IT budgets maintaining legacy systems, creating a trapped-capital dynamic where modernisation ROI is compelling but risk-aversion delays it. AI is reducing perceived migration risk by offering lower-cost pilots before full commitment.
Enterprise Adoption Patterns #
- AI Coding Impact 2026 Benchmark Report (Opsera, 2026) — The enterprise adoption paradox in hard numbers: AI generates 42% of code; PR cycle time is 20% faster; incidents are up 23.5%; failure rates up 30%. The critical finding for this topic: AI-generated PRs wait 4.6× longer in review and introduce 15–18% more security vulnerabilities. The governance gap is not just a narrative — it is a measured quality deficit that manifests in production.
- Claude Enterprise Guide 2026: Deployment & Training Specs (IntuitionLabs, 2026) — Enterprise teams are transitioning from “chat-first experimentation” to “permanent repeatable infrastructure.” The organisations deploying AI reliably are encoding standards in shared skills files and CLAUDE.md templates, not improving prompts. Companies achieving the most reliable outcomes are those that treat AI tooling as infrastructure requiring configuration, not assistants requiring persuasion.
Cross-links #
- Vibe Coding Approaches Opsera’s productivity paradox data (42% AI code, 23.5% more incidents) is directly relevant; the vibe-coding-applications dimension is how organisations are responding to this data — with governance infrastructure, not by reducing adoption.
- Team & Org Use of Claude The “encoding internal standards” pattern from the enterprise deployment guide maps to the skills-replacing-prompts pattern in claude-teams; both reflect the same organisational learning.
- Emerging theme: The Codurance case study is the first independently published legacy modernisation outcome with a specific percentage gain (50%) using current agentic tooling. The number is headline-worthy but the methodology note (structured oversight, not AI autonomy) is the important part — it corroborates the spec-driven governance pattern rather than the vibe-coding model.
- Emerging pattern: The 72% of IT budgets on legacy maintenance is a structural pressure that makes the ROI calculation for AI-assisted modernisation compelling regardless of governance readiness. Organisations may adopt before governance infrastructure is in place because the cost of maintaining legacy systems exceeds the risk tolerance for AI-generated quality issues.