> 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-14-der-gap-zwischen-feeearner-und-feeburner.md).

# Session 14: Der Gap zwischen „FeeEarner“ und „FeeBurner“

Thursday, May 21st 2026

Law Firms – der Gap zwischen „FeeEarner“ und „FeeBurner“ | Der Blick von außen - wie ein Dienstleister die Kanzleien von heute wahrnimmt 

### About the Speaker:

[Olivia Engels](https://www.linkedin.com/in/olivia-engels-b9aa351a1/), DACH Account Manager at Morae

### Abstract

Einigen Studien zufolge erfolgen nur zwischen 20 – 40 % der Wertschöpfung in der Kanzlei durch die FeeEarner. Die Wahrnehmung ist aber andersherum. Das spiegelt sich auch beim Invest in IT, Legal Tech und KI – im Fokus stehen Harvey, Legora & Co, also Tools für die rechtliche Beratung, während Operations noch im Abseits steht.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.lawfirm-operations.org/roundtables-and-exchange/session-14-der-gap-zwischen-feeearner-und-feeburner.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.