CRM implementation stalls when staff have to type the same thing into two programs, when the system is built around a process they don’t follow, and when it gives them nothing back. What works is the opposite: the CRM pulls data from the programs a business already uses, follows the way people actually work and saves time every day for whoever sits in it. Roll it out in stages, and judge the result by the work itself: how many leads became deals and how many clients came back.
What CRM implementation means in practice
“Implementation” sounds like buying a system, configuring it and handing out passwords. In practice it means moving people’s daily work into one place: leads, messages, calls, documents, payments. The software is only part of it. The rest is agreeing where each piece of data now lives and who fills it in.
Skip that, and you get a familiar picture. The owner sees empty cards in the CRM, managers keep clients in a spreadsheet and their personal messenger, and six months later the system is written off as a bad purchase.
Why staff don’t use the CRM
There are usually only a few reasons, and they all show up in the first week.
Double entry. The most common one. At a chain of cosmetology studios we are working with now (a project under NDA), bookings, the till and staff payments lived in YCLIENTS, a booking program widely used by Russian salons, while the client base and leads lived in amoCRM. The same client existed in two systems as two different people: bookings in one, leads and messages in the other, and neither knew the whole story. An administrator whose phone line is overloaded in the evening has no time to copy data from one program to the other, so they don’t.
A process that isn’t theirs. An off-the-shelf CRM arrives with its own sales pipeline. Cosmetology runs on a different rhythm: facial massage weekly as a course, peels as a course and by season. A “lead - deal - payment” pipeline has no room for that, so the cosmetologist’s recommendations stayed in the card and the end of a course was remembered only by chance.
Nothing in it for the employee. If the CRM exists only for reports to the boss, people fill it in at the last minute and carelessly. Someone will open the system on their own when it answers a work question faster than memory or a spreadsheet: who is calling, what is left on their package, when they are due back.
Data scattered across programs. At the legal firm GORONO, clients, deals, documents and money sat in different programs and spreadsheets, each paid for separately, with data copied between them by hand. Answering “how much did we earn in June” cost the accountant half a day.
| Why it stalls | What it looks like | What helps |
|---|---|---|
| Double entry | A client is two different people in two programs | Data from the working program reaches the CRM by itself |
| Someone else’s process | Recommendations sit in the card, nobody reminds about the end of a course | A repeat rule is set once and the reminder goes out by itself |
| No benefit to staff | Cards are filled in for reports | The administrator sees who is calling before picking up |
| Scattered data | “How much did we earn” takes half a day of reconciling | One database: deals, documents, bank and accounting |
CRM implementation for a business: which programs to keep
The first decision is about the programs that stay; choosing the CRM comes after. At the studio chain we kept YCLIENTS: it is the salon’s working tool and everything there is set up. We are replacing only amoCRM, with a system of our own built for cosmetology and tightly linked to YCLIENTS.
Programs can be linked when they offer an open way to exchange data. YCLIENTS has a REST API: it returns clients, bookings and visits, lets you search visit history, and sends changes to webhook addresses. That is why booking data reaches the client card on its own and the administrator doesn’t have to move it.
Before choosing anything, walk through the working day of every role and note where each kind of data lives today: bookings, the till, messages, calls, documents, money. Each kind should end up with one place where it is entered, and the other programs only read it.
Rolling out a CRM in stages
Launching everything at once is a reliable way to get a system nobody uses. We start from whatever gets in the way of work every day.
Stage 1. One client card
At the studio chain the first step is a single card: visits, packages and what is left on them, the cosmetologist’s recommendations after a treatment, messages from every channel and calls. Leads from the website, social media and messengers go into one pipeline. From then on a client has one history, not two halves.
Stage 2. What saves the employee time
Next comes the reason an administrator will open the system without being told. On an incoming call they see the name, recent visits, package and upcoming booking before picking up. After the call the conversation can continue in WhatsApp or Telegram, and the messages land in the same card. We deliberately do not put a voice robot on the first line at this stage: order in the data comes first, automatic replies later.
Stage 3. Rules that used to live in people’s heads
Then we move into the system what only the administrator and the cosmetologist remembered. We separated two things. A protocol is a rule for repeating a treatment going forward: set once, it schedules the client’s reminder by itself. Reactivation is a pass over the base built up over the years: who hasn’t been in for a long time, who finished a course and never returned. Each group gets its own win-back scenario.
Stage 4. Documents and money
Once client work is in order, documents and payments are connected. At GORONO, leads from the website, the bot and paid consultations become deals with the right service straight away. The contract is assembled with one button from the deal, the bank statement is pulled in every hour, and a payment attaches itself to the deal when there is only one match. Unclear payments go to a “sort out manually” list instead of being booked at random.
Access and rules inside the system
When several roles work in one system, each should see its own part. GORONO has four portals: for the client, the lawyer, the administrator and the accountant. A lawyer sees only their own clients and has no access to their phone numbers or email. The accountant sees the bank, contracts, invoices, acts and taxes, and nothing else. Client and lawyer talk through the bot, phone numbers are cut out of messages, and the administrator sees the whole conversation.
This pays off in money too: a client can’t be taken away from the firm, because the lawyer doesn’t know their number. And the rule that a document can’t be returned without a comment ended arguments about who is waiting for whom: the screen says whose move it is.
A separate question is where the client base is stored. A CRM almost always holds personal data: names, phone numbers, visit history. Article 18 of Russia’s personal data law (No. 152-FZ) forbids recording, organising, accumulating and storing personal data of Russian citizens in databases located outside Russia, apart from a few cases listed in the law. When choosing a cloud CRM, ask where its servers are. A system of your own runs wherever the owner decides: at the flower studio Doch Sadovnika, the catalogue, customers, money and staff run on the studio’s own server.
What to count as a result
“Everyone logs into the CRM” is a weak measure: people can log in just to tick a box. Look at what changed in the work.
At GORONO it shows in specific things. A contract with an invoice takes a couple of minutes instead of 30-40. Finding out how much was earned in June takes one screen. The system checks the government registers by itself, and nobody browses regulators’ websites any more.
At the studio chain the project is still in development and there are no figures yet. The goal is clear in advance: the client stops existing in two systems, the reminder about the next treatment goes out without the administrator, and the large base of past visits starts bringing repeat visits.
It helps to write such measures down before work starts. A few months later you can compare instead of arguing about impressions.
Frequently asked questions
How long does CRM implementation take?
It depends on how many programs have to be linked and how many roles work in the system. We launch in stages: first one client card, then what saves staff time, then rules and documents, so the first part is working before everything is finished.
Should I implement Bitrix24 CRM or build my own system?
An off-the-shelf CRM such as Bitrix24 fits if your process sits inside its pipeline and you don’t need deeper links to your working programs than it offers. A system of your own makes sense when staff have to enter the same data twice, or when important rules, such as the rhythm of treatments, don’t fit into a ready-made product.
Can a 1C CRM be implemented without double entry?
Yes, if each kind of data has one place where it is entered and the other programs only read it. 1C, the most widely used accounting system in Russia, stays the main place for its own data, and the CRM receives that data through an exchange, as in our project where bookings and the till stay in YCLIENTS and the data reaches the client card on its own.
What if staff resist using the CRM?
First find out what gets in their way: most often it is double entry or no benefit to them personally. It helps to start with a feature that saves that particular person time, such as showing who is calling before they pick up.
Who this approach fits
Companies that already bought a CRM which lives apart from their working programs, and those about to implement one who want to avoid other people’s mistakes. Especially salon and clinic chains with bookings in YCLIENTS or a similar program, and firms where a service runs for weeks and is built from the client’s documents. More examples of our systems are under directions. If this sounds like your situation, describe it in the form below and we will work out which programs to keep and where to start.
