Skip to content

By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

EO StudioEO Studio

Built Two Unicorns in 12 Years. The Rule Has Never Changed | Glean, Arvind Jain

Arvind Jain had already built a unicorn. He could have stopped there. But when he saw his own team drowning in information they couldn't find, losing hours every day to questions no one could answer, he couldn't ignore it.

Arvind Jainguest
May 14, 202611mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

At a glance

WHAT IT’S REALLY ABOUT

Glean’s Arvind Jain on focus, speed, and enterprise AI execution

  1. Jain started Glean after seeing productivity fall at Rubrik because employees couldn’t find internal information or the right experts quickly.
  2. Because enterprise search had a history of failures, Glean stayed in stealth for roughly two years to reach a “Google-quality” experience before charging customers.
  3. Early traction came from intense internal and design-partner usage, including strong user pushback when security teams tried to disable the tool—signaling product necessity.
  4. Glean’s strategy is to move fast with focus by integrating best-in-class foundation models (e.g., OpenAI/Google/Anthropic) and concentrating engineering on enterprise context, access, and workflows.
  5. Jain’s core founder advice is to develop conviction through initial validation, then protect the idea from being diluted by lukewarm external feedback.

IDEAS WORTH REMEMBERING

5 ideas

Start from a painful, universal workflow problem—not a cool technology.

Glean’s premise came from a repeated, company-wide frustration: employees couldn’t find knowledge or the right people, directly harming per-person productivity.

In “failed categories,” quality is the strategy.

Because enterprise search had “universally failed” before, Glean assumed it would get one real chance and delayed launch until the experience met a Google-like expectation.

Usage signals beat opinions—especially when the product is threatened.

Free beta usage, raves from employees, and internal “revolts” when teams tried to shut it off provided stronger validation than polite stakeholder interest.

Win by building the missing layer: enterprise context on top of foundation models.

Rather than training their own models, Glean focuses on connecting to company data/systems and supplying the context LLMs lack so answers and actions are enterprise-relevant.

Don’t reinvent the wheel; redirect engineering to neglected problems.

By partnering with frontier model providers, the team can invest disproportionately in integration, permissions, relevance, and reliability—areas others may underinvest in.

WORDS WORTH SAVING

5 quotes

Customers, they are looking for solutions to problems. They're not looking to buy great technology.

— Arvind Jain

Building a business is never easy. And a lot of times you give up.

— Arvind Jain

For us, we knew that we would only have one chance to succeed, and we had to build a product with very high quality.

— Arvind Jain

We were actually offering the product for free for the first two years.

— Arvind Jain

I think the number one thing for any aspiring founder is belief and conviction.

— Arvind Jain

Read the available transcript
Origin story from Rubrik productivity painEnterprise search category fatigue and trust gapTwo-year free/beta period and “Google-quality” barDesign partners, word-of-mouth, and conversion to paidPartnering with foundation-model providers vs building modelsEnterprise context and connecting to company systemsFounder conviction, resilience, and cold outreach humility

SPEAKERS

  • Arvind Jain

    guest

    Founder and CEO of Glean; previously co-founded Rubrik and has built multiple high-growth enterprise startups.

High quality AI-generated summary created from speaker-labeled transcript.

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.