The difference in plain terms
CRM is a system about selling. Who the customer is, what stage the deal is at, who owns it, what was promised, when to call back. Its job is to make sure no enquiry is lost and to make visible who is actually working and who is performing the appearance of work. Scope and price of a custom system are on the CRM development page.
ERP is a system about operations. How much stock is in which warehouse, what has been purchased, what is in production, what it costs, whether the books balance. Its job is to make every department work from the same numbers. More on the ERP development page.
Signs you need a CRM
- Enquiries arrive in messengers and inboxes, some get lost, and nobody can say how many.
- When a salesperson leaves, the negotiation history and half the customers leave with them.
- It is unclear which channel brings in money, as opposed to which brings in enquiries.
- Repeat sales are accidental: there is nobody to remember a customer at the right moment.
Signs you need an ERP
- Stock in the spreadsheet does not match reality, and you find out at dispatch.
- Cost of goods is calculated by hand and every department arrives at a different number.
- Purchasing is done by feel, and money is frozen in stock that will not sell.
- A management report takes two days to assemble and is out of date by the time it is ready.
Off the shelf or custom
If your processes are standard, buy an off-the-shelf solution. We tell clients this plainly, even though the opposite pays us better. Custom development pays off in three cases: you have a non-standard process no product covers; customising an off-the-shelf product already costs more than building; or you have hit licence costs that grow with headcount.
Do the maths over three years: licences for the whole team, the cost of customisation to your rules, vendor dependency, and the cost of leaving if they raise prices.
How to roll it out without rejection
The main risk in a rollout is human, not technical: people carry on keeping records in a notebook because “the system is awkward”. So we deploy department by department rather than company-wide, and we start with the most painful area — that is where the benefit shows fastest and where allies appear.
- 01
Describe how the work runs today
And separate what is worth automating from what is simpler to eliminate. Automated chaos is still chaos — only now you cannot route around it.
- 02
Ship the first working module
A few weeks after the start, not six months in. People need to see the benefit before they get tired of the change.
- 03
Migrate the data with verification
Before the switch we run a trial migration so you can see your own numbers in the new system in advance. How that works technically is in the walkthrough on zero-downtime migration.
- 04
Train and stay close
Train the people who will use it every day, not just the manager. And stay available through the first weeks after launch.
Frequently asked questions
Can we get by with a single system?
Yes, and for most companies that is the right path. Modern systems are built on one platform: sales, stock and reporting live in a shared database, and the CRM/ERP split becomes nominal. What matters is not the number of systems but that data is not being re-keyed by hand. If your books already live in 1C, it is connected to the new system — see 1C integration.
What does a custom CRM or ERP cost?
A CRM built around your processes starts at $6,000 and about 6 weeks: customers, deals, tasks, two roles, Telegram notifications. With branches, telephony, messengers, reports and 1C it costs $20,000–45,000 and about 14 weeks; enterprise for 100+ users with an app, BI and AI costs $60,000–150,000. The same product costs $6,000 or $150,000 — functions set the price, and the configurator on this site shows the exact range for your set. ERP starts with one area — stock, finance or HR — from $20,000 and about 12 weeks; a full ERP costs $60,000–110,000. You get the first working module within a few weeks of the start — we roll out in parts rather than in one big launch. Ranges for every product are on the pricing page.
What happens to the data in our old system?
We export it, clean up duplicates, map the reference data and migrate with checksum verification. Before the switch we always run a trial migration: you look at your data in the new system before the old one is turned off.
How long will staff take to adapt?
With a sensible interface and training, one to two weeks per department. We design the interface for the people who work in it daily rather than for a demo to the boss, and we stay close through the first weeks after launch.
These articles are written by engineers working on the projects and published under the desk’s name. The studio and the desk’s published rules stand behind every text, not a single author; articles about our own open-source code carry the author’s name.
How we write and what we verify