> 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-6-9-months-of-law-firm-operations-where-do-we-stand.md).

# Session 6: 9 Months of Law Firm Operations – Where Do We Stand?

## About the Speaker: 

Michael Roth: Senior Manager at KPMG Law

## Abstract: 

After nine months of focused work under the umbrella of our Law Firm Operations initiative, it's time to take stock: Where do we stand today – and what lies ahead?

\
We’ll be exploring three bold theses that reflect the core pillars of the overarching project:\
Legal Professionals: “The job of the traditional lawyer is dead.”\
What does this mean for roles, training, and (future) careers in law firms?\
Economic Questions: “Who’s going to pay for AI?”\
Between investment pressure and viable business cases – how do we make new technologies economically sustainable?\
Execution: “Established law firms are too slow to keep pace with current developments.”\
What does it take to move beyond innovation talk and truly drive change?


---

# 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-6-9-months-of-law-firm-operations-where-do-we-stand.md?ask=<question>&goal=<endgoal>
```

`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.