How to Design Sales Pipeline Stages in a CRM

CRM sales pipeline stages are the agreed steps an opportunity passes through from qualified interest to won or lost. A stage is not a mood and not a task list. It is a state the deal is in, with a definition the next salesperson would recognise.

Good stage design makes reports comparable across branches. Weak stage design makes “quotation” mean “we emailed a price” in one team and “the customer signed” in another.

Start from decisions, not from a template

List the decisions that actually change how your company treats the deal. Typical decisions for a Malaysian B2B team:

• We know the account and the need.
• We have submitted a priced quotation.
• The buyer is in an internal approval.
• We have a verbal or written acceptance.
• Finance or operations has a committed order.

Each decision can be a stage. If two labels do not change the next action, merge them. Five to seven stages is usually enough. More stages feel precise and get skipped.

Entry and exit criteria

Write one or two sentences for every stage:

• Entry: what must already be true.
• Exit: what must be true before someone moves it forward.
• Owner: who is allowed to move it.

Example for “Quotation sent”:

• Entry: account and primary contact exist, products or scope are identified, a price has been issued from the approved process.
• Exit: the buyer has accepted, rejected, or asked for a revision that returns the deal to an earlier stage.
• Evidence: the quotation number is stored on the opportunity.

Without evidence, people drag cards to look busy.

Won, lost, and the reasons

Won should mean the commercial commitment you care about, not “we feel good.” For some firms that is a signed quotation. For others it is a sales order in accounting. Pick one.

Lost needs a reason list that is short enough to use: price, timing, competitor, no budget, no response, not a fit. Free-text-only reasons cannot be counted. A deal with no activity for a defined period can be a “stalled” view, but do not auto-mark it lost unless the team agrees.

Reopened deals should create a new opportunity or an explicit reopen event. Silently dragging a lost deal back to stage one destroys history.

Keep reporting honest

Stage reports assume every opportunity uses the same path. Exceptions belong in a second pipeline (for example tenders versus repeat orders), not in optional stages people sometimes skip.

Probability by stage is a forecasting choice. Define it in CRM sales forecasting, after the stage meanings are stable. If you change stage names mid-year, keep a map from old names to new names or the annual comparison breaks.

A practical example

A solar installer uses: Qualified, Site surveyed, Quotation sent, Customer approval, Won, Lost. “Site surveyed” cannot be entered without a survey date. “Quotation sent” cannot be entered without a quotation number. “Won” means the deposit invoice exists in accounting, not a WhatsApp “ok.” Deals with no reply after 21 days stay in their stage and appear on a stalled list, with a required next task.

Key takeaways

• Stages describe decisions, backed by evidence.
• Entry and exit rules matter more than colourful boards.
• Won and lost need definitions and a small reason list.
• Test the pipeline on real deals before training day.

FAQ

How many stages should we have?

Enough to change the next action, and few enough that people will update them. If a stage has no exit rule, remove it.

Should every product line share one pipeline?

Share one pipeline when the decisions match. Split pipelines when a tender and a repeat spare-part order move in genuinely different ways.

Can workflow rules move the stage automatically?

They can, when the evidence is a system event, such as “quotation document generated.” Do not auto-advance because an email was opened. Trigger design is covered in how CRM workflow automation triggers work.