Control How Every Deal Moves Through Your Pipeline
Build separate pipelines with your own stages, probabilities, required fields, and movement rules. Keep every deal move, stale flag, weighted value, and close outcome connected to the same record.
The Short Version
What Is CRM Pipeline Management?
CRM pipeline management is the process of defining the stages deals move through, controlling how they progress, and tracking what happens at every point in the sales process. In KudosCRM, each pipeline can have its own stages, probabilities, required fields, SLA windows, movement rules, card setup, and closing reasons. Teams can work those deals in Kanban, List, Forecast, or Timeline views while the CRM keeps stage history, weighted value, stale status, and closing data tied to the deal.
Define the Process
Set the stages, probabilities, exit criteria, and other rules that belong to a pipeline.
Control Every Move
Stop stage skipping, block backward movement, and require information before a deal progresses.
See What Needs Attention
Use stage SLAs, stale indicators, Deal Checks, and filters to find deals that are no longer moving.
Keep the History Clean
Record who moved a deal, where it moved from, how long it stayed there, and why it eventually closed.
Your pipeline defines the process. KudosCRM makes sure the deal follows it — the same stage requirements and movement rules apply from the board, bulk actions, the API, and automations alike.
Build Different Pipeline Rules for Different Sales Processes
A renewal deal should not have to follow the same stages as a new-business deal. KudosCRM lets each pipeline keep its own structure so different sales motions can follow different rules without mixing their stages or closing logic.
Create Separate Pipelines
Run different processes for new business, renewals, partner sales, or other deal types. Each pipeline can have its own stages, currency, color, icon, position in the pipeline switcher, close reasons, stage rules, and card layout.
Choose the Default Pipeline
Set one pipeline as the default for new deals and related reporting. Changing the default transfers that role cleanly to the newly selected pipeline.
Clone a Working Pipeline
When another sales process is similar, clone an existing pipeline rather than rebuilding it. Choose whether to copy stages, stage properties, movement rules, card layout, and close reasons.
Review Deals Across Pipelines
Use the List view with All Pipelines when you need one cross-pipeline view. Kanban stays pipeline-specific because its columns belong to one pipeline's stage structure.
Keep Your Working View
The selected pipeline, view, and owner scope persist for each user and stay represented in the URL, making a filtered pipeline view easy to revisit or share.
One workspace, separate processes
New Business
Default5 stages · USD · default
Renewals
3 stages · its own close reasons
Partners
4 stages · admin-locked final stage
Each pipeline keeps its own stages, movement rules, card layout, and Won/Lost reason lists. Clone one when the next process is similar.
Before a deal can enter Proposal
Required fields
Move stopped: 2 fields missing
The same check runs for drag and drop, bulk moves, API changes, and cross-pipeline moves.
Configured vs. real conversion
Probability 20% · converted 47% over the last 365 days
Too few deals in the sample? No percentage is shown.
Decide What Must Happen Before a Deal Can Move
Pipeline stages should describe real progress, not just different column names. KudosCRM lets admins define what each stage requires and which movements are allowed. Those controls run on the server, so the same rules apply whether a deal is moved by drag and drop, bulk edit, API, or another supported workflow.
Set Up Each Stage
Create, rename, reorder, and recolor open stages. Each open stage can also have a 0–100% win probability, required fields, suggested fields, an SLA window, and written exit criteria.
Require Fields Before Progress
Attach built-in or custom fields to a stage. When required information is missing, KudosCRM stops the move and tells the user which fields still need to be completed — for Kanban moves, bulk stage changes, API changes, and cross-pipeline moves alike.
Control Which Moves Are Allowed
Pipeline movement rules can block stage skipping, block backward movement, lock selected stages to admins, and require new deals to start in the first stage. These are defined rules, not approval workflows, and not AI-based.
Compare Your Assumption with Real History
A stage has a configured probability, but KudosCRM can also calculate how deals have actually converted from that stage over the previous 365 days. For example, a configured 20% probability might sit beside a 47% recent conversion. When the sample is too small, KudosCRM does not invent a percentage.
Archive a Stage Without Losing History
Removing a stage does not simply delete it. If open deals still sit there, an admin chooses another stage for them, KudosCRM records the transitions, and closed deal history stays attached to the archived stage. The stage can later be restored.
Work the Same Pipeline from Four Different Views
The deal data should stay the same even when the question changes. KudosCRM gives teams Kanban, List, Forecast, and Timeline views so they can work the same pipeline from different angles without moving data into another tool.
Kanban for Stage Movement
Drag a deal between stages. Before dropping, KudosCRM can show the move as allowed, requiring extra information, involving a close or reopen, or blocked by a rule. Each stage column also shows deal count, total value, weighted value, and owner avatars.
Customize What Deal Cards Show
Managers can define a team card layout, and each user can maintain a personal My View. Choose up to 10 fields from 16 available card fields, including deal value, contact email, contact phone, next activity, days in stage, deal age, probability, tags, and urgency.
List for Detailed Review
Use columns, sorting, and detailed filtering across 25+ fields, including deal fields, custom fields, and linked Contact or Company fields. Saved views can be private, team-visible, favorited, and reordered.
Forecast for Revenue Timing
Forecast view shows six months of Booked, Commit, Best Case, and Weighted using the same deal records as the rest of the pipeline.
Timeline for Date-Based Planning
Timeline places deals on a date axis with grouping, sorting, zoom, and collapsible groups.
One set of deal records
Proposal Sent
60%Every Kanban column shows deal count, total value, weighted value, and owner avatars
My View
Up to 10 of 16 card fields — a team default from managers, a personal layout for each user
Saved List views
25+ filterable fields; views can be private, team-visible, and favorited
Catch Deals That Stop Moving Before They Disappear from Attention
A deal can still look open long after meaningful progress has stopped. KudosCRM uses stage SLA rules, stale indicators, and verifiable Deal Checks to surface specific problems instead of hiding them behind an unexplained score.
Give Each Stage Its Own SLA
A short qualification stage does not have to use the same stale threshold as a longer negotiation stage.
Make Stale Deals More Visible Over Time
Warnings move from an amber indicator to a stronger stale treatment to a red warning with the number of days past SLA. A server process refreshes stale state every 15 minutes.
Use Deal Checks Instead of a Fake Score
KudosCRM does not calculate a deal engagement score. Instead, the Checks panel surfaces specific verifiable conditions such as no Contact linked, expected close date passed, or no next step.
Suggest a Close Date from Real History
When enough recent Wins exist, KudosCRM can calculate a suggested close date from the median deal cycle, only once the required sample size is available. Teams can also opt into auto-archiving open deals with no activity beyond a configured period, defaulting to 120 days.
Make Win and Loss Data Part of the Pipeline Process
A Won or Lost status says what happened. It does not explain why. KudosCRM lets every pipeline maintain its own structured closing rules so reps capture useful outcome data at the moment a deal closes.
Keep Separate Won and Lost Reasons
Each pipeline can have its own reason lists for Won and Lost. Admins control reason names, order, active status, and whether more detail is required — for example, Competitor can require a name, and Other can require a note.
Require a Reason Before Closing
A pipeline can require users to select a close reason. Strict picklist mode can also block unsupported free-text reasons when the team wants a controlled taxonomy.
Turn Repeated Free Text into Structured Reasons
When free text is allowed, repeated responses can appear in a suggestion queue. Admins can create a new structured reason, map the suggestion to an existing one, or dismiss it.
Keep Historical Reporting Clean
Renaming a reason does not create a second reporting bucket — historical deals follow the current reason label.
Record the Final Signed Amount
When a deal is Won, the closing flow can capture the final amount, so Won revenue reflects what was actually signed rather than the previous forecast figure.
Reopen a Closed Deal Deliberately
Reopening is explicit. KudosCRM restores the previous valid open stage, clears the old close data, records who reopened the deal, and keeps the prior history. A close reason can also be corrected without reopening the deal.
How It Works
How Does a Deal Move Through a KudosCRM Pipeline?
The pipeline defines the rules around a deal from entry to close. The same stage requirements and transition logic apply whether the move comes from the board, bulk actions, API, or an automation.
Choose the Pipeline
Create a new pipeline or use one already configured for that sales process.
Enter the Starting Stage
New deals begin inside the pipeline according to its stage rules.
Complete What the Next Stage Requires
Required fields and movement controls are checked before the deal progresses.
Move the Deal
Move through Kanban, supported bulk actions, API, or another allowed workflow. KudosCRM records the transition.
Watch for Stale or Incomplete Deals
Use SLA indicators, Deal Checks, filters, and saved views to find deals that need attention.
Close with a Clear Outcome
Mark the deal Won or Lost, record the relevant close reason and final information, and keep the outcome available for reporting.
What's Actually in the Box
Pipeline Controls Available in KudosCRM
Pipeline Structure
Multiple parallel pipelines
Default pipeline
Pipeline cloning
Pipeline ordering
Pipeline colors and icons
Per-pipeline currency
All Pipelines List view
Persistent pipeline and owner context
Stage Controls
Custom stage names, order, and colors
Stage probabilities
Historical conversion comparison
Required and suggested fields
Stage SLA and exit criteria
Safe stage archiving and restoration
Cross-pipeline moves
Stage-skip and backward-move blocking
Admin-only stages
Stage-one start rule
Pipeline Views
Kanban, List, Forecast, Timeline
Custom deal cards
Team card defaults
Personal My View
Column count, value, and weighted value
Search and owner scopes
Secondary filters
Saved List views
Deal Control
Stale deal indicators
Deal Checks
Quick-add by stage
Inline deal editing
Stage transition audit trail
Bulk stage, owner, status, and close-date changes
Close-reason backfill
Closing
Won and Lost reason lists
Required close reasons
Strict reason picklists
Reason-specific details
Close-reason suggestion queue
Final close amount
Controlled deal reopening
Reason correction without reopening
Pipeline Measurement
Weighted deal value
Per-deal probability override
Forecast categories
Revenue Forecast report
Stage conversion
Sales Funnel report
Close Reasons report
Win/Loss reporting
KudosCRM Pipeline Controls vs. a Basic Kanban Deal Board
Make Every Pipeline Stage Mean Something
Set what each stage requires, control how deals move, and keep the history behind every transition.
Pipeline Controls for Every Kind of Sales Team
Different industries move deals differently. KudosCRM keeps stages, rules, and closing reasons consistent whichever industry you work in.
Works with the Tools Your Team Already Opens
Keep deal activity connected to email and calendar tools while the pipeline stays the single source of truth.
Gmail
Outlook
Google Calendar
SlackGo Deeper
Explore More Features
Pipeline is part of the Sales & Pipeline stage of the journey — the structure every deal moves through, while the Deals feature holds the record itself.
All FeaturesFAQ
Frequently Asked Questions
Control the Process
Build a Pipeline That Controls the Process, Not Just the Columns
Define what each stage means, decide what a deal needs before it moves, catch stalled opportunities, and keep every close outcome connected to the history behind it.