Bitrix Project Cost Calculator: Dependencies and Urgency

Imagine a client fills out a form, selects "Integration with 1C" without "Exchange Setup", and gets a price 40% below real. The result is either renegotiation or dissatisfaction. Our calculator avoids this. We develop project cost calculators on 1C-Bitrix. This isn't just a sum of line items—it's a tool that considers dependencies between modules, urgency coefficients, margin, and automatically sends a brief to the CRM. Such a calculator helps IT companies and agencies segment incoming leads: filter out irrelevant requests and nurture serious clients. The main problem with homemade calculators is ignoring dependencies, leading to underestimated estimates and losses during negotiation.

Over 5+ years, we've built more than 50 such solutions for studios, design bureaus, and integrators. Our calculators handle from 10 to 200 functional blocks and deliver up to 90% estimation accuracy, thanks to certified specialists and years of experience.

How we calculate project cost on Bitrix

The data model is built on HL-block ProjectBlocks. Each record is a work block with category, complexity (simple/standard/complex), hour range, and hourly rate. Dependencies and mandatory blocks are described in fields UF_DEPENDS_ON and UF_IS_REQUIRED.

Why a calculator must account for dependencies

Without dependencies, a client might choose "Mobile App Development" without "Screen Design" or "Integration with 1C" without "Exchange Setup", skewing the estimate. Our PHP calculator automatically adds missing blocks and mandatory modules.

namespace MyProject\Services\Calculators;

class ProjectCostCalculator
{
    private array $blocks;
    private array $selectedIds;
    private float $urgencyCoeff;
    private float $marginPercent;

    public function __construct(
        array $allBlocks,
        array $selectedIds,
        string $urgency = 'normal',
        float $marginPercent = 30
    ) {
        $this->blocks       = $allBlocks;
        $this->selectedIds  = $this->resolveDependencies($selectedIds, $allBlocks);
        $this->urgencyCoeff = match ($urgency) {
            'urgent'   => 1.5,
            'fast'     => 1.25,
            'normal'   => 1.0,
            'flexible' => 0.9,
            default    => 1.0,
        };
        $this->marginPercent = $marginPercent;
    }

    public function calculate(): array
    {
        $breakdown    = [];
        $totalHoursMin = 0;
        $totalHoursMax = 0;
        $totalCost     = 0;

        foreach ($this->selectedIds as $blockId) {
            $block = $this->findBlock($blockId);
            if (!$block) continue;

            $hoursMin = $block['UF_HOURS_MIN'];
            $hoursMax = $block['UF_HOURS_MAX'];
            $rate     = $block['UF_HOURLY_RATE'];

            $costMin = $hoursMin * $rate * $this->urgencyCoeff;
            $costMax = $hoursMax * $rate * $this->urgencyCoeff;

            $totalHoursMin += $hoursMin;
            $totalHoursMax += $hoursMax;
            $totalCost     += ($costMin + $costMax) / 2;

            $breakdown[] = [
                'id'       => $blockId,
                'name'     => $block['UF_BLOCK_NAME'],
                'category' => $block['UF_CATEGORY'],
                'hours'    => "{$hoursMin}–{$hoursMax}",
                'cost_min' => round($costMin),
                'cost_max' => round($costMax),
            ];
        }

        $margin    = $totalCost * ($this->marginPercent / 100);
        $finalCost = $totalCost + $margin;

        return [
            'breakdown'      => $breakdown,
            'hours_min'      => $totalHoursMin,
            'hours_max'      => $totalHoursMax,
            'cost_min'       => round($finalCost * 0.85),
            'cost_max'       => round($finalCost * 1.2),
            'cost_avg'       => round($finalCost),
            'urgency_coeff'  => $this->urgencyCoeff,
            'weeks_min'      => ceil($totalHoursMin / 40),
            'weeks_max'      => ceil($totalHoursMax / 40),
        ];
    }

    private function resolveDependencies(array $selectedIds, array $blocks): array
    {
        $resolved = $selectedIds;
        foreach ($blocks as $block) {
            if (in_array($block['ID'], $selectedIds, true) && !empty($block['UF_DEPENDS_ON'])) {
                $depId = (int)$block['UF_DEPENDS_ON'];
                if (!in_array($depId, $resolved, true)) {
                    $resolved[] = $depId;
                }
            }
            if ($block['UF_IS_REQUIRED'] && !in_array($block['ID'], $resolved, true)) {
                $resolved[] = $block['ID'];
            }
        }
        return array_unique($resolved);
    }
}

What's better: a dependency-aware calculator or a simple sum?

A simple calculator sums block prices but ignores relationships, yielding 50-60% accuracy. Our approach with automatic dependency resolution boosts accuracy to 90%—1.5-2 times better. The client gets a realistic estimate, and you get fewer renegotiations. According to our data, companies using such a calculator spend 40% less time on negotiation, which translates to significant savings when scaling.

Official 1C-Bitrix documentation on HL-blocks confirms the correctness of the data model.

How calculator development happens

1. Business logic analysis: gather block list, dependencies, coefficients.
2. HL-block design: create data storage infrastructure.
3. Core calc implementation: PHP class with calculation and dependency resolution methods.
4. CRM integration: REST API sends the brief to Bitrix24 or amoCRM.
5. Interface and UX: configure checkboxes with hints and a dynamic total.
6. Testing: validate with real scenarios and edge cases.

What's included in calculator development?

Each project includes:

• Designing block structure and dependencies
• Implementing HL-block and PHP calculator
• Interface with checkboxes and hints
• CRM integration (Bitrix24, amoCRM, etc.)
• Configuring brief transfer and calculation history
• Documentation and team training

Outcome: the client gets a preliminary estimate in 2 minutes, and you get a qualified lead with a filled brief.

UX: checkboxes with tooltips

The calculator interface comprises groups of checkboxes. Each checkbox has a short description so the client understands what's included.

// Update total on every change
document.querySelectorAll('.block-checkbox').forEach(cb => {
    cb.addEventListener('change', async () => {
        const selected = [...document.querySelectorAll('.block-checkbox:checked')]
            .map(el => parseInt(el.value));

        const urgency = document.querySelector('[name="urgency"]:checked').value;

        const resp = await fetch('/ajax/calculator/project/', {
            method: 'POST',
            body: new URLSearchParams({
                selected: JSON.stringify(selected),
                urgency,
                sessid: BX.bitrix_sessid(),
            }),
        });

        const data = await resp.json();
        updateResultPanel(data);
    });
});

Transferring the brief to CRM

The calculation result forms a structured brief that immediately creates a deal in the CRM.

// Creating a deal in Bitrix24 or a lead in the site's CRM
$comments = "PROJECT COST CALCULATION\n\n";
$comments .= "Selected blocks:\n";
foreach ($calcResult['breakdown'] as $item) {
    $comments .= "— {$item['category']}: {$item['name']} ({$item['hours']} hrs.)\n";
}
$comments .= "\nTotal: {$calcResult['cost_min']} – {$calcResult['cost_max']} RUB\n";
$comments .= "Timeline: {$calcResult['weeks_min']} – {$calcResult['weeks_max']} weeks\n";
$comments .= "Urgency: {$urgency}\n";

Timeline

Key rule: the calculator must never quote a price below the real one. We build in a 20-30% buffer and clarify it's a preliminary estimate. This sets realistic client expectations and reduces renegotiations. Implementing such a calculator can save significant costs on each project by cutting renegotiations.

Our calculators have been battle-tested on 50+ projects—from web studios to major systems integrators. Get a free consultation and demo. Contact us to discuss your scenario.

Common mistakes in calculator development

• Ignoring mandatory blocks: without "Server Setup" for high-load projects, the estimate is too low.
• Missing dependency checks: selecting "Integration with 1C" without "Exchange Setup" leads to an incorrect total.
• Forgetting caching: under heavy load, the calculator slows down. We use tagged result caching.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.