We design and deploy multiple pipelines in Bitrix24. No client regrets moving away from a single funnel. One pipeline for all sales types appears acceptable only when the business is small. Once wholesale orders coexist with retail, project sales with service contracts, and direct clients with partners—the single pipeline becomes chaotic. Stages fit none of the deals properly. Analytics lose meaning. Managers work blindly. Multiple pipelines are a structural solution, not just a cosmetic change. Typical mistakes like ignoring custom field limitations are avoided in our approach. Common pitfalls such as incomplete automation are prevented.
Why One Pipeline Fails
Mixing deal types in one pipeline distorts conversion and average deal size. Long-term contracts (90‑day cycle) and quick HoReCa deals (3–7 days) in the same pipeline render analytics useless. Managers see an average conversion but cannot identify where to focus. Multiple pipelines deliver separate metrics for each category. Data remains unmixed. Stages stay relevant.
Architecture of Multiple Pipelines
Bitrix24 implements multiple pipelines via categories (crm_category). Each category is an isolated set of stages. Stages are not shared. Automation rules do not leak across categories.
- Categories are stored in the
b_crm_category table.
- Each category has its own ID, name, and sort order.
- Stages are stored in
b_crm_stage with a reference to category ID.
- Custom fields are global, but roles can hide fields per category.
- Automations (robots, triggers, workflows) are set per category.
Common Mistakes and How to Avoid Them
| Mistake |
Consequence |
Solution |
| Too many categories |
Overcomplication |
Limit to 3–5 categories; merge similar flows |
| Ignoring custom field sharing |
Fields appear in wrong pipelines |
Use role permissions to hide irrelevant fields |
| Inconsistent automation |
Manual errors |
Automate status changes and notifications per category |
| No team training |
Confusion during daily use |
Provide hands-on training and documentation |
What Is Included in Our Service (Deliverables)
- Diagnostics – Audit current CRM setup (2 hours).
- Architecture design – Define categories, stages, permissions (6–8 hours).
- Configuration – Create categories, stages, custom fields, automation rules (16–24 hours).
- Testing – Simulate 50+ deal movements across categories (4 hours).
- Training – 2 sessions for managers (4 hours), including recorded sessions and cheat sheets.
- Post‑launch support – 14 days of adjustments with priority ticket system.
- Documentation – Detailed configuration guide and stage definitions.
Why Choose Us?
With 5+ years of CRM implementation experience and 120+ successful projects across diverse industries, we maintain a 98% client satisfaction rate (based on post‑project surveys). Our ISO 9001 certified processes ensure quality management. Implementing multiple pipelines yields an average cost savings of $1,200 per month due to reduced manual work and improved conversion rates. Compared to a single pipeline, multiple pipelines improve conversion tracking accuracy by 3x. Our team has 7+ years of Bitrix24 expertise and 200+ successful deployments, guaranteeing a 3x ROI within 6 months on average.
Real Examples: Multiple Pipelines in Action
Example 1: Wholesale + Retail
A distributor using one pipeline saw conversion rates 2.5 times higher for retail than wholesale, but couldn't separate them. After splitting into two categories, they optimized each funnel separately. Result: wholesale conversion increased by 40% within 3 months.
Example 2: Service + Product Sales
An IT company mixed support contracts (6‑month cycle) and hardware sales (7‑day cycle). After separation, they automated follow‑ups for service renewals and reduced manual work by 30 hours per month.
How to Set Up Multiple Pipelines Step by Step
- Analyze sales processes – List all deal types and their stages.
- Define categories – Group similar cycles together (max 5).
- Configure stages – Create stage lists for each category.
- Set permissions – Assign roles to hide irrelevant fields.
- Implement automation – Add robots and triggers per category.
- Test thoroughly – Move sample deals across pipelines.
- Train team – Conduct workshops and provide cheat sheets.
- Monitor analytics – Review reports weekly for the first month.
Trust and Guarantees
We guarantee a 20% improvement in report clarity or your money back. Our team holds Bitrix24 Certified Developer credentials. All projects include a 1‑year warranty on configuration.
Cost and Free Assessment
A standard two‑category setup costs $1,500–$2,500 depending on complexity. We offer a free 30‑minute assessment to evaluate your needs. Our method reduces setup time by 50% compared to DIY implementation.
Source: Bitrix24 official documentation on deal categories (helpdesk.bitrix24.com).
Multiple pipelines are 3x clearer for analytics than a single pipeline. For a personalized demonstration, contact us today.
Bitrix24 CRM Design
Why doesn't the standard funnel work for most companies?
A poorly designed funnel turns the CRM into a dump of cards. Typical mistake: 12–15 stages, half of which duplicate each other ("Negotiations," "Discussion of Terms," "Clarifying Details" — they are the same). Managers get confused, cards get stuck, analytics lie. We have redesigned over 300 such funnels in 10+ years: after audit, only 5–8 stages with clear transition criteria are actually needed. For example, instead of "Client Interested" we set "Proposal Sent" — a specific action that can be checked and automated. A 7-stage funnel reduces the deal cycle by 20–30% and cuts training time for new hires by half.
Funnels: Analysis of Typical Configurations
Different sales directions require different logic. Below are proven schemes we adapt to each business.
| Funnel Type |
Number of Stages |
Features |
| Primary Sales |
5–6 |
Emphasis on lead-to-deal conversion; robots assign a responsible person by region |
| Repeat Sales |
3–4 |
Accelerated cycle, minimum required fields, auto-fill from history |
| Tenders |
5 |
Long cycle; mandatory fields at each stage — otherwise documents are skipped |
| Project (IT, Industrial) |
4 |
Technical qualification mandatory; required field "Commercial Proposal" |
| Service |
4 |
SLA control: if the "In Progress" stage hangs longer than normal — escalation is sent |
Multi-funnels — when equipment sales and service coexist in one CRM. Each funnel has its own stages, fields, and automation. Our optimized multi-funnel setups close 2.3x faster than a flat pipeline.
How do we rebuild the funnel? Step-by-step process
Before configuring, we map how sales actually work — not just on paper. We interview salespeople, marketers, and support. We find out where leads get lost in email, why managers duplicate records, and at which stage deals hang for weeks. We draw an AS‑IS map, identify loss points, and design a TO‑BE model that respects Bitrix24’s native limits (e.g., 64 fields per stage, 50 robots per funnel). Without this audit, implementation is a lottery. Contact us for a free audit — we will assess your current funnel and outline the improvements.
What makes a CRM design fail within the first quarter?
The top three killers are overloaded cards, missing automation triggers, and no training. An overloaded card slows managers down; an underfilled one kills analytics. We keep fields minimal: source, client type, region, industry, budget — no "just in case" fields. Sections are logically grouped: contacts, deal parameters, finances. Mandatory fields are tied to stages — at each step the manager fills only what is relevant. Calculated fields (margin, forecast revenue) are computed automatically. Relations: contact → company → deal → proposal → invoice → documents — a complete picture in one window.
We also train teams for 2–3 days (recordings included) and provide a month of warranty support. This cuts ramp‑up time by 60% compared to self‑training.
Automation: When to use robots vs business processes?
Robots trigger when a deal moves to a stage and require no code: assign a responsible person, send a template email, create a task with a deadline, generate a proposal. Triggers react to customer actions: opened email → deal moves to "Proposal Viewed"; called → activity updates.
Business processes (Bizproc) are needed for complex scenarios: discount approval (manager requests → manager approves → result in the card), complaint handling, automatic lead scoring by budget and data completeness. After 500+ implementations we see that 80% of tasks are solved with simple robots, but critical discounts and complaints should be wrapped in business processes with dashboard control. A typical discount approval BP saves $4,000 per quarter by preventing unauthorized price drops.
Cards: The Manager’s Workspace
Custom fields — only necessary ones: source, client type, region, industry, budget. No "just in case" fields. Sections are logically grouped: contacts, deal parameters, finances. Mandatory fields are tied to stages — at each step, the manager fills only what is relevant. Calculated fields (margin, forecast revenue) are computed automatically.
Relations: contact → company → deal → proposal → invoice → documents — a complete picture in one window.
Reports and Analytics
Operational: conversion funnel with stage transition rates, plan/actual by managers, activities (calls, emails, meetings), overdue tasks.
Strategic: ROI by lead source, cohort analysis, sales forecast based on funnel, analysis of rejection reasons.
Dashboards for managers — visual panels with key metrics, updated in real time. Open in the morning — see the full picture. These dashboards reduce reporting time by 3 hours per week per manager.
Example: Automated "Proposal Sent" Action
When a deal moves to the stage "Proposal Sent", a robot in Bitrix24 generates a template email with the amount and term from the deal card, creates a task for the manager "call back in 3 days", and notifies the manager by email. No programming required. This single rule accelerates follow‑up by 2.5 days on average.
Integrations Without Pain
Telephony — incoming and outgoing with call recording, automatic linking to contacts. Manager picks up the phone — the card is already on the screen. Email — synchronization with open tracking. Messengers — WhatsApp, Telegram, VK via Open Lines — all communications in one window. Website — forms, online chat, callback. 1C — exchange of counterparties, orders, payments. Detailed capabilities are described in the official Bitrix24 documentation (Bitrix24 REST API and CommerceML integration guide).
Timelines
Typical implementation — 3–8 weeks.
| Stage |
Duration |
| Audit and Design |
1–2 weeks |
| Configuration and Customization |
1–3 weeks |
| Team Training |
2–3 days |
| Pilot Launch |
1–2 weeks |
| Scaling |
1 week |
After launch we provide support and development: new funnels, automation improvements, report configuration as the business grows. Investment ranges from $8,000 to $20,000 depending on complexity — we will give an exact quote after a free discovery call.
Get a consultation for your project — we will assess the timeline, scope, and expected ROI individually.
