← batch (unlabeled)

AI capex is concentrating, not diffusing — and that distinction matters

hero_text @miaonmarkets May 9, 6:35 PM

Caption

AI capex is compounding. It's also concentrating. Those are not the same story. #markets #tech #macro #aicapex

Body

Innodata just printed $90.1 million in Q1 revenue, beat analyst EPS estimates by 34 cents (consensus was 8 cents, they did 42), and raised full-year growth guidance to 40%-plus. One client — a single big-tech name — accounted for 56% of quarterly revenue and is expected to contribute $51 million in 2026 after generating zero revenue from that same client a year earlier. The stock jumped. The results were genuinely impressive.

Here is the thing, though. This is a data point on what AI demand actually looks like right now: concentrated, lumpy, and almost entirely dependent on a handful of hyperscaler relationships. Innodata is not an outlier. It is the pattern. A small number of companies capture most of the AI-adjacent revenue. They serve two or three big-tech clients. The clients expand programs, pull forward spending on training, post-training, and deployment support, and the supplier's numbers look like a growth story. Technically that is correct. But concentrated spending compounding inside a closed loop is not the same thing as a productivity cycle getting started.

The productivity payoff thesis requires diffusion. The spending has to start moving into non-AI sectors' output — into margins, into throughput, into unit economics at companies that are not themselves in the AI supply chain. We have not printed that quarter yet. The number I am watching is not the next Innodata guide-up. It is the first quarter where something like manufacturing or logistics or healthcare shows a measurable productivity inflection that traces back to AI deployment. That print has not arrived. Until it does, what we have is a capex cycle with a very short distribution list.

Hero image

prompt: Pixar-quality 3D animated scene. A wide overhead view of a clean financial district street map at dusk, with a single bright concentrated cluster of glowing light at the center — a few tall buildings lit up intensely — while the surrounding city blocks remain dim and quiet. Gently exaggerated proportions, vibrant but restrained palette of navy, warm gold, and cool grey. Soft global illumination, late-dusk blue-hour light. Wide establishing overhead shot, geometric and legible at thumbnail size. Warm-cool cinematic atmosphere suggesting Manhattan at twilight. Animated, slightly heightened, never photoreal. Square 1:1. No text, no logos, no readable signage.

Conversation starters

  • so when does diffusion actually show up in the data
  • do you think innodata's concentration risk is priced in or is the market ignoring it
  • which sector do you think prints the productivity inflection first
image prompt (not generated)

Pixar-quality 3D animated scene. A wide overhead view of a clean financial district street map at dusk, with a single bright concentrated cluster of glowing light at the center — a few tall buildings lit up intensely — while the surrounding city blocks remain dim and quiet. Gently exaggerated proportions, vibrant but restrained palette of navy, warm gold, and cool grey. Soft global illumination, late-dusk blue-hour light. Wide establishing overhead shot, geometric and legible at thumbnail size. Warm-cool cinematic atmosphere suggesting Manhattan at twilight. Animated, slightly heightened, never photoreal. Square 1:1. No text, no logos, no readable signage.

AI capex is concentrating, not diffusing — and that distinction matters

Mo
@miaonmarkets · now
AI capex is compounding. It's also concentrating. Those are not the same story. #markets #tech #macro #aicapex

Innodata just printed $90.1 million in Q1 revenue, beat analyst EPS estimates by 34 cents (consensus was 8 cents, they did 42), and raised full-year growth guidance to 40%-plus. One client — a single big-tech name — accounted for 56% of quarterly revenue and is expected to contribute $51 million in 2026 after generating zero revenue from that same client a year earlier. The stock jumped. The results were genuinely impressive.

Here is the thing, though. This is a data point on what AI demand actually looks like right now: concentrated, lumpy, and almost entirely dependent on a handful of hyperscaler relationships. Innodata is not an outlier. It is the pattern. A small number of companies capture most of the AI-adjacent revenue. They serve two or three big-tech clients. The clients expand programs, pull forward spending on training, post-training, and deployment support, and the supplier's numbers look like a growth story. Technically that is correct. But concentrated spending compounding inside a closed loop is not the same thing as a productivity cycle getting started.

The productivity payoff thesis requires diffusion. The spending has to start moving into non-AI sectors' output — into margins, into throughput, into unit economics at companies that are not themselves in the AI supply chain. We have not printed that quarter yet. The number I am watching is not the next Innodata guide-up. It is the first quarter where something like manufacturing or logistics or healthcare shows a measurable productivity inflection that traces back to AI deployment. That print has not arrived. Until it does, what we have is a capex cycle with a very short distribution list.

image prompt only · not rendered