Designing Sales Funnel Stages in Bitrix24

Designing Sales Funnel Stages in Bitrix24

"Our stages are: New, In Progress, Closed" — that answer comes up far more often than it should. Three stages yield zero analytics: it becomes impossible to pinpoint where deals are being lost, how much time each step takes, or which managers have been stuck on "In Progress" for weeks.

Stages are the operational notation of the sales process. Design starts with understanding the process itself — not with opening Bitrix24 settings.

Technical Model of Stages

In Bitrix24, deal stages are stored in the b_crm_status table with ENTITY_ID = DEAL_STAGE (for the primary funnel) or DEAL_STAGE_{categoryId} (for pipelines/multi-funnels). Each stage has:

• STATUS_ID — system identifier (e.g., NEW, C1:NEW)
• NAME — display name
• SORT — order in the funnel
• STAGE_SEMANTIC_ID — semantics: P (process), S (success), F (failure)

Semantics is not just a label. Stages with STAGE_SEMANTIC_ID = S and F are terminal: once a deal enters them, it is considered closed. Conversion metrics, the "Sales Funnel" report, probability calculations in forecasts — all rely on these three semantics. Wrong semantics = wrong analytics.

Criteria for a Good Stage

A stage works if the manager can answer unambiguously: "What must happen for a deal to reach this stage?"

Bad stage: "In Progress" — answers nothing.

Good stage: "Proposal Sent" — it is clear what happened, and an automatic reminder can be set to fire after 2 days without a reply.

Checklist when designing each stage:

• Is there a clear entry criterion?
• Who is responsible for the transition?
• What is the maximum time allowed in this stage?
• What happens when that time is exceeded (escalation)?
• What actions must be completed before leaving the stage?

Number of Stages

There is no universal formula, but there are guidelines:

• Fewer than 4 stages — detail is lost, the funnel is uninformative.
• 4–8 stages — the working range for most B2B and B2C pipelines.
• 9–12 stages — justified for long, complex cycles (real estate, industrial equipment, government procurement).
• More than 12 stages — several different processes are likely being merged into one funnel.

Loss stages are counted separately. There can be several — they form a classifier for reasons of loss. In analytics they serve as a breakdown of "why we are losing."

Loss Stages as an Analytical Tool

The typical mistake is a single "Rejected" stage. This is meaningless: it catches "No budget," "Bought from a competitor," "Client went silent," and "Not our niche" all at once. There is nothing to aggregate.

The right approach: design a classifier of rejection reasons. Usually 5–8 categories:

• No budget / budget frozen
• Chose a competitor (with a "Which competitor" field)
• Not our niche / non-targeted request
• Client went silent / unreachable
• Project postponed / deferred
• Technically cannot deliver

Each of these reasons is a stage with STAGE_SEMANTIC_ID = F. Alternatively, one terminal stage "Closed — Lost" with a mandatory "Reason for loss" field (dropdown). The second option is technically simpler and sufficient in most cases.

Automation on Stages

Stages are the trigger points for robots and business processes. When designing, record for each stage:

On stage entry:

• Create a task (for whom, with what deadline?)
• Send a notification (to whom?)
• Populate a field automatically

While in the stage for X days:

• Remind the responsible manager
• Notify the supervisor (escalation)

On stage exit:

• Write the transition date to a custom field
• Launch the next step

Case Study: Funnel for a Real Estate Agency

Client — a real estate agency handling new-build and secondary market properties. Deal cycle: 30–180 days. Original funnel: 5 stages, the same for both markets. Problem: the new-build market had a "developer reservation" stage and a "mortgage approval wait" stage that did not exist on the secondary market — "In Progress" accumulated deals with no meaningful distinction.

Two funnels were designed:

New-build market (9 stages): Inquiry received → Qualified → Property search → Viewings scheduled → Viewings completed → Property selected → Mortgage / approval → Developer reservation → Deal closed

Secondary market (7 stages): Inquiry received → Qualified → Property search → Viewings → Negotiation / price discussion → Deposit received → Deal closed

Loss stages: No budget / Chose another property / Chose another agency / Postponed / Not our niche.

For the "Mortgage / approval" stage a robot was configured: if a deal stays in the stage for 7+ days — a notification goes to the responsible manager and supervisor.

After two months it became clear that 34% of deals were stalling at "Viewings scheduled → Viewings completed" — it turned out managers were scheduling viewings but not recording the outcome. This was revealed by time-in-stage analytics that simply had not existed before.

Timeline

Designing stages for one funnel (interview + diagram + implementation + automation) — 3–6 business days. For multiple funnels with different processes — 8–16 days.