Custom fields and card layout
Industry-specific fields, dependent lists and role-based screen layouts. No code needed.
Services
Where the standard setup is not enough
Bitrix24's standard structure is enough for most companies. Where it is not, we look at configuration before code; unnecessary development becomes a maintenance burden later.
At a glance
- Custom fields and card layout
- Smart Process Automation (SPA)
- Workflow design
- REST API apps
- Custom reports
When is customisation actually needed?
Most incoming requests are not really customisation but a need for correct configuration. Cases that genuinely need customisation look like this:
- Your work does not fit the standard CRM record types (lead, deal, contact, company)
- You have calculation or pricing logic specific to your industry
- You need two-way, real-time data exchange with your own system
- The standard screen layout slows the team down
- There is a step in your process with no equivalent in Bitrix24
What we build
From light to heavy; we decide together where to stop.
Smart Process Automation (SPA)
Your own record types: service tickets, contracts, applications, projects ; with their own stages and automations.
Workflow design
Multi-step approvals, conditional branching and RPA for work that falls through the cracks.
REST API apps
Custom interfaces, calculators and services running inside the portal that talk to outside systems.
Custom reports
Dashboards built on BI Builder for measurements the standard reports do not cover.
Market app
Packaging a repeatable need as an app on Bitrix24.Market.
Configuration first, code second
A good share of customisation requests can be met with Bitrix24's existing tools. Custom fields, smart processes, automation rules and the workflow designer together get you a long way without code.
So every request goes through a "can configuration solve this?" filter first. If it can, we do not write code; because every line written means maintenance, testing and update work later.
- Custom field and dependent list structures
- New record types through SPA without code
- Automation rules and the workflow designer
- Evaluating ready-made Market apps
Smart Process Automation: your own record type
Bitrix24's standard CRM objects do not fit every business. A service company needs a "fault ticket", a school needs an "application", a developer needs an "apartment".
SPA lets you create those record types with their own fields, stages, Kanban view and automation rules. They can be linked to standard CRM records and use the same reporting layer.
- Record types with their own fields and stages
- Kanban, list and calendar views
- Links to CRM records
- Their own automation rules and workflows
When code is needed: the REST API
For work that genuinely requires development we use Bitrix24's REST API. That approach has an important advantage: because the code does not live inside the portal it is not affected by Bitrix24 updates.
Apps are authorised with OAuth 2.0, reach only the scopes they need, and event payloads are checked with signature validation.
- OAuth 2.0 or webhook-based authorisation
- Scopes defined on a least-privilege basis
- Rate limiting and retry logic
- Verified on a test portal before going live
We talk about maintenance cost up front
Every piece of development is a liability as much as an asset. The code has to be tested, kept compatible with Bitrix24 updates and changed as requirements move.
So the quote shows not only the build cost but the maintenance expectation afterwards, in writing. Sometimes that conversation ends with deciding not to build at all and living with configuration instead.
- Build and maintenance costs shown separately
- Responsibility for compatibility with Bitrix24 updates
- Source code and documentation handed over to you
How would this work in your process?
In a free 30-minute call we listen to your workflow and map out how this would run in your company.
How customisation runs
At every step we ask again whether it is really needed.
- 01
Needs analysis
We work out the real job behind the request; the answer is often something else.
- 02
Solution options
Configuration, SPA, a Market app or development ; presented with their costs.
- 03
Build
The agreed solution is written and verified on a test portal.
- 04
Go-live
Released, demonstrated to the team, documentation handed over.
What you end up with
- A written comparison of options with build and maintenance costs
- A solution verified on a test portal and released to production
- Source code and technical documentation
- A short walkthrough for the team using it
- A definition of who maintains compatibility with Bitrix24 updates
Features
Related features
The modules we most often roll out alongside this one; they reinforce each other in the same setup.
REST API
Bitrix24 is not a closed box. The REST API gives programmatic, scope-controlled access to your CRM entities over standard HTTP; and we design, build and monitor the integration for you.
Workflows
When approvals run over email and chat, nobody knows where a request is sitting. We turn your internal processes into flows with defined steps, owners and deadlines.
Automation Robots
If a rep's day goes to logging records, setting reminders and retyping the same email, that is revenue leaking. We move that work to robots and give your team back the conversations.
Access Management
Access management is more than a password policy: permissions, audit trails and retention are designed together. We map Bitrix24's role-based model onto how your company actually works.
Other services
Bitrix24 Setup
Opening a Bitrix24 account takes five minutes. The real work is getting your sales process correctly placed inside that account; that is what we mean by setup.
Bitrix24 Training
We design training as the team doing their own work on their own screen, not as a generic product tour. No slide deck, everyone opens their own record.
Technical Support
Things keep changing after setup: new products, new people, new processes. A support plan lets you make those changes without opening a project each time.
Frequently Asked Questions
Will customisation break when Bitrix24 updates?
Apps written against the REST API do not live inside the portal, so they are not directly affected by updates. Bitrix24 does occasionally change the API; for customers on a support plan we track that compatibility.
Do we get the source code?
Yes. We hand over the source code and technical documentation of anything we build. If you continue with another team you have a complete handover package.
Is deeper customisation possible on-premise?
Yes. On-premise gives source code access, so you can go deeper than the cloud allows. It also increases your update and maintenance responsibility; we weigh that up together.
Would you still build if a Market app exists?
No, we would recommend the ready-made app first. If something on Bitrix24.Market meets your need, building is both more expensive and more work to maintain. Filling the gaps a Market app leaves is the better route.
How long does it take?
Custom fields and screen layouts take a few days, an SPA design one to two weeks, a REST API app two to six weeks depending on scope. We give the exact timeline in writing after analysis.
Let's configure this around your business
Book a free intro call and we'll walk through your process and show which settings fit you.