Cases
Without disclosing clients: problem, approach and operational result.
CRM / Bitrix24
CRM and lead/visit duplicates
Duplicate leads, deals and contacts; visits were lost; a lead was linked to the wrong deal; data was reconciled manually.
Result: Managers stopped reconciling visits manually, the database was cleaned of duplicates.
lada-dabracar.by
Bitrix24 ↔ 1C synchronization
Expense and travel requests, stock levels and employee data were synced between 1C and the CRM by hand — approvals got lost and data drifted apart.
Result: Requests and stock levels stopped drifting apart manually, approvals got faster — the approach was proven on two independent rollouts with different 1C setups.
lada-dabracar.by
Car selection and deal processing right in the CRM
At the LADA dealership lada-dabracar.by, a sales manager ran a deal in three places at once: stock was checked in a separate spreadsheet, the work order was signed on paper, and payment status came from a call to accounting. While one step was being sorted out, the client could walk to another dealer.
Result: A manager closes the deal without leaving the card: from choosing the car to payment and the contract — in one window, every step visible and nothing lost between departments.
HR processes in Bitrix24: onboarding and absence tracking
Onboarding a new employee and filing a sick leave or day off went through chats and paper: HR collected documents by hand, and a time-off request could easily get lost in a chat — nobody reconciled absences.
Result: Onboarding and absence tracking became a process with a history instead of chat threads: HR sees the status, and a manager sees workload and absences in one dashboard.
Employee goal-setting and review system on Bitrix24
The company needed a goal-setting and performance review system with multi-step approval and a final rating, without buying a separate HR module. A second version of the module grew in parallel with the first, and requests started "getting lost" between them.
Result: The company got a full goal-setting and review cycle without buying a separate HR module, and the audit produced an exact list of reasons requests were "getting lost" between the two versions, plus a stabilization plan.
sattar.kz
One-click notification and document automation
At sattar.kz, a manager drafted a contract or a claim by hand, separately called or messaged the client, and hunted for the case files scattered across a disk — the routine took longer than the actual case work.
Result: Routine messaging and file-hunting disappeared: one click on the deal — the document is ready, the client is notified, the file is in the right folder.
lada-dabracar.by
A custom BI dashboard on top of Bitrix24
At the LADA dealership lada-dabracar.by, management and the call center needed a single "inquiry to visit to sale" funnel on top of Bitrix24 — the CRM's built-in reports did not cover that view.
Result: Management and the call center got a single tabbed funnel dashboard (overview/visits/calls/agents/directions) instead of Excel exports — with caching and clearly documented metric limitations.
A reusable Bitrix24 integration library
Every new integration with Bitrix24 and external services (e-signature, warehouse) was written from scratch — requests, error handling and logging got duplicated across projects.
Result: New Bitrix24 and adjacent-service integrations started being assembled from a ready reusable transport-and-logging layer instead of being written from zero every time.
Traffic-source analytics in Bitrix24
The client did not know which ad channels actually drove inquiries and sales — budget was split by gut feel, and some campaigns quietly ran at a loss.
Result: The client saw which channels and campaigns actually drove deals and could reallocate budget deliberately — instead of guessing.
Tasks and quality control for a multi-department site on Bitrix24
A large site with many departments had no control over work quality: tasks were assigned verbally, issues were "resolved" by word of mouth, and some just got lost.
Result: Tasks stopped getting lost or settled by word of mouth: every department has its own process, a review checklist, and a visible work status.
Operations automation for the Big Tech business center
A growing business center handled operational matters by hand and by phone: clearing a parking debt meant calling the front desk, tenant registration was on paper, security patrols went unlogged, and invoices and service requests were collected manually.
Result: Clearing a parking debt and registering a tenant are now handled by a bot instead of a call to the front desk; security patrols and staff onboarding got a digital process instead of verbal agreements and paperwork.
Floor plans and occupancy analytics for a business center network
The management company behind a network of business centers showed vacant space as a price list and verbal description — no floor-by-floor visualization, and occupancy across the network sites was not visible in one report.
Result: Across the network: 93 floors, 1,087 offices and 152 uploaded floor plans — with occupancy that updates from the CRM automatically instead of being reconciled by hand for every site.
Integrations
Bitrix24 ↔ MoySklad integration
Products, stock and orders diverged between the CRM and the warehouse, sync was unstable and duplicates appeared.
Result: An exchange history appeared: it is clear where and why sync fails; data no longer diverges manually.
sattar.kz
TrustMe e-signature integration
Sending contracts for e-signature was implemented separately on several CRM portals: no shared storage of signing status and no protection of the webhook against re-processing.
Result: E-signature stopped being a set of similar scripts scattered across portals: the integration got a single architecture, a status history, and a webhook that no longer fears redelivery.
Event-driven Bitrix24 integration via Kafka
One-off HTTP calls to an external system did not scale and left no event history: a failure meant the exchange was simply lost, and outages were discovered after the fact from client complaints.
Result: The exchange became event-driven and recoverable: a handler failure no longer loses the event or stays silent — there is retry and an alert instead of silence.
sattar.kz
Adata integration: counterparty checks on the deal card
At sattar.kz, before handling a case or releasing money, a counterparty was checked by hand: open a third-party site, search by tax/business ID, copy the status back into the CRM.
Result: Checking a counterparty took seconds right inside the deal instead of a trip to a third-party site and manual copy-pasting.
Document signing via NCALayer (Kazakhstan e-signature)
Some documents legally had to be signed with the state digital signature rather than a third-party e-signature service — the signing process ran separately from the CRM, with signed files attached by hand.
Result: State-signature signing became part of the same flow as every other deal document — no separate "sign and attach by hand" step.
Online payment intake for a booking platform
Booking without prepayment turned into a problem: some clients simply did not show up, and support had to reconcile payments for every order by hand.
Result: Booking payment became transparent: the client pays at checkout, the booking status updates automatically, and support no longer reconciles payments by hand.
sattar.kz
Court-case search on a portal with no public API
At sattar.kz, counterparty court cases needed to be searched programmatically on a state court portal — there is no public API, only a dated JSF/RichFaces web interface.
Result: Searching for a counterparty's cases became a programmatic JSON call instead of a manual trip to the portal, resilient to small markup changes thanks to fallback parsing.
Multi-channel notifications with automatic fallback
A booking platform needed to notify users and venues about order statuses, cancellations and events across several channels — with no message-queue broker and no manual sending.
Result: Notifications for 15+ business scenarios now go through a single point with automatic channel fallback and minimal manual upkeep.
Face ID attendance tracking via Hikvision
Employee attendance was not collected centrally anywhere — Face ID turnstile data just stayed on the terminals themselves.
Result: Face ID turnstile data no longer stays trapped on the terminals — every hour it is collected into a single timesheet viewable on a report page, instead of checking each terminal by hand.
Cabinets
Laravel Client Cabinet
Clients had nowhere to see statuses, requests and invoices on their own; everything went through support.
Result: Part of the requests moved to self-service, the load on support dropped.
sattar.kz
A client cabinet built on top of Bitrix24
At sattar.kz, clients could not check the status of their cases and documents themselves — everything went through calls and messages to a manager, and giving clients access to the CRM itself was not an option.
Result: Clients got self-service without direct CRM access: case status, documents and invoices — in a separate cabinet with its own protected authentication.