The Agent Wars Are Over. The Substrate Wars Just Started
Three titan announcements in two weeks reveal what enterprise software vendors are actually fighting over in 2026, and it is not agents. If you have been tracking enterprise AI announcements through 2025, you have been watching a race about agent counts. How many prebuilt agents. How many industry-specific use cases. How many customer stories. Agents were the marketing, the demo, the SKU. A year of the same playbook. Something shifted in April 2026. Inside a two-week window, Salesforce, SAP, and ServiceNow each published an announcement that, at first glance, looks like more of the same agent theater. Salesforce launched Headless 360 at TDX 2026 and the Agentforce Experience Layer. SAP pushed a simplified-architecture argument alongside a persistent agent memory layer on BTP. ServiceNow rolled out Context Engine and, on its SPM community blog, Fred Champlain published an essay reframing governance itself as “strategic decision debt”. Different products. Different audiences. The same structural move. All three titans just walked one layer down the stack. Read individually, each announcement is a product release. Read together, they are a category shift. The competition is no longer about who has the best agent. It is about who owns the substrate those agents operate on. And each titan is staking a different piece of it. The Pattern Nobody Is Naming Strip the vendor branding from all three sets of material and the structural claim is identical: “Your agents are only as good as the layer underneath them. The data they ground on, the logic they inherit, the memory they carry, the permissions they respect, and the decisions they represent. That layer is what we...
Beyond the Honeymoon: Why Map Communications Bets on Zoho for a Decluttered Tech Stack
Recently, while on the ground in Austin, Texas, attending ZohoDay 2026, I had the pleasure of sitting down with Vaibhav Dani, the CEO of Map Communications. In the enterprise software ecosystem, we talk endlessly about digital transformation, but it is always refreshing to ground those lofty concepts in reality by speaking directly with the leaders navigating these complex implementations. Our conversation touched on a surprisingly common, yet notoriously difficult challenge: harmonizing a homegrown operational tech stack with off-the-shelf enterprise software. Map Communications’ journey with the Zoho ecosystem provides a masterclass in pragmatic architecture, the age-old “buy versus build” dilemma, and the foundational data hygiene required to actually make artificial intelligence work. TL;DR If you do not want to read this, here’s the full length video interview. Everybody else, please read on. The Business Context: Bespoke Service at Scale To understand their technology strategy, you first have to understand their business. Map Communications is a nationwide, employee-owned (ESOP) virtual receptionist and bespoke answering service operating across the US, Canada, and the UK. They serve a wide array of clients, ranging from legal firms and SMBs to large enterprises in various industries. Because their core service is highly specialized, Map relies on its own proprietary, homegrown software lineup to manage day-to-day operations and real-time answering services. However, when it comes to managing the customer lifecycle from the moment a prospect lands on their website to the execution of contracts and ongoing support, they rely on the Zoho suite. The Age-Old Dilemma: Buy vs. Build As businesses grow and their processes add complexity, leadership is inevitably faced with a choice: do we build custom modules...