Area 12 · Development and websites

Bitrix24 and portals

A paid licence on its own changes nothing. The system comes alive at the moment working in it becomes easier than in a chat and a spreadsheet. We fit it to how you actually work and take it to the point where staff open it daily rather than remembering it once a quarter.

3
services in this area
2-6 weeks
the usual time to go live
Partner
partner pricing on licences
Training
comes with the setup

Hosted or on-premise

The decision is made at the start. Moving later is possible but costs time and money, so it is wiser to decide straight away.

For most companies

Option 1

Hosted

Everything runs on the vendor's infrastructure: you pay a subscription and worry about nothing.

Start
Works the day you pay
Payments
A monthly or annual subscription
Where the data lives
With the vendor
Customisation
Only through apps
Updates
They arrive automatically

Option 2

On-premise

The installation runs on your own hardware: more capability, but more to look after.

Start
A server and an installation are required
Payments
A one-off purchase plus renewals
Where the data lives
In your server room
Customisation
Almost no limits
Updates
Whenever you decide

Result

What to choose

You can move later, but it costs time and money, so it is better decided at the start.

The hosted option fits
For most companies with no special requirements
The on-premise edition is needed
When there are data residency requirements
And the on-premise edition too
When serious customisation is needed

What kills a rollout is not the software but the absence of agreed rules. Until the salesperson is told plainly that notes in a notebook no longer count, they will keep writing in the notebook. That is why the project always includes an agreement: at what point an enquiry becomes a deal, who creates the customer record and what moves it to the next stage.

How the rollout goes

We go live in parts rather than all at once: first the customer work, then tasks, then the rest. People need time to get used to it.

01

We map the processes

We trace the customer's path from first contact to payment and find where they drop out. The stages are built from how things actually are, not from a textbook diagram.

02

We build the pipeline

Stages, the field set, access control, connecting mail, telephony and website enquiries. Requests no longer settle in managers' personal inboxes.

03

We migrate the data and train

We import the customer records and run training by role: a manager and a salesperson need different things.

04

We stay close for the first weeks

The key stage: we adjust the settings from the staff's feedback before the new habits have set.

Questions and answers

This is the most common complaint. The root cause is almost always the same: the system was rolled out from a template without being fitted to how you work, and no rules were agreed. We start with a conversation: what irritates the salesperson, which fields are redundant, where the same thing is typed twice. After reworking the settings and training the staff the portal comes alive without further investment.

Yes, data flows both ways: invoices and payments show up on the customer record, and new counterparties reach the accounting system. The effort depends on the platform version and how heavily the configuration has been customised.

Pricing follows the number of staff with access rather than the number of departments. It often turns out that half the workforce only needs to see tasks, and the final figure comes out lower than expected.

The information stays where it is, but new versions and vendor support become unavailable and some features switch off. We warn you well before the date so it does not fall in your busiest season.

We will work out how things are set up at your end

Опишите, каким образом сегодня ведётся работа с покупателями и что при этом ускользает. Предложим схему настройки и рассчитаем стоимость лицензий по партнёрским условиям.