OpenAI’s Altman: Optimistic on Revenue, Addresses Losses

Sam Altman, Chief Executive Officer of OpenAI, expressed optimism regarding the company’s revenue forecasts in a podcast and stated that he would seize the opportunity to counter critics. When asked how OpenAI could make a financial commitment exceeding $1 trillion while reporting an annual revenue of only $13 billion, Altman said, “Our actual revenue is far higher than this figure.” In recent weeks, OpenAI has successively announced large-scale artificial intelligence infrastructure partnerships with enterprises including NVIDIA, Broadcom, and Oracle. While OpenAI continues to raise billions of dollars from investors and generate more revenue, Altman also warned that losses would persist. Earlier, some media outlets, based on an analysis of Microsoft’s released financial reports, suggested that OpenAI’s quarterly loss might exceed $12 billion. The financial reports indicated that Microsoft’s investment in OpenAI resulted in a $3.1 billion decrease in its net profit. Given that Microsoft holds approximately a 27% stake in OpenAI, analysts speculate this implies OpenAI’s net loss for the quarter is around $11.5 billion. Considering pre-tax losses and Microsoft’s previously higher ownership stake, the actual loss could surpass $12 billion.

Separate leading indicators from financial outcomes

Usage, retention and pipeline often move before recognized revenue or cash. A useful dashboard combines these leading signals with financial results so management can distinguish a temporary accounting lag from a real deterioration in demand. Definitions should remain stable enough that teams do not change the metric when performance becomes inconvenient.

Document assumptions beside the forecast. Model outputs are only as reliable as their assumptions about pricing, conversion, cost and timing. Keeping those assumptions visible makes scenario analysis faster and reduces false precision.

Review the model when product behavior changes

New modalities, pricing plans or sales motions can invalidate old averages. Finance models should evolve with the product rather than forcing new behavior into outdated categories. Measure the full contribution margin.

Gross revenue can hide payment fees, AI serving cost, creator share and support burden. Contribution margin is more useful for deciding whether growth is creating economic value. Segment the calculation by product or customer type because one blended percentage can conceal weak economics in a fast-growing area.

Use scenario analysis for uncertain inputs

AI businesses face volatile usage and infrastructure cost. Base, upside and downside cases help management see which assumptions matter most and where protective actions are available. Reconcile forecast with actual drivers monthly.

Instead of only comparing total spend or revenue, explain how much variance came from volume, price, mix and unit cost. This turns the forecast into a learning system for the business.

Start with the business driver behind the metric

A finance ratio is useful only when teams understand what operational behavior moves it. Break revenue, margin or payback into user volume, conversion, pricing, usage and variable cost so a variance can be traced to a real product or sales change. This makes forecasts easier to update because assumptions can change independently instead of rebuilding one large top-down model.

Use cohort evidence before extrapolating growth. AI products often change quickly, so recent cohorts may behave differently from early adopters. Compare retention, spending and support cost by signup period or customer segment before assuming historical averages will continue.

Connect financial metrics to operational decisions

The purpose of the model is not only reporting. It should help decide pricing, hiring, infrastructure commitments and channel spend while there is still time to change course. Practical finance check.

Before acting on the metric described above, define the decision it is supposed to support and the operating assumptions behind it. Compare the forecast with actual user behavior, payment timing and serving cost so changes can be traced to real drivers. Scenario ranges are usually more useful than one precise projection when usage, collections or infrastructure cost remain uncertain.