Tim Cook's Last Quarter: Apple Got Caught by Its Own Demand Forecast

On July 30, Tim Cook hosted the last earnings call of his tenure.

He warned that iPhone, iPad and Mac will all be supply-constrained in the September quarter, and that the constraint will hit revenue. Apple currently has less flexibility in the supply chain than normal, and there is a shortfall in the leading-edge capacity that makes its own silicon.

On the same call, he called memory chip pricing a “hundred-year flood,” and admitted Apple did not want to raise prices — the exponential rise in memory costs forced it.

The stock fell 7%–8% after the report. iPhone revenue grew 22% year over year this quarter. Guidance for next quarter is 9%–10%, below the 12% analysts had expected.

Those two numbers only matter together. 22% is what Apple sold. 9%–10% is what Apple can build. The gap in between is not demand disappearing; it’s product that can’t be shipped. Cook drew the causal line himself on the call: guidance came down precisely because supply constraints will hit revenue.

A company cutting guidance because it’s selling too well is not a common sight.

On September 1, John Ternus becomes CEO and Cook moves to executive chairman.

1. He got caught by the thing he’s best at

Cook joined Apple in 1998 as senior vice president of worldwide operations. Steve Jobs hired him to fix one problem: Apple’s inventory turned over painfully slowly, with months of product sitting in warehouses.

Cook shut most of the company-owned factories, outsourced manufacturing, and compressed inventory turns from months to days. That playbook became the standard move for the entire consumer electronics industry, and it was the whole reason he got the top job — he was not the product genius; he was the guy who could actually build the product, cheaper than anyone else.

In his 15 years running Apple he shipped every iPhone since the 4S, plus Apple Watch, AirPods, Apple Pay, Vision Pro, and the Mac’s move off Intel onto Apple silicon.

Now, in his last quarter before the handoff, Apple’s problem is that it doesn’t have enough parts.

The irony doesn’t need spelling out. But the irony isn’t the interesting part — where in the chain the root cause sits is.

2. The root cause isn’t the supply chain, it’s the demand forecast

Cook was explicit on the call: this is not a supply issue but a demand forecast issue.

The substance of it: this product cycle for iPhone and Mac came in stronger than planned, and demand ran beyond Apple’s expectation. Suppliers didn’t drop the ball. Apple didn’t expect to sell this well.

That’s a product judgment error, not an operations error.

Semiconductor capacity is locked in advance. To get parts next year, you place the order and sign the long-term agreement this year. How much you order depends on your forecast for next year’s volume. In any company, forecasting isn’t procurement’s job. It belongs to product and to the business.

Forecast low, and you don’t lock enough capacity. By the time demand actually shows up, there’s nothing left to buy — which is visible from upstream:

• Micron’s 2026 high-bandwidth memory capacity is already sold out under existing pricing agreements
• SK Hynix told investors its advanced packaging lines are fully booked through the end of 2026

The capacity isn’t unaffordable, it’s unavailable. Money doesn’t solve this, because the slots were taken a year ago.

The tighter constraint is leading-edge process

Cook called out one line separately: there’s a shortfall in the leading-edge capacity that makes Apple’s own silicon.

That’s harder to solve than memory. Memory at least has multiple suppliers, plus mainland Chinese capacity ramping — in theory there’s a “find another supplier” option. Wafer capacity at the most advanced node has no such option. There are only a handful of lines in the world that can do it, and the queue isn’t just Apple; it’s every company fighting for AI compute.

Apple has always stood near the front of that queue as a long-running launch customer for TSMC’s leading node. But “near the front” is ordered by volume, and volume comes back to the same question: how much did you commit to a year ago?

So the two bottlenecks here are two exits from the same bottleneck. Memory and leading-edge process are both things you have to lock far in advance, in quantities determined by a forecast. Forecast low, and both ends squeeze at once.

3. One memory price chain, four companies, four endings

I’ve been writing about different faces of the same story for days, and today it closes the loop.

DRAM and NAND prices are up 63%–75% year over year. On the same chain, four companies got four completely different outcomes:

One external variable, four ways of handling it, four fates. The variable was shared. The endings were bought with each company’s own judgment.

Microsoft’s line is the one worth studying: memory prices pushed it to $190 billion in April, and three months later it said it didn’t need to spend that much, because efficiency gains across CPU and GPU fleets let existing infrastructure do more. It didn’t fight the price increase. It changed consumption on its own side.

Apple’s position is different. iPhone memory content isn’t something you schedule away — it’s a fixed line in the hardware BOM. Apple had exactly two moves: lock capacity early, or raise prices. It didn’t do enough of the first, so only the second was left.

4. Locking capacity is a product decision, not a procurement task

Most companies treat “lock upstream capacity years ahead” as a supply chain department job.

It isn’t. It’s a bet on your read of the next two years of volume, and once placed it’s hard to unwind — these are long-term agreements, with penalties if you take less and dead inventory if you take more.

Only product and the business can make that call, because only they know what you’re selling next year and how much of it.

The difficulty is the timing mismatch: you have to buy materials for two years out before the product exists and before the market has validated anything. Get it right and nobody praises you (the parts are just there). Get it wrong and it hurts in both directions — too little means shortages, too much means inventory.

And the costs of those two errors are wildly asymmetric, which is the real reason this is hard.

Over-lock capacity and the loss is definite and countable: the extra money, the trapped cash, the inventory you write down. It’s ugly, but it shows up on a statement anyone can read.

Under-lock capacity and the loss is invisible: the people who couldn’t buy wanted to buy, but they won’t wait three months for you — they leave. That loss never lands on any statement, and you don’t even know how big it is. You can see what you sold. You can’t see what you could have sold.

Because one side is visible and the other isn’t, almost every organization skews systematically conservative on this decision. The extra money gets questioned; the churn from buying too little doesn’t. That’s the direction Apple got caught in — its forecast didn’t miss randomly, it missed toward safety.

I have exactly the same bias in the tiny things I build. Before launch I size servers and quotas against “roughly how many people will use this,” and that “roughly” is always an undercount, because the extra spend comes out of my pocket at the end of the month, while the person who hit a page that wouldn’t load and left is someone I’ll never hear about.

Apple came in short this time. Not absurdly short: it has locked parts for roughly 80 million new iPhones, covering iPhone 18 Pro, Pro Max and the first foldable iPhone, with the foldable’s production target raised to 10 million units. The problem is that demand is bigger than that.

One move that may get overlooked: per a CNBC report on July 2, Apple is evaluating memory chips made in mainland China, with both CXMT and YMTC under consideration. This is supply diversification under duress — when your only remaining fix is “find someone else who can ship,” your negotiating leverage is already gone.

5. “We didn’t want to raise prices but had to” is a confession about cost structure

Cook said Apple didn’t want to raise prices, that the exponential rise in memory costs forced it. Analysts speculate the iPhone 18 Pro could go up by $200.

That’s an honest statement, and it also exposes something.

If any single line in a product’s bill of materials satisfies three conditions at once — a large share of cost, violent price swings, and no long-term agreement locking it — that line is a time bomb. Whether it detonates depends on external market conditions, not on how well you execute.

Memory in a phone BOM hits all three.

What I build is as small as it gets, but the structure is identical at small scale. I wire external model APIs into my own tools, and the most expensive line is inference, whose unit price I control not at all. If I price my product to work exactly against the API price of the day, one vendor adjustment takes my margin to zero — and I did nothing wrong.

The move isn’t forecasting the price. It’s asking one question at design time: if this line doubles, does my product still work? If it doesn’t, you either cut consumption now, or build headroom into pricing now, or go lock a long-term price now. All three have to happen during product definition. The day the price moves is too late to start.

Apple picked the third path and ran the failing version of it: it locked, but not enough.

6. He hands over an Apple that can’t get parts

Ternus is 50, joined Apple in 2001, and has run hardware engineering since 2021. Cook is 65, and took the company from Jobs in 2011.

This is Apple’s first CEO change in 15 years, and the handoff lands on a very concrete problem: the iPhone 18 Pro, Pro Max and first foldable iPhone shipping in September may be short of supply and may cost more — and the reason isn’t in the factories, it’s in a volume forecast made a year ago that was too low.

The interesting part is that the successor comes from hardware engineering. When Cook took over, what Apple needed was the ability to build the product. What Apple needs now may be something else: in an environment where materials cost can rise 70% in a year, deciding again how much memory a device should carry, what it should sell for, and how much capacity to commit to two years out.

I don’t know how Ternus will handle that one.

But this report has already drawn a line for him. For the past decade-plus, Apple’s supply chain was its moat — costs and delivery nobody else could match. When upstream turns into a seller’s market, when capacity has to be fought for two years ahead, when the tightest few line items have only a handful of suppliers, “executing better than everyone else” stops being decisive. “How much did you commit two years ago” is.

This is the turn from an operations problem back into a product problem. The ledger Cook hands over states the issue plainly: selling too well is also a miscalculation.