> For the complete documentation index, see [llms.txt](https://docs.rox.com/development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rox.com/development/product/organization-level-configurations/opportunity-stage-management.md).
# Opportunity Stage Management
Stages are the building blocks of your opportunity pipeline. From **Settings → Opportunities**, you can create new stages, edit existing ones, reorder them, and define what each stage is for.
### Stage groups
Stages are organized into three groups that reflect a deal's lifecycle:
* **Lead** — early-funnel stages before a deal is actively in flight.
* **In Progress** — active selling stages (discovery, demo, proposal, etc.).
* **Completed** — terminal stages (Closed Won, Closed Lost, Non Qualified).
You can add stages to any group using the **+** button next to the group header.
### Creating a stage
1. Go to **Settings → Opportunities**.
2. Click **+** next to the group you want to add the stage to (Lead, In Progress, or Completed).
3. Fill in the stage details (see below) and click **Save**.
### Editing a stage
Click the **⋯** menu next to any stage and choose **Edit**. The Edit Stage modal lets you configure:
* **Color** — the chip color shown in the kanban and lists. Use color to signal stage health or grouping at a glance.
* **Name** — short, recognizable label (e.g., "Discovery", "Proposal").
* **Description** — internal note about what the stage represents. Visible to admins managing the pipeline.
* **Objective** — the goal of this stage. Answers *"What are we trying to accomplish here?"* (e.g., "Confirm budget and decision-maker.")
* **Activities** — what reps should *do* in this stage. (e.g., "Schedule discovery call, send recap email, qualify on BANT.")
* **Exit Criteria** — what must be true before a deal can leave this stage. (e.g., "Decision-maker confirmed, budget verified, timeline agreed.")
* **Won** — *(Completed-group stages only)* marks the stage as a "deal won" outcome. Deals in won stages are excluded from risk generation and counted as wins in reporting. Closed Won is set to Won by default.
* **Hidden** — when toggled on, the stage is hidden from the pipeline view but existing deals in it remain.
Objective, Activities, and Exit Criteria are free-text guidance fields — they help reps understand the stage. The Rox agent uses them when **assessing deal risk** and when **deciding if a deal is ready to advance to the next stage**. Filling them in improves the accuracy of both.
### Reordering stages
Drag and drop any stage to change its position. Order matters: it controls the left-to-right flow of your kanban *and* defines what counts as "the next stage" when Sequential Stage Progression is enabled.
You can also drag stages between the Lead, In Progress, and Completed groups.
### Deleting a stage
Click **⋯** next to a stage and choose **Delete**. Before deleting, make sure no opportunities are currently in that stage — Rox will warn you if there are. If you want to retire a stage without losing history, prefer the **Hidden** toggle on the Edit modal instead.
---
# 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:
```
GET https://docs.rox.com/development/product/organization-level-configurations/opportunity-stage-management.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.