OpenAI Hires New CRO

OpenAI named Dali Rajic as its new Chief Revenue Officer on August 13, 2026, replacing Denise Dresser after just eight months in the role — the third major commercial executive to exit the company in roughly six months. Rajic, who most recently served as President and COO at Wiz, the cloud-security firm Google acquired for $32 billion, steps into a seat that has become the focal point of OpenAI's push to double down on enterprise sales.

Background You Need

The CRO role itself is new to OpenAI. Dresser became the company's first-ever chief revenue officer when she was appointed on December 9, 2025, arriving from Slack, where she had been CEO since 2023. Hiring a CRO at all was a signal: OpenAI was moving from a research-forward culture into something that looked more like a scaled software business. At the time, the company was balancing rapid API growth with a consumer product in ChatGPT that was attracting hundreds of millions of users but converting them to paid accounts at uncertain rates.

Her departure doesn't arrive in isolation. Earlier in 2026, COO Brad Lightcap left the company, followed by Fidji Simo, who had held the unusual title of "CEO of AGI deployment." Three senior commercial leaders out the door in six months is not a routine churn pattern — it signals either a deliberate organizational reset or a deeper disagreement about how to run the business at scale, or both. Multiple reports indicate that executives privately and publicly confirmed the company has not hit all of its revenue targets, and Sam Altman has become increasingly explicit about cutting internal experiments to concentrate resources on enterprise deployment and what he has described as "measurable business impact."

The timing matters too. OpenAI ran a $7 billion employee tender offer before any IPO filing — unusual sequencing. Companies that are 12 to 18 months from going public typically don't pre-liquefy employees; they preserve that incentive for the IPO itself. Reading the tender offer as a retention and morale tool rather than a pre-IPO milestone suggests the public offering is further out than the market had assumed, probably 2028 or later. That matters for enterprise buyers, because it means there's no public accountability on pricing, product terms, or API deprecation schedules for at least another year or two.

What's New

Rajic's background is a clean signal of what OpenAI thinks it got wrong — or at least what it thinks it needs more of. At Wiz, she was present during one of the most compressed growth runs in enterprise software history, building out the operational infrastructure that supported the company's rise to a $32 billion acquisition. Before Wiz, she was CRO and COO at Zscaler, another cybersecurity firm built almost entirely on selling to large enterprise and government accounts, and Chief Customer and Revenue Officer at AppDynamics. Her entire career is in enterprise: not the developer-first, product-led, bottoms-up motion that OpenAI's API business has partially relied on, but the top-down, procurement-heavy sales motion that wins seven-figure contracts.

That orientation isn't accidental. According to reporting by the SF Standard and relayed via Crypto Briefing, OpenAI's enterprise segment grew to roughly 40% of total revenue under Dresser's watch, with internal targets set to push that figure to 50% by the end of 2026. A separate source adds that her cybersecurity background may prove relevant in a specific way: security and compliance concerns are consistently cited as the single biggest barrier to enterprise AI adoption. A CRO who speaks fluent CISO and understands how large organizations run procurement and vendor risk management is a different profile than a Slack-era SaaS executive, even a very good one.

What the two sources diverge on slightly is emphasis. TechCrunch frames the hire primarily as part of a continuing executive shakeup and a symptom of OpenAI's commercial struggles. The Crypto Briefing piece, by contrast, leans more toward Rajic's qualifications and reads the move as a rational pivot toward a business model that enterprise sales can actually sustain at scale. Both are probably true simultaneously — you can be replacing leadership because the prior strategy underperformed and be replacing it with someone well-suited to the new direction at the same time.

Altman's own stated rationale reinforces the enterprise-first framing. He has been publicly cutting what he calls experimentation and consolidating around products and go-to-market motions that show up in revenue numbers. Rajic's entire operating history is in environments where that's the default mode, not a pivot.

The Pushback

The skepticism worth naming is whether the problem is actually the CRO, or whether it runs deeper. Dresser inherited a company whose API pricing has been in flux, whose enterprise product still competes against Microsoft's deeply integrated Azure OpenAI Service, and whose primary rival in the enterprise segment — Anthropic — has been making quiet inroads with procurement-friendly contracts and a reputation for taking safety and audit requirements seriously. A sales leader, however accomplished, doesn't fix a situation where the product and pricing strategy are still being debated at the board level.

There's also the question of continuity costs. Each executive departure resets relationships. Enterprise sales cycles run 6 to 18 months; a new CRO coming in needs at least a quarter to assess the pipeline, another to put her own playbook in place. If the goal is to hit 50% enterprise revenue by end of 2026, the clock is already tight. Our read is that the Wiz pedigree is genuinely impressive, but the organizational disruption from three commercial leadership changes in six months is a real cost that doesn't disappear just because the replacement hire is strong on paper.

One more unresolved question: whether OpenAI's enterprise ambitions require a structural change to how the company handles security certifications and data residency, not just better sales execution. Rajic's cybersecurity background may help open those conversations, but the engineering work that backs them up is a separate bottleneck — one a CRO can't fix alone.

Sources