# Deal Pipelines

Pipelines in Projetly define the stages your deals move through, ensuring every opportunity follows a structured sales process.&#x20;

Each pipeline represents a sequence of deal stages (such as *Discovery*, *Proposal*, *Negotiation*, *Closed Won etc*), helping sales teams visualize where every deal stands and what actions are needed next.&#x20;

Pipelines are used while creating a new deal. Click on 'Add Pipeline'&#x20;

| Label                | Action                                                | Description                                                                                                                                                    |
| -------------------- | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Template Name        | Add a name for the Pipeline                           | For example, Standard B2B Sales Pipeline, Enterprise Sales Pipeline etc.                                                                                       |
| Template Description | Add a brief description                               | Description is optional and helps identify the pipeline purpose                                                                                                |
| Add Stage Name       | Add stages within the pipeline and click 'Add Stage'. | For example, for the standard B2B sales pipeline, stages can be lead qualification, discovery call, proposal shared, negotiation, closed won, and closed lost. |

Click on 'Create Pipeline' to save.&#x20;


---

# Agent Instructions: 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:

```
GET https://docs.projetly.ai/home/documentation/administration/deal-pipelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
