Pipelines and stages

Every workspace starts with one pipeline, and you can add more — say, one for new business and one for renewals. Stages belong to a specific pipeline, not to the workspace, so each pipeline defines its own path from first contact to closed.

A deal lives in a stage

A deal does not have a pipeline field of its own. It sits in exactly one stage, and that stage determines which pipeline it belongs to. Moving a deal to a stage of another pipeline is how a deal changes pipelines — there is no separate transfer step.

Managing pipelines and stages

In Settings, the pipelines list sits beside the stages of whichever pipeline is selected. Create a pipeline, name it, then add and order its stages. Reordering uses up and down arrows on each row, for both pipelines and stages.

The default pipeline

One pipeline per workspace is the default. It is where new deals land when nothing else is specified, and it is the pipeline a CSV import maps stage values against. If no pipeline is explicitly marked default, the first one in your list acts as it.

Moving deals

• Drag. On the pipeline board, drag a card to another column with the mouse or by touch.
• Menu. Each card has a "Move to" menu listing the other stages — the precise option, and the keyboard-friendly one, since the board itself has no keyboard drag.

Closed deals are frozen

Once a deal is won or lost, its stage is locked — changing it after the fact would distort your cycle-time and conversion metrics. Trying to move a closed deal is rejected with "Reopen the deal before changing its stage." Reopen it first, move it, and close it again if that is what really happened.