Complex Bitrix24 work that usually takes a team of integrators — in one pair of hands. Deep customization, integrations, REST. Directly with the engineer: estimated in hours, with a guaranteed delivery date.
No out-of-the-box setup — engineering only.
Custom field types, tabs and interfaces in entities, custom forms, extending the CRM card activity stream (without REST embedding), event handlers, access rights, customizing standard module logic — without breaking upgradability. I know the modules’ source code and limits, and re-check the system before starting.
Telephony (Asterisk/FreePBX), marketplaces, accounting systems (1C), banks and any REST/SOAP API. I own the Bitrix24 side: exchange, data handling, queues, idempotency, fault tolerance. Work inside the external system (e.g. 1C exchange) is handled by its own developer — I integrate over an agreed protocol.
Full-featured modules inside Bitrix24: Helpdesk (SLA, tickets, support tiers, ticket lifecycles), a unified inbox (calls, emails, open-line chats, queues) and other commercial solutions.
Complex, long-lifecycle business processes, custom BP activities, robots and triggers, approvals and document generation.
I set up an engineering process for the project: multiple environments (dev/stage/prod), CI/CD on GitLab, version control. Migrations transfer structure (fields, entities, settings) uniformly between environments — no manual repetition.
Bitrix24 Marketplace apps, REST apps and REST embeddings for cloud Bitrix24. Apps and webhooks are hosted only on the client’s side.
Real projects and products. Some details anonymized under NDA.
Many smart processes, custom forms to manage related items right inside entity tabs, custom entity selectors that depend on other field values, and document generation in DOCX/XLSX/PDF.
A telephony module and a Bitrix24 app: user synchronization, custom call-binding logic, a form builder for the call card, telephony event handling.
Calls, emails and open-line chats in a single interface, with employee queue setup and request distribution.
A ticketing system with SLA, support tiers and ticket lifecycles — a full service desk inside the portal.
For a site on 1C-Bitrix Site Management — a separate authorization tier and REST extensions for a client mobile app. Requests are served directly, bypassing the standard server stack: lower latency and load.
A desktop app on Oracle DB had no external API. I agreed DB changes with its developers, implemented exchange via triggers and stored procedures with buffer tables, and deployed a lightweight web service on the DB server for two-way exchange with Bitrix24.
Also: e-commerce-to-marketplace integration, CRM-to-ESIA integration with extra data processing, CRM card activity extension, CI/CD setup (GitLab) — and many more tasks.
Transparent: tasks against your spec, estimated in hours with a guaranteed delivery date.
Reviewing the task and requirements from your spec, clarifying constraints, proposing an architecture.
Effort estimated in hours and a guaranteed delivery date. No hidden terms.
Implementation, interim demos, revisions within the agreed scope.
Testing, production rollout, brief instructions and handover.
No spec yet? “Spec development” is a separate, hourly-billed stage: analysis, design and task definition. Development then runs against that spec.
Craftegra is an independent engineering practice focused on advanced Bitrix24 development: deep on-premise customization, integrations, custom modules and REST. I know the standard modules’ source code well — their capabilities and limits — and re-check the system before starting. You work directly with the engineer, with no agency markup and no meaning lost between managers.
Transparent ways to work together. Exact estimate after we discuss the task.
A client task with a ready spec. Effort estimate and a fixed delivery date.
When there is no spec: analysis, design and task definition as a separate stage.
Reinforcing the development side for integrators and product teams.
Work is estimated in hours and taken against your spec with a guaranteed delivery date. Support and formalities stay on the client side.
Discuss a projectHow the work is structured, in brief.
Custom field types, tabs and interfaces in entities, custom activities and business processes, customizing standard module logic, custom modules and integrations. I don’t take routine out-of-the-box CRM setup.
No. I own the Bitrix24 side: REST/exchange, data handling, integration logic and reliability. Work inside 1C is handled by your 1C developer — I integrate over an agreed exchange protocol.
No. I take development tasks with a clear result and delivery date, which keeps the focus on engineering.
Effort is estimated in hours with a guaranteed delivery date against your spec. No fixed “per-project” price and no hidden terms.
Ideally yes — a task against your spec. If there is none, spec development is a separate hourly-billed stage, after which development begins.
Yes. A dedicated full-time engineer format is available — for integrators and product teams.
Yes. I reinforce integrators’ teams on the development side where an engineer for advanced Bitrix24 work is needed.
Both: cloud Bitrix24 via REST and on-premise versions with source-code and module customization.
Describe your task — a reply with options usually within a day.