Pipelines
A pipeline is the set of stages a deal moves through, and you can run multiple pipelines side by side for different parts of your business.
A pipeline defines the journey of a deal: the stages a deal can sit in, the order it moves through them, and the probability you assign to each stage. The columns on your deals Kanban board are the stages of the pipeline you're viewing.
Informly creates a default pipeline for you the first time you open the CRM, so you can start working immediately and refine the stages later.
Manage pipelines
Go to CRM → Pipelines to see every pipeline in your organization. From here you can create a new pipeline, open one to edit its stages, or delete a pipeline you no longer use.
Stages
Each stage has these fields:
| Field | What it does |
|---|---|
| Name | Shown as the column header on the deals board (e.g. Qualified). |
| Probability | The % chance a deal at this stage will close, used in forecasting. |
| Color | The accent color for the stage column and badge. |
| Position | The stage's place in the order, left to right on the board. |
Reorder stages
Open a pipeline and drag a stage up or down to change its position. The new order is what shows up immediately as the left-to-right column order on the deals board.
Reordering doesn't move existing deals. Each deal stays in whatever stage you last set it to, even if that stage is now in a different position.
Use multiple pipelines
You're not limited to one pipeline. Many teams run a few side by side — for example, one for new business and one for renewals, because the stages are genuinely different.
Create the pipeline
Go to CRM → Pipelines → + New pipeline, give it a name, and save.
Add the stages
Add each stage with its name, probability, and color. Drag them into the right order.
Assign deals
When you create a deal, pick the pipeline it belongs to. Each deal lives in exactly one pipeline at a time.
Switch between pipelines on the deals board using the pipeline picker at the top.
Tips
- Keep your stages to the smallest set you actually need. Five to seven works for most teams.
- Use the probability field consistently — it's what makes the forecast report meaningful.
- If you change a stage's name, the rename applies everywhere the stage appears, including the activity log.