> 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/what-is-an-opportunity.md).
# What is an Opportunity?
Simply put, an **Opportunity** is when one of your Contacts expresses an interest in a product or service you offer.
For example:
* Your Contact talks about a budget amount for an upcoming project they are considering.
* They talk to you about a proposed deadline.
* They ask you detailed questions about the services or products that you offer.
* You have been invited to visit the client for a meeting about your services.
All of these could be considered buying signs, and may indicate your prospect is interested in becoming a customer. As a business, you will need to decide what constitutes a **trigger** to create an Opportunity.
Depending on your business or industry there may be a variety of reasons to add an Opportunity to Daylite. Maybe one or more prospects you have been working on expresses *buying signs* or perhaps an existing client contacts you to talk about a repeat service or product purchase.
In any case, it is important for you to decide on when you should create New Opportunities.
{% hint style="success" %}
**Pro Tip:**
If you are reasonably confident that this deal will move forward, you should add them as a New Opportunity, and immediately assign a **Pipeline**.
{% endhint %}
---
# 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/what-is-an-opportunity.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.
