The New Compact: What Suppliers Owe Consumers When Customers Can Build Anything

For decades, the relationship between technology suppliers and enterprise consumers ran on a simple exchange: customers described what they needed, suppliers built it into the roadmap, and everyone waited. Mythos-class AI ended that arrangement. Enterprise teams can now write virtually any feature, integration, or workflow they need — in days, not quarters. The feature request is dying. What customers cannot write for themselves is the thing underneath: the platform, the telemetry, the supported surfaces, and the trust that what they build will run safely on infrastructure the supplier stands behind.

This session puts both sides of the new compact on the same stage. Tom Gillis and a senior Anthropic executive represent the platform providers — the network and security infrastructure the enterprise runs on, and the AI systems the enterprise builds with. Tsvi Gal and Bala Vaidyanathan represent the consumers — enterprises that are no longer waiting for roadmaps, and whose internal teams now extend, automate, and reshape their environments directly.

Together they work through what each side now owes the other:

• From roadmaps to platforms. If customers build the features, what is the supplier’s product? Open APIs, rich telemetry, stable and supported extension points — and what happens to vendors whose value was the feature list.

• The support and accountability question. When a customer-written agent misconfigures a production network, who owns the outcome? What does “supported” mean when the supplier didn’t write the code running on its platform?

• Co-engineering as the new normal. The patch storm forced suppliers and consumers to operate as one team — prioritized remediation lists, shared tooling, joint cadences. Which parts of that wartime relationship should become permanent?

• What consumers must bring. Platform access is not a one-way demand. Enterprises must invest in verification, guardrails, and the engineering discipline to be a safe co-developer on someone else’s platform.

• The economics. What does pricing, licensing, and the vendor relationship look like when value shifts from features delivered to platform capability exposed?

The promise of the session: a frank negotiation, in public, of the new terms between the companies that provide the platforms and the enterprises that now build on them — with both sides saying out loud what they need the other to do differently, starting now.