Back office ops · Production

Webflow saves 300+ hours a month with Glean

The problem

Webflow's employees relied on Slack, Google Drive, and Atlassian to store knowledge but lacked a unified search layer, forcing manual checks across each system and leaving new hires dependent on colleagues to find resources.

Workflow diagram · grounded in source
1
Fragmented search triggered
trigger
“Webflow's teams relied on tools like Slack, Google Drive, and Atlassian to document and store information, but without a unified search solution, finding knowledge was frustrating and inefficient”
2
Glean indexes 20+ tools
integration
“Glean integrated with Webflow's 20+ business tools, indexing data and providing employees with a single, powerful search experience”
3
AI surfaces relevant knowledge
ai_action
“Employees quickly surfaced relevant knowledge, regardless of where it lived”
4
Support ticket resolution
output
“Support teams resolved tickets faster by retrieving insights from Slack, Zendesk, and Jira”
5
Self-serve onboarding
output
“New hires found onboarding materials independently, reducing reliance on tenured employees”
Reported outcome

After deploying Glean, 65% of Webflow employees use it for knowledge discovery, saving 300+ hours monthly, and over 3,400 Glean agents have been created in total.

Reported metrics
Employee adoption rate65%
Hours saved monthly300+
Glean agents created in first 6 weeks500
Glean agents created total3,400+
Reported stack
GleanSlackGoogle DriveAtlassianZendeskJira
Source
https://www.glean.com/resources/customer-stories/webflow
Read source ↗

Frequently asked questions

What did this team achieve with this AI workflow?

After deploying Glean, 65% of Webflow employees use it for knowledge discovery, saving 300+ hours monthly, and over 3,400 Glean agents have been created in total.

What tools did this team use?

Glean, Slack, Google Drive, Atlassian, Zendesk, Jira.

What results were reported?

Employee adoption rate: 65%; Hours saved monthly: 300+; Glean agents created in first 6 weeks: 500; Glean agents created total: 3,400+ (source-reported, not independently verified).

How is this back office ops AI workflow structured?

Fragmented search triggered → Glean indexes 20+ tools → AI surfaces relevant knowledge → Support ticket resolution → Self-serve onboarding.

Related back office ops cases