All case studies
    STRUCTURAL DIVERGENCEMarch 2026· 7 min

    Apollo vs ZoomInfo: Same Layer, Opposite Strategies, Different Fates

    Apollo.io logoApollo.io
    ZoomInfo logoZoomInfo
    L1L7
    Verdict: L1b headless vs L1b + L7b tax

    ZoomInfo Market Cap

    Peak

    $24B

    Now

    ~$5B

    -79%

    Layer Scoring

    L-1
    Resources
    L0
    Infra
    L1
    Data
    L2
    Models
    L3
    Gates
    L4
    Access
    L5
    Execution
    L6
    Orchestration
    L7
    Surface
    L8
    Memory

    Apollo.io sits at L1b, proprietary data. 275 million contacts. Headless API + MCP connector. This is the structural definition of "safe."

    Why Law III protects Apollo: When models (L2) commoditize, every agent needs data. When surfaces (L7) commoditize, every interface needs enrichment. The scarcer the data, the more valuable it becomes.

    Compare to ZoomInfo: Same layer (L1), but ZoomInfo charges premium for a UI wrapper on increasingly commodity data. The UI tax is a liability when agents don't need UIs.

    The verdict: Data refineries are the safest position in the stack. But only if you go headless.

    What This Means for You

    Product Leader

    Map your product to the layers it actually owns vs. rents. The rented ones are where the counter-move work belongs.

    Investor

    Underwrite layer ownership, not feature count. The Cube footprint is the moat.

    Operator

    Audit your stack against Supply Chain of Intelligence. Anything sitting only at L7 is the layer to watch.

    AA

    Anand Arivukkarasu

    Ex-Meta product leader. Creator of Supply Chain of Intelligence™. Writes about where AI value accrues, and who can fire your product. LinkedIn

    Get the next teardown in your inbox.

    One issue when something structurally important happens, usually weekly. No spam, no filler, unsubscribe anytime.

    Worth sharing? Pull-quote: "L1b headless vs L1b + L7b tax"