> 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/opportunities/probability.md).

# Probability

This is a percentage scale from 0% to 100%, and is intended to represent the likelihood that the Opportunity will have a successful outcome. In Daylite, the Probability is considered a **subjective value** that you should update regularly as your Opportunity progresses along the Pipeline. It represents your current level of confidence in a successful outcome, based upon everything that is currently known about your Opportunity.

The Probability in Daylite is **not** tied to the **actual value** of the Opportunity.&#x20;

Assigning a 75% Probability to a $10,000 deal does not change the total Value of the Opportunity to $7,500.&#x20;

The Probability value **does not** control the Stage in an Opportunity.&#x20;

For example, an Opportunity might only be in the initial Stage of the Pipeline but has a probability of 80%. This means that there is a high level of confidence that the Opportunity will have a successful outcome. In this case it might be a repeat transaction or there has been direct communication from the client to indicate that it will happen.&#x20;

Alternatively, an Opportunity might have progressed quite far along the Pipeline, but still have a relatively low probability, let's say 30%. There may be a tender process with multiple other competitors, and the outcome may be partially out of your control.

<figure><img src="https://4293187824-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fyn0qJKdoNp6M4xqrQfMG%2Fuploads%2FQGHncM9qUmrgMRcccZ9C%2Fprobability%5Cnew-opportunity.png?alt=media&amp;token=b9cffedc-e096-4777-894e-5b5936eabb67" alt=""><figcaption></figcaption></figure>


---

# 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/opportunities/probability.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.
