Join the event trusted by enterprise leaders for nearly two decades. VB Transform brings together the people building real enterprise AI strategy.\u00a0Learn more<\/em><\/p>\n\n\n\n Over the last 100 years,\u00a0<\/span>I<\/span>BM\u00a0has seen many different tech trends rise and fall. What tends to win out are technologies where there is choice.<\/p>\n\n\n\n At VB Transform 2025 today, Armand Ruiz, VP of AI Platform at IBM detailed how Big Blue is thinking about generative AI and how its enterprise users are actually deploying the technology. A key theme that Ruiz emphasized is that at this point, it\u2019s not about choosing a single large language model (LLM) provider or technology. Increasingly, enterprise customers are systematically rejecting single-vendor AI strategies in favor of multi-model approaches that match specific LLMs to targeted use cases.<\/p>\n\n\n\n IBM has its own open-source AI models with the Granite family, but it is not positioning that technology as the only choice, or even the right choice for all workloads. This enterprise behavior is driving IBM to position itself not as a foundation model competitor, but as what Ruiz referred to as a control tower for AI workloads.<\/p>\n\n\n\n \u201cWhen I sit in front of a customer, they\u2019re using everything they have access to, everything,\u201d Ruiz explained. \u201cFor coding, they love Anthropic and for some other use cases like\u00a0 for reasoning, they like o3 and then for LLM customization, with their own data and fine tuning, they like either our Granite series or Mistral with their small models, or even Llama\u2026it\u2019s just matching the LLM to the right use case. And then we help them as well to make recommendations.\u201d<\/p>\n\n\n\n IBM\u2019s response to this market reality is a newly released model gateway that provides enterprises with a single API to switch between different LLMs while maintaining observability and governance across all deployments.\u00a0<\/p>\n\n\n\n The technical architecture allows customers to run open-source models on their own inference stack for sensitive use cases while simultaneously accessing public APIs like AWS Bedrock or Google Cloud\u2019s Gemini for less critical applications.<\/p>\n\n\n\n \u201cThat gateway is providing our customers a single layer with a single API to switch from one LLM to another LLM and add observability and governance all throughout,\u201d Ruiz said. <\/p>\n\n\n\n The approach directly contradicts the common vendor strategy of locking customers into proprietary ecosystems. IBM is not alone in taking a multi-vendor approach to model selection. Multiple tools have emerged in recent months for model routing, which aim to direct workloads to the appropriate model.<\/p>\n\n\n\n Beyond multi-model management, IBM is tackling the emerging challenge of agent-to-agent communication through open protocols.<\/p>\n\n\n\n \u00a0The company has developed ACP (Agent Communication Protocol) and contributed it to the Linux Foundation. ACP is a competitive effort to Google\u2019s Agent2Agent (A2A) protocol which just this week was contributed by Google to the Linux Foundation.<\/p>\n\n\n\n Ruiz noted that both protocols aim to facilitate communication between agents and reduce custom development work. He expects that eventually, the different approaches will converge, and currently, the differences between A2A and ACP are mostly technical.<\/p>\n\n\n\n The agent orchestration protocols provide standardized ways for AI systems to interact across different platforms and vendors.<\/p>\n\n\n\n The technical significance becomes clear when considering enterprise scale: some IBM customers already have over 100 agents in pilot programs. Without standardized communication protocols, each agent-to-agent interaction requires custom development, creating an unsustainable integration burden.<\/p>\n\n\n\n In terms of how Ruiz sees AI impacting enterprises today, he suggests it really needs to be more than just chatbots.<\/p>\n\n\n\n \u201cIf you are just doing chatbots, or you\u2019re only trying to do cost savings with AI, you are not doing AI,\u201d Ruiz said. \u201cI think AI is really about completely transforming the workflow and the way work is done.\u201d<\/p>\n\n\n\n The distinction between AI implementation and AI transformation centers on how deeply the technology integrates into existing business processes. IBM\u2019s internal HR example illustrates this shift: instead of employees asking chatbots for HR information, specialized agents now handle routine queries about compensation, hiring, and promotions, automatically routing to appropriate systems and escalating to humans only when necessary.<\/p>\n\n\n\n \u201cI used to spend a lot of time talking to my HR partners for a lot of things. I handle most of it now with an HR agent,\u201d Ruiz explained. \u201cDepending on the question, if it\u2019s something about compensation or it\u2019s something about just handling separation, or hiring someone, or doing a promotion, all these things will connect with different HR internal systems, and those will be like separate agents.\u201d<\/p>\n\n\n\n This represents a fundamental architectural shift from human-computer interaction patterns to computer-mediated workflow automation. Rather than employees learning to interact with AI tools, the AI learns to execute complete business processes end-to-end.<\/p>\n\n\n\n The technical implication: enterprises need to move beyond API integrations and prompt engineering toward deep process instrumentation that allows AI agents to execute multi-step workflows autonomously.<\/p>\n\n\n\n IBM\u2019s real-world deployment data suggests several critical shifts for enterprise AI strategy:<\/p>\n\n\n\n Abandon chatbot-first thinking<\/strong>: Organizations should identify complete workflows for transformation rather than adding conversational interfaces to existing systems. The goal is to eliminate human steps, not improve human-computer interaction.<\/p>\n\n\n\n Architect for multi-model flexibility<\/strong>: Rather than committing to single AI providers, enterprises need integration platforms that enable switching between models based on use case requirements while maintaining governance standards.<\/p>\n\n\n\n Invest in communication standards<\/strong>: Organizations should prioritize AI tools that support emerging protocols like MCP, ACP, and A2A rather than proprietary integration approaches that create vendor lock-in.<\/p>\n\n\n\n \u201cThere is so much to build, and I keep saying everyone needs to learn AI and especially business leaders need to be AI first leaders and understand the concepts,\u201d Ruiz said.<\/p>\n Daily insights on business use cases with VB Daily<\/strong><\/p>\n If you want to impress your boss, VB Daily has you covered. We give you the inside scoop on what companies are doing with generative AI, from regulatory shifts to practical deployments, so you can share insights for maximum ROI.<\/p>\n \n\t\t\t\t\tThanks for subscribing. Check out more VB newsletters here.\n\t\t\t\t<\/p>\n An error occured.<\/p>\n<\/p><\/div>\n
\n<\/div>The Multi-LLM gateway strategy<\/h2>\n\n\n\n
Agent orchestration protocols emerge as critical infrastructure<\/h2>\n\n\n\n
AI is about transforming workflows and the way work is done<\/h2>\n\n\n\n
Strategic implications for enterprise AI investment<\/h2>\n\n\n\n
![\"\"\/](\"https:\/\/venturebeat.com\/wp-content\/themes\/vb-news\/brand\/img\/vb-daily-phone.png\")
\n\t\t\t\t<\/div>\n<\/p><\/div>\n<\/div>\t\t\t<\/div>\r\n