> For the complete documentation index, see [llms.txt](https://docs.daylite.app/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.daylite.app/help/sales-guide/forecasting-your-sales/what-is-sales-forecasting.md).

# What is Sales Forecasting?

Simply put, sales forecasting allows you to make future predictions about multiple Opportunities, and as a result, larger operational decisions about your business development activities.

As you know, on an individual level, each Opportunity allows your team to:&#x20;

* Keep all client communications in one place.
* Provide key parameters such as State, forecast close date, total value, contacts involved etc
* Track the progress via a Pipeline.&#x20;
* Log upcoming and completed Tasks.
* Provide progress updates through the use of Notes.

&#x20;Working with multiple potential deals, you need to be able to properly analyze and compare all of your Opportunities at a glance. Only by having visibility of all the key parameters in a single view can you get a full picture of new business activity.

&#x20;This will help you with:

* Prioritizing resources in order to close Opportunities.
* Cashflow&#x20;
* Sales funnel management


---

# 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://docs.daylite.app/help/sales-guide/forecasting-your-sales/what-is-sales-forecasting.md?ask=<question>&goal=<user_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.
