From a 70-Page Playbook to an Answer Engine

Case study: turning 70 pages of internal knowledge into answers every employee could reach.

A founder-led company partnered with Open Sesame to solve a problem that grows with every hire: the knowledge that made the business work lived in one person’s head and a 70-page playbook that nobody could navigate quickly.The goal was simple. Stop the same questions landing on the founder and senior team, and give the whole company consistent, source-grounded answers drawn from documents it already owned.

The problem

The company’s hardest-won knowledge was real, written down, and almost impossible to reach in the moment. Employees interrupted senior staff for answers that already existed somewhere in the playbook.Senior people pulled into repeated, answerable questions instead of higher-value work.Inconsistent answers depending on who you happened to ask.Knowledge at risk every time an experienced person left.

The approach

We connected Open Sesame to the company’s existing documents, including that 70-page playbook. No migration, no change to where files lived, no new workflow for employees. Within days, the whole team could ask plain-language questions in the browser and get consistent, source-grounded answers.

The outcome

The founder’s knowledge stopped being a bottleneck. The questions that used to interrupt senior staff now answer themselves, with the source attached. New employees ramp faster, and every answer points back to an approved document. The team shifted from answering repeat questions to the work only they could do, with knowledge that no longer walks out the door. Live in five business days, from connecting documents to the team’s first answers.
What do you think?

From our blog

Articles & insights

Your policies, SOPs, and playbooks already hold the answers your team needs. The problem is reaching them. Here is why knowledge sits trapped, and what
You could build an internal answer engine on Copilot Studio. Should you? An honest look at the real cost of DIY knowledge AI versus buying
Before you put AI in front of your documents, run this checklist. Permissions, data residency, model training, and audit: the questions that separate safe internal