We run SAP, Salesforce and Workday. How does your platform integrate with our estate — really, not on a slide?

The full executive answer

Let me split that precisely into what ships today and what is roadmap, because I will not blur that line. Today, three real integration surfaces. First, the MCP grounding plane — the emerging open standard for connecting AI systems to enterprise tools — which is how live data actually reaches the analysis: protocol-generic, read-only by policy, approval-gated by a second admin, with per-figure provenance tracking. Your Salesforce, SAP or Workday estate is reachable TODAY through an MCP server on your side of the fence, and governed CRM write-back rides the same plane with human approval. Second, live outbound notifications into Slack, Microsoft Teams, Google Chat, Discord and Zapier — incoming-webhook connectors that fan every catalogued platform event into the rooms where your executives live. Third, the developer surface: a versioned public REST API with an OpenAPI 3.1 specification, TypeScript and Python SDKs, signed outbound webhooks, and CSV plus Excel/Word/PowerPoint/PDF export out, CSV import in.

What I will NOT claim: native API adapters for Salesforce, HubSpot, Jira, ServiceNow, PagerDuty and Notion are catalogued and in development, not yet dispatching — the registry labels them exactly that way in the product, with the MCP path as the route to use today. SAP and Workday likewise have no native adapter, demand-sequenced rather than dated. The compensating controls are real, not hand-waving: the MCP plane covers grounded reads now, the Zapier connector and generic signed webhooks reach the iPaaS platforms your integration team already runs — Mulesoft, Boomi, Workato all speak REST and webhooks — and the OpenAPI spec means your team can generate a client for our API mechanically.

Architecturally we follow the TOGAF integration principle of standard interfaces over point-to-point spaghetti: everything flows through one documented event catalogue and one documented API surface, so adding an SAP connector later is another consumer on an existing backbone, not a new integration pattern. In the pilot, I would propose your integration team validates the webhook-plus-API path against one real system first.