Your own CRM or amoCRM and Bitrix24
An off-the-shelf CRM pays off while your process matches its template, and we will say so plainly. A custom system pays off once the specifics start: pipeline stages the box does not have, KPI and payroll calculation, customer payments and debts, branches with different permissions, accounting sync. At that point integrators patch the box, licences grow with every hire and the company still bends to the software. Do the maths over several years: per-seat licences, customisation and vendor lock-in against a one-off build of a system you own. If you run amoCRM or Bitrix24 today, you can also keep it and connect it to your accounting.
What drives the price
Start is customers, deals, tasks, two roles and Telegram alerts: enough for a sales team leaving spreadsheets. Business adds branches and permissions, telephony with recording, messenger conversations on the deal, reports on pipeline, reps and sources, and 1C sync. Enterprise is built for hundreds of users: redundancy, a staff mobile app, an owner’s BI dashboard and AI that scores calls and coaches reps. KPI and payroll, contract templates, payments and debts, online booking and an AI sales agent for Instagram are add-ons. Data migration is its own line in the configurator, because its cost depends on how many years of history and files you bring.
How the work runs
The first weeks go to process mapping: how a deal moves today, where customers drop off and what the head of sales wants in a report. We agree stages, roles and fields using your real deals. Then we build in modules, starting with the most painful area, usually pipeline and tasks, then channels and reports. Every two weeks you get a working version and the sales team tries it on real data. Before go-live we run a trial migration so you see your own data early, then train staff and support the first weeks. The timeline from 6 weeks is in the contract; every day of delay cuts the invoice by 2%, up to 10% of the contract in total.
Local rails and typical risks
A CRM for Uzbekistan needs what foreign templates lack: SMS through Eskiz for reminders and codes, invoice exchange with 1C and Didox, Telegram alerts and a bot where customers check their request status, Uzbek and Russian interfaces. Elsewhere the same logic applies to your own SMS gateway and accounting system. The risks are universal. A CRM assembled in a hurry, without server-side permission checks, hands the customer base to anyone who guesses a request URL, and without a queue and retries it drops website leads whenever something fails. We enforce permissions on every action and check for duplicates. Bugs are fixed free with no time limit, and your engineer may audit the code: any unfulfilled item means a 10% refund.