> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/estimating/creating-estimates/what-is-a-sales-rate.md).
# What is a Sales Rate?
Understand sales rate as total project price divided by total hours to determine project profitability and discount flexibility.
A sales rate in PaintScout is the total project price divided by the total project hours. It shows how much revenue each labor hour generates and helps you gauge project profitability and discount flexibility.
## Where do you find the sales rate?
Open the sidebar menu on the right of any estimate and expand the **Calculations** section.
## How is the sales rate calculated?
**Sales Rate = total project price / total project hours.**
Items that add to the price without adding hours (e.g., extra materials or flat-fee line items) increase your sales rate. Use this metric to assess project profitability and determine how much room you have for discounts.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.paintscout.com/support/estimating/creating-estimates/what-is-a-sales-rate.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
