View as agent
This is what an AI agent reads. Same page, second kind of user.
Every page on this site has a markdown version that agents can read, cite, and act on, with links that lead to more markdown. Your software is getting the same new user. We help make it ready.
/case-studies/enterprise-genai-people-operations.md162 lines · 7 KB · text/markdown
---title: "Enterprise GenAI for People Operations | Case Study"description: "How we consolidated people ops knowledge across a PE roll-up into one SharePoint repository and deployed a generative AI assistant for the entire enterprise."url: https://appstream.studio/case-studies/enterprise-genai-people-operationsmarkdown_url: https://appstream.studio/case-studies/enterprise-genai-people-operations.md--- [Home](https://appstream.studio/index.md) · [Work](https://appstream.studio/case-studies.md) Private Equity Private Equity/ Engineer · Operate # One AI assistant. Every acquired company's HR knowledge. One place to ask. A PE-backed study abroad provider had acquired multiple companies, each with its own HR systems, policies, and tribal knowledge. We consolidated everything into SharePoint and built a generative AI assistant that answers people ops questions across the entire enterprise. Client PE-Backed Enterprise Engagement Ongoing Focus RAG + AI Assistant Compliance Enterprise data governance  01 ## The work One of the nation's largest private equity-backed study abroad program providers, formed through serial acquisition. Multiple companies operating under one umbrella, each with its own systems, policies, and institutional knowledge. What was getting in the way - Every acquisition brought its own HR systems, policy documents, and SOPs. Nothing was consolidated.- Employees had no single place to find answers. They had to know which legacy system from which acquired company held the information.- Every new deal compounded the problem. More systems, more doc formats, more policies that may or may not align.- Finding basic HR information meant knowing who to ask, not where to look. Institutional memory was the search engine.- The people ops function couldn't scale with the acquisition pace. Each integration was manual discovery and reconciliation. 02 ## What changed Consolidate everything. Then put AI on top. We started by mapping the people operations landscape across every acquired entity. Where documentation lived, what formats it was in, what questions employees were actually asking, and which sources they were using or failing to find. 03 ## What we built We deployed an enterprise SharePoint system as the single repository, organized by function and policy area. All people ops documentation from every acquired company — SOPs, benefits, policies, procedures — migrated, structured, and indexed for AI retrieval. Then we built the generative AI assistant on top of it. Employees ask natural language questions about HR, benefits, policies, or procedures and get answers grounded in the company's actual documentation. Not generic responses. Sourced, verifiable answers from indexed content. And when the next acquisition closes, their docs get added to the same knowledge layer. AI Agents RAG Pipelines SharePoint Architecture Knowledge Management 04 ## How it works - All people ops documentation consolidated from multiple acquired companies into one enterprise SharePoint repository- Generative AI assistant deployed enterprise-wide for natural language HR queries- Answers grounded in actual company documentation, not generic AI responses- Repeatable onboarding process for new acquisitions — add their docs, they're searchable- HR teams fielding fewer basic information requests. Employees finding answers on their own.- First enterprise AI deployment for the company, with architecture designed to expand beyond people ops 05 ## Business impact of employees 100% AI assistant deployed across every acquired company knowledge layer 1 Consolidated from scattered systems across multiple acquisitions rebuild per deal 0 New acquisitions onboarded into the same knowledge layer > “We had HR information scattered across every company we'd acquired. Now any employee can ask a question and get the right answer, sourced from the actual policy. It scales every time we do another deal.” Ryan Sylvester , CIO, CEA CAPA 06 ## What’s next Turn acquisition sprawl into AI-powered access If your portfolio companies have fragmented knowledge across systems and acquisitions, we've built the playbook to consolidate and deploy AI on top. [Talk to an AI engineer](https://appstream.studio/schedule-a-discovery-call.md) · [More work](https://appstream.studio/case-studies.md) Team - Justin Tannenbaum Solutions Architect- Lukasz Chmielewski Lead Engineer- Cesar Bustamante Engineering- Taylor Larson Product Manager- Ernesto Quispe Product Design Stack .NET · Azure · SharePoint · M365 · Semantic Kernel · MAF Related - [Engineer](https://appstream.studio/solutions/engineer.md)- [Operate](https://appstream.studio/solutions/operate.md)- [Agent Engineering](https://appstream.studio/solutions/agent-engineering.md)- [Agent Knowledge Layer](https://appstream.studio/solutions/agent-knowledge-layer.md)- [Private Equity](https://appstream.studio/industries/private-equity.md) More work ## Keep reading. [All work](https://appstream.studio/case-studies.md) - [Healthcare/ Engineer · Operate A scheduling engine on a legacy EMR books 250,000 appointments a year. Read the case study](https://appstream.studio/case-studies/healthcare-scheduling-transformation.md)- [Healthcare/ Engineer AI scores reimbursement likelihood before a medical device ships. Read the case study](https://appstream.studio/case-studies/ai-reimbursement-eligibility-engine.md)- [Proptech/ Engineer A 50-state buy-side marketplace, with search that understands intent. Read the case study](https://appstream.studio/case-studies/buy-side-marketplace-agentic-search.md) --- ## AppStream Studio AppStream turns frontier AI capabilities into production systems that perform real work. Talk to an AI engineer: https://appstream.studio/schedule-a-discovery-call · Email: contact@appstream.studio - [Home](https://appstream.studio/index.md)- [Solutions](https://appstream.studio/solutions.md)- [Advise](https://appstream.studio/solutions/advise.md)- [Engineer](https://appstream.studio/solutions/engineer.md)- [Operate](https://appstream.studio/solutions/operate.md)- [Govern](https://appstream.studio/solutions/govern.md)- [How we work](https://appstream.studio/how-we-work.md)- [Work (case studies)](https://appstream.studio/case-studies.md)- [Industries](https://appstream.studio/industries.md)- [Insights](https://appstream.studio/blog.md)- [Partners](https://appstream.studio/partners.md)- [About](https://appstream.studio/about-us.md)- [Contact](https://appstream.studio/contact.md) Agents are becoming a second user of your software. Readable content is the start. Scoped, auditable access for agents to act is the next step.
Talk to an AI engineer