London

June 28–29, 2027

New York

September 15–16, 2026

Berlin

November 9–10, 2026

How to justify runaway AI coding tool budgets

How to measure ROI in numbers that survive the next budget review


Date & time

17:00

Register for the panel discussion

Login or join LeadDev.com to view this content

Create an account to access our free engineering leadership content, free online events and to receive our weekly email newsletter. We will also keep you up to date with LeadDev events.

Register with google

We have linked your account and just need a few more details to complete your registration:

Terms and conditions

 

 

Enter your email address to reset your password.

 

A link has been emailed to you - check your inbox.



Don't have an account? Click here to register

Enterprise spend on AI coding agents has roughly tripled in sixteen months, according to Gartner. By 2028, the average company’s AI coding costs will overtake the average developer’s monthly salary.

Yet, when asked about productivity, leaders can’t just point to adoption numbers. It’s time to explain how each tool, on each specific workflow, is worth the token spend. That means pinpointing improvements in throughput, incident rate, and release cadence to show real progress toward business goals.

In this panel, we will explore how to map developer coding tools — such as Cursor, GitHub Copilot, and Claude Code — to the delivery outcomes they actually move. This enables engineering leaders to walk into the next budget cycle with clear evidence of what’s worked and a plan for which of the next generation of coding agents to bring in.

Key takeaways:

  • How to tell which AI coding tools are actually earning their token spend
  • How to build an evaluation framework for the next generation of coding agents
  • How to bring your board a plan, not just a budget request

panelists:

Moderator: