Market Map: AI-Native Search & Post-Google Information Access
1. Thesis
The unbundling of the "ten blue links" is shifting value from ad-monetized traffic aggregation to answer delivery embedded in workflows — collapsing the distinction between search, assistant, and agent, and forcing a rebuild of the entire economic layer (crawling rights, attribution, monetization) underneath.
---
2. Segments
A. Consumer Answer Engines
Perplexity, OpenAI (ChatGPT Search), Google (AI Overviews / Gemini), Microsoft (Copilot/Bing), You.com (You.com has pivoted increasingly toward enterprise/API — less sure of current consumer emphasis)
Dynamics: Brutal capital-intensity war; differentiation is thin because all rest on similar model capabilities and web indexes. Incumbents (Google) are cannibalizing themselves defensively. Monetization unsolved — CPM-style ads don't map cleanly onto single-answer surfaces.
B. Search Infrastructure & Retrieval APIs
Exa (formerly Metaphor), Brave (Search API), Tavily, Vespa.ai, Algolia, Elastic
Dynamics: "Selling shovels" — every agent and AI app needs web retrieval or semantic search primitives. Sticky, usage-based revenue, but exposed to hyperscalers bundling retrieval into model APIs (OpenAI/Anthropic native web search tools compress this layer).
C. Enterprise / Internal Knowledge Search
Glean, Hebbia, Sana (Sana — reasonably confident but verify current positioning), Coveo, Microsoft (Copilot for M365)
Dynamics: Highest willingness-to-pay in the market; ROI is legible (analyst/employee time). Permissions-aware retrieval across SaaS silos is genuinely hard, creating a real moat vs. generic LLMs. Microsoft's distribution is the existential threat.
D. Vertical / Domain-Specific Answer Engines
Harvey (legal), OpenEvidence (medical), Consensus (scientific literature), AlphaSense (financial/market intelligence), Elicit (research)
Dynamics: Depth beats breadth — proprietary corpora, citations that professionals can defend, and workflow integration justify premium pricing. Most defensible against foundation-model encroachment because trust and liability matter more than raw capability.
E. Content Economics & Attribution Layer
TollBit, Cloudflare (pay-per-crawl / bot management), ProRata.ai, Scale-adjacent licensing deals (e.g., OpenAI–News Corp, Perplexity Publisher Program)
Dynamics: Nascent and chaotic — the market is renegotiating who pays for the content answers are built on, via lawsuits (NYT v. OpenAI), licensing deals, and crawl-blocking. Whoever standardizes the transaction layer captures a toll position.
---
3. Where Value Accrues: Segment D (Vertical Answer Engines), with C close behind
- Pricing power: Harvey and OpenEvidence charge for outcomes, not queries; no dependence on solving the ad-model problem that plagues Segment A.
- Defensibility: Proprietary/licensed corpora + regulatory trust + workflow lock-in are moats general models can't easily replicate.
- Segment A will see the most revenue flow through it but the worst value capture — margins are being competed away and Google/OpenAI will absorb the general case.
- Segment B is real but compressible; Segment E is optionality with fat tails but binary legal/standards risk.
---
4. White Space
- Agent-to-agent commerce/search protocol layer: As agents (not humans) become the dominant "searchers," no player offers a neutral standard for machine-readable offers, structured intent, and agent-negotiated transactions — the "SEO + payments rail" for agentic traffic. (Stripe and Cloudflare circle this; no one owns it.)
- Provenance-verified answer infrastructure for regulated industries: A cryptographically auditable "chain of citation" — proving exactly which source versions produced an answer, at query time — for compliance, litigation, and audit contexts. Vertical players cite sources, but nobody sells verifiable citation infrastructure as a horizontal product.
---
Confidence notes: Company names and core positioning are current as of my knowledge cutoff (early 2025); funding stages and product pivots (especially You.com, Sana, ProRata) move fast and should be re-verified.