AI Fixed Code. Not Teams. How KPMG Stopped Handing Off.

​AI coding tools promise to collapse the distance between design and engineering. But in most large organizations, that distance isn't a tooling problem, it's a working-relationship problem. Designers hand off. Engineers rebuild. The loop is slow, the context gets lost, and the work that ships rarely resembles what was designed.

​At KPMG, a design lead and an engineer started working differently after adopting Builder. The designer stepped into branches, pull requests, and repos for the first time in a 25-year career, not to become an engineer, but to meet one in the middle. The engineer started receiving work that was already halfway home. A year in, they talk every day, ship faster together, and are now using Builder to develop an internal MVP platform for the firm.

​In this session, Matt Ardinger (Director, User Experience at KPMG US) and Abhijeet Rokde (Specialist Director, AI & Digital Solutions) join Builder for an honest conversation about what changed when their workflow stopped revolving around handoffs and started operating in a shared workspace. They’ll also talk about what it takes to make that shift actually stick inside an organization the size of KPMG.

​We'll cover:

• ​Why the design-to-engineering handoff is a relationship problem, not just a tooling one

• ​How Builder gave a senior designer a safe on-ramp to branches, PRs, and repos

• ​What engineers get back when designers work in a shared environment instead of throwing work over the wall

• ​How Builder fits alongside the tools engineers already love (Cursor, Claude Code, and others) rather than replacing them

• ​How this new way of working is holding up on a real, high-stakes internal build at KPMG