Glean lands in engineering and support

The key to Glean’s sales motion is that it can prove value in one team before asking an entire company to standardize on it. Engineering and support are natural beachheads because they already live in systems like Jira, Confluence, Slack, and Zendesk, where workers constantly hunt for past decisions, docs, and answers. Once Glean is wired into those systems and seat usage spreads, the same retrieval layer can be sold into adjacent teams, which helps explain how seat expansion has been a major driver of revenue growth from $100M ARR to $200M ARR.1 2 3

• The first departmental sale is usually easy to justify because Glean is priced like a broad employee tool, not a niche expert system. Research on Glean notes plans starting around $30K per year and scaling to more than $5M for very large deployments, which fits a start with one team, then add more seats motion.1
• Horizontal search products work best when many employees across many apps need the same answer layer. Glean’s differentiation is that it searches across Slack, Zendesk, Confluence, Notion, and Jira, instead of staying inside one suite, so every new department added makes the product more useful and harder to replace.2
• This is different from vertical AI tools like Hebbia, which are sold to a small number of high value users in finance and legal at much higher per seat prices. That contrast helps explain why Glean pushes for wall to wall adoption after the initial land, while vertical tools expand by adding workflows, not broad employee coverage.3

Going forward, the expand motion should get even stronger as Glean moves from search into agent building. Once one team uses Glean to find information, the next sale is letting more teams use that same connected data to automate work, which turns a search deployment into a broader internal tools standard.2 4