Talk about your next project
Glean case study

The lesson

Lead with the customer’s quantified business case, then explain the knowledge-access problem in plain operational terms.

The move

The page opens with the title “Duolingo achieves 5x ROI, saving 500+ hours monthly with Glean’s AI-powered knowledge tools,” followed by a “See the full customer story” button and anchor links for “The challenge,” “The solution,” and “The impact.” Before the story begins, two result callouts state “>$1.1M in yearly time savings” and “5x ROI.” The body then moves through scattered information across Google Drive, Slack, Confluence, and Zendesk, the limits of Duolingo’s internal Metasearch tool, Glean connecting existing tools, and Glean Chat as a faster way to get answers. The impact section repeats the time saved and yearly savings, with quotes from Art Chaidarun, Principal Software Engineer at Duolingo.

Why it works

  • Our readThe result callouts arrive before the problem, so a reader can understand the business value before reading the full story.
  • Our readNaming the prior tools and Duolingo’s internal Metasearch makes the challenge specific instead of a generic search problem.
  • Our readThe customer quote about Glean Chat explains a product capability through a user behavior: asking Glean instead of sending Slack messages.

What not to copy

Don't copy Duolingo’s Metasearch name, its language-learning context, or Art Chaidarun’s comparison to ChatGPT and Google. Keep the structure of quantified value first, then scattered-work problem, prior workaround, connected solution, named feature, and customer-owned impact.

More from Glean

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.