Blog · CRM27.10.2026

Bitrix24 or a custom CRM: how to choose

If your process is standard (a sales pipeline, tasks, a few managers), go with Bitrix24 or another ready-made CRM. It launches in days, and a custom system won't pay for itself on such a process.

A custom CRM is needed when the ready-made one has to be customised for a long time around orders, stock, roles or several sales channels, and staff still keep half their work in spreadsheets next to it. Below we look at how to tell which situation you're in and how to do the maths.

What Bitrix24 does well

We often recommend starting with a ready-made system ourselves. Bitrix24 has strengths that a custom CRM would take a long time to catch up with:

  • Quick start. You can open the cloud version today and enter deals tomorrow. A custom system, even in our format, needs a prototype and a month to the pilot.
  • Many modules at once. CRM, tasks, file storage, chat, video calls, telephony, a mobile app. If you need all this in standard form, writing it again makes no sense.
  • A market of specialists. There are many integration partners, and it's easier to replace a contractor than with a custom-built system.
  • Ready-made exchange with 1C. Standard synchronisation of counterparties, products and invoices is set up without development.

If you have five managers, a standard pipeline and deal reports, stop there. It's worth reading on if something in the next section sounds familiar.

Where the difficulties begin

The problems are usually not in Bitrix24 itself but in the company's process no longer fitting its framework. The signs repeat from project to project.

  • Licences grow with headcount. Cloud plans are limited by the number of users, and the on-premise version is sold per number of employees and requires an annual update renewal. When the system is used not by five managers but by hundreds of people, as in the portal for 400+ employees we built for PKF SNARK, licences become a noticeable expense every year.
  • Customisation hits the limits of the platform. The cloud version offers a REST API, apps and business processes in a visual editor, but server code can't be changed. In the on-premise version you can write your own modules, but changes to the core conflict with updates: every update turns into a check that nothing has broken.
  • Your own accounting doesn't fit into deals. Stock kept as a movement log, requests with regulatory deadlines, an estimate based on a laboratory's price list, an order that goes through quote, contract, drawings, production and shipment. All of this can be modelled with deals and custom fields, but it becomes awkward for staff, and they move to Excel.
  • Several sales channels. The website, a Telegram Mini App and the phone must produce one order and one stock level. In a ready-made platform channels are often connected as separate modules, and data has to be synchronised.
  • Permissions don't match the staff. The warehouse worker should see picking but not revenue. A section foreman files requests from a phone while wearing gloves. Platform roles can only be configured within the limits the vendor provided.

In the project for a home decor online store we counted five such places: channels, stock, roles, customisation and costs. After that, a custom system became cheaper than continuing to adapt to the boxed product.

Point-by-point comparison

Bitrix24
Custom CRM
Start
Days. Sign-up, pipeline setup, client import
Prototype in 5–9 days, pilot on your data within a month
Payments
A subscription or a licence per number of users, every year
Development once, then hosting and support as needed
Customisation
In the cloud via the API and apps, on-premise via modules with a risk of conflicts on updates
Anything, the code belongs to the client
Interface
Shared by all the platform's customers, unnecessary sections are hidden in settings
Only the screens you need, for specific positions
Data
In the vendor's cloud or on your server with the on-premise version
On your servers or in a cloud in Russia, in a closed network if needed
Risk
Dependence on the vendor's plans and decisions
Dependence on the developer if the code and documentation aren't handed over

The last row matters for both sides. A custom CRM without the repository, database schema and deployment instructions in the client's hands is worse than a boxed product. That's why we hand all of this over on delivery.

How to calculate the money

Compare the cost of ownership over three years, not the starting price. For Bitrix24 it adds up like this:

  • licences or subscription × number of users × 36 months;
  • integrator work: setup, customisation, checks after updates;
  • staff time on workarounds: spreadsheets next to the CRM, manual stock reconciliation, moving requests from channel to channel.

The third item is usually forgotten, although it's the most expensive. An hour of a manager's or engineer's time in a large company costs 1,500 to 5,000 roubles, and ten hours of manual reconciliation a week per employee add up to half a million roubles a year.

For a custom CRM: development of the modules you need, hosting and support. There are no per-user licences, so the cost barely changes as headcount grows. In our experience, a custom system costs 2–3 times less than deep Bitrix customisation. If no customisation is needed, Bitrix24 is cheaper, and we'll say so.

A five-minute check

Answer "yes" or "no":

  • More than 50 employees use the system, and the number is growing.
  • Orders come from two or more channels and are reconciled by hand.
  • You have your own accounting: stock, regulatory deadlines, estimates, production.
  • Part of the work lives in Excel next to the CRM because the CRM is inconvenient.
  • Customisation by the integrator takes months or breaks after updates.
  • Data has to be kept inside your own network because of 152-FZ (the Russian personal data law) or your security team's requirements.

Zero or one "yes": stay with a ready-made CRM. Two or three: calculate the cost of ownership using the scheme above. Four or more: a custom system is almost certainly cheaper.

A middle option

You don't have to leave Bitrix24 entirely. Often tasks, chat and the calendar stay in it, while the accounting that doesn't fit is moved into a separate module: stock, production, requests with deadlines. The module exchanges data with Bitrix24 via the API, and staff keep working in the familiar interface where it's convenient.

You can also leave completely without stopping work. In the online store the new system grew alongside the old one and took over sections one at a time, and sales didn't stop for a single day.

Where to start

Describe your process on a half-hour call: which channels, what accounting, how many employees. We'll tell you honestly whether a ready-made CRM is enough. If not, we'll show a working prototype of the key screen in 5–9 days with no prepayment or contract, so you can compare it with what you have now.

FAQ

When is Bitrix24 a better deal than a custom CRM?

When the process is standard: a sales pipeline, tasks, deal reports, few users and no accounting of your own. Then the ready-made system launches in days and needs no development.

When is a custom CRM a better deal than Bitrix24?

When there are more than 50 users and the number is growing, orders come from several channels, you have your own accounting (stock, regulatory deadlines, estimates, production), part of the work lives in Excel next to the CRM, and customisation by the integrator takes months.

How much does a custom CRM cost compared with Bitrix24?

Compare the cost of ownership over three years. For Bitrix24 that is per-user licences, integrator work and staff time spent on workarounds. For a custom CRM: development, hosting and support. In Legenda Studio's experience, a custom system costs 2–3 times less than deep Bitrix customisation. If no customisation is needed, Bitrix24 is cheaper.

Can you move from Bitrix24 to a custom CRM without stopping work?

Yes. The new system grows alongside the old one and takes over sections one at a time. You don't have to leave completely either: keep tasks and communication in Bitrix24 and move accounting into a separate module that exchanges data via the API.

Examples of our systems