Pipelines

Pipelines let you configure deal stages — names, probabilities, colors, order, and won/lost flags — per business unit. Every tenant starts with a default sales pipeline that mirrors the legacy stage enum (Lead → Qualified → Proposal → Negotiation → Closed Won / Closed Lost) so deals from the pre-pipeline era keep working with no migration.

Navigate to Settings > Pipelines (or click the gear icon next to the pipeline switcher on the Deals page).

Pipeline List

The list view shows every pipeline with:

• A Default badge if it's the default for new deals.
• A description, if you added one.
• A row of stage chips colored by each stage's color, with Won (✓) and Lost (✗) markers on the closing stages.
• The total stage count on the right.

Click any pipeline to open the editor.

Creating a Pipeline

1. Click + New pipeline in the header.
2. Enter a name and optional description.
3. Tick Use as default pipeline for new deals if this should be the default — only one pipeline can be default at a time, and selecting a new one un-defaults the previous.
4. Add stages in the Stages table. Each row has:
   • Order — drag with the up/down arrows.
   • Name — human label (e.g. "Discovery", "Negotiation").
   • Slug — stable identifier used as the stored stageId. Auto-fills from the name; override if you need a specific string.
   • Prob. — default win probability (0-100). Used by the forecast service for weighted values when a deal doesn't carry its own override.
   • Color — hex color picker for kanban + funnel rendering.
   • Won? / Lost? — mark terminal stages. The forecast service uses these to classify deals as open / won / lost. Marking a stage Won automatically un-marks Lost and vice-versa.
5. Click Save.

Editing a Pipeline

The editor is the same as creation. Stage order, names, slugs, probabilities, colors, and won/lost flags can all be edited. Editing a stage's slug does not rewrite existing deals — the safe path is to add a new stage with the new slug and migrate deals using the deals API.

Deleting a Pipeline

The default pipeline can't be deleted; the editor's Delete button only appears on non-default pipelines. Deletion is soft (the row stays in Mongo with deletedAt set); deals on the pipeline keep their pipelineId reference but disappear from list views that filter by pipeline.

Switching Pipelines on the Deals Board

The Deals page toolbar has a pipeline picker between the search bar and the view toggle. Switching renders the kanban with the selected pipeline's stages, colors, and order. The chosen pipeline persists per browser. When dropping deals between columns on a non-default pipeline, the move endpoint receives { pipelineId, stageId } so the new stage is recorded against the right pipeline.

Why Multi-Pipeline Matters

Different motions have different stages. A renewals book doesn't go through Discovery → Qualification → Proposal; it goes through Renewal-Notified → Negotiation → Renewed / Churned. A partnerships pipeline has its own swim lanes. Per-tenant pipelines let your team model the motion that actually exists instead of compressing every deal into one shape.