In the field.

An Apple-tech retailer handling ~10 website orders a month, with inquiries scattered across chat threads, no process control, and orders getting lost as volume grew.

Full-cycle CRM implementation since 2021: process mapping, configuration, custom development and team training, followed by CRM-to-ERP synchronization and Ringostat telephony with call tracking.

As the GRO team put it in the Ringostat case: from ~10 orders a month to ~10 a day, with an average call length of ~1:20. The growth is the GRO team’s own work; the CRM and the CRM↔ERP order flow kept it manageable. Joint case on the Ringostat blog.

The agency sells property, lets it long-term, works with new developments and handles deals for clients from many countries. For years it ran on its own CRM, which held the photo catalogue, owners and clients and fed listings to portals and the agency websites. It had no rentals section, a person who sold and later bought was entered twice, and website enquiries were assigned by hand. The move had to keep portals and websites getting the same data.

Phase 0: brief, specification, architecture. Phase 1 in Bitrix24 Cloud: six roles with regional access; pipelines for purchases, new developments, rentals, listing acquisition, after-sales and deal support; a property smart process with 100+ fields; email, calendar, mobile app, broker webinars. Website forms create leads with source and UTM. Our own migration tool moved properties with photos, owners, contacts and companies; old deals and emails stayed in the archive by design. The CRM now builds the feeds for idealista, Fotocasa, Kyero, pisos.com and the websites.

Phase 1 closed in July 2026. The old system syncs into Bitrix24 every hour, the portal feeds match its output byte for byte, and since September the CRM publishes new listings to the agency websites. Two-way XML exchange with partner agencies is in acceptance. Parsing portal emails into leads, enquiry-to-property matching, new developments and AI are the next stages, some already estimated. The project is ongoing.

A large machinery and spare-parts distributor was launching a CRM from scratch on its own server and needed it connected to its 1C accounting system, with telephony and field-sales tracking to follow.

A pre-project assessment, then on-premise Bitrix24 from 2024 and an integration with 1C 8.2 (machinery deals sync every 5 minutes); automatic call-back lists, AI call analysis, GPS check-ins for field visits and five training sessions for managers. Kyivstar telephony is being connected to the portal.

Assessment, 1C integration and implementation are complete; the GPS app was delivered in July 2026; telephony is in progress. Ongoing support since 2024.

A US trucking holding with several divisions needed to move from cloud Bitrix24 to its own server and then have ongoing technical support: backups and updates, messages to drivers and changes for individual divisions.

In August–September 2025 we installed Bitrix24 On-Premise on the holding's server and moved the data from the cloud. Then support on request: our own module for messages to drivers' group chats with segmentation, a password-storage smart process with access by division, a weekly metrics dashboard for managers, field-change triggers and monthly backups and updates.

The holding runs on its own server, messages to drivers go out through our module and managers enter their metrics in the dashboard. Support is ongoing.

A business-education association with several divisions, from a children’s business school and school placement to events and clubs, runs its CRM on a 250-user plan. The pipelines no longer matched its new structure, website forms kept failing, ad leads were imported by hand, and the owner runs the organization from the UK.

A CRM rebuild around the new structure: one lead, deal and contact layout for every division, field labels in three languages, website forms, a product catalogue, invoices for accounting, company mailboxes, training and guides. Mailings moved from Mailgun to SendPulse, and Make.com brings in ad leads automatically. A website AI agent was put on test in 2025.

A CRM → Make → SendPulse pilot with three automated sequences has run since December 2025, and UK-number telephony since September 2026. The AI agent was switched off at the client’s request in October 2025; a new version is in progress. VIP support 2024–2026.

A sanitaryware manufacturer selling through partner outlets needed a CRM on its own server, connected to 1C, and a way to check its sales reps’ field visits by country and city.

On-premise Bitrix24: the client’s team set up the CRM records with our guidance, and we built the 1C integration (outlets, holdings, deals, order numbers), a check-in app with Google Maps routes and start/end visit coordinates, cascading “country → cities” fields and outlet stock checks.

About 200 hours of implementation from June 2025 to March 2026; the 1C integration and the visit app are delivered. Ongoing support since then, including Ringostat and Open Channels; deal integration with 1C is in progress.

A group of two haulage and freight-forwarding companies and an accounting and legal firm in Poland works in one CRM. After a previous integrator, it needed email automation, sales and forwarder processes, accounting routines, document templates, debt collection and omnichannel.

An assessment and a four-phase proposal: a core CRM with monthly accounting deals, our own app that files emails into deals, business processes in Polish (shortfall notes, debt collection) and online consultations. Then leads and quotes in place of a Teams group, a sales-plus-forwarder process with client reactivation, contract and power-of-attorney templates, WhatsApp (two channels) and Telegram.

All four proposal phases delivered, the last in February 2026. The sales-plus-forwarder process has run since May 2026, and WhatsApp and Telegram are connected. Working together since August 2025.

A recruiting agency kept candidates in its applicant-tracking system, while the commercial side — employer leads, deals, sourcing strategies and the search itself — had no system of its own.

Uspacy CRM: a 12-stage sales funnel for employer leads with loss reasons, a deal funnel, smart objects for sourcing strategies and the search process, access by role for recruiters, sorters and management, and tasks and reminders on stage changes.

Stages 1–2 (structure and automation) are live: employer leads, deals, sourcing strategies and searches run in one Uspacy portal.

A developer running on-premise Bitrix24 on its own server wanted approvals, hiring and apartment sales in the CRM: stock, deals and reports were being pulled together by hand from spreadsheets.

Since 2025: installing the CRM on the client’s server, office-only logins, business processes for barter, feasibility, contract and quote approvals, and hiring. Phase 1 with Floorix: an apartment board, a 12-stage Real Estate pipeline, document generation, four BI-Builder reports and instalment plans.

Approvals and hiring were delivered in February–March 2026. The Floorix board went live in July 2026 and basic training took place in October; documents, reports and instalments are in progress.

A company brokering live pigs — selling piglets, buying back finished pigs and offering free veterinary follow-up — ran suppliers, trips and payments without one system: temperature on the road was not recorded anywhere, partial payments and debts were counted by hand, and forwarders needed access limited to their own trips.

A pre-project assessment over three meetings and a written specification on Uspacy: a lead funnel with three successful outcomes, separate funnels for piglet sales and buy-back, a trip card for transport, eight smart objects, 23 reference lists, around 200 fields in the requirements and six roles with separate access, plus integration with Finmap for finance.

Assessment and specification done. Setup to the specification is going in blocks — CRM module, stage automation, reporting, Finmap; the project is in progress.

A long, document-heavy service run across nine funnels, where payment stages followed no single logic and paid consultations needed one path from booking to the meeting.

Payment stages realigned across the funnels — every “awaiting payment” stage followed by a “payment received” one — and a consultation funnel fed by booking forms in four languages, with card payment, email reminders and webhook automation that records the session time and moves the deal.

Payment stages aligned in every funnel that takes money; the consultation flow configured and checked on test scenarios. The project continues.

A bakery-confectionery with online orders where the site, CRM and accounting were not connected — orders never reached accounting, payment links and Telegram notifications failed, cake items did not show, and delivery intervals were lost.

A site → CRM → accounting link: a business process that posts orders to accounting, an order funnel with finalization, payment-link generation (with switchable entity/requisites), Telegram notifications, delivery fields and intervals carried through, and cake-catalogue sync.

An end-to-end order path site → CRM → accounting with pay-by-link and Telegram notifications; an order funnel and delivery with time-slots. Support since at least 2024.

An online store for winemaking and fruit-processing equipment, with a separate site for Georgia, where the product feed from accounting to the site kept failing, and which needed courier delivery and an AI chat on the site.

Support and enhancement of the CRM-platform sites plus a catalogue feed from accounting; delivery set up; an AI site chat launched with post-processing of answers and file intake for AI analysis.

A stable accounting → site feed across two domains; delivery configured; an AI consultant working on the site. Working together since 2022.

A wedding-dress brand selling to brides and to bridal salons ran its sales in two separate CRMs: there was nowhere to bring together sales, salon payments and manager performance, and the owner needed reports and KPIs.

A one-off move of contacts and deals from NetHunt and KeepinCRM into one CRM, leads from two websites, dresses with measurements as deal products, automation of leads, deals and salon payments, BI reports (plan-vs-actual on dresses, KPIs, upsell / cross-sell), team training and Instagram.

Brides and salons in one CRM; automation delivered in August 2025 and the reports in March 2026; Instagram connected to the CRM.

A salon-atelier selling evening and bridal dresses off the rack and made to measure in its own workshop had no CRM. Later, fitting bookings sat in Altegio apart from the CRM, and clients paid in instalments, so the salon needed to see the balance due.

In 2021: three deal pipelines (sales, made-to-measure, atelier), website forms with UTM tags and automation rules. In 2024: a production pipeline with workshop tasks by stage, leads from Altegio when a client arrives, deposits through Bitrix24 invoices with an automatic balance, Nova Poshta, TurboSMS and messengers.

About 45 hours of work in two rounds, 2021 and 2024. A made-to-measure order opens a production deal on its own; the owner kept some workshop transitions manual because the process kept changing.

A tour operator could not trust where its leads came from: Bitrix24 end-to-end analytics was counting wrong, requests from the PrestaShop website were entered by hand without UTM tags, and one person’s same-day requests became separate leads.

Database cleanup and an Enterprise upgrade instead of moving on-premise; a REST API website integration with UTM-based source rules; same-day duplicate merging via webhook; a “Source (site)” filter field; a Formspree handler that adds new landing pages by itself.

Website and landing page requests reach Bitrix24 as leads with UTM tags, same-day duplicates are merged within a minute, and leads can be filtered by site. Ongoing support in 2024–2026, about 60 hours.

An online clothing retailer with a heavy flow of customer messages — mostly in Instagram, plus Viber, Telegram and the website chat — needed an AI consultant to take routine questions off managers.

An AI consultant and stylist built by Grow2.ai, Auspex’s AI division. It works in Instagram, Viber, Telegram and the website chat, writes results to the CRM and takes orders: the order goes to accounting and the customer gets a payment link in the chat.

6,400+ dialogues from April to July 2026, about two thirds of them in Instagram; median reply time 13 seconds.

A lash and brow brand sells to retail customers and through representatives abroad. Inquiries from several Instagram accounts, Messenger, WhatsApp and the website got lost or went unanswered, and invoices and reference lists lacked the data needed for export.

Sales-team support from May to September 2022: telephony for new managers; Instagram accounts, Messenger and WhatsApp connected to the CRM; chatbots with separate greetings for retail and representatives and an out-of-hours reply; inquiries split between managers; new countries in the reference list (Iran, Austria, China and others); company details and EUR/USD in invoices; mandatory fields; troubleshooting of the existing 1C exchange.

Sales channels brought into the CRM; invoices go out with company details in EUR or USD. The engagement ran for five months in 2022.

A car accessories manufacturer serves B2C and B2B customers through Instagram, Viber, Telegram and its website: many messages are routine — price, availability, delivery — and take up managers’ time.

First we analysed the archive of customer conversations in the CRM: price is asked most often, followed by the product range, delivery and documents. On that basis we wrote the specification of an AI sales agent for the messengers and the website, connected to the CRM: it is to answer routine questions, check prices and stock, calculate Nova Poshta delivery, collect order details and hand complex requests to a manager with context.

The conversation analysis and the specification are done. The agent has not been launched yet, so there are no results to report.

Courses, groups and subgroups already lived in the CRM as smart processes, but next month’s schedule was still assembled by hand before the 15th: eight-hour days, no weekends, no two groups of one course on the same hours, short and long groups alternating, numbering restarting each year. Clashes only surfaced once students had arrived.

A custom “Group schedule” module on top of the boxed CRM, with zero changes to the platform core: a working-day calendar with filters, print, continuation markers and red clash highlighting; auto-generated drafts corrected by drag & drop; two-phase finalization that assigns year/sequence numbers and creates the real group records; per-course auto-generation settings and three access roles.

The schedule is generated in one click and corrected by dragging; clashes are flagged before the month starts, not after. ~6,500 lines of custom code, 73 unit tests, three dedicated tables, no core changes — so CRM updates leave the module intact. Lettered subgroups and a methodologist hours view are next in the queue.

A group of car dealerships with several brands needed every WhatsApp and Telegram message to reach the right brand and department: customer communication was fragmented.

WhatsApp and Telegram connected to the CRM’s open channels, plus a scripted routing bot: the customer picks a brand and a department, the bot collects contact details (looking the phone number up in the CRM) and hands the chat to that department’s channel, taking working hours into account.

Stage 1 — WhatsApp/Telegram omnichannel with the routing bot — delivered on 20 May 2026; stage 2, a self-service AI agent, is in progress.

A window and door showroom sells, measures, delivers and installs, and keeps its books in 1C. Requests, measurements and installer visits had to live in the CRM, with orders and payments synced to 1C. In 2026 the client moved 1C to another server, and part of the deals from July 2025 never reached the CRM.

Since 2020: an on-premise CRM on the client’s server; installers booked for measuring, delivery and installation, with our own app creating their tasks from the booking (each installer sees only their own); a 1C integration — customer orders, payments, products and prices, stock — where 1C documents move the deal stages. In 2026: 1C on SQL Server with RDP access, six months of deals loaded and a weekly scheduled exchange.

The 1C → CRM exchange was restored in June 2026 and runs on schedule; support continues.