Keep active deal stages between 3 and 8 so coaching stays clear and reps keep selling.
Key takeaways for how to set up sales pipelines for coaching
- Pipeline count limit: Freshsales restricts the number of pipelines based on your plan, allowing a maximum of 25 pipelines on the Enterprise plan, 10 on Pro, and 1 on Growth, as noted in Freshsales.
- Stage gating rule: Microsoft defines "stage-gating" as the requirement to add business-required or system-required columns to your form when adding them to a business process flow stage, according to Microsoft.
- Process flow limit: Microsoft states that each row can have multiple process instances associated, with each instance tied to a different business process flow definition, up to a total of 10 instances, as noted in Microsoft.
- Process flow limit: Microsoft specifies that you can activate up to 10 business process flow processes on one table, as detailed in Microsoft.
- Stage alignment check: Close advises that opportunities can move through statuses independent of the lead status but should align with your overall sales process, according to Close.
Set your pipeline stage count between 3 and 8 for coaching clarity
According to Close, above 8, for either motion, the pipeline gets bureaucratic and reps spend more time updating statuses than selling. If your current structure exceeds this limit, the administrative burden likely outweighs the strategic value of the additional steps.
Enterprise motions often require more granularity than standard sales cycles. According to Close, enterprise motions stretch this to 7–8 stages with explicit Legal/Security review steps. This specific range accounts for the additional compliance and technical validation phases typical in larger software deals. When designing your pipeline, identify if your motion includes these explicit review steps. If it does, the upper end of the 3-to-8 range is appropriate. If your motion lacks these specific legal or security gates, fewer stages may suffice to keep the process lean.
The goal is to balance sufficient detail for tracking progress with simplicity for execution. Each stage should represent a distinct shift in the deal’s status that requires a specific rep action. If a stage does not trigger a clear next step or a required field update, it may be redundant. Redundant stages contribute to the bureaucratic overhead described in the source. By keeping the count within the recommended range, you reduce the cognitive load on reps during daily updates. This allows more time for selling activities rather than administrative maintenance.
When evaluating your current pipeline, count the number of stages from initial contact to closed won. Exclude closed lost stages from this count, as they do not represent active selling steps. Focus on the active path. If you have more than 8 active stages, consider merging similar steps. For example, if you have separate stages for "Initial Discovery" and "Deep Discovery," evaluate whether both require distinct rep actions. If they do not, combine them. This consolidation helps keep the pipeline within the 3-to-8 range.
Illustrative example of stage counts for call reviews
A manager counts active stages from initial contact to closed won and leaves closed lost out of that count. One motion uses 8 stages and includes the legal and security review steps that sit in the 7 to 8 range. A faster motion uses 4 active stages. Another motion uses 5 active stages. Each count stays at or under 8, so the weekly pipeline review looks at selling steps rather than extra status updates. The same manager keeps these motions in separate pipelines only because their stages are not the same.
A filled reference table of pipeline limits by vendor
The following table lists the specific vendor rules and limits that define your pipeline structure. Each row cites the exact constraint from the source publisher.
| Publisher | Rule Type | Limit or Guidance | Source URL |
|---|---|---|---|
| Freshsales | Pipeline count limit | A maximum of 25 pipelines can be created (depending on the plan - Growth: 1, Pro : 10, Enterprise : 25) | Freshsales |
| Close | Stage count guidance | Above 8, for either motion, the pipeline gets bureaucratic and reps spend more time updating statuses than selling. | Close |
| Close | Motion stage range | Enterprise motions stretch this to 7–8 stages with explicit Legal/Security review steps. | Close |
| Microsoft | Stage gating rule | This requirement is commonly called "stage-gating." If you're adding a business-required or system-required column to a business process flow stage, add this column to your form as well. | Microsoft |
| Microsoft | Process flow limit | You can activate up to 10 business process flow processes on one table. | Microsoft |
| Freshsales | Admin access rule | Deal stage customization is an admin-only capability. | Freshsales |
| HubSpot | Pipeline separation logic | Separate pipelines are only recommended if your processes have unique stages that require different pipelines. | HubSpot |
| Close | Stage alignment check | Opportunities can move through Statuses independent of the Lead Status but should align with your overall sales process. | Close |
| Close | Manager review habit | These rules work best when the manager owns the Smart Views and reviews them in 1:1s or weekly pipeline reviews. | Close |
Use this table to verify your current setup against these specific vendor constraints before adjusting your coaching checkpoints. For the weekly pass, follow Deal stage progress: 7 checks for weekly coaching.
Determine if your motion needs separate pipelines
HubSpot advises that separate pipelines are only recommended if your processes have unique stages that require different pipelines, according to HubSpot. This logic applies when your sales process diverges significantly from your standard motion. If your stages mirror your primary pipeline, consolidation is the appropriate choice.
Close notes that B2C product portfolios commonly justify multiple pipelines, according to Close.
Close observes that B2C and transactional motions usually need fewer (3 to 5 active stages), because the buying decision is faster and qualification is lighter, according to Close. Your B2B motion likely requires more stages to accommodate longer sales cycles. Do not force your B2B pipeline into a B2C structure.
Close explains that B2C motions typically compress Discovery and Demo into a single Consultation stage and skip the formal Negotiation stage when pricing is fixed, according to Close. If your pricing is fixed and your sales cycle is short, consider merging your Discovery and Demo stages.
To decide if you need separate pipelines, map your current stages against these criteria. If a segment of your deals skips a stage or adds a unique step, that segment may need its own pipeline. If all deals follow the same path, keep them in one pipeline to maintain coaching consistency.
Apply stage gating to enforce coaching checkpoints
Microsoft defines this requirement as "stage-gating," which applies when you add a business-required or system-required column to a business process flow stage. To implement this correctly, you must add that specific column to your form as well, ensuring the requirement is visible and actionable for the user. This structural alignment creates a natural checkpoint for your coaching process.
When you design your pipeline, you need to ensure that the status changes reflect the reality of your sales motion. Close notes that opportunities can move through statuses independent of the lead status but should align with your overall sales process. This distinction is critical because a lead's status and an opportunity's status serve different tracking purposes. If your opportunity statuses do not mirror your actual sales steps, your coaching reviews will lack the context needed to identify where a rep is struggling.
Pair the review with Sales call review: 5 notes to write first.
To make stage gating effective for coaching, map each required field to a specific skill or action. For example, if a stage requires a "Next Steps" field, that becomes a coaching point to review how the rep defined those steps. You are not just checking for data entry; you are evaluating the quality of the rep's planning. By tying required fields to coaching objectives, you transform administrative compliance into a developmental tool.
Consider the practical application of these rules in your current setup. If you are using a business process flow, verify that every stage has at least one required column that corresponds to a coaching checkpoint. If a stage lacks a required field, it may be too vague to provide useful feedback during a call review. You might find that some stages are purely administrative and do not require a coaching checkpoint, while others are critical decision points that do.
Check admin access and process flow limits
Before you configure stages, confirm who can actually change them. Freshsales documentation states that deal stage customization is an admin-only capability, according to Freshsales. This means your reps cannot adjust the pipeline structure themselves; they can only move deals through the stages you define. If you are a front-line manager, you likely do not have this admin access. You must coordinate with your IT or CRM administrator to make any changes to the stage names, order, or required fields. Do not assume that because you can see the stages, you can edit them. The permission model separates the people who use the pipeline from the people who build it.
Microsoft’s Power Automate documentation provides specific limits on how many business process flows you can run. According to Microsoft, you can activate up to 10 business process flow processes on one table. This limit applies to the total number of active flow definitions you can have running simultaneously on a single data table. If you are using multiple pipelines or different coaching tracks, each one may require its own process flow definition. You need to count how many distinct flows you plan to activate. If you exceed the 10-flow limit, you cannot activate additional flows until you deactivate existing ones.
These limits affect how you design your coaching checkpoints. If you need more than 10 distinct process flows to track all your coaching activities, you must consolidate your flows. You might combine several minor checkpoints into a single flow definition to stay under the limit. Alternatively, you may need to simplify your pipeline structure to reduce the number of active flows. The admin access rule and the 10-flow limit work together to define the boundaries of your coaching system. You must work within the limit of 10 active business process flows on one table.
Expected value when you map coaching stages
When defining the required field for each stage, consider how deal value is calculated. According to Close, Confidence multiplied by Value produces Expected Value (a $20,000 deal at 50% Confidence has $10,000 Expected Value). You can use this formula to determine if a deal has moved to a stage where the expected value justifies the coaching effort. This calculation can help you decide which deals warrant a deeper review in your one-on-one meetings.
Use a Sales One-on-One Agenda for Coaching Software Sellers.
Action: List your current deal segments. Identify any segment that skips a stage or adds a unique step. If found, consider a separate pipeline for that segment.
FAQ: How to set up sales pipelines for coaching
How many active stages should a B2B sales pipeline have?
Close advises that above 8 stages, the pipeline gets bureaucratic and reps spend more time updating statuses than selling. Enterprise motions stretch this range to 7–8 stages with explicit Legal/Security review steps. Inbound and product-led motions often compress this further to 3–4 active stages because qualification happens partially before the deal becomes an Opportunity, according to Close.
Which Freshsales plans include multiple deal pipelines?
Enterprise and Pro plans of the Freshsales Suite and the Freshsales web applications include multiple deal pipelines, according to Freshworks. The most pipelines you can create is 25: Growth allows 1, Pro allows 10, and Enterprise allows 25, according to Freshsales.
Can reps change deal probability manually in Freshsales?
Freshsales states that users can change the probability of deals manually if required, according to Freshsales. This manual adjustment capability exists alongside the fact that there is no cap on the number of stages inside a pipeline in the same system.
Do B2C motions need more or fewer stages than B2B?
Close notes that B2C and transactional motions usually need fewer (3 to 5 active stages), because the buying decision is faster and qualification is lighter. B2C motions typically compress Discovery and Demo into a single Consultation stage and skip the formal Negotiation stage when pricing is fixed, according to Close.
Is stage gating required for business process flows in Microsoft?
Microsoft states that this requirement is commonly called "stage-gating." If you're adding a business-required or system-required column to a business process flow stage, add this column to your form as well, according to Microsoft.