Taking A 'Lego-Like' Approach: Why Enterprises Should Prioritize Stackable AI Agents

Enterprise AI is no longer a buzzword; it's an imperative part of business operations. Yet, for many organizations, the promise of intelligent automation is colliding with the hard reality that AI projects aren't generating ROI. In 2025, the grace period of "just figuring it out" is over. Many executives are now confronting a quiet truth—the ROI showcased in demos and marketing decks simply isn’t showing up in most applications. To combat the potential misallocation of capital, time, and resources, some organizations are still cautiously kicking the tires in limited, internal sandboxes.

The central challenge to ROI isn't a lack of vision, but the absence of a safe, scalable, and governable bridge from today's hype to tomorrow's ROI. The path forward, it turns out, may not be a revolutionary leap but a disciplined, architectural strategy that looks surprisingly familiar.

We spoke with Al Liubinskas, Vice-President and NA Cloud Integration Practice Lead at Capgemini, an executive who has spent over two decades architecting enterprise systems at scale. With his deep experience managing complex integration platforms like MuleSoft, TIBCO, and Apigee, Liubinskas argued that to understand the future of AI, we must start small and utilize a structured framework for turning AI into manageable, value-driven components. In other words, success comes from a Lego-like approach: assembling small, governed, stackable AI agents that can scale safely, deliver measurable value, and avoid the chaos of agent sprawl.

• The Lego block approach: "Companies will not hit a grand slam with one pitch," Liubinskas said. "I'm envisioning a Lego block model where you'll have an agent to create orders and another to offer different product options. It's a Lego approach versus having a sales agent that does everything from prospect to lead to order as one gigantic agent."

• Component-based architecture: According to Liubinskas, this modularity is also the key to accountability. "When something goes bad, there has to be a way of triaging what exactly happened. People want answers." He further argued that by putting it into a component-based architecture, it lets you scale when you want, how you want, without worrying about ruining the whole project in the process.

This Lego-like construction is a direct response to the primary hurdle facing enterprises today: scaling safely. While a proof-of-concept in a lab or sandbox is one thing, a production system that touches customers or sensitive data is another. For industry adoption, Liubinskas noted, there has to be a "guarantee of accuracy," which is precisely where enterprises are struggling. The delta between a demo and a deployed solution is vast.

• In the blind spot: "Everybody's focused on how to build the use case and get the use case working," Liubinskas said. "But to put it into production, it has to be bulletproofed, it has to be tested, and it needs to be effectively protected for the company that's providing that service."