When a CRM comes up, the first question is almost always about money. A “from $X” answer explains little, so below we go through what the price of a custom CRM is made of, what levels a system can have, how to compare building one honestly with a subscription to a ready-made CRM, and what costs come after launch.
If you have not yet decided whether you need a CRM at all, and which kind, start with CRM for small business. This article is only about cost.
What the price of a CRM is made of
A developer does not estimate “a CRM” but a specific set of tasks. Six things affect the price the most.
- Roles and access rights. Manager, technician, cashier, owner. Each role sees its own data and its own buttons. Two roles and five roles with different rights differ several times over in effort.
- Workflow stages. How many steps a request or order goes through, whether there are branches, who moves it forward and when, what happens on cancellation.
- Integrations. Website, Telegram bot, WhatsApp, telephony, online payments, the 1C accounting system. Every link to an outside system is separate work, and often the least predictable. More in connecting a website and CRM to 1C.
- Reports. One revenue report for a period is simple. A dozen reports with filters, charts and Excel export are a noticeable part of the budget.
- Phone access. A convenient mobile version in the browser is almost always included. A separate app for field staff is priced separately.
- Data migration. Clients and history from spreadsheets or a previous system. Clean data moves quickly. Duplicates and phone numbers in different formats add work.
The most expensive part of a CRM is usually not the screens but the logic between them: rules, rights, integrations and reports. That is what deserves detailed discussion at the brief.
System levels and prices
To make it easier to navigate, let us split a CRM into three levels. These are NOVO starting prices; the exact figure comes after the brief.
Prototype — from $300
Clickable key screens without a real database. You and your staff click through them and check whether they are convenient. It is the cheapest way to find mistakes in the process before you pay for them in code. Why it is worth starting here: prototype first.
First version — from $1,200
A working system that solves one main problem. Usually that means:
- clients and their history;
- requests or orders with stages;
- requests coming in from one or two channels, for example the website and Telegram;
- notifications to clients and staff;
- two or three roles and one simple report.
Full system — from $3,000
A CRM the whole business runs on: stock or inventory, payments, several locations, integrations with 1C and online payments, a set of reports for the owner, sometimes a customer account or an app for staff.
Most companies are better off going step by step: a prototype first, then a first version, and the rest added once the system is running and it is clear what is missing.
Custom CRM or subscription: how to compare
A ready-made CRM looks cheaper because the first month costs little. A fair comparison covers two to three years.
Take a hypothetical example. A subscription costs $20 a month per employee, and 15 people use it:
- per month: 15 × $20 = $300;
- per year: $3,600;
- over three years: $10,800, plus paid add-ons and a growing team.
A custom CRM in this example is a one-off build followed by a server and support. The total does not grow because you hired five more people.
But a subscription has advantages money does not capture: it is live within days and does not require you to know your process in detail. So:
- a team of up to 5–7 people with standard sales — a ready-made CRM usually wins;
- a large team, your own process, integrations with 1C and the website — a custom system pays off in a year or two;
- a process that is still changing — start with a ready-made one and order your own once you know exactly what you need.
Costs after launch
The development price is not the last payment. Plan for:
- A server or hosting. For a small CRM usually from a few tens of dollars a month, depending on the number of users and the amount of data.
- Backups. Client data must not be lost; copies should be made automatically and stored separately.
- Support. Bug fixes, updates, help for staff. Most often a monthly fee or a bundle of hours.
- New features. New reports, fields, integrations. After six months of use there is always a wish list.
- Paid services. SMS, telephony, payment fees, if the CRM is connected to them.
What support usually includes and how to agree on it: support after launch.
How not to overpay
- Describe the process, not the features. Explain how work goes today and where requests get lost. The developer will suggest what to build and will not price what you do not need.
- Start with a first version. Add complex reports, stock and integrations once working without them becomes awkward.
- Pay in stages. Prototype, first version, new features — each stage with its own sign-off. More in paying in stages.
- Keep ownership on your side. The code, the database and the server must belong to you, or switching contractors will cost more than the CRM itself. More in who owns your website.
- Ask about post-launch costs before signing the contract, not after.
In short
- A CRM’s price is driven by roles, stages, integrations, reports and data migration, not by the number of screens.
- NOVO reference prices: a prototype from $300, a first version from $1,200, a full system from $3,000.
- Compare with a subscription over two to three years, not over the first month.
- After launch there are costs for the server, backups, support and new features.
- The cheapest path is to start with a first version and grow as needed. More on how we work on the CRM development page.