Build an Industry-Specific Solution on Bitrix24
Standard Bitrix24 configurations cover 60–70% of tasks for a universal business. The remaining 30–40% is industry-specific—custom entities (real estate property, insurance policy, medical case), non-standard pipelines, deep integrations with industry systems, and specialized calculations and automations. In our practice, every second Bitrix24 implementation project requires custom development beyond typical CRM functionality. An industry-specific solution is an add-on over standard Bitrix24, implemented through a combination of the platform's low-code tools, custom REST applications, and server-side logic. Developing such a solution is fundamentally different from routine setup: this is where real engineering begins. We use an Agile approach with two-week sprints to quickly adapt to changing business requirements. We design each solution with long-term evolution in mind and guarantee support at all stages.
How to Choose Between Extension and Integration?
The first decision in an industry solution project is determining what goes into Bitrix24 and what stays in external systems. Both extremes are equally bad:
- Everything in Bitrix24 — creating a monolith where the platform is overloaded with functions it wasn't designed for. Financial accounting, warehouse logistics, production planning—these are not CRM tasks.
- Bitrix24 as a thin client — then why pay for a license? The whole point of a unified work environment is lost.
The optimal boundary: Bitrix24 handles customer communications, deal and task management, and visualization of data from external systems. Industry systems (1C, HIS, ERP, WMS) handle the domain logic. This approach ensures flexibility and lowers maintenance costs.
Which Bitrix24 Tools to Use?
Smart Processes (SPA)
The foundation for custom entities in Enterprise and higher plans. They allow creating "Construction Object", "Insurance Policy", "Medical Case" with custom fields, pipelines, access rights, and robots. With REST API 22.x, smart processes have become a full-fledged replacement for custom modules. According to our estimates, developing on SPA is 3 times faster than building a custom module on D7 core.
// Creating a smart process item via REST CRest::call('crm.item.add', [ 'entityTypeId' => 138, // Your SPA ID 'fields' => [ 'title' => 'Object: Northern Residential Complex', 'ufCrm138_1234' => 'Residential complex', // custom field 'ufCrm138_5678' => '2025-12-31', // planned deadline 'assignedById' => 42, ], ]); More about smart processes
Smart processes are a low-code platform for creating custom entities. They support robots, business processes, access rights, and REST API. Ideal for industry-specific objects: real estate property, insurance policy, medical case. Not suitable for complex database-level logic or unique calculation algorithms.REST Application on Marketplace
For solutions intended for replication. Application registration, OAuth 2.0, webhooks on CRM events. This path is more complex but allows selling the solution to other clients.
Embedded Pages (Embeddable Apps)
Iframe insertions of custom UI into CRM cards. Implemented via placement.bind and allow displaying data from external systems in the side panel of deal cards: order status from 1C, support ticket history from a ticket system, technical specifications from an ERP.
When Are Smart Processes Not Suitable?
If unique database-level logic or complex calculations are required, a custom module is better. But for 80% of industry tasks, SPA is sufficient. Maintenance savings can reach 50%.
Case Study: Industry Solution for a Real Estate Agency
Our client is an agency with 50 agents, working in primary and secondary markets with developer partner programs.
The problem with standard Bitrix24: no "Property" entity with characteristics (type, area, floor, cost per m², sale status), no property-to-multiple-deals relationship (from different agents), and no agent commission calculation.
Solution architecture:
Smart Process "Property" ├── Fields: type, area, floor, cost, status (available/reserve/sold) ├── Relation: Developer (Company in CRM) └── Relation: Deals (Standard entity) Smart Process "Commission" ├── Relation: Deal ├── Fields: percentage, amount, payment status └── Robot: auto-calculate when deal moves to "Won" REST Application "Property Catalog" ├── Embedded page in contact card ├── Shows available properties matching client criteria └── Button "Reserve" → creates a Deal + updates Property status Implementation in 6 Weeks
| Week | Work |
|---|---|
| 1–2 | Analysis, entity design, approval |
| 3 | Configure SPA, fields, relations |
| 4 | Develop REST application (catalog + reservation logic) |
| 5 | Integrate with the website (parse developer properties) |
| 6 | Testing, training, launch |
Result: time from client request to property selection reduced from 2 hours to 15 minutes. Time savings of 87%, and successful deals increased by 40% in the first quarter.
Integration with Industry Systems
For most industries, bidirectional synchronization with accounting systems is critical. Common patterns:
- 1C → Bitrix24 (data from accounting to CRM): invoice payment statuses, warehouse balances, shipment data. Implemented via 1C connector or through REST API with a cron agent in 1C.
- Bitrix24 → 1C (deals into orders): on deal win, automatically create an order in 1C. Trigger via webhook ONCRMDEALSTAGEIDCHANGE, transfer through COM object or 1C REST.
- External APIs: for insurance — AIS OSAGO/KASKO insurers, for healthcare — HIS via FHIR protocol, for logistics — transport company APIs (CDEK, PEC).
Comparison: Custom Module vs Smart Process
| Criterion | Custom Module | Smart Process |
|---|---|---|
| Development speed | 3–4 weeks | 1–2 weeks |
| Flexibility | High | Medium (SPA limitations) |
| Platform updates | Require adaptation | Automatically compatible |
| Maintenance cost | High | Low |
For most industry tasks, smart processes are the optimal choice unless unique database-level logic is needed. Using SPA reduces development costs by 30–50%.
What's Included in Industry Solution Development
We provide a full cycle of work:
- Analytics and design of entities, pipelines, access rights.
- Development of smart processes, REST applications, embedded pages.
- Integration with external systems (1C, ERP, WMS, APIs).
- Architecture and operational documentation.
- Training key users (2–3 days).
- 3-month warranty support after launch.
Version Control and Deployment
An industry solution is code that needs versioning. Mandatory stack:
- Git repository for REST application and server scripts
- Staging environment (separate Bitrix24 portal or test On-Premise instance)
- CI/CD for automated change deployment
Without versioning, after six months no one will remember why a particular field was added to a smart process, and changes will start breaking each other.
An industry solution is a long-term product that lives and evolves with the business. Architect with changes in mind: modularity, documentation, clear boundaries of responsibility between Bitrix24 and external systems.
Get a consultation on your project — we will analyze your industry and propose the optimal solution. Request an audit of your current CRM to identify necessary customizations.