Custom CRM development built around your process
When you need your own CRM
Bitrix24 and amoCRM work well while the process is standard: a sales funnel, a few managers, standard reports. Trouble starts when the boxed product needs long rework and staff keep half of their work in spreadsheets next to it.
A system of your own pays off if you have:
- several order channels. The website, Telegram, phone and email should all land in one list with one status;
- your own accounting. Stock as a movement log, requests with deadlines set by your rules, estimates from your own price list;
- roles that match your staff. The storekeeper sees picking and stock, the manager works with orders, only the owner sees revenue and the log;
- links to other systems. 1C, payments, delivery, counterparty directories;
- many employees. Per-user licences in a boxed product cost more than building the modules you actually need.
If none of this applies, start with a ready-made CRM. We'll tell you so on the call. How to calculate the cost of ownership and check yourself in five minutes, we explained in the article "Bitrix24 or a custom CRM".
What the CRM includes
We build only the modules you need. We have already built each of them in live projects:
- Orders and deals. One list from all channels: statuses, items, payment, delivery. The server always recalculates the total; the system never accepts a price from the browser.
- Customers and history. A card with contacts and order history, company details checked by tax ID via DaData.
- Stock. The balance is the sum of log entries: receipt, sale, write-off, stocktake. Every figure can be explained.
- Requests and deadlines. Each request knows its deadline under your rules, and overdue items are flagged in advance.
- Promotions and content. The manager switches on promo codes with limits, banners and collections on the website, with no developer involved.
- Roles and log. Permissions for each position and an action log: who changed what, and when.
- Notifications. New orders and overdue items arrive in Telegram and by email.
CRM integration with 1C and other services
The CRM exchanges data with 1C via CommerceML, REST, webhooks or files, so the catalogue, stock, orders and counterparties never have to be re-entered by hand. Employees and the org chart are imported from 1C or Excel.
Integrations already running in our projects: YooKassa with receipts under 54-FZ, CDEK delivery pricing and pick-up points, a Telegram Mini App on the same data as the website, counterparty checks via DaData and Ofdata.
How we work
We build the prototype with no prepayment and no contract: you see how the system will work for you specifically, and only then decide. If you don't continue, you keep the prototype.
Risky changes go through a test server first. We replace the old system gradually, without stopping your work. After handover the code, the database and the deployment guide stay with you, and small fixes in the first month are free of charge.
CRM systems we have already built
FAQ
How much does CRM development cost?
The cost depends on the number of modules and integrations, so we estimate it after a 30-minute call. Before any contract we show a working prototype in 5–9 days with no prepayment, so you can judge the result on your own process. Payment is made in stages, against signed acceptance acts.
How long does development take?
The prototype is ready in 5–9 days. A pilot on your data goes live within a month. After that, new modules are added as separate releases while the system keeps running.
Which is better value: customising Bitrix24 or amoCRM, or building your own CRM?
If your process is standard and you have only a few sales managers, take an off-the-shelf system: it is faster. Your own CRM costs more at the start and pays off when the boxed product needs long rework for orders, stock or roles. In our experience, a custom system costs 2–3 times less than deep Bitrix customisation, and there are no per-employee licences.
Can you migrate data from our current system, spreadsheets or 1C?
Yes. We move customers, the catalogue and reference lists from an export of your current system, spreadsheets or 1C. In the online store project the new system grew next to the old one and took over sections one by one, and sales never stopped.
Who owns the code and the data?
After handover everything stays with the client: the repository, the database schema, the deployment guide and the environment variables. There is no dependence on our infrastructure.
Where is the data stored, and what about 152-FZ?
For projects with personal data (152-FZ, the Russian personal data law) we keep the infrastructure in Russia, and if needed we deploy the system inside the client's network with no internet access. Every action of every employee is written to a log: who changed what, and when.
Tell us where your orders, customers and stock live today. On the call we will show which modules you need and build a prototype on your process.