How the pricing model works
Bitrix24 charges per portal, not per user, up to a user limit that is set by the plan. That single fact explains most pricing confusion. A plan covering fifty users costs the same whether you have twelve or fifty, so the question is never 'how much per person' — it is 'which ceiling do we sit under, and which features do we need on the way'.
The practical consequence is that the cost curve is a staircase, not a slope. Adding one more person is free until it is expensive, and the jump happens at the ceiling. If you are within a few users of a limit, model the next tier before you commit to an annual term.
Which plan fits which situation
- Free — genuinely usable for a small team testing CRM discipline, with real limits on storage, automation and reporting. See our guide to the free plan's limits before you build a process on it.
- Basic — a small sales team that needs a working pipeline, CRM forms and basic telephony, without deep automation.
- Standard — the common starting point for growing teams: more users, marketing features and stronger CRM automation.
- Professional — where sales automation, workflow design and reporting get serious. Most of our implementation clients land here or above.
- Enterprise — multi-department or multi-branch organisations needing scale, advanced permissions and heavier automation.
- On-premise (self-hosted) — a separate licence model entirely. Worth it only where data residency rules or deep server-side customization genuinely require it.
Annual versus monthly, and why most teams should wait
Annual billing is meaningfully cheaper per month than monthly, and Bitrix24 discounts longer terms further. The temptation is to take the longest term on day one. Resist it until the implementation is live and the team is actually using the portal, because the tier you need after go-live is frequently not the tier you expected before it.
Once usage is stable, the annual or multi-year term is usually the right call — and the renewal date becomes the moment to re-check the fit rather than a formality.
The costs that are not the licence
- Implementation — pipeline and field design, automation, permissions, migration, training. Typically the largest first-year line item, and the one that determines whether the licence gets used at all.
- Integrations — WhatsApp Business API, telephony, portals and ERP connections, each with their own provider costs on top of development.
- WhatsApp Business API messaging fees, billed by your provider per conversation, not by Bitrix24.
- Telephony minutes or your existing PBX, depending on how calls are routed.
- Data migration from spreadsheets or a legacy CRM, where de-duplication is the real work.
- Ongoing support or an internal admin — someone has to own changes after go-live.
Where teams overspend and underspend
Overspending almost always takes one of two forms: a tier bought for a single feature nobody ends up using, or a user count inflated by people who have left or never logged in. Both are invisible on an auto-renew and both are straightforward to fix at the renewal date.
Underspending is less obvious and often more costly. Teams on a plan that is too small build workarounds — a spreadsheet beside the CRM, a report exported and reformatted by hand every week, an automation that cannot be built so someone does it manually. That time is real money in a budget line nobody counts against the licence.