Fetching from the wire…
01
02
03
04
05
06
07
08
Top 5 · 2026-04-01 · source-backed
I don't usually lead with survey data. But ICONIQ Capital's survey of ~300 high-growth B2B executives has numbers too specific to ignore.
AI-native companies (32% of respondents) have a burn multiple of 0.8x at $100M+ ARR. AI-enabled companies burn at 1.6x. Non-AI companies burn at 2.0x. That's not a trend line. That's a canyon. AI-native companies move through the product lifecycle 3.6X faster. 79% are building agentic workflows versus 62% for AI-enabled companies. Engineering allocation for AI at high-growth companies will hit 37% by 2026, maintaining a 9-10 percentage point lead over peers.
The gross margin story is equally stark. AI product gross margins are projected to hit 52% in 2026, up from 41% in 2024. That margin expansion is coming from inference cost declines (model providers racing to the bottom on pricing) and from AI-native architectures that don't carry the legacy cost structures of pre-AI companies.
Here's what caught me off guard: the 0.8x burn multiple. That's not "slightly more efficient." That's capital efficiency that fundamentally changes the math on when a company can become profitable. A non-AI SaaS burning 2.0x at $100M ARR needs $200M in annual capital to stay alive. An AI-native company at the same revenue needs $80M. That $120M difference is the cost of not being AI-native, and it compounds every year.
This data confirms what PitchBook's Q1 2026 analysis shows from the investor side: 10 mega-rounds over $1B accounted for $71.5B (80% of total consumer AI funding). The capital is concentrating at the top, and it's concentrating in AI-native companies that demonstrate this efficiency gap. If you're building a SaaS company in 2026 and you're not AI-native from day one, you're starting with a 2.5x capital efficiency handicap. That's not a headwind. That's a wall.
Each link below shares sources, entities, or timing with this story.
Zendesk uses SaaS / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Zendesk uses SaaS); both cover ARR, B2B; reported by the same outlet (saastr.com).
Intercom uses SaaS / Shared entities / Same source domain / What happened next
Linked by a graph relationship (Intercom uses SaaS); both cover ARR, SaaS; reported by the same outlet (saastr.com).
Linked by a graph relationship (Intercom uses SaaS); both cover ARR, SaaS; reported by the same outlet (saastr.com).
Intercom uses SaaS / Shared entities / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Intercom uses SaaS); both cover ARR, SaaS; reported by the same outlet (saastr.com).
Zendesk uses SaaS / Shared entity: SaaS / Same source domain / Shared topic / What happened next
Linked by a graph relationship (Zendesk uses SaaS); both cover SaaS; reported by the same outlet (saastr.com).
Intercom uses SaaS / Shared entities / Same source domain / What happened next
Linked by a graph relationship (Intercom uses SaaS); both cover ARR, B2B, SaaS; reported by the same outlet (saastr.com).
Shared entities / Same source domain / Shared topic / What happened next / Tension
Both cover ARR, SaaS; reported by the same outlet (saastr.com); overlapping topics (ai-native, company, efficiency, gross, margin).
Intercom uses SaaS / Shared entities / What happened next
Linked by a graph relationship (Intercom uses SaaS); both cover ARR, SaaS; picks up the ARR thread on 2026-04-24.