Skip to content

Create New Stage

The Create New Stage modal allows users to add a new step in a sales pipeline. Stages define how deals progress from initiation to closure and help structure the entire sales workflow.

This feature enables full customization of pipeline structure based on business needs.

Purpose

The Create New Stage action is used to:

  • Extend an existing sales pipeline
  • Define new steps in the deal lifecycle
  • Improve workflow flexibility
  • Customize sales processes per team or business model

When the user clicks “Add New Stage”, a modal appears with the following fields and actions:

Create New Stage

Fields

Stage Name

Type: Text input (required)

Placeholder:
e.g. In Progress, Qualified...

Purpose:
Defines the name of the pipeline stage.

Guidelines:

  • Use clear, action-based names
  • Keep naming consistent across pipeline stages
  • Reflect real sales process steps

Example Stage Names:

  • Lead
  • Contacted
  • Qualified
  • Proposal Sent
  • Negotiation
  • Closed Won
  • Closed Lost

Actions

A. Create Stage

Button: Create Stage
Function:

  • Validates input
  • Adds the new stage to the pipeline
  • Updates pipeline structure in real time
  • Makes stage available for deal assignment and movement

B. Cancel

Button: Cancel
Function:

  • Closes modal
  • Discards any unsaved input
  • No changes are applied to the pipeline

System Behavior

After creating a stage:

  • Stage is added to the pipeline instantly
  • Appears in pipeline board as a new column
  • Becomes available in:
    • Deal creation form
    • Deal edit form
    • Drag-and-drop movement system
  • Updates pipeline analytics structure automatically

Validation Rules

  • Stage Name is required
  • Duplicate stage names may be restricted (based on configuration)
  • Empty submissions are not allowed

Best Practices

  • Keep stage names short and meaningful
  • Avoid duplicate or unclear stage definitions
  • Align stages with real sales workflow steps
  • Limit number of stages for better pipeline clarity (5–8 recommended)
  • Use action-oriented naming (e.g., “Proposal Sent” instead of “Proposal”)