Skip to main content

What Is a Pipeline Stage? (Web)

A pipeline stage represents a step in your main business process. Pipeline stages are ordered sequentially to form a linear progression that accounts move through — for example, Blank Pin → Lead → Set → Sit → Closed.

Written by Hunter Allred
Updated over a month ago

How Pipeline Stages Work

Every workflow begins with a Blank Pin (Prospect) stage. This is the default starting stage for all accounts and cannot be removed or reordered. From there, you define additional pipeline stages in the order that reflects your sales or service process.

Each pipeline stage has a defined order (0, 1, 2, 3...) that determines its position in the progression. Accounts move forward through pipeline stages when users take actions — for example, a "Pitch" action might move an account from "Lead" to "Set."

Pipeline Stage Properties

Name — The display name of the stage (e.g., "Lead," "Set," "Sit," "Closed").

Short Code — A short label up to 4 characters, displayed on tiles and compact views (e.g., "SET," "SIT").

Plural Name — The plural form used in reports and lists (e.g., "Leads," "Sets").

Description — An optional description explaining the purpose of this stage.

Color — A color used for the stage icon and visual indicators throughout the app.

Scope — Controls the visibility of accounts in this stage. Options include:

  • Company — Visible to all users in the company.

  • Downline — Visible to the user and their management chain.

  • Within Restrictions — Visibility based on restriction rules.

  • Self — Only visible to the account owner.

Restricted — When enabled, limits who can see accounts in this stage based on the scope setting.

Outgoing Actions — The actions available to users when an account is in this stage. Actions are what move accounts between stages.

Required Fields — Fields that must be filled in before an account can reach this stage. Required fields accumulate as accounts progress — if "Lead" requires a phone number and "Set" requires an email, then an account at the "Set" stage must have both.

Auto-Trigger

Pipeline stages can be configured to automatically transition accounts to another stage after a set amount of time. For example, you could set accounts in "Pending" to automatically move to "Follow Up" after 48 hours. Auto-trigger options include hours, days, or years.

Quarterly Plan Configuration

Each pipeline stage can optionally track setter, closer, and self-gen metrics for quarterly planning. Each role can be configured with:

  • Include on Plan — Whether this stage counts toward the user's plan.

  • Allow Payment — Whether reaching this stage triggers compensation tracking.

Did this answer your question?