> For the complete documentation index, see [llms.txt](https://docs.leanscale.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leanscale.team/measuring-metrics/sales-metrics.md). # Sales Metrics {% embed url="" %} ### 1. Bookings to Plan * Definition: The value of signed contracts, representing expected revenue. * Segments: Company level, territories/regions, individual goals. * Importance: Key performance indicator reflecting business goals. ### 2. Sales Cycle and Conversion Rates * Definition: Time and percentage of conversion from sales qualified lead to closed opportunity. * Segments: The stages between a sales qualified lead and a closed deal. * Importance: Informs marketing team's sales qualified lead goals and planning. ### 3. Weighted Pipeline Forecast and Coverage * What is it? A predictive measure of whether we’ll hit our bookings target, calculated by applying weights to open opportunities based on stage, qualification, and deal health. * Segments: Opportunities in the system with weights assigned. * Significance: Aids in the assessment of progress towards our booking goals. ### 4. Pipeline Created * Definition: Measures the speed of generating new sales qualified leads. * Segments: By rep, lead source. * Importance: Ensures enough pipeline coverage and evaluates lead source performance. ### 5. Win-Loss Analysis * Definition: The examination of opportunities that were not secured, to pinpoint the reasons behind the outcome. * Segments: Lost opportunities. * Importance: Provides insights for improving sales strategies and product offerings. ### 6. Pipeline Development Over Time * Definition: Compares pipeline changes over time, such as month-to-month or quarter-to-quarter. * Segments: Time increments. * Importance: Identifies trends and patterns in pipeline movement. --- # 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.leanscale.team/measuring-metrics/sales-metrics.md?ask=&goal= ``` `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.