Ninety-Three Percent Growth Meets a Fifty-Point Margin Band
The orchestration layer just won the defensibility argument on public numbers — but the reporting alongside it is hard evidence that AI-native businesses do not earn software gross margins, and the two facts have to be priced together.
The multiple that matters is on gross profit
Start with the arithmetic most private marks quietly skip. A company at 15x ARR on 55% gross margin is really trading at 27x gross profit, while old-fashioned per-seat software at 15x ARR on 85% margin trades at 17.6x. Same headline number, materially different asset. The empirical gross-margin band for AI-native businesses now sits at 50-60% against 80-90% for per-seat SaaS, which is a 35-40% discount to SaaS revenue multiples before anyone opens the growth-rate argument.
The comforting counter-thesis, that cheap inference restores the margin, has been tested and it failed. Token prices fell more than 95% over three years and enterprise spend on large language models still more than doubled in six months to $8.4B, because cheaper calls bought more calls. Margin expansion at this layer is an engineering program (routing, caching, small models, per-action pricing) rather than a gift from the market, and that program eats the roadmap capacity that would otherwise ship features. Salesforce, Intercom and GitHub Copilot have already moved to per-action or per-outcome pricing. That is incumbents conceding a flat seat cannot absorb usage-scaled cost.
Where the sources genuinely diverge
The Information reads Palantir as evidence that value accrues to the orchestration layer, and the capital-intensity spread is the argument: roughly 1% capex against cash flow, at a company that went from $533M to $1.9B a quarter and from 13% growth in mid-2023 to 93% now. Morning Brew supplies the companion fact nobody puts on the same slide, which is that the same equity is quoted at $123.06, down 30.8% year to date, in a July when the Nasdaq fell 3.2%. Two measurements, not a contradiction. The growth figures are the reported operating quarter, the quote is a July market mark, and nothing in the reporting revises the growth rate down. What contracted was the multiple on that growth, from a peak that assumed someone would keep paying it indefinitely.
So the honest synthesis is narrower than the bull case: orchestration is where the cash flow is, and it is not where a 2025 peak multiple survives. Both facts are on the record. Only one is in most private marks.
The growth-quality tell to screen for
Snap is the cleanest teaching case. Headline revenue grew 19% and the shares popped 10% after hours, but subscriptions rose 85% to $316M, about a fifth of revenue and roughly 58% of incremental dollars, while advertising, the actual business, grew 9%. North American daily users were flat quarter over quarter at 92 million and down 7% year over year. Any portfolio company posting subscription growth above 50% against flat-or-declining core engagement in its highest-ARPU market is running a bridge, not a re-rating.
What the smart move looks like
This may be wrong, but the edge here looks procedural rather than predictive. Private comp adjustment lags a public print by two to six weeks, and this print is the anchor every enterprise-AI deck will cite. Three ways it resolves: comps reset toward gross-profit math and the discipline pays, the multiple recovers and the discipline costs only time, or per-action pricing lifts the margin band and the denominator argument softens. Diligence that converts revenue multiples into gross-profit multiples, and demands cost-per-action disclosure instead of blended ARR, is the cheapest differentiator available this month.
Capital intensity, not model ownership, is now the sorting variable — but gross margin, not revenue, is the denominator you underwrite it on.
Caveat worth holding: one quarter is not a category. Palantir's lead rests on data-graph depth and forward-deployed people, an execution moat rather than a structural one, and the services-heavy motion is exactly what lower-touch fast followers will attack.
What to do
Re-underwrite every open AI-native term sheet on gross profit rather than revenue, requiring cost-per-action and inference-cost trend disclosure before the committee meets.
Commission a portfolio-wide screen this quarter for the subscription-bridge pattern: attach-rate revenue growing above 50% while core engagement in the highest-ARPU market is flat or falling.
Add a mandatory pricing-architecture question to the diligence template by month-end: is any usage-scaled AI capability still sold on flat seats, and what is the migration plan?