One Person Playing Integrator, Project Manager, and Licensing Manager on Bitrix24 Projects: How It Actually Works
A personal take on why combining three roles into one person isn't a compromise for an SMB client without an in-house IT team — and what rules keep the model stable.

On paper, implementing Bitrix24 is the work of three different specialists: a technical integrator, a project manager, and a licensing manager. In practice, when working with small and mid-sized businesses that don't have their own IT department, one person often covers all three roles. I'm one of the people who works this way, and this article isn't theory — it's how it actually works from the inside.
Why this isn't a compromise for SMB
A large business has the budget and headcount to keep a dedicated project manager, a dedicated technical specialist, and a separate person tracking tariffs and licenses. The owner of a small online store or service company usually doesn't have that budget — and, more importantly, doesn't need it. What they need is one person they can call, explain a problem to in plain language, and get a result from, rather than figuring out which of three contractors to email about which issue.
When all three roles sit with one person, there's no communication gap between them. There's no need to relay a technical constraint to a project manager who then passes it on to the client in a distorted form. There's no need to wait for a licensing manager to check a tariff against an integrator who's the one actually configuring integrations for that tariff. The decision gets made immediately, because the entire context lives in one head.
Where combining roles genuinely saves the client money
The most common mistake for a small business without its own IT is buying a tariff "to grow into," simply because nobody explained what's actually needed right now. When the same person who later configures the system also handles the licensing questions, they see the whole picture: how many users will really work in the CRM, which integrations are planned, whether a BI builder will be needed in the next six months or if that's next year's problem.
The same goes for integrations. A conversation about connecting 1C or telephony is simultaneously a technical and a budget topic: in complex cases, integrating with 1C can require a separate subscription or custom development, and the client needs to know that at the planning stage — not after the money for the basic tariff has already been spent.
Where this model has limits
To be honest: combining roles doesn't work at every scale. On a project with fifty-plus users, multiple legal entities, and a complex integration architecture, one person physically can't be the technical core, the project management, and the licensing support all at once — that's a case where the roles genuinely need to be split, or quality starts slipping somewhere.
For that scale, the honest position is to tell the client directly: "One specialist won't be enough at this size — you need a team, or an expanded contractor." Trying to single-handedly carry an Enterprise-level rollout with simultaneous 1C, ERP, and BI integration is a guaranteed way for all three roles to start suffering at once.
What this means for a client choosing a contractor
If a business has no in-house IT and the project involves a few dozen users, standard integrations, and understandable business processes, it's worth looking not at the size of the contractor's company but at whether one person can clearly answer three questions at once: how this will work technically, when it will be ready, and what it will cost both now and over time. If the answer to any of the three requires "let me check with a colleague" — that's not always a bad sign, but it does mean a delay and a risk of losing context has entered the chain somewhere.
Bottom line
Combining the integrator, project manager, and licensing manager roles into one person isn't a way to cut corners on specialists — it's a working model suited to a specific class of projects: small and mid-sized businesses without their own IT, where the value of fast decisions and context continuity outweighs the value of a scalable team. Once a project outgrows that scale, it's more honest to recognize the limit and offer the client an expanded team, rather than carrying all three roles alone until something starts to break.
Related reading
23Bitrix24 Integration in 2026: Where the Platform Is Heading and What Business Should Watch For
MCP connections to external AI, deeper 1C sync, a BI builder, and a growing integrations marketplace — a look at what's changing in the Bitrix24 ecosystem and how to use it without data chaos.
Tell us about your task — we'll propose a solution
Free consultation: we'll analyze processes, select a license and estimate implementation for your business.
