> ## Documentation Index
> Fetch the complete documentation index at: https://docs.buildbetter.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Pipeline

> Opportunity pipeline from Attio and/or Salesbricks, enriched with Health and Convert context

The Pipeline page (`/success/pipeline`) shows opportunities as a kanban board, table, and settings view. It overlays health, usage, conversion likelihood, and renewal context onto CRM pipeline data.

## Live Data Requirements

Pipeline can use **Attio** and/or **Salesbricks**:

* With Attio connected, pipeline items can support editable stage movement.
* With Salesbricks only, open orders are shown as read-only pipeline items.
* If neither is connected, the page shows **Pipeline is not connected yet** with **Open Integrations** and **Preview with demo data**.

Optional HubSpot and Salesforce sources may appear in the source filter when the pipeline data layer returns them.

## Summary Cards

The live page shows:

* **Total deals**
* **Active deals**
* **At risk**
* **High likelihood**

These cards summarize the currently loaded pipeline data and the Success overlays attached to it.

## Views

### Kanban

Kanban is the default view. Columns come from the connected source's stage options. Cards show the opportunity/account and key context. Dragging stage-editable Attio deals between columns updates the stage; Salesbricks open orders are read-only.

### Table

The table view is better for comparing many opportunities. Each row shows:

| Column      | Meaning                                                       |
| ----------- | ------------------------------------------------------------- |
| **Deal**    | Company or opportunity name plus owner/domain.                |
| **Source**  | Attio, Salesbricks, HubSpot, or Salesforce when available.    |
| **Stage**   | Current stage, with inline editing when the item is editable. |
| **Value**   | Opportunity value.                                            |
| **Health**  | Health score and risk badge, or no health match.              |
| **Usage**   | Active-user context when matched.                             |
| **Convert** | Conversion likelihood when matched to a trial candidate.      |
| **Renewal** | Days until renewal, or Unknown.                               |

### Settings

The Settings tab configures which connected pipeline sources and stages should be surfaced. It is useful when your CRM has many stages but only some represent active pipeline.

## Source Filter

If multiple eligible sources are connected, the page shows a source filter:

* **All sources**
* **Attio**
* **Salesbricks**
* **HubSpot**
* **Salesforce**

The exact options depend on connected sources returned by the backend.

## Partial Enrichment

Pipeline can be live while some overlays are missing. For example, a deal may have no health match, no usage match, or no trial match. When broader coverage is incomplete, the page shows a warning above the summary cards.

## Routing From Pipeline

Pipeline is where deal context meets customer-success risk:

* Route to **Health** when an opportunity exposes account risk.
* Route to **Convert** when a trial should return to conversion outreach.
* Route to **Contracts** when a deal becomes a contract/subscription workflow.
* Route to **Re-engage** when an opportunity goes closed-lost but remains worth revisiting.

## Demo Mode

**Preview with demo data** loads sample pipeline records so you can inspect the kanban, table, filters, and overlays without Attio or Salesbricks connected.

<Tip>
  Watch for the combination of a late-stage opportunity and critical health. Pipeline makes that conflict visible so the account team can intervene before the deal slips.
</Tip>
