Multiple pipelines
Run multiple named deal pipelines per workspace, each with its own stages, forecast, and won/loss taxonomy.
Pact lets you run more than one deal pipeline in a single workspace. Each pipeline is a first-class object with its own stages, its own forecast, and its own won/loss reasons — so a new-business motion and a renewals motion never share a board or a definition of "won."
Admin-only configuration
Creating, cloning, and deleting pipelines, and editing their stages, happens in the admin area. Anyone can work deals on a pipeline; only admins shape it.
Where pipelines live
| Route | What you do there |
|---|---|
/pipeline | The board — drag deals between stages |
/pipeline/deals | The deals list for the pipeline |
/admin/pipelines | List, create, clone, and delete pipelines |
/admin/pipelines/[id] | Configure one pipeline |
The per-pipeline configure screen is organized into tabs: Stages, Won/Loss, Automation, and Analytics.
Creating and defaulting pipelines
Admins can create a pipeline from scratch, clone an existing one, or delete one they no longer need. You set a workspace default pipeline for everyone, and each user can additionally choose their own personal default — handy when different teams live in different pipelines.
Stages
Every pipeline owns its own stages. Within a pipeline you can create, edit, reorder, and delete stages. Each stage carries:
- a probability, used in forecasting
- a color for the board
- a type — open, won, or lost
- any required fields that must be present before a deal can advance into it
Because stages belong to the pipeline, two pipelines can model completely different sales motions without compromise.
Deals belong to one pipeline
A deal lives on exactly one pipeline at a time. You can move it freely between stages of that pipeline. Moving a deal into a stage that belongs to a different pipeline is not a normal advance — it is blocked, and requires the explicit Transfer action instead. This keeps cross-pipeline moves deliberate rather than accidental.
Analytics and forecasting per pipeline
Every stage move is recorded along with time-in-stage, which powers stage-duration analytics. Each pipeline gets:
- its own FX-normalized forecast, so multi-currency deals roll up correctly
- its own won/loss reason taxonomy, so close reasons mean the same thing across the pipeline
Legacy single-pipeline view
A legacy single-pipeline view also exists in Pact. This page describes the first-class multi-pipeline system, which is what you should use for new work.