Glean adds $200m of run rate in 15 months, reaching $300m ARR

The cadence is what makes this legible: $200m of new run rate spread across 15 months is roughly $13.3m added every month without a visible pause ^[10], and a tripling over that window annualises to about 2.4 times a year ^[11], which is the figure a competing knowledge-layer pitch now has to be measured against rather than the softer claim of category leadership.

Price has to be weighed against value here. The last mark was $7.2bn on a $150m Series F in June ^[7], so the company is carried at about 24 times its current run rate ^[12], and that mark is now eleven months stale against a top line that has moved a long way since.

That benchmark is worth a second look. Glean says it was preferred roughly 2.5 times as often as off-the-shelf MCP tools, that those tools consumed 30% more tokens on average, and that its win rate rose from 66% on simple tasks to 73% on multi-step ones ^[19]. Thirty percent more on the other side of the ledger is about 23% fewer on Glean's ^[13], and the 2.5x preference is not an independent data point so much as the same wins restated as odds, since 70 against 30 is about 2.3 to one ^[14].

Pricing is the term that deserves close attention here. Arvind Jain describes both a consumption model and a hybrid one, where a fixed monthly fee for active users sits beside separate usage fees for model consumption ^[8], while the headline benefit he sells is that customer AI bills fall because the AI performs fewer operations ^[3]. Sell that well enough and one of your own line items contracts: the per-active-user fee is the durable part, and the consumption fee is the part Glean is actively teaching its buyers to reduce. TechCrunch made the adjacent point that a consumption model has no strictly recurring component, so some portion of the $300m reads better as an annualised run rate than as ARR ^[15]; Glean had not responded to its request for comment at publication ^[9].

There is an obvious counter-thesis: Google, Microsoft, OpenAI, Anthropic, Salesforce and Atlassian are all building versions of this ^[6], and each can fold a context graph into seats a customer already pays for, which is exactly how a separate budget line reverts to a feature. Jain's answer is that the first four or five years were competition-free ^[5] and that the moat is connectivity into environments others decline to touch ^[21]. Note where the spending went: more than 250 features in a year ^[20], plus a Model Hub and an MCP Gateway that let customers swap models, clouds and frameworks ^[4]. That is a company buying plumbing and governance instead of a model.

This is probably wrong in one specific way, but I read the 45% weekly-to-monthly active ratio, said to be more than twice the SaaS benchmark ^[18], and the more than 85% of customers spanning five or more departments ^[17], as firmer evidence of a real budget line than the revenue number is, because horizontal usage is what survives the procurement review that consolidates AI spend. What would falsify it: a run rate that flattens at constant customer count, which is the consumption tell.