Skip to main content
    Tuesday, September 8, 2026

    AI Stack Economics

    Where is the AI money going, what value is it creating, and what should be scaled, optimized, or stopped — modeled from one workflow to the whole enterprise.

    Unsaved scenario
    Portfolio

    Model a company

    Type a company name or ticker — the calculator pre-populates from its public filings (revenue → archetype, sector → vertical, headcount → modeled users) as a starting point you can edit.

    Modeled enterprise program: $15.5M/yr AI spend across 8,562 seats (26% of the workforce) creating $24.7M/yr in modeled value — 45% ROI on year-one TCO. Operations leads on modeled net value.

    Modeled, not observed — the whole view extrapolates this scenario's per-seat economics across 33,333 employees. Edit any function's adoption or intensity below; drill in to model one function's program in full.

    AI P&L by function

    Each row is that org's modeled program: seats = headcount × adoption; cost = its usage + a seat-share of the shared platform; value = the productivity lever at its scale. Adoption and intensity are editable modeled defaults.

    FunctionHeadcountAdoptionIntensitySeatsCost / yrValue / yrNet / yrROIActions
    Operations
    COO
    18,3334,583$5.78M$12.70M$6.92M120%
    Sales
    CRO
    3,0001,350$2.56M$3.74M$1.18M46%
    Marketing
    CMO
    833417$880K$1.15M$275K31%
    People / HR
    CHRO
    467210$355K$583K$228K64%
    Corporate / CEO office
    CEO
    667334$776K$924K$149K19%
    Legal & compliance
    GC / CCO
    23393$237K$258K$22K9%
    Finance
    CFO
    500275$756K$762K$5.9K1%
    Technology
    CIO / CTO
    2,0001,300$4.13M$3.60M$-523K-13%
    EvidenceEModeledheadcount splitEModeledadoption, intensity & value extrapolation — see Method & sources for the grading scale
    • · No workforce split on this scenario — modeled a 33,333-employee enterprise at typical functional shares (type your company in the quick start, or edit headcounts, to replace it).
    • · Per-function value is the productivity lever only (seats × hours saved × loaded rate); the configured use case's structural levers (process cost, revenue, risk, cycle time, retired tech) are counted once at enterprise level.
    • · Shared platform, governance, and FinOps program costs are counted once and allocated by seat share; each function adds only its variable usage cost.
    Keep going — across the app