> For the complete documentation index, see [llms.txt](https://docs.3dolphins.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3dolphins.ai/5.1.x/sales-activity/deal/pipeline.md).

# Pipeline

A pipeline is a defined set of stages for tracking a process. This helps the sales team to be able to make deals consistently. Only the **Sales Manager** and **Admin** can add and edit the pipeline.

The image below is an example of a sales pipeline. From the picture below, we can see that there are several stages of sales, namely New Deals, Product Presentation, Aanwijzing, and Final Deal. This sales stage can be different for each company and you can customize stages for your business in the pipeline.

At each stage, you can see the potential sales value. This value is the total value of the sales opportunity at each stage of the sale. This value does not reflect the company’s potential sales, because at each stage there is still a percentage of the opportunity as described above.

![Deal ](/files/-MToAaSstFjcmTW1XzIO)


---

# 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://docs.3dolphins.ai/5.1.x/sales-activity/deal/pipeline.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.
