In-Ear Insights: Switching AI Providers, Backup AI Capabilities

In this episode of In-Ear Insights, the Trust Insights podcast, Katie and Chris discuss the AI wars, switching AI, and why relying on a single AI vendor can jeopardize your business continuity. You’ll discover how to build an abstraction layer that lets you swap models without rebuilding your workflows and see practical no‑code tools and open‑weight models you can use as a safety net. You’ll understand the essential documentation and backup practices that keep your AI agents running. Watch the full episode to protect your AI strategy. Watch the video here: Can’t see anything? Watch it on YouTube here . Listen to the audio here: https://traffic.libsyn.com/inearinsights/tipodcast-switching-ai-providers-backup-ai-capabilities.mp3 Download the MP3 audio here . Need help with your company’s data and analytics? Let us know! Join our free Slack group for marketers interested in analytics! [podcastsponsor] Machine-Generated Transcript What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for listening to the episode. Christopher S. Penn: In this week’s In Ear Insights, it is the AI Wars. Katie, you had some thoughts and some observations about the most recent things going on with Anthropic, with OpenAI, with Google XAI and stuff like that. So at the table, what’s going on? Katie Robbert: I don’t want to get too deep into the weeds about why people are jumping ship on OpenAI and moving toward the cloud. That’s in the news, it’s political, you can catch up on that. The short version is that decisions from the top at each of these companies have been made that people either agree with or don’t based on their own values and the values of their companies. When publicly traded companies make unpopular decisions that don’t align with the majority of their user base, people jump ship. They were like, okay, I don’t want to use you. We’ve seen it with Target and many other companies that made decisions people didn’t feel aligned with their personal values. Now we are seeing people abandoning OpenAI and signing on to Anthropic’s Claude. That’s what I wanted to chat about today because we talk a lot about business continuity and risk management. What happens when you get too closely tied to one piece of software and something goes wrong? We’ve talked about this on past episodes in theory because, up until now, software outages have generally been temporary. You don’t often see a mass exodus of a very popular piece of software that people have built their entire businesses around. Before we get into what this means for the end user and possible solutions, Chris, I would like to get your thoughts, maybe your cat’s thoughts on what’s going on. Christopher S. Penn: One of the things we’ve said from very early on in the AI space, because it changes so rapidly, is that brand loyalty to any vendor is generally a bad idea. If you were a hater of Google Bard—for good reason—Bard was a terrible model. If you said, I’m never going to touch another Google product again, you would have missed out on Gemini and Gemini 3 and 3.1, which is currently the top state‑of‑the‑art model. If you were all in on Claude, when Claude 2.1 and 2.5 came out and were terrible, you would have missed out on the current generation of Opus 4.6 and so on. Two things come to mind. One, brand loyalty in this space is very dangerous. It is dangerous in tech in general. Not to get too political, but the tech companies do not care about you, so there’s no reason to give them your loyalty. Second, as people start building agentic AI, you should think about abstraction layers. This concept dates back to the earliest days of computing: we never want to code directly against a model or an operating system. Instead we want an abstraction layer that separates our code from the machinery. It’s like an engine compartment in a car—you should be able to put in a new engine without ripping apart the entire car. If you do that well when building AI age

Listen