Owners know the moment when answers start to drift. Two people tell customers two different things, a document goes stale, and the one person who knew the right answer is on vacation.
Lemonade, the insurance company, faced that at scale. Its Learning & Development team supports over 500 globally distributed Makers across Customer Experience, Claims and Underwriting. Anthony Manluccia, Training Lead, L&D, describes the team's answer in a vendor customer story published by Guru.
What Lemonade did
According to Guru's April 2026 story, the team built a lightweight workflow in Slack that sends every knowledge request through one governed pipeline: Guru for knowledge, Zendesk macros for customer communications and 360Learning for training content. Requests arrive through a central Slack channel with structured forms. Zapier routes them by department, product or workflow and tags the right content owner, and the whole discussion stays in one thread.
Subject matter experts write the first draft, so the content owners can focus on governance and accuracy. In Manluccia's words: "We ask stakeholders to submit the first draft". Google Sheets tracks request type, volume, who handled each request and turnaround time, and a scheduled December audit catches knowledge that came in outside the request flow.
What it already gives the business
As reported by Guru, the team processes 200 to 300 knowledge requests a month, sees 90% weekly Guru adoption and reached a 93% accuracy rate in the annual audit. Its Pet Claims Collection of over 2,000 Cards is 100% verified.
The tracking also changed planning. Guru reports data-driven workload planning that led to hiring an additional team member to support high-volume teams. Manluccia: "This system gives us visibility into what we're doing, helps our manager understand capacity, and shows stakeholders the impact of our work."
The ExValu perspective, a hypothesis
Where a Company Brain could take it next
Lemonade is a large public company, so the useful part for a smaller business is the model: experts write, one person verifies, every request is logged and once a year someone audits the lot. All of that can run on a shared channel, a form and a spreadsheet.
A Company Brain could add the reasons behind the content: why a claims rule changed, which customer complaint led to a new macro. The knowledge base would then answer why as well as what. That is our hypothesis, and the customer story does not describe it.
What an owner and a buyer would look for
Track requests per month, turnaround time, the share of verified content and the result of each annual audit.
A buyer's due diligence looks for exactly this trail: who asked for a change, who approved it and when it was last checked. A request log and audit results show that knowledge is kept current by a process a new owner can run. Keep customer personal data out of request threads and knowledge articles.
The problem behind this case
Facing the same problem?
About this analysis
* The image is AI-generated and does not show Lemonade staff. The facts and figures on this page come from the published source named below.
This is an independent ExValu analysis of a published case. Facts, figures and names are as reported in the source below, which our team checked on October 14, 2026. The ideas for next steps are our own perspective and make no claim about conditions inside Lemonade. To request a correction or removal, write to [email protected].
Primary source: Vendor customer story, Guru, April 2026. Available at www.getguru.com/customers/lemonade-trusted-knowledge-scale.