Morgan Stanley says SpaceX hits $3.4T by 2040. That's 182x last year's sales
The bank co-leading the deal projects a revenue multiple no company has ever cleared — a 2.15x growth 'residual' that sits beyond even Tesla's record. An analyst's essay asks the only real question: is this Elon's frontier, or the market extrapolating one outlier onto another?
The forecast needs a 79% EBITDA margin at $3.4T — versus Aramco's 55% and software's 45% — which would make SpaceX roughly 6% of US GDP.
The thread split: one camp said the same 'highly unlikely' was said of early Tesla; the other replied that the most extreme Tesla predictions never came true either.
The number, and why the author calls it a fantasy
Matt East's essay takes apart a specific forecast: Morgan Stanley, "as co-lead underwriter," projects SpaceX at $3.4 trillion in 2040 revenue — "182× what SpaceX sold last year." His objection is statistical, not vibes-based. Hitting that target requires a growth "residual" of 2.15×, and he places it against the historical record:
"Tesla's 1.49× is the record — just inside the outlier fence. SpaceX's required 2.15× falls beyond it." — Matt East, in the essay
The margin assumption gets the same treatment: the model implies a "79% EBITDA margin. At $3.4 Trillion," which East compares unfavorably to Saudi Aramco's 55% and software's 45%. At that scale SpaceX would be "~6% of U.S. GDP." His framing question is the one the thread adopted as its own: "is Elon Musk on a frontier of his own — or is the market extrapolating one proven outlier onto an unproven one?"
The thread caught the headline editorializing
A careful reader pointed out the HN title answered the essay's open question for it — and the author had, too:
"The actual takeaway question is 'is Elon Musk on a frontier of his own — or is the market extrapolating one proven outlier onto an unproven one?' The HN title editorializes its own answer." — DenverR
Someone who covers the industry confirmed the author's hand was visible — a storyteller at The Aerospace Corporation and former TechCrunch editor noted "it's a rhetorical question, not a real one. the author's inclination is clear as day."
The Tesla precedent, and the Tesla counter-precedent
The bull case leaned on history rhyming:
"early in Tesla's forecasts, I've seen many 'highly unlikely' articles, but Tesla ended up blowing past expectations. … I hate just dismiss it as unlikely especially with Elon at the helm" — m3kw9
The rebuttal was that selective memory is doing the work — the most extreme Tesla calls also failed:
"Blown past? It was only a few years ago people were saying Tesla was going to own the entire car market … The Cybertruck was going to be the best selling car of all time … None of these things happened." — itsgonnabebad
A third line argued the forecast can only be "rescued" by a scenario nobody should want — sustained 70% inflation that lifts the nominal number while the dollar loses reserve status. As one reply put it, "I'm not pricing a stock today based on the assumption that this country will turn into a theocratic autocracy with a 70% YoY inflation rate."
The form of the argument matters
Even the essay's presentation became evidence. A commenter noted the "essay in scrolls" format — a Claude-Code-style animated landing page — undercuts a quantitative argument: "This kind of … landing page turns people off when the content is otherwise meaningful." The substance survives the criticism. The honest version of East's point isn't "SpaceX will fail." It's that an underwriter's 2040 number assumes a company simultaneously breaks the all-time revenue-growth record and the all-time margin record at multi-trillion scale — and that pricing the deal off that assumption is the part worth being skeptical about, separate from whether you believe in Starship.
Get breakdowns like this every day
The top Hacker News stories, unpacked — by email, Telegram, or RSS.
A 3-person startup raised $5.5M to make Postgres shard without touching your code
PgDog is a Rust proxy that shards, pools and load-balances PostgreSQL — and claims 2M queries per second in production across dozens of deployments. The thread is full of people who already run it, and one who asks how three people will QA all this.