Sales Operations System
More than one pipeline can be defined, each carrying its own set of stages.
New business and renewals do not follow the same steps, and neither do two product lines sold to different buyers. Forcing them through one stage set makes every stage name a compromise and every conversion rate meaningless.
Several pipelines must be definable, and the stage set must belong to the pipeline rather than to the account.
Act! lets an administrator create new opportunity processes and their stages, defining a new process, adding custom stages with specific probabilities to it, and applying that process to an opportunity. Stages belong to a process in the data model, so each process carries its own stage set.
An unlimited number of pipelines can be created, each with its own stages, its own default currency and its own deal assignment method, with the vendor giving separate sales processes as the worked example.
Sales cycles are separate pipelines, each holding its own ordered set of sales stages, and the vendor illustrates this with two cycles running side by side for different lines of work with different stage names in each. A default cycle is supplied and further cycles are created and reordered by the administrator.
Status attributes can be created on any object and on any list, and each status attribute defines its own ordered set of stages which becomes the columns of a kanban view. A workspace can therefore run several independent pipelines - additional status attributes on the deals object, or separate lists each with its own status attribute. There is no single pipeline entity with a pipeline picker on the deal record; a deal's membership of a given process is expressed by which status attribute or which list it sits in.
Team Pipelines let an organisation run several pipelines side by side for different processes, and each Team Pipeline can hold multiple sub-pipelines where a different stage sequence is needed. Each pipeline carries its own field layout, with unused fields removable and custom fields addable per sub-pipeline. The documented ceilings are 25 stages per pipeline, at least two open stages, up to five closed stages, and up to five sub-pipelines per Team Pipeline in the organisation.
Each list functions as one pipeline and the vendor states that an unlimited number can be created, with a single record able to sit in several pipelines at once. Stages belong to a specific pipeline rather than to the account: the API Status object carries the identifier of the list it belongs to, so each pipeline holds its own stage set.
An administrator can create multiple sales pipelines, up to 30 active at once, and each pipeline has its own set of milestones so separate sales processes can be tracked independently. Lost reasons are the exception and are shared account-wide across every pipeline.
A pipeline is a named, ordered group of opportunity statuses, additional pipelines can be created alongside the default one, and status names need only be unique within a given pipeline, so each pipeline carries its own stage set. Statuses can also be dragged across pipelines.
More than one pipeline can be created and each carries its own stages, named, reordered and deleted independently, with opportunities movable between pipelines. Pipelines can be flagged as revenue-tracking, and stage win probabilities are set per pipeline.
Custom fields are defined per group and are not shared across groups, so each deal group carries its own Status field and therefore its own stage set. Within a group, more than one view can be created and a pipeline view can be grouped by whichever single-select field the user chooses, so several boards with different stage sets can coexist.
Multiple deal pipelines can be created under Admin Settings, each with its own customisable stage set and its own stage probabilities. Pipeline names must be unique and each pipeline needs at least three stages, with no documented upper bound on stages. Vendor documentation records a maximum of 25 pipelines.
Accounts with more than one sales process can create additional deal pipelines, each holding its own set of ordered stages with their own probabilities.
Administrators add pipelines under System Settings, choose whether each applies to opportunities or projects, and edit that pipeline's own stage list, with an optional win probability per stage. Each new pipeline then appears as a choice when creating or editing an opportunity.
More than one pipeline can be created, each from a template or from scratch, and each pipeline's stage names and stage count are set independently at creation. Deals can also be moved from one pipeline to another.
A table can carry more than one business process flow, each with its own ordered stage set, and administrators set which flow is applied to new rows using the Order Process Flow command. More than one active process can run on the same record, and a process can span up to five tables.
monday CRM documents unlimited customisable pipelines, and because each pipeline is a board with its own Stage status column, each pipeline carries its own independent stage labels.
Administrators add pipelines under Settings, each with its own name, description, colour, currency, stage list and custom fields, and pipelines can be edited at any time or archived when no longer used. A deal can also be moved from one pipeline to another.
Multiple pipelines can be run at once, each tracking its own stages, so different sale types or post-sale processes can be modelled separately, with stages, goals, tasks and automation configured independently per pipeline. Leads can be distributed into the correct pipeline by rule, and pipeline choice can follow territory.
Multiple pipelines can be created and each pipeline carries its own set of stages, so different products or workflows can be modelled separately. Pipelines cannot be viewed combined on a single board even where stage names match.
The vendor states that many customers run more than one opportunity pipeline where different sales processes need different approaches, giving new customer sign-up versus a weekly repeat order as the example, and each pipeline is built from its own ordered status list. Quotes carry their own separate pipelines in addition.
Administrators create multiple sales processes in Setup, each containing a chosen subset of picklist values, then attach a process to an opportunity record type and expose that record type by profile. Different divisions therefore work different stage sets on the same object.
Pipelines are created from the Gmail navigation, listed together, and can be hidden, copied or deleted individually. Each pipeline holds its own stages and its own columns, configured from that pipeline's stages and columns settings, so unrelated workflows are modelled side by side without sharing a stage set.
Vtiger publishes a sales administration article whose stated subject is setting up sales pipelines and the benefits of having more than one, so multiple pipelines exist as an administrator-configured construct, and deal stages are configured through picklist values per module. Whether each pipeline carries its own independent set of stages, rather than sharing one stage picklist, is not stated in the documentation reviewed.
Multiple sales pipelines can be created, each with its own stage set, so distinct sales processes are modelled separately. Pipelines are attached to deal layouts, which also governs which users see which process and what detail each captures.