OpenAI has named Dali Rajic as its new Chief Revenue Officer, according to an announcement from OpenAI. The move fills a role that formalizes how the company sells its products — ChatGPT Enterprise, API access, and related offerings — to businesses at scale.
Details on Rajic's mandate beyond the title are limited in the source material; OpenAI's announcement does not specify reporting lines, revenue targets, or whether the role absorbs existing sales leadership functions. Those specifics remain unconfirmed as of this writing.
What is clear is the signal: a company that grew explosively through consumer adoption and viral product-market fit is now investing in a formal revenue function, the kind of hire typically associated with scaling enterprise contracts, managing channel partnerships, and building out account-based sales motions. This is a common trajectory for infrastructure-layer AI companies once the initial land-grab phase gives way to a monetization phase focused on larger, stickier accounts.
For the B2B operator audience INITE AI serves — companies with 10 to 200 employees running sales, support, or operations on top of tools like OpenAI's API — this kind of executive hire rarely produces immediate changes. Pricing doesn't shift overnight, and API terms don't usually change the week a CRO starts. But it is a leading indicator worth logging. Companies that build formal revenue organizations tend to follow with segmented pricing tiers, minimum commitment thresholds for "enterprise" support, and sales-assisted renewal conversations that didn't exist when the product was self-serve. If your team currently interacts with OpenAI purely through a credit card and an API key, that relationship may look different in twelve months.
The deeper operator lesson isn't really about OpenAI specifically — it's about vendor concentration risk. Many mid-market companies have quietly built customer support bots, sales qualification workflows, or internal ops automations directly on top of a single model provider's API, with no abstraction layer in between. That's a reasonable starting point, but it creates exposure: if pricing changes, rate limits shift, or support tiers get reorganized around enterprise accounts, teams without a plan can find themselves renegotiating under time pressure.
The practical takeaway for operations leaders: audit where your automations sit relative to any single AI vendor, understand your current contract terms and renewal dates, and build in the flexibility to swap or renegotiate before you're forced to. A CRO hire at a major model provider isn't an emergency — but it's a nudge to check your own exposure before the next pricing announcement forces the conversation.