When off-the-shelf CRMs can't keep up: when a business needs its own CRM

Off-the-shelf CRMs such as amoCRM and Bitrix24 are good products. For most companies they cover the core of the task, and they do it quickly and at a reasonable price. This isn't an article about them being bad.

This is an article about what happens with the rest: when business processes are so specific that the company starts adapting itself to the system instead of the system working for the company. And about how to tell when that moment has arrived.

Why companies switch CRMs

Companies that deploy a CRM often end up choosing a system again a couple of years later. The reason is almost always the same: the system doesn't match the real processes of the business.

This doesn't mean the "wrong" CRM was chosen. Often it means the business grew or changed, and what fit at the start no longer fits now. Or the company's processes were specific enough from the outset that an off-the-shelf solution couldn't cover them. While the team is small, the gaps are tolerated. When dozens of people work in the CRM, every small inconvenience is multiplied by the number of employees and working days.

Signals that an off-the-shelf CRM has run its course

You work "around" the system

Managers keep parallel Excel spreadsheets because the CRM won't let them record the information they need. Part of the conversation with customers lives in WhatsApp on personal phones because it's inconvenient in the system. Reports get exported to Excel and finished by hand because the built-in analytics don't give the cut they need. If this sounds familiar, the system isn't working for you.

The cost of customizations rivals the cost of a new system

Off-the-shelf CRMs can be customized: through APIs, marketplace apps, integrations. But every customization costs money and time. When the total cost of customizing an off-the-shelf system approaches the cost of building your own, the economics shift in favor of a custom solution. And even then, a customized box still remains constrained by someone else's product architecture.

License costs grow along with the team

amoCRM charges per user. Bitrix24 prices its plans per company with a user limit: when the team outgrows the limit, you move to a higher plan. While there are only a few managers, this goes unnoticed. As the headcount grows, the subscription becomes a visible line in the budget, and over a few years it adds up to an amount comparable to building a system, for the right to use one that still doesn't cover all your needs. A custom CRM is paid for once under a contract and belongs to you; after that only hosting and support remain.

Data is stored on someone else's servers

For companies with sensitive data, such as healthcare, finance, legal services or government contracts, storing the customer base in a third-party cloud creates legal and reputational risks. In Kazakhstan there is also the personal data law: Law of the Republic of Kazakhstan No. 94-V requires personal data to be stored in a database located in Kazakhstan. What this means for forms and databases is covered in our personal data guide. A custom CRM is deployed on your own server or with a hosting provider in Kazakhstan, so the data stays with you. Some off-the-shelf CRMs also offer a self-hosted version: if storage location is the only issue, check that with the vendor first.

Unique processes that off-the-shelf solutions don't have

A project business with a complex subcontracting structure. Production tied to technical specifications. Multi-level approvals with a complex role model. Non-standard funnels that branch across dozens of parameters. Requests, warehouse and delivery that need to be seen in one window. When your processes are fundamentally different from what an off-the-shelf system was designed for, no amount of customization will make it fit.

See also: CRM implementation and custom CRM development

When an off-the-shelf CRM is the right choice

This is important to say honestly, because a custom CRM isn't for everyone.

If your sales fit a standard funnel ("lead → qualification → negotiation → close"), the sales team is small and you have no specific data requirements, an off-the-shelf CRM will cover the task for less money and faster. Customizing a ready-made solution for minor nuances is usually cheaper than building your own. Bitrix24 is convenient when you need sales, tasks and a website in one system; amoCRM suits a sales team that lives in messengers. A detailed comparison is in amoCRM, Bitrix24 or a custom CRM, and how we set up a ready system is on our Bitrix24 page.

The line is where the cost of licenses and customization of an off-the-shelf system over a three-year horizon exceeds the cost of custom development. Or where the box's architectural limits fundamentally prevent implementing the functionality you need.

What a custom CRM delivers

A system built around your processes, not the other way around

A custom CRM is designed around how your business actually works, accounting for the specifics of the industry, the product, and the team structure. No compromises between how a process should work and what the system allows. Each role has its own screens: managers see deals, the executive sees the funnel and the money, the warehouse sees orders to ship.

Full control over your data

The entire customer base, interaction history, and analytics live on your infrastructure. No dependence on a third-party service's terms, availability, or data policies. The requirements of the personal data law are built into the architecture rather than patched on later.

No per-seat fees

Development is paid for once. Ongoing costs are limited to hosting, support and further development. For a growing team over a horizon of several years, a custom system often turns out cheaper in total cost of ownership. Run the numbers on your own figures, not on someone else's example.

Integration without limits

A custom CRM integrates with any system: 1C, the warehouse, Kaspi, the ESF e-invoicing system, telephony, WhatsApp, industry services, without the limits imposed by a boxed solution's architecture. The API is designed around your needs, not around the capabilities of a ready-made product. How a link with accounting works is shown on our 1C integration page.

A competitive advantage

A unique customer-management system is part of your operational advantage. A competitor can buy the same CRM you have. They can't copy your custom system, tailored to your processes.

How to make the decision

A simple checklist to assess:

• Your staff spend a noticeable share of working time operating "around" the CRM or in parallel spreadsheets
• The annual subscription has become a visible budget line and grows with headcount
• Customizing the off-the-shelf system over the past couple of years cost about as much as the system itself
• There are processes that fundamentally can't be implemented in the current system
• Customer personal data is stored outside Kazakhstan, although the law requires otherwise

If three or more of these apply, the economics of custom development most likely add up. The precise answer comes from calculating the total cost of ownership of the current solution over three to five years compared with the cost of building and supporting your own system. The calculation includes the subscription, customizations, integrations, staff time spent on workarounds, and risks.

How the switch from an off-the-shelf CRM goes

The switch doesn't have to be abrupt. A working order looks like this:

1. Process review. We walk the path of a deal from the first WhatsApp message or website request to payment and documents in 1C, and fix the roles, stages, fields and reports the executive needs.
2. Screen prototype. Before development we show how the deal card, the funnel and the reports will look for each role. Changes at this stage are the cheapest.
3. First version. We build the core: customers, deals, tasks, reports and one main link, for example with WhatsApp or 1C.
4. Parallel run. For a while the team works in the new system while the old one stays available for reference, so migration errors show up before it is switched off.
5. Migration and switch-off. We move the history, check that nothing was lost, and only then drop the old CRM.
6. Further development. The next modules are added in turn: warehouse, Kaspi, ESF invoices, telephony, a customer portal.

The main rule: the subscription to the old system is cancelled last, not first.

Cost and how the work goes

A custom CRM from us starts from 800 000 ₸ for the first version. The price and scope are fixed in the contract after we review your sales process. We work in iterations: the first working version appears within a few weeks, then modules are added one at a time, and each stage is estimated before it starts. Migrating customers, deals and history from amoCRM, Bitrix24 or Excel is part of the project and estimated separately. The work carries a six-month warranty, and we hand over the source code and access, so the system can be developed further with any team.