> For the complete documentation index, see [llms.txt](https://docs.darcyiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.darcyiq.com/grow/customer-intelligence/opportunities.md). # Opportunities Opportunities are the revenue moments on an account: a renewal coming up, a new product to cross-sell, room to expand a successful engagement. Customer Intelligence captures them, scores them, and gives your team a clear lifecycle to work them — so expansion is proactive, not accidental. {% hint style="success" %} **A proactive expansion pipeline**: The agent spots that a customer's successful POC could expand into a paid rollout, records it as an opportunity with an estimated value and a recommended next step, and the account manager reviews it, accepts it, and works it — all without leaving the account. {% endhint %} ## Anatomy of an Opportunity | Field | Description | | ---------------------- | -------------------------------------------------------------------------------------------------- | | **Title** | Short description of the opportunity | | **Type** | Cross-sell, Upsell, Renewal, Expansion, or New service | | **Estimated value** | A T-shirt size — Small, Medium, Large, or Extra large — mapped to a dollar value for pipeline math | | **Confidence** | The agent's confidence (0-100) that the opportunity is real | | **Recommended action** | The concrete next step to advance it | | **Priority** | A computed 0-100 priority score and a High / Medium / Low tier | | **Status** | Where it sits in the lifecycle (see below) | | **Stale flag** | Marks opportunities with no recent movement so nothing falls through the cracks | Priority, weighted value, and the stale flag are all derived from your organization's settings — see [Health Score & Scoring Settings](/grow/customer-intelligence/settings-and-scoring.md). ## The Opportunity Lifecycle Opportunities move forward through **New -> Reviewed -> Accepted**, and can be **Promoted** to your CRM or **Dismissed** at any point. ```mermaid stateDiagram-v2 [*] --> New New --> Reviewed Reviewed --> Accepted New --> Dismissed Reviewed --> Dismissed Accepted --> Promoted Accepted --> Dismissed Promoted --> [*] Dismissed --> [*] ``` | Status | Meaning | | ------------- | ---------------------------------------------------------------------------------------------------- | | **New** | Freshly surfaced (usually by the agent); not yet reviewed | | **Reviewed** | An account team member has looked at it and it's ready for a decision — *not* a commitment to pursue | | **Accepted** | The team has committed to pursuing it | | **Promoted** | Pushed forward as a real deal (e.g. to your CRM) | | **Dismissed** | Set aside, with a reason captured for the feedback loop | {% hint style="info" %} **Reviewed means "ready for your review," not "moving forward."** It signals the opportunity is worth a decision; the team still moves it to Accepted to commit. Moving an opportunity to Reviewed or Accepted notifies the account team — see [Notifications & Digests](/grow/customer-intelligence/notifications.md). {% endhint %} ## Managing Opportunities The **Opportunities** tab on a customer is where the pipeline is worked: * **Filter** by Stage, Priority, and Source using compact dropdown pills * **Advance** an opportunity to the next status, or **Dismiss** / **Promote** it * **Bulk update** status across multiple opportunities at once ## CRM Deal Linkage When your CRM (Salesforce, HubSpot, or Microsoft Dynamics) is connected, opportunities can be linked to CRM deals via a deal reference, and CRM deal stages map into Customer Intelligence statuses on sync. {% hint style="info" %} **Closed-lost deals become Dismissed.** By default, a synced CRM opportunity whose stage indicates *closed lost* is mapped to **Dismissed** in Customer Intelligence (matched flexibly, so appended stage text like "Closed Lost - Budget" still resolves). See [CRM Sync](/grow/customer-intelligence/crm-sync.md). {% endhint %} ## Next Steps | Goal | Documentation | | ----------------------------------------------- | --------------------------------------------------------------------------------------- | | See where opportunities come from | [The Account Management Agent](/grow/customer-intelligence/account-management-agent.md) | | Tune deal sizing, priority tiers, and staleness | [Health Score & Scoring Settings](/grow/customer-intelligence/settings-and-scoring.md) | | Sync deals from your CRM | [CRM Sync](/grow/customer-intelligence/crm-sync.md) | | Get notified on status changes | [Notifications & Digests](/grow/customer-intelligence/notifications.md) | --- # 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.darcyiq.com/grow/customer-intelligence/opportunities.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.