AI Agents That Don't Slash Maintenance Costs Will Sink Your Team

James Shore drops a critical take for teams adopting AI coding agents: if your agent doesn't reduce maintenance costs proportionally to its speed gains, you're digging a hole. He models the math bluntly — and it's ugly.

Maintenance costs dominate long-term productivity

Shore uses a crowd-sourced model: for each month of writing code, expect 10 days of maintenance in the first year, then 5 days per year forever. Simulated over 10 years, teams spend >50% of time on maintenance after 2.5 years. Halving maintenance estimates buys 3 more years before hitting 50%. Doubling them pushes the team below 50% in under a year.

The AI trap: speed now, pain forever

Shore's extreme example: your AI doubles output but also doubles maintenance cost per line. Result — after ~5 months, productivity drops back to baseline. A few months more, and you're worse off than never using the agent. Even if AI code matches human maintainability, the productivity gains erode over time as the maintenance burden compounds.

“You produce two months of work in a month, and each 'month' of output costs twice as much to maintain. Next month's maintenance costs quadruple.”

You can't go back

If you drop the agent, the speed benefit vanishes — but the accumulated higher maintenance costs remain. You've permanently indebted your future productivity for a temporary boost.

Takeaway for teams

Shore's core message: demand AI tools that reduce maintenance costs, not just write code faster. Measure maintenance burden per feature. If your agent's output isn't significantly cheaper to maintain per unit of functionality, you're trading short-term speed for long-term pain.

The full post (link below) includes a spreadsheet model to run your own numbers.