Why Multi-Pipeline Architecture Beats a Single Funnel
In Bitrix24, separating your CRM into distinct pipelines — cold prospecting, primary sales, re-engagement, and repeat sales — gives each deal type its own automation logic and keeps conversion data clean and comparable across pipeline segments.
A single monolithic funnel is the most common setup mistake we see in new Bitrix24 implementations. When cold outreach, active negotiations, and repeat upsells share the same pipeline, stage-level conversion rates become meaningless and robots fire on the wrong audience.
Based on our project archive, a practical architecture for B2B companies includes four dedicated pipelines:
| Pipeline | Purpose | Typical next step |
|---|---|---|
| Cold B2B Prospecting | Work unqualified leads, identify interest | Move to Primary Sales or Re-engagement |
| Primary Sales | Qualified buyers: requirements → proposal → contract → payment | Move to Repeat Sales on win; Re-engagement on loss |
| Re-engagement | Warm up declined prospects over time | Return to Primary Sales or Repeat Sales |
| Repeat Sales | Existing customers, cross-sell / upsell cycles | Archive on completion |
When a deal is moved between pipelines, Bitrix24 creates a copy of the original card in the source pipeline for historical statistics, while transferring all relevant field data to the new pipeline. This means your conversion metrics remain intact and auditable at every handoff point.
For companies with distinct product lines, a separate "Finished Goods Sales" pipeline alongside a "Returning Customers" pipeline is a clean alternative — with up to 15 stages per pipeline configured per client need.
How to Structure Stages Inside Each Pipeline
A well-designed Bitrix24 pipeline uses 7–15 named stages that map exactly to your real-world sales steps, with mandatory fields enforced at each transition to prevent deals from advancing without critical data.
Stage count varies by complexity: simpler transactional funnels may need only 7–10 stages, while B2B pipelines with contract negotiation often reach 15–20. From our implementation work, a typical Primary Sales pipeline looks like this:
- New / Incoming
- Qualification
- Requirements confirmed
- Proposal sent
- Conditions under discussion
- Objections handled
- Contract sent
- Contract signed
- Invoice issued
- Payment received ✓ (Win)
- Lost — reason recorded ✗
Two terminal outcomes always exist: a successful close that moves the card to the next pipeline, or a failed close that records a loss reason and sends the card to the re-engagement pipeline. Mandatory loss-reason fields are configured to fire when a deal is marked unsuccessful — this data feeds the conversion reports later.
Deal cards in each pipeline are configured with required fields for stage progression. Across all pipelines combined, a mid-size implementation typically maps 40–150 custom fields (fields shared across pipelines count once).
Leads Pipeline: The Pre-Funnel Layer
Bitrix24's separate Leads pipeline acts as a qualification gateway — up to 10 stages, up to 30 card fields — and only converts a qualified lead into a linked Contact, Company, and Deal when readiness is confirmed.
Not every project needs a Leads pipeline, but for teams handling high inbound volume it provides a critical filtering layer before deals enter the sales funnel. Key configuration elements:
- Up to 10 lead stages (e.g. New → Contacted → Needs Identified → Qualified / Disqualified)
- Up to 30 card fields — capturing contact details, company info, and enquiry specifics from all lead generation channels
- Auto-creation from web forms — integrating multiple website forms so that each submission creates a lead card automatically
- Outcome logic: Qualified leads auto-generate a linked Contact, Company, and Deal with all data pre-populated. Unqualified leads are closed with a recorded reason.
- Up to 5 robots + 3 business processes per lead funnel for automated follow-up tasks and escalations
This separation ensures the sales pipeline stays clean and every deal that enters Primary Sales has already been validated.
Robots and Automation: What Gets Configured Per Pipeline
Bitrix24 robots are the core automation engine: each pipeline supports up to 10–15 robots and up to 10 business processes, firing on stage entry or exit to assign tasks, send notifications, move cards, and escalate overdue deals.
The diagram below shows how automation connects the key pipeline layers — from lead capture through to repeat sales and reporting.
The following flow illustrates how inbound leads, telephony events, and web forms enter the Lead pipeline, get qualified into the Sales pipeline, and how robots govern card movement, task creation, and escalation throughout the cycle.
flowchart TD
WEB[Website Forms] --> LEADS[Leads Pipeline]
PHONE[Telephony / Calls] --> LEADS
LEADS -->|Qualified| DEALS[Primary Sales Pipeline]
LEADS -->|Disqualified| REENG[Re-engagement Pipeline]
DEALS -->|Won| REPEAT[Repeat Sales Pipeline]
DEALS -->|Lost| REENG
REENG -->|Interest re-confirmed| DEALS
DEALS --> ROBOTS[Robots & Business Processes]
ROBOTS --> TASKS[Auto-tasks for managers]
ROBOTS --> ESCAL[Escalation to supervisor if overdue]
ROBOTS --> DOCS[Document generation from templates]
REPEAT --> ROBOTS
Practical robot patterns used across our project implementations:
- Stage-entry task creation — on entering each stage, a task is automatically assigned to the responsible manager with a due date and checklist
- SLA overdue reminders — if a card stays on a stage beyond a defined time threshold, a reminder task is created for the manager; if still unresolved, an escalation task fires to the team lead or supervisor
- Cross-pipeline card transfer — when a deal is won, a robot moves the card to the Repeat Sales pipeline and simultaneously preserves a copy in the source pipeline for conversion statistics
- Document generation — up to 5 document templates (proposals, contracts, invoices) auto-populated from CRM card fields, triggered by stage progression
- Lead round-robin assignment — incoming leads are distributed sequentially across available managers automatically
A larger implementation may use up to 15 robots per pipeline alongside up to 10 business processes (longer workflow chains for approvals, payment tracking, and production coordination).
Smart Processes (a separate Bitrix24 entity) can be layered on top of the deal funnel for payment approvals, production scheduling, and document sign-off — up to 4 smart processes in a typical mid-size setup.
If you want to understand total implementation scope before budgeting, Bitrix24 Implementation Hours by Module provides a detailed breakdown by configuration area.
Stage-Gate Fields: Enforcing Data Quality at Every Transition
Mandatory fields at stage transitions are the single most effective way to prevent incomplete deals from advancing — a contact card supports up to 30 fields, a company card up to 50, and deal cards up to 150 cumulative custom fields across all pipelines.
Field limits by entity type in a standard implementation:
| Entity | Configurable fields |
|---|---|
| Lead card | Up to 30 |
| Contact card | Up to 30 |
| Company card | Up to 30–50 |
| Deal cards (all pipelines combined) | Up to 40–150 |
Fields shared across multiple pipelines count as one. The exact field list is defined during discovery sessions with the implementation specialist — this is why a thorough Bitrix24 onboarding questionnaire before configuration starts saves significant rework.
Typical required fields per transition include: deal value, contact phone, decision-maker name, next meeting date, loss reason (terminal stages). When a required field is empty, the system blocks the stage move and prompts the manager — preventing the "ghost deal" problem where cards drift through the pipeline with no usable data.
Conversion Tracking and Reporting
Bitrix24's built-in reports deliver stage-to-stage conversion rates, deal counts per manager, revenue per manager, and pipeline velocity — with custom reports available when standard views don't cover your KPIs.
Standard reports available out of the box:
- Stage conversion funnel — percentage of deals advancing from each stage to the next, across any pipeline
- Deals by manager — volume and value per rep, filterable by period and pipeline
- Revenue by manager — closed-won totals, useful for commission tracking
- Loss reason analysis — frequency distribution of recorded loss reasons, identifying systemic objections or process gaps
When teams need metrics beyond what standard reports provide — multi-touch attribution, cross-pipeline journey analysis, custom KPI dashboards — additional custom report development is scoped separately.
For RevOps teams migrating from platforms with more advanced analytics, migrating from HubSpot to Bitrix24 covers what report structures carry over and what needs to be rebuilt. Teams coming from Salesforce can review the Salesforce to Bitrix24 migration guide for a TCO-focused comparison.
Telephony Integration and Call-Driven Deal Creation
Connecting telephony to Bitrix24 completes the lead capture loop: inbound and outbound calls automatically create lead or deal cards, attach call recordings, and log call metadata directly to the relevant contact or company card.
Core telephony automation in a funnel setup:
- Inbound call from unknown number → auto-creates a Lead card
- Inbound call from known contact → opens existing deal card and logs the call
- Call recording attached to the card timeline for manager review and coaching
- Call outcome can trigger a robot (e.g. "call completed → create follow-up task")
For teams using AI-assisted quality monitoring on top of call recordings, AI call analysis in Bitrix24 covers transcription, scoring, and sales coaching workflows that plug directly into the CRM pipeline.
Team Onboarding and Adoption
A 2-hour group training session covering deal card workflow, stage progression, task management from CRM, and report reading is the minimum viable onboarding — recorded for async replay by new hires.
No funnel design delivers ROI if the team reverts to spreadsheets. Training scope for a standard funnel rollout covers:
- Processing deal cards through stages, including mandatory field completion
- Marking deals as won or lost with required data recorded
- Creating and managing tasks from within CRM cards
- Using task filters and assigning tasks to project groups or the general pool
- Reading standard conversion and revenue reports
Group sessions are conducted remotely with screen recording, so the session serves as a reusable onboarding asset. Additional modules — advanced filtering, custom reports, smart processes — are scoped separately based on role requirements.
If you're evaluating whether Bitrix24's funnel capabilities justify a switch from your current tool, Bitrix24 vs HubSpot and Bitrix24 vs Zoho offer direct feature and pricing comparisons relevant to sales ops teams.