Pipelines that reflect how work actually moves.
A pipeline isn’t only for deals. Candidates move through interview stages, policies move through renewal, jobs move through dispatch. Because pipelines sit on top of your objects rather than being welded to a Deal table, you can build one wherever work has stages.
- Pipelines per object
- Multiple
- Objects that support pipelines
- Any
- Time-in-stage tracking
- Automatic
- Stage-change automation
- Built in
Stages you name, in the order you work
Add, rename, reorder, and retire stages without a migration, and mark which ones count as won or lost so forecasting and conversion reporting stay meaningful. Every object can have more than one pipeline — a new-business pipeline and a renewals pipeline behave differently and shouldn’t be forced to share stages.
Moving a card is an event other things can listen to
Dragging a card to “Proposal sent” can start a follow-up sequence, create a task for the owner, notify a channel, and stamp the date it entered the stage. You configure that once on the stage rather than remembering to do four things by hand — and it fires the same way whether the move came from the board, the record page, the API, or an automation.
- Time-in-stage tracked automatically for every card
- Rotting rules that surface cards sitting longer than they should
- Required fields per stage, so a deal can’t advance while half-filled
- Per-lane totals and counts for value, weighted value, or any numeric field
The board is a view, so it filters like one
A board is the same underlying query as your table views, drawn differently. That means the filters you already know apply: show only your own cards, only this quarter, only deals above a threshold, only accounts in a particular segment. Switch a filtered table view to board layout and back without rebuilding anything.
Pipelines, in detail.
Can two teams use different stages on the same object?
Yes. Multiple pipelines per object exist for exactly this — new business and renewals can each have their own stages, and reporting can treat them separately or together.
What stops a rep dragging a deal to Closed Won with nothing filled in?
Per-stage required fields. If Closed Won requires a signed date and an amount, the card can’t land there until they exist, and the rep is told what’s missing rather than being silently blocked.
Does reordering stages break historical reporting?
No. Stage history is recorded as events with timestamps, so conversion and velocity reporting still reflect what actually happened even after you restructure the pipeline.
How do I spot deals going stale?
Set a rotting threshold per stage. Cards past it are visually flagged on the board and can be filtered into a view or used to trigger an automation.
Try it on your own data.
Free workspace, an industry pack installed at setup, and every price published. No mandatory call.
Free trial · no card required · every price published