Winners in enterprise software become ecosystems. What is your platform-and-ecosystem play beyond your own features?

The full executive answer

The ecosystem primitives are already shipped, which is unusual pre-launch and deliberate. Developer surface: a versioned public REST API documented with OpenAPI 3.1, official TypeScript and Python SDKs in the repository, per-key scopes and rate limits, and signed webhooks for every catalogued platform event — everything a partner needs to build on us without asking permission. Integration surface: one MCP grounding plane — the emerging open standard for connecting AI systems to enterprise tools — protocol-generic, approval-gated and provenance-tracked, which is how live enterprise data reaches the analysis today; live chat notification connectors into Slack, Teams, Google Chat, Discord and Zapier; and six API adapters (Salesforce, HubSpot, Jira, ServiceNow, PagerDuty, Notion) catalogued as in-development with the MCP path as the route today — the registry says exactly that, because integration claims match dispatch reality here.

The staged play from here: today, integrate-out — our events and insights flow into your existing tools, lowering adoption friction. Next, build-on — partners and customers consuming the API and SDKs for their own workflows; the OAuth application framework for a marketplace already exists in the codebase as scaffolding. Then, the network layer: anonymised cross-organisation benchmarking, where the aggregate becomes a data asset no single customer or competitor can replicate — the classic ecosystem moat.

Honest sequencing: a marketplace with revenue share is a scale phenomenon, not a launch feature — platform strategy research is clear that forcing the ecosystem before liquidity fails. What matters now is that the technical substrate — API, events, SDKs, OAuth framework — will not need re-architecture when demand arrives. It will not.