London

June 28–29, 2027

New York

September 15–16, 2026

Berlin

November 9–10, 2026

What successful engineering organizations do differently with AI

Learn how leading engineering organizations measure AI ROI, improve team effectiveness, and turn growing AI investments into business value.

Speakers: Roman Musatkin

Register or log in to access this video

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
November 17, 2026
NYC 27 Pre sale ticket block image

AI is getting more expensive. Learn what the best engineering organizations do to make sure the spend pays off.

In many companies, AI spend already equals 20% of fully loaded headcount cost, and it’s only going to grow. That money buys real speed for individual engineers. But faster coding doesn’t automatically make an organization better at delivering software, and most teams have no clear way to tell whether the extra cost is paying off.

In this talk, Roman Musatkin, Head of Product & Design at Swarmia, shares what the most effective engineering organizations are doing differently. They’re building the system that builds the product: raising how much you can safely hand to agents, changing how teams work, and keeping quality high as more code and more actors move through the codebase.

He’ll introduce Swarmia’s Build framework, a practical way to look at AI leverage, engineering effectiveness, and return on engineering together, so you can make sure you’re focusing on what matters instead of chasing vanity metrics.

Key takeaways

You’ll walk away with:

  • A practical framework that contains three questions that matter: are we creating the conditions for AI to succeed, are we delivering value faster and sustainably, and what business value is all this engineering producing.
  • A concrete way to measure whether your AI spend is justified, including cost per pull request and AI cost per engineer, so you can bring a real number to your next budgeting conversation.
  • Three culture shifts you can try right away: prototype an end-to-end version before you prioritize, hand engineers open-ended problems instead of finished specs, and run small live sessions where product, design, and engineering build together instead of in sequence.

Promoted Partner Content