> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/etats/preisliste.md).

# The price list concept

We created a short video to introduce you to the **pricing list concept** and the **differences between agency and customer account price lists** If you prefer to read the content, you can find all the information further down on this page.

{% embed url="<https://www.youtube.com/watch?v=DWgqGZg8Q_I>" %}

{% embed url="<https://www.youtube.com/watch?v=4mQQ-w-H3No&t=1s>" %}

### What is a price list?&#x20;

A price list describes all functions or types of services offered by an agency with the respective hourly rate. For example, an agency offers consulting, copywriting, design and art direction services. These functions are listed in the price list together with the hourly rates. An employee can select one or more functions when recording their working time, if applicable.\
\
Which function an employee can use to record time can be configured on the employee.

{% content-ref url="/pages/6ad60844b9e6dcb9e9361a7bd64c4a76331d1c90" %}
[Functions](/die-agenturverwaltung-en/einstellungen-1/zeiterfassung/funktionen.md)
{% endcontent-ref %}

### What should be considered for price lists?&#x20;

Less is often better: too many functions increase complexity and make the price list and functions confusing for project staff, accounting and customers. Some functions are used more frequently than others. These should be quickly selectable. In the user management, functions can be individually sorted for each user.

### Customer account price list and the agency price list

What if we negotiated different conditions with a customer than those in the existing agency price list? Reasons for this can be, for example, special conditions offered or historically conditioned contractual terms that remain valid for a long-standing customer.

To support this, Die Agenturverwaltung enables the **configuration of price lists in customer accounts**. In Die Agenturverwaltung there is therefore a cross-customer, overarching agency price list and a price list for each individual customer account with its associated jobs. It is explicitly possible to even maintain two customer accounts with different prices within one customer.\
When a new customer account is created, it initially uses the overarching agency price list. After the customer account is created, the customer account price list is adjusted according to the agreements with the customer.

In the customer account price list, the general hourly rate for a function can be overridden for all jobs of that customer account.

New functions are added in the overarching agency price list. The designation of the functions can be changed here across customer accounts:

{% content-ref url="/pages/96240e3033c741dbab2cea1007326612d09d41a7" %}
[The standard price list of agency services](/die-agenturverwaltung-en/onboarding/initial-financial-settings/funktionen.md)
{% endcontent-ref %}

## Define templates for customer account price lists on the customer

Price list templates can also be defined on the customer. However, we recommend this only in exceptional cases; here is how to do it:

{% content-ref url="/pages/a3f0ed4b5313432f1bda123cb36d07ca002ae77f" %}
[Templates for customer account price lists](/die-agenturverwaltung-en/projektverwaltung-1/untitled/einstellungen.md)
{% endcontent-ref %}


---

# 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/projektverwaltung-1/etats/preisliste.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.
