How to Use This Reference
Use these hour ranges as planning brackets: multiply by your agreed rate to get a cost floor and ceiling before your first scoping call.
Every project starts with unknowns. The figures in this article come from actual service plans and contracts across a wide range of industries — logistics, legal services, recruitment, automotive, events, and more. They reflect the labour booked and delivered, not theoretical estimates from a sales brochure.
A few ground rules before reading the tables:
- Ranges, not quotes. A single-funnel CRM setup for a 10-person team is at the low end; a multi-branch deployment with custom Smart Processes and ERP integration is at the high end.
- Hours are additive. You pick the modules you need and sum the ranges. Discovery and training are always present regardless of scope.
- Scope locks hours. The single biggest driver of overruns is an incomplete technical specification at the start. Projects with a signed, detailed spec consistently land closer to the low end of each range.
For a broader view of cost and calendar timelines, see our Bitrix24 implementation cost and timeline reference.
Stage 1 — Discovery & Technical Specification
Discovery typically takes 5–10 hours of billable consultant time and produces the technical specification document that controls the entire project budget.
This stage is non-negotiable. Without it, every downstream estimate is a guess. Based on our project archive, the work breaks down as follows:
| Activity | Typical Hours |
|---|---|
| Stakeholder interviews (online sessions) | 4–5 h |
| Review of existing documentation & current processes | 2–3 h |
| Writing the technical specification (TZ) | 3–5 h |
| Stage total | 5–10 h |
The output is a document that maps Bitrix24 entities (leads, deals, contacts, companies, Smart Processes) to each business process, lists mandatory fields and pipeline stages, and provides the effort estimate for all subsequent stages. Final hours for stages 2 and 3 are confirmed only after this document is approved.
A thorough onboarding questionnaire completed by the client before discovery sessions cuts interview time by 30–40%.
Stage 2 — Core CRM Setup
Basic CRM configuration — portal install, user structure, contact/company cards, and a lead funnel — runs 25–45 hours; adding multiple deal pipelines and complex role-based access pushes this to 55–75 hours.
This is the largest variable block in any project. The table below reflects granular task-level data from multiple work plans.
| Task | Typical Hours |
|---|---|
| Portal installation & base settings | 6–8 h |
| Organisational structure & user onboarding (phase 1+2) | 2–4 h |
| Contact & company card configuration | 4–6 h |
| Lead funnel setup | 5–7 h |
| Deal pipeline setup (per pipeline) | 4–6 h |
| Role-based access model (per role tier) | 2–4 h |
| Smart Process setup — simple (1 process) | 4–6 h |
| Smart Process setup — complex (e.g. 7 HR processes) | 18–24 h |
| Custom field reconfiguration & mandatory-field logic | 1–3 h |
| Deal-closing automation (e.g. block close without sub-items) | 1–2 h |
| Cross-entity data copy automation | 1–2 h |
| Currency recalculation across linked entities (custom dev) | 10–14 h |
Key insight from the archive: a multi-branch company (5 regional offices, 12+ configured roles) required approximately 22 hours for the access model alone. Single-location SMBs with 3–4 roles typically need 4–6 hours.
Stage 3 — Automation & Business Processes
Automation setup ranges from 5 hours for simple trigger-based rules to 30+ hours for multi-stage business process workflows with document generation.
Automation work falls into three tiers:
- Native robot/trigger rules — status-change notifications, field updates, task creation on stage move. These are low-effort (1–3 h per pipeline) and should be included in the CRM setup estimate above.
- Business Process (BP) automation — copying deal data to sub-entities, enforcing approval chains, conditional branching. Budget 4–8 h per complex BP.
- Custom Smart Process with document output — for example, a "Meetings" Smart Process that auto-generates a PDF summary from a template. Based on a real project, this cost approximately 8 hours.
If you are evaluating AI-assisted automation such as call transcription and automatic deal-card population, see our guide on AI call analysis in Bitrix24.
Stage 4 — Integrations
A single standard integration (telephony, payment gateway, or website form) takes 8–12 hours; bidirectional ERP/accounting integration (e.g. with 1C or a comparable system) adds 15–30 hours on top.
The diagram below shows how data flows between external systems and Bitrix24 in a typical multi-integration project.
The following describes the architecture: the website and telephony system each push events into Bitrix24. Bitrix24 syncs bidirectionally with the ERP/accounting system. Bitrix24 also pushes outbound data to a payment gateway and, where required, to a partner CRM via REST API webhooks.
flowchart LR
SITE[Website / Forms] --> B24[Bitrix24]
PHONE[Telephony] --> B24
B24 <--> ERP[ERP / Accounting\ne.g. 1C]
B24 --> PAY[Payment Gateway]
B24 --> PARTNER[Partner CRM\nvia REST API]
| Integration Type | Typical Hours |
|---|---|
| Telephony (connect + basic config) | 8–12 h |
| Website lead forms → CRM | 3–6 h |
| Payment gateway (one account) | 6–10 h |
| Partner CRM via REST API webhooks (one-way) | 8–12 h |
| ERP / accounting system (bidirectional, scoped) | 15–30 h |
Note: hours on the ERP side are the Bitrix24 partner's effort only. Configuration on the ERP side is billed separately by the ERP team.
Stage 5 — Reporting & Analytics
Standard CRM reports take 6–18 hours; custom BI dashboards built in the Bitrix24 BI Builder pulling from multiple data tables range from 40 to 50 hours per dashboard set.
Reporting is the most underestimated module in budgets. Clients often discover mid-project that the data they want to visualise is spread across deals, activities, tasks, and comments — tables that require joins not available in native CRM reports.
| Report Type | Typical Hours |
|---|---|
| Standard CRM funnel & manager performance reports | 6–18 h |
| Sales department efficiency dashboard (data already in CRM) | 6–10 h |
| Sales department efficiency dashboard (requires ad-source integration) | 10–15 h |
| Custom BI dashboard (multi-table, complex joins) | 40–50 h per set |
| Weekly summary / consolidated pivot reports | 8–14 h |
The key question at discovery: does the data you need already exist in Bitrix24? If advertising traffic, source attribution, or financial actuals are not currently logged in the system, integration work must be budgeted before any report development begins.
Stage 6 — Data Migration
Migrating contacts, companies, and deal history from a previous CRM typically adds 10–30 hours, depending on data volume, source system, and field mapping complexity.
Migration effort is driven by three factors:
- Source system — structured exports (CSV, API) are faster than screen-scraping or legacy database extracts.
- Field mapping — custom fields on both sides require a mapping document; budget 2–4 h for this alone.
- Data hygiene — deduplication and normalisation before import can easily double the migration hours.
For platform-specific migration playbooks, see: - How to migrate from HubSpot to Bitrix24 - Pipedrive to Bitrix24 migration guide
Stage 7 — User Training
End-user training is consistently scoped at 2–6 hours per session in our project work plans, with the total block ranging from 4 to 12 hours depending on role count and module complexity.
Training is delivered as recorded online sessions with screen capture, so the videos remain available for onboarding future staff. Standard training covers:
- CRM module: activities (calls, meetings, tasks), deal card navigation, kanban / list / calendar views
- Filters, standard reports, deal-manager breakdown views
- Tasks & Projects: creating tasks from CRM, grouping into projects, task reports
- Communication channels: email, telephony, open lines
- File storage: shared drive for client-facing materials
| Training Block | Typical Hours |
|---|---|
| Basic CRM user training (1 session) | 2–4 h |
| Extended training incl. Tasks & Projects module | 4–6 h |
| Manager / analytics training (reports, BI dashboards) | 2–4 h |
| Total training block | 4–12 h |
Summary: Typical Hour Ranges by Scope Size
A small single-pipeline rollout lands at 30–50 total hours; a mid-market deployment with integrations, custom automations, and BI reporting typically runs 100–180 hours.
Use the table below as a first-pass budget model. Multiply hours by the partner's hourly rate to get a cost range. Rates vary significantly by region.
| Scope | Modules Included | Estimated Total Hours |
|---|---|---|
| Starter | Discovery + basic CRM (1 pipeline) + training | 30–50 h |
| Standard | Discovery + CRM (2–3 pipelines) + automations + telephony + training | 55–90 h |
| Advanced | Above + ERP integration + custom Smart Processes + reporting | 100–150 h |
| Enterprise | Above + multi-branch access model + BI dashboards + migration | 150–200+ h |
These ranges assume no custom software development. Any work that goes beyond Bitrix24's configuration interface (custom REST applications, external database connections, bespoke modules) is scoped and priced separately.
For a full breakdown of how these hours translate to project timelines and total cost, see our Bitrix24 implementation cost and timeline data reference.