Алматы

Bitrix24 customisation for your business

Before customising, it is worth checking whether the task is solvable with standard features — in half the enquiries it is. The other half needs code, and that is normal: every business has its specifics.

Timelinefrom 2 weeks
Formatapplication or code
Estimateby scope of work

We scope the estimate before the work starts; timelines and warranty go in the contract.

What the work includes

Standard features first

We check whether development is needed at all.

Custom calculations

Logic that cannot be assembled from robots and fields.

Integrations

Exchange with external systems through the API.

Your own interface

A role-specific screen where the standard one is awkward.

Survives updates

Written through official mechanisms, never by editing the core.

Sources to the client

The project can be handed to any team.

When customisation is not needed

When the task sounds like «we need a field» or «we need a notification» — that is configuration, not development, and it costs a fraction.

When a report is needed that the standard builder can assemble. Writing code for that means paying twice: for the development and then for maintaining it.

We say this plainly, even though customisation is more profitable for us than configuration. Paying for code where a checkbox suffices is a bad deal for both sides.

When customisation is needed

When there is custom calculation logic: complex pricing, conditional checks, working with external data at the moment of the deal.

When a role-specific interface is required — an operator workplace, a configurator, a calculator for managers.

And when the portal must exchange with a system that has no ready connector. In all cases we write through the REST API and applications — editing the core makes the portal impossible to update.

How we run it

  1. Task review. Checking whether standard features solve it.
  2. Specification. Behaviour in words, before code.
  3. Estimate. Price and timeline by stage.
  4. Development. On a test portal.
  5. Rollout. Installation, training, documentation.

Frequently asked

How much does customisation cost?

By scope: we split it into stages so you can proceed gradually and stop at any point.

Will a portal update break it?

Not if the customisation goes through the API and applications. That is exactly why we never edit the core.

Can you take over someone else's work?

Yes. First we look at what exists and in what state the code is — that needs a short audit.

Does it work with the on-premise version?

Yes, with both cloud and on-premise. On-premise allows more, and demands more care.

Do we get the sources?

Yes, with documentation. There is no lock-in to us.

Смета за 24 ч — бесплатно
Распознавание документов (OCR) для банков и бизнеса в Казахстане →