A manager enters a deal but doesn't know which stage it's on. A pipeline of 15 stages confuses, analytics shows zero forecasts, automation doesn't work. Typical situation after a boxed installation of Bitrix24. We configure deals for the real sales cycle—with well-thought-out stages, required fields, and robots. Our experience: 5+ years working with Bitrix24, over 30 CRM setup projects.
How to Avoid Chaos: Pipelines and Stages
Bitrix24 supports multiple pipelines (directions)—each with its own set of stages. This is useful for separating B2B and B2C, different products, or regions. Setup: CRM → Deals → the "⚙" button next to the pipeline → "Configure pipeline".
Stages. Each stage has a name (visible to the manager), a system identifier (STAGE_ID), a type (Successful, Failed, Normal), a closing probability (0-100%), and a color. A successful stage (e.g., "Closed. Paid") and failed stages (e.g., "Rejected", "Couldn't reach") are terminal—the deal doesn't move further.
Why Too Many Stages Is a Mistake?
15 stages instead of 5-7—managers stop differentiating them. Transition criteria blur, analytics lose meaning. Optimal: 5-8 stages with a clear transition rule. Example: "Qualification" → "Quote Sent" → "Negotiations" → "Approval" → "Payment".
Custom Fields: Only What's Needed
CRM → Settings → Custom Fields → Deals → "Add field". Types: string, number, date, list, checkbox, link, link to employee or entity. Fields get the name UF_CRM_*_XXXXX and are accessible in robots, reports, and the REST API for deals.
Don't create fields "just in case". Each required field without filling is friction for the manager. 5-7 well-designed fields are better than 30 half-empty ones.
How to Set Required Fields? Step by Step
- Go to CRM → Settings → Deal card.
- Select the stage where data control is required.
- In the "Required" field, choose "Required when changing stage".
- Specify the fields that must be filled: for example, "Deal amount" or "Next contact date".
- Save. When trying to move the deal, the manager will see a warning and cannot change the stage without filling.
How Robot Automation Saves Time?
Robots are tied to stages: when a deal enters stage X, action Y is performed. Typical robots: task to the responsible person, notification in chat, change of responsible person, start of a business process, sending an email/SMS, changing fields.
Triggers are the reverse logic: event → change of stage. For example: the client opened an email → the deal moves to the "Showed interest" stage. Or: invoice payment → stage "Paid". Automation reduces manual input by 40% and speeds up deal progression.
What Access Rights Are Optimal?
A deal is linked to a contact (CONTACT_ID), company (COMPANY_ID), lead. The card displays the history of activities: calls, emails, meetings. To configure rights: CRM → Settings → Access Rights → Deals. Basic matrix: role → operation → scope (own / department / all). Typical setup: manager sees only their own deals, head of department sees department deals, commercial director sees all. Without configuration, everyone sees everything, which violates confidentiality and provokes "interception" of clients.
| Role |
Scope |
Typical Operations |
| Manager |
Only own |
Read, edit |
| Department head |
Department deals |
Read, edit, delete |
| Commercial director |
All deals |
Full access |
What's Included in Deal Setup
Audit of the current pipeline, design of stages with criteria, configuration of custom fields, robots and triggers, access rights differentiation, training for managers, documentation, and final launch. Estimated time: 5–10 days depending on complexity. Cost is calculated individually. Contact us — we will evaluate your pipeline and offer a solution.
| Comparison |
Typical pipeline |
Optimized pipeline |
| Number of stages |
10–15 |
5–8 |
| Transition criteria |
Blurred |
Clear, fixed in card |
| Required fields |
None or all |
Only on key stages |
| Automation |
Absent |
Robots on each stage |
| Access rights |
None or everyone sees all |
Role matrix |
Case Study
One project: a company selling equipment. Original pipeline—13 stages, managers didn't update deals. After an audit, we reduced it to 6 stages, added the fields "Client type" and "Budget", configured robots to send quotes and reminders. After a month, conversion increased by 22%, revenue forecast became accurate. The result—deals stopped hanging, analytics started working. As stated in the Bitrix24 documentation, a properly configured pipeline increases forecast accuracy.
Checklist: Typical Mistakes in Deal Setup
- Too many stages (more than 10)
- Lack of clear transition criteria
- Required fields on all stages without distinction
- Robots not tied to specific stages
- Access rights not configured (everyone sees everything)
Order turnkey deal setup — get a working CRM with a transparent pipeline and automation. Contact us for a free audit of your current pipeline.
How to ensure CRM implementation success?
We have been working with Bitrix24 for over 10 years — during that time we have completed 500+ projects. Every second one starts with the same problem: a company buys CRM, sets it up "by the book," and three months later managers fill two out of twelve fields, deals stall at "Negotiations" for months, and management cannot extract analytics. The root is not bad software — it's the approach. CRM is configured without auditing real processes, without considering staff objections, and without a step-by-step automation plan. In this article — a step-by-step guide on how we avoid this.
All specialists are certified by 1C-Bitrix, the methodology is proven on hundreds of cases. 1C-Bitrix is a platform that, when paired with Bitrix24, provides real end-to-end analytics if configured correctly.
Reality of CRM implementations: 80% fail to deliver results
Why do employees sabotage CRM?
Managers are accustomed to Excel and notepads — they perceive CRM as total control. Our solution: involve key employees at the design stage, show personal benefits — automatic reminders, ready-made proposal templates, less routine. We train on real scenarios, not abstract examples. Resistance drops 4 times faster than with "command" implementation.
How to prevent incomplete data entry?
Mandatory fields are filled, others are ignored — familiar picture? We solve it on three levels:
- Set mandatory fields per funnel stage (only relevant data at each stage).
- Implement auto-fill from UTM tags, email parsing, data from open databases.
- Remove redundant fields — fewer fields, higher quality.
According to our practice, field optimization reduces omission rates by 70% within the first month.
How to design funnels correctly?
Too many stages, no transition criteria, duplicate stages — typical mistakes. We design the funnel based on reality: how sales actually work, not as written in textbooks. We use CRM data from the first 2 weeks of audit to identify real stages and loss points. This shortens the deal cycle by 25–40%.
What automation should be done first?
We set up robots and business processes from day one — so the team immediately feels the difference. For example, lead distribution, sending emails after status changes, creating tasks for colleagues. Companies that implement automation at the start achieve plan targets 3 months faster.
What Bitrix24 features accelerate sales?
- Inquiries from all channels (phone, email, messengers, forms) are captured automatically.
- Leads are created and distributed without manual intervention.
- Visual kanban with custom stages — drag a card to the next stage, an email is sent automatically, a task is created.
- Omnichannel: unified window for telephony, email, WhatsApp, Telegram, Viber, VK, Instagram, online chat.
- Robots and business processes: mailings, document generation, reminders, escalations — no coding required.
- Analytics: funnel, conversions, lead sources, manager workload, average handling time.
What does integrating a 1C-Bitrix website with Bitrix24 CRM provide?
Synergy of the two products yields measurable results, and we implement it through direct data exchange. Site forms transfer leads to CRM instantly with full UTM markup — you see where the client came from. Online chat connects via open lines: a visitor writes on the site, the manager responds from CRM. Orders in the store based on infoblocks v2.0 become deals with full purchase history, enabling cross-selling. Call tracking with number substitution links calls to advertising channels. We use CommerceML to exchange data with 1C Trade Management/ERP: nomenclature, stock balances, prices — synced via agents without manual intervention. End-to-end analytics collects advertising costs, visits, leads, sales in one report — ROI per channel. For non-standard logic, we use REST API and high-load blocks to store arbitrary data (e.g., tech support interaction history). In one project, we configured this bundle for a retail chain: 1C cash register integration with CRM created contacts automatically upon loyalty card purchase, and CRM marketing via Bitrix24 increased repeat purchases by 18% in six months.
How we set up CRM: the process
-
Audit. We analyze how sales work currently. Where are leads lost? Which channels bring clients? We form recommendations before technical implementation.
-
Design. Multiple funnels for different directions, custom fields, mandatory stages and transition conditions. Structure reflects the real process.
-
Integrations. Connect to website, telephony, email, messengers, Yandex.Direct, Google Ads, 1C.
-
Custom modules. When standard is not enough — applications for Bitrix24: specific reports, non-standard business logic, integrations with industry systems.
-
Migration. Transfer databases from amoCRM, Megaplan, Salesforce, HubSpot, Excel. Relationships, communication history, attachments — everything intact.
-
Training. Trainings tailored to your configuration, video instructions, documentation.
What is included in the work?
| Deliverable |
Description |
| Technical documentation |
Funnel scheme, robot settings, field structure, integration plan |
| Access and configurations |
List of integrations, API keys, logins/passwords (provided under NDA) |
| Team training |
2–3 webinars tailored to your configuration, video instructions, cheat sheets |
| Post-implementation support |
2 weeks of incident management + regular usage audits |
Cloud or on-premise: which to choose?
| Parameter |
Cloud (SaaS) |
On-Premise |
| Time to start |
1–2 days |
1–2 weeks |
| IT requirements |
None |
Server and admin required |
| Data control |
Limited |
Full |
| Customization |
Standard limits |
Unlimited |
| Best for |
Teams up to 100 people, standard processes |
Large companies, strict security requirements |
Comparison: the cloud version is 2–3 times cheaper initially, but for B2B companies with large data volumes, on-premise pays off in 1.5–2 years due to no per-user subscription fee.
Metrics we track for your business
-
Funnel stage conversion. If 80% are lost at the proposal stage — the problem is pricing, not managers. Norm: 5–15% for B2B, 1–5% for high-ticket B2C.
-
Lead response time. A 5-minute response increases conversion 10x compared to a 30-minute response. We set alerts — if a manager doesn't respond within 15 minutes, the lead is reassigned.
-
LTV. CRM segments clients by lifetime value — managers focus on the most valuable.
-
Average deal cycle. If it increases, something is broken. Reasons for rejections are gold for product and script adjustments.
Our case studies
Manufacturing company (B2B). A plant with high annual turnover. Leads were lost in email; management only learned about large deals post-factum. We set up automatic inquiry capture, a funnel "qualification → calculation → proposal → approval → contract → payment," and robots that generate proposals from templates. Conversion increased by 23%, lead processing time dropped from 4 hours to 20 minutes. Manager payroll savings exceeded $1,000 per month due to reduced routine.
IT service company. Three funnels: new clients, upselling, tenders. Auto-generation of contracts and invoices, integration with Jira — after signing, tasks automatically appear in the development department. Management received a weighted revenue forecast with 90% accuracy. The project paid off in 4 months.
Implementation timeline and cost
| Scale |
Timeline |
What's included |
| Basic |
1–2 weeks |
Funnel, telephony, email, database import |
| Standard |
1–2 months |
Custom funnels, automation, website and 1C integrations |
| Comprehensive |
2–4 months |
Multiple funnels, custom modules, training, end-to-end analytics |
The cost is calculated individually based on your scope of work. After implementation — tech support with SLA (response from 1 hour), regular usage audits, and feature development.
Ready to discuss your situation? Contact us — we'll conduct a free audit of your current CRM within 2 days and propose an implementation architecture with a result guarantee. Request a consultation — we'll show you in numbers how much you'll save with proper setup.