Pomio CRM keeps the shared pipeline visible to the team. A hard ceiling on how many open stages you allow is how you keep that board readable: enough steps to show progress, not so many that every nuance becomes its own column and nobody agrees what “next” means.
What a maximum number of stages means
It is a deliberate design rule for the pipeline: pick a fixed upper count of open stages (closed-won and closed-lost sit outside that count), write what each stage is for, and refuse new columns unless an old one is retired or merged. Pair this with exit criteria on every CRM stage so a short pipeline still has clear gates instead of vague labels.
Why unlimited stages hide stuck deals
When anyone can add a stage, reviews fill with micro-steps that exist for one seller’s habit. Deals stall in half-named columns; forecasts disagree because stage names no longer map to the same meaning. That is the same hygiene failure as undefined stage language — see why sales and management need shared stage definitions — only now the mess is structural: too many columns, not just fuzzy words.
How to set a practical ceiling
For most small and mid-sized sales teams, five to seven open stages is enough: qualify, discover, propose, negotiate, commit — adjust names to your motion, not your org chart. Count closed-won and closed-lost separately. If a stage exists only to store “waiting on legal” forever, prefer a next-step date and a note on the current stage over a permanent parking column — the same visibility habit as showing days in the current CRM stage.
Exceptions that still need a rule
Enterprise motions with a true legal or security gate can keep one dedicated stage — still inside the ceiling, not as an open invitation to invent more. Partner or channel tracks belong in a separate pipeline with its own cap, not as extra stages bolted onto the core board. Temporary campaign tags are fields or lists, not new stages. Adding a stage “just for this quarter” without retiring another is how ceilings die.
How Pomio CRM keeps stage count visible
The pipeline the team can see makes column sprawl obvious in the same place as day-to-day deal work. After you set the maximum, review the board in pipeline meetings: merge near-duplicate stages, require a note when a stage change needs context — stage changes that require a note — and treat unexplained extra columns as incomplete hygiene until someone owns the redesign.
A practical pipeline stage-count checklist
Before you add a stage: write the buyer behaviour that only this stage can represent; check an unused stage could not absorb it; confirm the total open stages stay at or under your ceiling; document exit criteria; map the stage to forecast language; train the team on the new board; archive or merge one stage if you are already at the cap — fix the count before debating chance percentages.
Go deeper
Is there one correct maximum for every company?
No. The right ceiling depends on deal complexity and how many real decision gates buyers pass. The rule is to set a maximum and enforce it — not to copy a vendor’s default list of twelve stages that nobody can recite.
Should closed-won and closed-lost count toward the maximum?
Usually no. Cap the open working stages the team moves deals through. Closed outcomes are results, not progress columns. Keep them few, named, and required when a deal leaves the open board.
Does Pomio CRM invent stages for us?
No. The product keeps the pipeline visible. Your team owns how many stages exist and what they mean; Pomio CRM makes sprawl easy to see and fix — it does not invent your sales process.
How does a stage ceiling relate to exit criteria?
A short pipeline without exit criteria is just fewer vague labels. Combine a maximum stage count with clear exit criteria and shared definitions so reviews stay honest and forecasts stay comparable week to week.