SaaS Ecosystem Interoperability

Today, B2B SaaS products perform impressively in isolation, providing functionality, efficiency and productivity gains. But they don’t play well with others. Vendors know they need to offer a wide set of native integrations, but that’s getting harder to achieve. As the B2B tech stack swells (the average business uses 371 SaaS apps), the number of integrations vendors need to build is skyrocketing. In the coming decade, this problem will increase even further as B2B software will operate across thousands of highly specialized applications. These systems won’t just coexist, they’ll need to interoperate in real time, across dynamic, evolving workflows. Current SaaS architectures struggle with integration complexity. Fragmented stacks, ad hoc APIs, and manual workarounds introduce bottlenecks at scale. To fully unlock the value of SaaS, vendors require infrastructure that abstracts the burden of bespoke integration development. Legacy solutions fall short: Embedded iPaaS enables point-to-point connectivity but lacks scalability and maintainability. Unified APIs offer abstraction, but constrain customization and depth of integration due to rigid schemas. What’s needed is a universal, API-agnostic integration layer, one that enables composable, reusable logic across heterogeneous systems at scale with hundreds of apps. At Integration App, we’re building exactly that. Our platform introduces a standardized integration framework that decouples integration logic from underlying APIs. Using AI, we generate adaptive, app- and tenant-specific implementations, allowing developers to build complex, multi-surface integrations with minimal overhead. This architecture dramatically reduces time-to-integration, supports scalable extensibility, and aligns with modern expectations for one-click deployments and dynamic orchestration. SaaS value is shifting from standalone features to ecosystem interoperability. The next generation of platforms will be defined by how well they connect.

What’s the #1 reason SaaS companies struggle to expand outside their home market? Most think it’s about product-market fit. Others believe it’s a sales execution problem. But the biggest issue? They try to build everything themselves instead of integrating into existing ecosystems. Too many SaaS companies believe they need to own the full stack to win in a new market. But here’s the truth: Customers don’t want an all-in-one suite—they want best-of-breed tools that work together seamlessly. Building everything in-house isn’t just expensive—it adds friction for customers: • Instead of making adoption easier, it forces users to abandon proven workflows • Instead of accelerating time-to-value, it delays innovation and go-to-market speed • Instead of focusing on differentiation, companies get caught in an endless feature war And here’s the biggest risk: If your product doesn’t integrate into the existing ecosystem, your competitors will. Instead of fighting for market share by reinventing the wheel, the winning approach is partnering with key local players while doubling down on unique value. • You focus on what makes you different (proprietary data, customer relationships) • You integrate with established players instead of forcing customers to switch • You remove friction, making adoption seamless and increasing retention This is what forward-thinking SaaS companies are doing today. They don’t treat partnerships as a workaround—they bake them into their GTM strategy from day one. How we apply this at Personio in the Benelux👇 When expanding in the Netherlands, we don’t try to compete with existing payroll solutions—we partnered with them. Like our strategic partnership with loket.nl a leader in the Dutch payroll space. • We focus on what we do best: delivering a world-class HR solution • We integrate payroll instead of competing, making adoption frictionless • Customers win—payroll just works, no extra effort required The Future of GTM: Compound Partnerships The best GTM teams aren’t trying to own every function—they’re building ecosystems that remove friction for customers. • Find partners that complement your core offering instead of building everything yourself • License, integrate, and co-brand where possible—let customers choose the best-fit tools • Go-to-market isn’t just sales & marketing—it’s about reducing friction Very excited about our strategic partnership with loket.nl. From our first conversations this partnership feels strong. Also excited about something unique is coming up for the Dutch market. But as with everything, we are building step-by-step; hand-in-hand with our mutual customers. Let’s go Marc, Luuk and team loket.nl 🤝

Everyone is talking about AI agents. Far fewer are discussing what agents actually require in order to function reliably at scale. Agents do not “𝘶𝘯𝘥𝘦𝘳𝘴𝘵𝘢𝘯𝘥 𝘵𝘩𝘦 𝘸𝘦𝘣” (just yet) the way humans do. They cannot interpret design intent, navigate visual hierarchies, or tolerate ambiguity. They require structure, standards and predictable contracts. An agent that is expected to compare products, trigger payments, coordinate with other systems, or execute multi-step workflows cannot depend on scraping HTML and inferring intent from loosely structured pages. HTML is built for rendering. Not for reasoning. From an agent’s perspective, the open web is noisy and inefficient: • Navigation elements clutter the signal • Cookie banners and pop-ups interrupt flows • JavaScript-heavy pages break deterministic parsing • Layout changes alter DOM structure • Hidden elements can inject malicious prompts Agents need clean access to clearly defined data fields, authentication logic, and execution rules. They need machine-readable schemas, explicit permissions, and deterministic APIs. Without that, reliability collapses. This is precisely why we are seeing a rapid influx of new standards and protocols: MCP, UCP, A2A, etc. Each of these attempts to define a shared language for how agents access data, verify identity, coordinate actions, and execute transactions across systems. Protocols are not cosmetic layers. They define interoperability. And interoperability determines whether agents can operate across platforms without brittle, custom integrations. There is, however, another dynamic at play: Large platform providers are not only solving technical problems. They are positioning themselves at the coordination layer. Whoever defines the protocol influences: • How value flows • Where transactions are completed • Which data becomes visible • Who controls identity and authentication This partly explains why we are seeing multiple “open” standards emerge simultaneously. Each ecosystem aims to anchor the agentic stack around its own infrastructure. Which of these protocols will ultimately dominate remains uncertain. For companies, the practical challenge is immediate: • Where do you integrate? • Do you prioritise MCP because it is widely adopted in model ecosystems? • Do you align with UCP because of its commerce implications? • Do you architect for multi-protocol compatibility from the outset? There is no universally correct answer today. What is clear, however, is that agents fundamentally depend on structured data and standardised access layers. If you focus on: • Clean entity modelling • Consistent schema • Well-documented APIs • Stable authentication flows • Modular system design … then protocol choice becomes an integration decision. Agents cannot reason over branding alone. They require structured, accessible, machine-readable data. And that is the foundation of the agentic stack I've been talking about.

Google Cloud NEXT '26 just raised the bar for enterprise agentic AI — and the signals are clear for where the industry is heading. The headline announcement was the Gemini Enterprise Agent Platform — providing the most comprehensive, integrated approach to agentic AI that brings together everything enterprises need to build, scale, govern, and optimize agentic deployments at scale — not as a collection of loosely coupled or discrete solutions for different phases of the agent lifecycle, but as a packaged stack — developer tools, agent frameworks, agent protocols, runtime capabilities (memory, context, state, orchestration), evals, security, and observability — all bundled into a coherent platform story. Infrastructure is the other half of the equation. 8th-generation TPUs, new storage and networking capabilities, and deep integrations and optimization with Kubernetes for Agentic AI positions Google Cloud as a genuine one-stop shop for development, training, inference, and scaling of agentic systems at enterprise grade. Google Workspace completes the loop. The new Workspace Intelligence capabilities bring agentic AI directly into the digital workflow layer — emails, meetings, files — grounding agents in the deep semantic context of how knowledge actually flows in an organization. But the most strategically important signal for ISVs and SaaS partners is Google's explicit commitment to an open, interoperable ecosystem built around this platform. Partner-built agents from the Agent Marketplace are now available directly inside the Agent Gallery in the Gemini Enterprise app — with partners like Dynatrace, Salesforce, ServiceNow, and Workday natively running within the Gemini Enterprise Agent Platform alongside custom internal builds in a single cohesive ecosystem. This signals a fundamental shift in the SaaS business model. The next evolution isn't just about buying and running SaaS platforms through cloud — it's about transacting agents and agentic capabilities of these ISVs with and through these marketplaces and enabling agent-to-agent collaborations across the ecosystem. The agent marketplace is now evolving into the new agent distribution layer. At Dynatrace, we're proud to be among the early partners of the Gemini Enterprise Agent Platform and agent marketplace — bringing our observability capabilities to auto-protect, auto-remediate, and auto-optimize agentic stacks at enterprise scale. Dynatrace for Gemini Enterprise integrates AI agents with Dynatrace observability data via the Gemini Enterprise Agent Platform and A2A protocol — enabling real-time insights into performance, infrastructure, and user experience, seamlessly enhancing AI workflows while ensuring enterprise-grade security and compliance. Looking forward to continued collaboration and co-innovation with Google Cloud. Exciting times ahead. 🚀. #GCPNext #AgenticAI #GoogleCloud #GeminiEnterprise #Dynatrace #AIObservability #PartnerEcosystem #EnterpriseAI

Why is Interoperability a Challenge When Integrating New Digital Solutions into Existing Enterprise Architecture?   14 Comprehensive Interoperability Challenges
   Integrating new digital solutions into established enterprise architectures is rarely a plug-and-play exercise. Industry leaders in banking, manufacturing, and telecom routinely face a 20–40% surge in costs and 6–18 month delays when stitching modern tools into legacy ecosystems—not due to technical complexity alone, but fractured processes, misaligned incentives, and hidden dependencies. From brittle API handshakes to cultural resistance, interoperability failures erode ROI, trigger compliance risks, and stall innovation. This breakdown uncovers the 14 root causes behind these setbacks, grounded in billion-dollar transformation lessons, and maps actionable fixes to turn integration roadblocks into strategic leverage.     14 Key Challenges (Exhaustive List) 1.    Heterogeneous Legacy Footprint Multi-generational systems (mainframes, COBOL, on-prem apps) clash with modern architectures (cloud, microservices). Protocol translation layers add complexity.   Impact: Increases integration costs by 40–60% and delays time-to-market by 6–12 months due to protocol translation and re-engineering.   2.    Proprietary Vendor Lock-In Closed APIs, proprietary SDKs, and OEM middleware trap organizations in costly ecosystems.   Impact: Forces reliance on costly vendor-specific tools, inflating TCO by 25–35% annually for middleware/reverse-engineering.   3.    Data Schema Misalignment Decades-old data models with conflicting naming conventions (“Customer_ID” vs. “ClientNum”) slow integration velocity.   Impact: Slows integration velocity by 30–50% as teams wrestle with manual data mapping and governance gaps.   4.    Embedded Business Logic Dependencies Critical rules (credit-scoring, order-routing) buried in legacy code create brittle integrations and outages.   Impact: Triggers 2–4x annual production outages when hidden legacy dependencies collide with new workflows.   5.    Inconsistent Security Posture Legacy SAML/perimeter security vs. modern OAuth2/zero-trust frameworks—reconciliation drains budgets.   Impact: Adds 30–40% to security budgets as teams reconcile SAML/OAuth2, encryption, and zero-trust policies.   Example: A bank ignoring Embedded Business Logic Dependencies faced $4M in outage costs during a core banking upgrade. Fixing it post-fact cost 3x the proactive refactor estimate.   Final Note: Every challenge here has derailed actual projects. Addressing all 14 ensures resilience—not just quick fixes. Detailed list with “Leadership Action Plans” is available in our Premium Content Newsletter. Do subscribe.   Image Source: Leading Practice     Transform Partner – Your Digital Transformation Consultancy

Learned something wild from a Senior Product Manager at a $2B SaaS co the other day. They had 8 product teams dedicated to building integrations. One PM per team plus 5-10 engineers. That’s 48-88 heads on recurring payroll. Likely 💰 $7-13M 💰 annual headcount cost. Their goal was to have full integration coverage to meet customer demand. Yielding major sales and retention benefits over their competitors 📈. But they ran into some issues: ➡️ Integrations take a long time to build, test, deploy, update ➡️ They weren’t getting them right - they aren’t SMEs on third party products ➡️ Hard to get customers to use them once built ➡️ They thought a few dozen integrations would do the trick, but turns out hundreds and eventually thousands are needed The overarching problem was the lack of scalability in their approach. More integrations = more heads on payroll. Eventually they said enough is enough, let’s open this thing up and crowdsource integrations. So they enhanced their API infrastructure, pieced together a developer portal and built a publishing mechanism for their app marketplace. It was a big bet. But the inbound demand was there… third party devs were ready/willing to build. Now, they’re delivering integrations at an exponential rate. They’re not limited by the capacity of their internal team. The idea of having thousands of integrations is no longer a pipe dream. It’s just a matter of time. At Partner Fleet, we believe the decision to “open up” should not be a big, expensive bet. Every SaaS company should have the opportunity to create an integration ecosystem without spending millions to build the infrastructure from scratch. Our mission is to make this strategy accessible to anyone who wants to pursue it.

Concise synthesis | EU #DataAct & #cloud #interoperability (Article 35) Key #takeaways from the European Commission’s Study on Interoperability of data processing services (Final report, Nov 2025), supporting the setup of the Union #repository for open specifications and harmonised #standards under the Data Act: ▪︎ Strategic purpose: The study supports the Commission in operationalising Article 35 and preparing the first batch of references (open specs / harmonised standards) for publication in the Union repository. ▪︎ Why it matters: The Data Act targets #cloud switching, #portability, and #interoperability (especially for #PaaS/#SaaS) as core enablers of competition and multi-cloud adoption. ▪︎ #Compliance effect: Once a relevant standard/specification is listed in the repository, providers must ensure compatibility within 12 months. ▪︎ Methodology contribution: The study builds an evaluation methodology combining #CAMSS and Data Act-specific criteria (plus Annex II of Regulation 1025/2012) to assess candidate standards/specifications. ▪︎ Two-step screening approach: ◇ Step 1: governance/coherence/maturity (CAMSS-based) ◇ Step 2: operational compliance with Article 35 (portability, interoperability, security/integrity, innovation, functional equivalence where relevant) ▪︎ Stakeholder-driven prioritisation: Inputs came from interviews, survey, and workshop; the study prioritised generic standards and more focus on PaaS (vs. case-specific SaaS). ▪︎ Initial candidates identified (for possible repository inclusion): OpenAPI, SECA, OCI, OASIS TOSCA, JSON/XML (with overlap considerations), and SQL (with versioning caveats). ▪︎ Gap analysis outcome: The #report highlights areas where new standardisation work may be needed, notably around federated/delegated IAM interoperability (e.g., building on OAuth/OIDC/SAML). ▪︎ Practical implementation support: The study also proposes processes for future screenings and contributes to the design/specification of the online repository platform. This is a foundational step toward making Data Act interoperability obligations practical, testable, and enforceable across the EU cloud ecosystem. https://lnkd.in/da9ZCF2D

Why do most b2bSaaS companies fail to achieve their partner ecosystem potential? ➡️ Most rely on loosely coupled partner networks that dont unlock enough value to justify the partnering investment. Hence the partner team layoffs. 🔑 The only solution is to move from loosely to tightly aligned ecosystems built on common objectives and coordinated and programmatic execution. Loosly coupled ecosystems typically consist of partners aligning on mutual value and better together stories without the benefit of clear and consistent playbooks that work for all parties in the ecosystem. Simply put, they fail to design programs and processes that deliver a win/win/win approach. 🎯Partnering strategies must focus instead on finding tightly coupled commercial & engagement models that align all players on common metrics and models and win/win outcomes. A good example of this is the Hyperscaler consumption metric. Here all players in the ecosystem see the value in achieving the common goal of more consumption and aligning to a program that ensures a win for the ecosystem and its joint customers. 🧐 Another example is a strategic alliance GTM (between two or more SaaS companies) that share a single, common playbook and execution plan that monetizes the alliance leveraging a shared sales & services channel. I’d love to hear your reflections on other tightly-aligned partner networks that are unlocking partner ecosystem potential. #ecosystemorchestration

AI Agent interaction is going to be one of the most interesting software interoperability paradigms of the future. Inevitably, no one software system contains all the knowledge or information to perform all the tasks that an enterprise or users needs. This means we’ll need AI Agents to coordinate and do work together. Since the influx of modern APIs with the rise of cloud and SaaS, software interoperability has been a relatively solved problem. Most modern software offers a set of APIs and we know how to get our technologies to talk to each other in deterministic ways. AI Agents, on the other hand, offer a new era in web interoperability to coordinate non-deterministic work. No longer is one system making precise calls to another system, but instead we’ll have AI Agents that process requests from a user (or system), farm out requests to Agents in other systems as relevant, then return an answer or result back to the user with further judgment applied. For instance, you may ask Salesforce a question about a customer and an Agent will combine in an answer from Agents that review contracts in Box or billing info in Stripe. Or, you’re onboarding as a new employee and you ask an Agent a question in ServiceNow, which fans out to HR documentation in Box or data in Workday. Or you want to build software with Replit or Devin, and the Agent talks to Agents in Box for product specs, project plans in Asana, or design assets in Figma. Agents in this case would operate in a very similar fashion to how another human would interact between different software tools. Doing a search between different apps, reviewing the data, and then collating it back in a final format. Of course there are many open questions in this new era of software. Will Agent interoperability work on a bidirectional way, or will one Agent always take the lead? How do we seamlessly handle permission access between systems What is the business and financial model of a world with Agents running around doing work for us between systems? How do we ensure accuracy on results and not have incremental hallucination or mistakes at each step? As an industry, we’ll have to work to make this insanely seamless for customers, but definitely one of them most exciting paradigm shifts.

Venture capital and media attention fixate on foundation model capabilities, but the competitive battleground in AI has shifted to the unsexy, boring parts of AI - things like orchestration layers, retrieval systems and connective infrastructure. Organisations do not deploy “a model”. They deploy workflows integrating models with proprietary data, existing software systems, human review processes, compliance controls and operational monitoring. The sophistication of this second-order infrastructure increasingly determines who wins in AI deployment. The Model Context Protocol exemplifies this shift. By providing a standardised interface for AI systems to connect with external tools and data sources, MCP solves the “M times N” problem that plagued earlier integration efforts. Connecting M models to N tools previously required M times N custom integrations, each demanding bespoke engineering, testing and maintenance. MCP reduces this to M plus N by providing a common protocol. The seemingly technical detail of interoperability standards enables the ecosystem effects that allow agentic AI to scale across organisations and use cases. Retrieval-Augmented Generation represents another critical infrastructure layer. Generic models know only what appears in their training data. Enterprise value requires grounding AI responses in current, proprietary organisational information. RAG systems retrieve relevant context from document stores, databases and knowledge graphs, then inject that context into the model’s reasoning process. The engineering required to make this work reliably encompasses vector databases, embedding models, semantic search, ranking systems, access controls and cache management. These components are invisible to end users but determine whether an AI system produces valuable insights or expensive nonsense. The orchestration market has grown explosively as organisations recognise that managing multiple specialised models and tools requires sophisticated coordination. Rather than forcing every query through a single expensive frontier model, orchestration systems route requests intelligently. Simple queries go to fast, cheap models. Complex reasoning tasks go to sophisticated models. Specialised tasks go to fine-tuned domain models. This arbitrage across model capabilities and costs determines the unit economics of AI deployment. These systems sit between enterprise users and external AI providers, enforcing usage policies, managing costs, logging interactions for audit and blocking potentially harmful outputs. Deploying AI without a gateway has become as negligent as deploying web servers without firewalls. The governance, compliance and risk management capabilities embedded in these infrastructure layers determine whether enterprises can scale AI deployment while maintaining controle. The companies building superior connective tissue will matter more than those training marginally better models.