OpenAI Made Its Enterprise Commitment Spendable on Adobe, Figma and Salesforce. 32 Partners Signed On to a New Meter.

OpenAI used its Tuesday keynote in San Francisco to ship a lot of things, but the one that matters most is the one that carries almost no product surface. It is called the OpenAI Marketplace, and it lets eligible enterprise customers apply part of their existing OpenAI spending commitment toward approved software from a launch cohort of 32 outside vendors. Adobe, Figma, Salesforce, ServiceNow, HubSpot, Datadog, Palo Alto Networks, CrowdStrike, Harvey, Legora, Sierra, Decagon, Baseten, DevRev, Glean and ElevenLabs are among the names on the day-one list.

Read the mechanic slowly, because it is the news. The partners still invoice the customer directly. OpenAI credits the qualifying amount against the customer's minimum OpenAI commitment. The compute contract stops being a compute contract. It becomes a voucher the buyer can spend on other people's software.

That is a change of state for the biggest single line item in a modern AI budget, and it happened in the middle of a keynote that most coverage led with always-on agents called dots.

How the Currency Works

Large OpenAI enterprise agreements can carry a spending commitment over the contract term. Until Tuesday, the only announced way to draw one down was to consume OpenAI's own products. Now a portion of it can be applied through the Marketplace instead, so long as the vendor is approved, the customer is eligible, and the specific purchase qualifies. OpenAI's help page limits the program to partner products built on OpenAI models, and says a partner being listed does not make everything it sells eligible.

OpenAI has not disclosed the percentage cap, the eligibility threshold, whether it takes any fee from partners, or whether the approved-vendor list is contractual or discretionary. What has been confirmed is the flow: customer discovers a partner in the Marketplace, buys the partner's software on the partner's paper, and OpenAI credits the qualifying dollars back against its own contract. Adobe, Figma and Salesforce keep the revenue. OpenAI keeps the customer.

The precedent is not a mystery. AWS Marketplace did not grow because the interface was elegant. It grew because it let a finance team redirect committed cloud dollars toward software the company was going to buy anyway. That mechanic is called commit burn-down in the cloud sales world, and it is the reason enterprise SaaS vendors spent a decade quietly turning their own field teams into co-sellers with AWS reps. Azure and Google Cloud each built their own version. Now OpenAI has it too, and OpenAI got it without spending a decade building an enterprise sales force first.

What the 32 Partners Actually Signed

The right way to read the launch list is category by category, not logo by logo. Design (Adobe, Figma). CRM and workflow (Salesforce, ServiceNow, HubSpot, DevRev). Security (Palo Alto Networks, CrowdStrike). Observability (Datadog). Vertical agents (Sierra, Decagon, Harvey, Legora). Search and knowledge (Glean). Voice (ElevenLabs). Infrastructure (Baseten). Many of the other names are AI-native startups, but this is not only an AI-native bench. The incumbents on it are a horizontal cut of the enterprise SaaS stack that publicly agreed to let OpenAI meter a slice of their sales.

Two of those companies are worth staring at longer.

Salesforce and ServiceNow both ship their own agent products, and they both position those products as the operating layer for enterprise work. Signing up to have SaaS sales counted on OpenAI's meter, on the same day OpenAI announced ChatGPT Space as a shared workspace for humans and agents, reads to me as a concession that the ChatGPT frontend is where the enterprise buyer already starts. My view is that you do not join a competitor's channel unless you have concluded that the funnel it owns is worth more than what you give up.

Adobe is the second one. Adobe has pitched Firefly and its own agent tooling as the way it keeps a direct relationship with the creative buyer. Joining the Marketplace at launch is not a reversal of that message, and Adobe still contracts with and invoices the customer. What is new is that a qualifying Adobe purchase can count against a customer's OpenAI commitment. Once the pipe exists, finance teams will use it.

Who Gets Disintermediated

Three groups, in roughly this order.

One, hyperscaler marketplaces. AWS Marketplace, Azure Marketplace and Google Cloud Marketplace have each spent the better part of a decade or more turning themselves into a default channel for enterprise SaaS. OpenAI just launched an alternative funded by a much smaller but faster growing budget line. The AI bill is one of the fastest growing procurement categories inside large companies right now, and I think it is the line with the most slack to route through Marketplace credits.

Two, direct enterprise sales teams at the partners themselves. Every software vendor that signs a marketplace of any kind eventually finds out that a share of its revenue was going to close either way. The honest number for AWS Marketplace is that some fraction of every GMV dollar was cannibalized off a deal that would have booked direct, minus the take rate the vendor pays the channel. Adobe, Salesforce and ServiceNow can run that math themselves. They still signed.

Three, the value of the OpenAI compute commitment itself as a concession. Enterprise procurement teams sign large OpenAI floors today because ChatGPT and the API are the strategic bet. Tomorrow they sign the same floor with more comfort, because a portion of it is now spendable on software the finance team was already planning to buy. That is an implicit price cut on the OpenAI contract. OpenAI has not said whether it takes a fee from partners to fund it.

The Antitrust Question Nobody Asked at DevDay

Bundling a growing platform commitment with distribution for third-party software has a specific regulatory history. The pattern shows up in the 1998 Microsoft antitrust case (Windows and Internet Explorer), in the European Commission's 2009 browser-choice settlement (and its 2013 fine when Microsoft broke it), and most recently in the Commission's 2025 decision accepting Microsoft's commitments to unbundle Teams from Office 365. In each of those cases the fact pattern that drew scrutiny was a dominant channel using its commitment as a lever on adjacent software categories.

OpenAI is not Windows, and 32 partners is not a bundling case. But the Marketplace mechanic (compute floor plus approved-vendor list plus commit burn-down) is exactly the fact pattern the FTC and the European Commission historically start looking at once the market share crosses a threshold. The interesting question over the next six quarters is not whether OpenAI ships Marketplace features. It is whether OpenAI publishes what, if anything, it takes from partner revenue, and whether it publishes how a vendor gets on or off the approved list.

Our Take

The number that matters is not 32. It is that Adobe, Salesforce and ServiceNow (each of them selling agent products of its own) all agreed to let OpenAI meter a portion of their enterprise SaaS revenue, on the same day OpenAI shipped ChatGPT Space and always-on Dots inside Slack and Teams. Read straight, that is the enterprise software layer conceding that the buyer's first click already lives inside OpenAI's product. Read cynically, they signed because the alternative was ceding the distribution window to Sierra, Decagon and Harvey, who signed anyway.

The Marketplace is the money-side complement to the OpenAI Partner Network we covered in June. One side is a target of 300,000 certified consultants trained to deploy OpenAI first. The other is 32 software vendors who can sell against an OpenAI-denominated budget. Put them together and OpenAI has the two halves of an enterprise go-to-market motion that AWS took a decade to assemble.

Practical read for anyone buying enterprise SaaS in Q4 2026: if your company has an OpenAI enterprise commitment, ask your Adobe, Figma or Salesforce rep which of their products qualify, because a listed partner does not make everything it sells eligible. Then ask your OpenAI account team how much of your commitment you can apply this quarter. The finance case for moving eligible dollars through the Marketplace becomes obvious the first time a CFO does the calculation.

Three signposts for the next 60 days: whether AWS Marketplace or Azure Marketplace responds with an AI credit conversion program of their own, whether Google or Anthropic launch a comparable marketplace against their own enterprise commitments (which would confirm the mechanic as a new industry standard rather than an OpenAI wedge), and whether any Adobe, Salesforce or ServiceNow filing quantifies the OpenAI channel as a distinct revenue line. The first company to disclose it publicly tells the rest of the market what the take rate, if there is one, actually is, and that is the number that decides whether this is a small distribution deal or a repricing of the enterprise SaaS stack.

We are tracking the deal cadence on our OpenAI provider page alongside the DevDay pricing and product moves. Next data point to watch: whether Microsoft, still OpenAI's most important enterprise channel partner, blesses or fences the Marketplace inside Azure, because the shape of that answer decides whether the OpenAI commitment lives inside the Microsoft enterprise agreement or alongside it.

Primary sources: OpenAI Marketplace product page, TechCrunch on the app-store framing, OpenAI Marketplace enterprise help doc, and CNBC DevDay live updates.