> For the complete documentation index, see [llms.txt](https://www.lawfirm-operations.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.lawfirm-operations.org/roundtables-and-exchange/session-7-has-outsourcing-become-obsolete-in-light-of-the-changes-brought-by-ai.md). # Session 7: Has outsourcing become obsolete in light of the changes brought by AI? ## About the Speaker: Markus Fuhrmann, Partner at KPMG Law ## Abstract: The rapid advancement of artificial intelligence is reshaping the way law firms operate. From document review and legal research to client communication and administrative processes. These developments raise important strategic considerations for staffing models.\ Will in-house teams expand their capabilities and reduce reliance on external providers?\ Could AI shift the cost-benefit equation that once made outsourcing an attractive solution?\ What new skills will be required, and how should law firms adapt their talent strategies? --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.lawfirm-operations.org/roundtables-and-exchange/session-7-has-outsourcing-become-obsolete-in-light-of-the-changes-brought-by-ai.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.