Pipeline Configuration

Pipelines define your sales process in meetergo CRM. Each pipeline contains stages that represent steps in your sales cycle, from initial contact to closed deal. This guide covers creating, configuring, and managing pipelines.

Understanding Pipelines

A pipeline is a structured sequence of stages that a deal moves through. Pipelines help you:

• Visualize where deals are in your sales process
• Track progress from lead to close
• Calculate weighted forecasts based on stage probabilities
• Ensure consistent sales processes across your team

Pipeline vs. Stage

Creating a Pipeline

1. Navigate to CRM → Deals
2. Click the Pipeline settings icon (gear icon near the pipeline dropdown)
3. Click New Pipeline
4. Enter a pipeline name (e.g., "Enterprise Sales", "Inbound Leads")
5. Click Create

Your new pipeline is ready for stage configuration.

Configuring Stages

Each pipeline needs at least one active stage plus a Won stage and Lost stage.

Adding Stages

1. Open pipeline settings
2. Select your pipeline
3. Click Add Stage
4. Configure the stage:

5. Click Save

Stage Types

Win Probability

Set the win probability for each stage to reflect the likelihood of closing:

Win probabilities are used to calculate the weighted forecast:

• Weighted Value = Deal Value × Win Probability

This helps prioritize deals and forecast revenue more accurately.

Stage Colors

Assign colors to visually distinguish stages on the Kanban board:

• Use progression (light to dark) to indicate advancement
• Use contrasting colors for different deal types
• Consistent colors help team members quickly identify stages

Reordering Stages

1. Open pipeline settings
2. Drag stages to reorder
3. Changes save automatically

Stage order determines left-to-right arrangement on the Kanban board.

Required Fields Per Stage

Ensure data quality by requiring certain fields before deals can enter a stage.

Setting Required Fields

1. Open pipeline settings
2. Select a stage
3. Find Required Custom Fields
4. Select which custom fields must be filled
5. Save changes

When a deal moves to a stage with required fields:

1. If fields are missing, a dialog appears
2. The user must fill in required information
3. Once complete, the deal moves to the new stage

Example: Proposal Stage Requirements

Before entering the "Proposal" stage, require:

• Budget (number field)
• Decision Maker Identified (checkbox)
• Proposal Due Date (date field)

This ensures proposals aren't sent without qualifying information.

Default Pipeline

Set one pipeline as the default for new deals:

1. Open pipeline settings
2. Find the pipeline you want as default
3. Click Set as Default

New deals will automatically use the default pipeline unless another is selected.

Managing Multiple Pipelines

Create separate pipelines for different sales processes:

Common Pipeline Types

When to Use Multiple Pipelines

Use multiple pipelines when:

• Sales cycles differ significantly in length
• Stage names vary between processes
• Different teams handle different deal types
• You need separate reporting by sales motion

When to Use a Single Pipeline

Use one pipeline when:

• Your sales process is consistent
• All deals follow the same stages
• Simpler reporting is preferred

Pipeline Best Practices

Keep It Simple

• 5-7 stages is typically ideal
• Too few stages lack visibility
• Too many stages create confusion

Name Stages Clearly

Use action-oriented or status-based names:

Set Realistic Probabilities

Base probabilities on actual historical data:

1. Review closed deals from the past year
2. Calculate close rates by stage
3. Use those percentages as win probabilities

Review Regularly

Evaluate pipelines quarterly:

• Are deals getting stuck at certain stages?
• Do win probabilities match actual outcomes?
• Should stages be added, removed, or renamed?

Pipeline Metrics

For each pipeline, you can view:

These metrics appear in the Reports view.

Editing a Pipeline

1. Open pipeline settings
2. Select the pipeline
3. Make changes:
   • Rename the pipeline
   • Add, edit, or remove stages
   • Adjust win probabilities
   • Set required fields
4. Save changes

Deleting a Pipeline

1. Open pipeline settings
2. Select the pipeline
3. Click Delete Pipeline
4. Confirm the deletion

Stage Rotting (Stale Deals)

Some CRM configurations support "rotting" detection — identifying deals that have been in a stage too long.

If enabled, deals past the rotting threshold are highlighted, prompting action:

• Follow up with the contact
• Move the deal forward
• Mark as lost if stale

FAQ

How many pipelines can I create?

There's no limit. Create as many as your sales process requires.

Can I move deals between pipelines?

Yes, edit the deal and select a different pipeline. The stage will reset to the first stage of the new pipeline.

What happens to historical data if I change win probabilities?

Probability changes affect future calculations. Historical weighted values in reports reflect the probabilities at the time.

Can different team members have different pipelines?

Yes, assign specific pipelines to teams or individuals based on their sales motion.

How do I archive old pipelines?

Rather than deleting, you can mark a pipeline as inactive (if this feature is available) or simply create a new pipeline and migrate active deals.

Can I duplicate a pipeline?

Currently, pipelines must be created individually. Recreate stages manually for a new pipeline based on an existing template.

Example Pipeline Configurations

B2B SaaS Sales

1. Lead (10%)
2. Qualified (25%)
3. Demo Scheduled (40%)
4. Demo Completed (55%)
5. Proposal Sent (70%)
6. Negotiation (85%)
7. Verbal Commit (95%)

Consulting Services

1. Initial Inquiry (15%)
2. Discovery Call (30%)
3. Needs Assessment (50%)
4. Proposal Development (65%)
5. Proposal Review (80%)
6. Contract Negotiation (90%)

Real Estate

1. Prospect (10%)
2. Viewing Scheduled (25%)
3. Viewed Property (40%)
4. Offer Made (60%)
5. Under Negotiation (75%)
6. Contract Signed (90%)
7. Awaiting Completion (95%)

Related Articles

• CRM Overview
• Creating and Managing Deals
• Using the Kanban Board
• Custom Fields
• CRM Reports