> For the complete documentation index, see [llms.txt](https://closingdealz.gitbook.io/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://closingdealz.gitbook.io/product-docs/features/analytics/pipeline.md).

# Pipeline

### **Overview**

The **Pipeline Analytics** in **ClosingDealz** provides a detailed breakdown of your **sales funnel**, tracking deal progress, conversion rates, and the efficiency of your sales process. By analyzing how deals move through different stages, you gain **actionable insights** to improve deal progression, optimize conversions, and forecast revenue more accurately.

With **stage-by-stage tracking, conversion rates, and time-based metrics**, the pipeline analytics ensure your sales process remains transparent and measurable.

***

### **Key Features**

* **Stage-Based Tracking** – Monitor deals as they progress through the pipeline.
* **Conversion Rates** – Understand how efficiently deals transition between stages.
* **Average Time to Advance** – Measure how long deals spend in each stage.
* **Sales Velocity** – Calculate the speed of deal closures relative to deal value and close rate.

***

### **Funnel Calculations & Rules**

The pipeline analytics follow specific rules to ensure accurate calculations and meaningful insights:

**1. Skipped Stages**

* Deals that bypass certain stages are **excluded** from the funnel metrics for those skipped stages.
* This ensures that conversion rates remain **stage-specific** and are not influenced by outlier deals.

**2. Backward Movement**

* If a deal moves **backward** in the pipeline (e.g., from Proposal back to Qualified), the previously recorded forward progress is **not considered** in the funnel metrics.
* This maintains accuracy in conversion tracking without inflating progress.

**3. Conversion Rates**

* Calculated based **only** on deals that moved **directly** from one stage to the next.
* This ensures realistic conversion tracking, reflecting how deals naturally progress through the pipeline.

**4. Average Time to Advance**

* Measures the **average duration** a deal spends in a stage **before advancing** to another stage.
* Deals that **remain in the stage during the selected period** are **excluded** from the calculation.

***

### **Metrics & How They Are Calculated**

| **Metric**                        | **Description**                                                                                                                      | **How It's Calculated**                                                                          |
| --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------ |
| **Close Rate**                    | The percentage of deals that were successfully closed out of all deals that reached a final outcome (closed or lost).                | **(Number of Closed Deals ÷ (Closed Deals + Lost Deals)) × 100**                                 |
| **Average Time to Close**         | The average time it takes to close a deal, measured from the deal's creation to when it is marked as closed.                         | **(Total Time Taken for All Closed Deals ÷ Number of Closed Deals)**                             |
| **Average Value Per Closed Deal** | The average revenue generated from each closed deal.                                                                                 | **(Total Value of Closed Deals ÷ Number of Closed Deals)**                                       |
| **Sales Velocity**                | Measures how quickly revenue is generated based on the number of closed deals, their average value, and how long they take to close. | **(Number of Closed Deals × Average Deal Value × Close Rate) ÷ Average Time to Close (in days)** |

### **How to Use Pipeline Analytics**

1. **Filter by Date & User** – Analyze sales performance for a specific period or salesperson.
2. **Review Deal Flow** – Track how deals move through each stage of the pipeline.
3. **Monitor Conversion Rates** – Identify weak points where deals are dropping off.
4. **Analyze Sales Velocity** – Measure how efficiently deals are closing and generating revenue.
5. **Optimize the Sales Process** – Use insights to refine strategies, shorten deal cycles, and improve close rates.

***

### **Why Use Pipeline Analytics?**

* **Identify Bottlenecks** – Find stages where deals stagnate or get lost.
* **Improve Forecasting** – Predict future sales performance based on conversion trends.
* **Enhance Sales Strategies** – Optimize how deals progress through the pipeline.
* **Measure Team Performance** – Track how effectively sales reps are moving deals forward.

With **Pipeline Analytics**, you gain a **clear, data-driven** view of your sales funnel, helping you make smarter decisions and improve deal conversion.


---

# 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://closingdealz.gitbook.io/product-docs/features/analytics/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.
