Skip to content
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. He started over from scratch. That became Glean, now valued at $7 billion. His edge wasn't a bigger model or a better deck. It was focus, and the refusal to build what someone else was already building well. 00:00 Intro 01:32 Why I Started Over After a Unicorn Company 03:48 The 2-Year Stealth Mode That Built $7B 08:04 Build Less, Win More EO stands for Entrepreneur& Opportunities. As we're looking to feature more inspiring stories of entrepreneurs all over the world, don't hesitate to contact us at partner@eoeoeo.net LinkedIn | @EO STUDIO X | @eostudi0

Arvind Jainguest
May 14, 202611mWatch on YouTube ↗

CHAPTERS

  1. 0:00 – 0:30

    Startup advantage: focus, speed, and strategic leverage

    Arvind explains the core “weapon” startups have: intense focus and the ability to move fast. He frames this as both an execution advantage and a strategic choice—leveraging existing tech so the team can concentrate on what others ignore.

    • Focus and speed as the durable startup edge
    • Strategy: avoid reinventing the wheel
    • Use industry innovation to stay ahead
    • Customers buy solutions, not impressive tech
  2. 0:30 – 1:38

    What Glean is: enterprise AI connected to company knowledge

    Arvind introduces Glean as an enterprise AI system—like ChatGPT, but grounded in a company’s internal data and context. He positions Glean as an early player in enterprise genAI (founded in 2019) with the ambition to reshape how people work.

    • Glean answers questions and completes tasks using enterprise context
    • Positioned as a “more powerful ChatGPT” for work
    • Founded in early 2019 as an early enterprise genAI company
    • Goal: transform knowledge work and productivity
  3. 1:38 – 2:08

    Arvind’s builder background: engineering identity and prior startups

    He traces his path through multiple startups and early Google, emphasizing that he identifies primarily as an engineer and product builder. He notes he didn’t set out to be a founder—companies emerged from wanting to solve real technical problems.

    • Computer science background; long career across startups
    • Experience at Google pre-IPO
    • Co-founded Rubrik (2014) before Glean
    • Motivated by product-building more than entrepreneurship
  4. 2:08 – 3:09

    Why start over after Rubrik: productivity collapse from knowledge friction

    As Rubrik scaled, Arvind noticed productivity per person declining across key metrics. Employee feedback pointed to a consistent pain: people couldn’t find internal information or the right experts, creating widespread frustration and wasted time.

    • Scaling revealed worsening per-person productivity metrics
    • Root cause: inability to find information inside the company
    • Second pain: difficulty finding the right people to help
    • Insight: knowledge friction is universal across companies
  5. 3:09 – 3:39

    From problem to company: deciding to build Glean

    Arvind describes how the opportunity felt obvious once he saw the scope of the problem. He didn’t start with a desire to found a company; he started with a technical/product mission, and forming a company became the means to build it.

    • Motivation: reduce frustration and help people work better
    • Belief that solving internal knowledge access is high-impact
    • Entrepreneurship as a vehicle, not the initial goal
    • Early vision: help every company’s employees be more productive
  6. 3:39 – 4:39

    Why enterprise search is hard—and why the category had “buyer fatigue”

    He explains the technical complexity of enterprise search: unifying many data types and understanding business context and activity. He also highlights the market challenge: many prior enterprise search products failed, leaving skepticism that had to be overcome.

    • Need to unify diverse sources: docs, tickets, images, etc.
    • Requires semantic understanding plus organizational context
    • Historical failures created deep category distrust
    • Glean had to fight the perception that enterprise search is “bad”
  7. 4:39 – 5:40

    Cold outreach humility: selling before you have a product

    To validate the idea, Arvind tried connecting with industry leaders on LinkedIn to get feedback—often getting no responses. He describes this as a humbling, stamina-building experience that tested conviction amid rejection and slow progress.

    • Early customer discovery via LinkedIn outreach
    • Difficulty securing even 30 minutes from strangers
    • Founder learning curve: selling and business development
    • Need for mental fortitude through disheartening phases
  8. 5:40 – 6:41

    Conviction + quality bar: aiming for Google-level expectations

    Arvind explains that nearly everyone agreed the problem was real, even if leaders weren’t used to buying a solution. Because they felt they had only one shot, the team chose to wait and invest until the experience met the “Google-quality” bar users expect from search.

    • Universal agreement: workplace info-finding is painful
    • Market risk: leaders weren’t accustomed to purchasing this category
    • Belief they had one chance—quality had to be exceptional
    • Decision to delay launch until experience felt “Google-quality”
  9. 6:41 – 7:12

    Two-year stealth + free beta: usage as proof and internal ‘revolts’

    The team used the product internally and offered it free to design partners for two years, watching for authentic pull. Strong usage and enthusiasm—including backlash when security teams tried to shut it down—validated that the product had become indispensable.

    • Dogfooding: the team couldn’t live without early Glean
    • Two years free for ~20 design partners
    • Signal: users raved even without being charged
    • Security shutdown attempts triggered internal “revolts”
  10. 7:12 – 8:13

    From word-of-mouth to Sequoia and a smooth GA monetization

    By 2022, Glean’s reputation spread through the free beta, drawing inbound investor interest rather than requiring heavy pitching. When Glean went GA and began charging, the transition was smooth because customers already expected it and saw clear value.

    • Sequoia invested in 2022 after product buzz
    • Investor interest came inbound due to word-of-mouth
    • GA announcement converted design partners into paying customers
    • Pricing felt natural because value was proven over time
  11. 8:13 – 9:44

    Build less, win more: partner on models; innovate on enterprise context

    Arvind outlines Glean’s engineering philosophy: don’t rebuild foundation models; integrate the best available (Google/OpenAI/Anthropic) and focus engineering on what makes AI work inside enterprises. The differentiator is delivering enterprise context, governance, and real workflows—not just model capability.

    • Core philosophy: don’t reinvent the wheel
    • Leverage leading foundation models instead of training your own
    • Customers want solved problems, not proprietary model bragging rights
    • Key challenge: injecting enterprise context models don’t have
  12. 9:44 – 10:44

    Scaling focus: pure-play enterprise AI and staying ahead

    He notes Glean is now a large company (1,000+ people) but remains focused on a single mission: making AI effective in the enterprise. Staying ahead comes from focus, investment, speed, and smart strategic choices that ride industry innovation.

    • Glean at 1,000+ employees; no longer a small startup
    • Pure-play enterprise AI with no legacy product distractions
    • Heavy investment in enterprise AI enablement
    • Competitive edge: focus + agility + leveraging ecosystem innovation
  13. 10:44 – 11:58

    Founder advice: belief, validation, and protecting your own idea

    Arvind closes with guidance for founders: start with belief grounded in a real problem, validate with conversations, then hold conviction through skepticism from investors and candidates. The key is not becoming the person who talks themselves out of the idea.

    • Belief and conviction are foundational for founders
    • Validate the problem with enough real conversations
    • Expect lukewarm reactions from investors and hires
    • Don’t ‘kill your own idea’ by abandoning conviction too early

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.