AI Spurs A Cultural Shift In A 1,000-Developer Insurance Company

Team working on AI software development with multiple monitors showing code and data visualizations

For technology leaders, the main lesson is not the productivity number itself but the operating model behind it. When AI takes over code generation, testing and documentation, the value proposition shifts from โ€œfaster deliveryโ€ to โ€œwho is accountable for quality, architecture and risk decisions.โ€ CIOs and IT directors should ask which controls are still human-owned, which are delegated to tools, and how those decisions are audited.

This also changes what โ€œgood engineeringโ€ means. If developers move from writing code to prompting, reviewing and validating, the organisation needs a new skills framework, new performance expectations and new career paths. That raises a practical management question: are teams being measured on output volume, defect rates, cycle time or business outcomes? Without that alignment, speed gains can mask fragile delivery or shallow understanding of the systems being built.

The trade-off is velocity versus governance discipline. A phased human-in-the-loop model can build trust, but it also introduces ambiguity if escalation paths, approval thresholds and exception handling are not explicit. Leaders should define:

  • which applications or change types are eligible for autonomous generation
  • what architecture and security reviews remain mandatory
  • how model output is validated before release
  • which metrics prove benefits beyond anecdotal productivity

The next question for portfolio leaders is whether this capability should be scaled as a platform capability or remain a team-by-team experiment. If it becomes enterprise standard, governance, training and vendor oversight need to be centralised. If not, benefits may stay uneven and difficult to reproduce across domains.


 
Generative and agentic AI are taking up the lower-level tasks of software development, such as code generation, testing, and documentation, enabling the rapid delivery of software as needed. But can it perform on a massive scale, for a large enterprise? One major insurance company is finding out in an extensive pilot that employs autonomous software development tools. GNP Seguros, Mexicoโ€™s largest insurer, is seeing tangible results from its AI-assisted development work, with a five to ten-fold productivity boosts for its development teams. Thatโ€™s the word from Enrique Ibarra, CIO and head of business transformation for GNP, who has moved into autonomous software development in a big way, enabling its 1,000 developers to ramp up the speed and quality of their deliverables. โ€œWe want to change the role of humans in the software development process,โ€ he told Michael Krigsman, host of CXOTalk in a recent interview. โ€œWe want to do it to achieve agility. We wanted to test a new generation of tools for generating software in an autonomous way.” Between 80% and 95% of development work at GNP is now completed autonomously, Ibarra said. โ€œWe accelerated development velocity of between 5X and 10X. The human is not writing the code. The human is directing a platform on how to write the code. Thatโ€™s a huge change in paradigm.โ€ Moving to autonomous development isnโ€™t just about AI and underlying machines โ€“ itโ€™s success depends on the people who will move these projects forward. โ€œYou donโ€™t just flip a switch to full autonomy,โ€ said Ibarra. โ€œYou have to build trust through a phased human-in-the-loop approach.” Cultural change is a key and necessary part of the transformation. โ€œWe need to shift the engineering mindset,โ€ Ibarra said. โ€œWe have to train our engineers to transition from being creators to editors and orchestrators. It’s a different role.โ€ The human leaderโ€™s job, he added, โ€œnow becomes defining the prompt, reviewing the architecture, and validating the AI’s execution.โ€ Ibarra pushed back on the notion that AI may severely reduce opportunities for developers and IT professionals. Instead, roles are being redefined around direction, not coding, he said. The company is โ€œshifting engineers from line-by-line coding into prompt authorship, architecture review, and validation of autonomous output, with co-pilots handling any residual work.โ€
The Prompt: Get the weekโ€™s biggest AI news on the buzziest companies and boldest breakthroughs, in your inbox.
Developers will always be in great demand, he emphasized. โ€œIf youโ€™re going to develop a system, you need to provide technical guidelines. You need to provide guidelines related to the platforms where the software is going to run, and an end user cannot do that.” GNP deploys its systems in Google Cloud, requiring human knowledge about โ€œtechnical features and technical settings,โ€ he explained. โ€œYou need to enable in the cloud platforms in order for the system to run. An end user is not going to do that.โ€ The role changes completely, he added. “The human is not writing the code. The human is directing a platform on how to write the code. So thatโ€™s a huge change in paradigm.โ€
https://www.forbes.com/sites/joemckendrick/2026/05/27/ai-spurs-a-cultural-shift-in-a-1000-developer-insurance-company/

Enjoyed this article? Sign up for our newsletter to receive regular insights and stay connected.