Sigma closes $80M Series E to lead "agentic analytics" inside the warehouse

verified

Tuesday, May 19, 2026

The News

Sigma closed $80 million in Series E financing at a $3 billion valuation. The round was led by new investor Princeville Capital with participation from new investors including Databricks Ventures, ServiceNow Ventures, and Workday Ventures (BusinessWire). The valuation jump from $1.5 billion to $3 billion reflects a company that has doubled its revenue in the same period. Sigma reached $200 million in annual recurring revenue, up from roughly $100 million a year earlier, with more than 2,000 customers including AMD, Duolingo, Colgate-Palmolive, and JPMorgan Chase. The category Sigma is claiming — "agentic analytics" — barely existed two years ago, and every major enterprise software vendor is racing to claim it: SAP unveiled more than 200 AI agents at Sapphire 2026, Google positioned its entire Cloud Next conference around agentic AI, and Snowflake forged a $200 million partnership with OpenAI to embed AI agents in the data warehouse.

The Read

The cap table is the story. Databricks Ventures, ServiceNow Ventures, and Workday Ventures all writing checks into the same agentic-analytics company isn't strategic alignment — it's three platform players hedging the same risk, which is that an independent governance layer becomes the buyer-of-record for "where AI runs on enterprise data." Sigma's flagship in this space — Sigma Agents — can operate in three modes: interactive (user approves actions), autonomous (agent monitors and executes on a schedule), and external (agent calls third-party APIs). The autonomous mode is the one the warehouse vendors actually fear, because it converts BI consumption from a license seat to an unattended workload — and they'd rather underwrite a friendly competitor than wake up next to one.

Do This Week

Walk your team through the three Sigma Agents modes — interactive, autonomous, external — and identify which of your existing data-access policies were written assuming a human in the loop. Anything in the "autonomous" or "external" column needs a written approval path before procurement signs the next analytics renewal, not after. Most existing data-loss-prevention controls were designed for a human pulling a report, not an agent calling an API at 3 a.m.

For Legal ops / Data governance lead