We specialize in landing page development on 1C-Bitrix, offering both constructor and custom Bitrix templates. A promo page on 1C-Bitrix can be built in two ways: using the built-in landing module ("Sites 24" constructor) or a bespoke template on the "Site Management" engine. In our practice, we use both approaches—the choice depends on the client's task. Over 7 years we have developed more than 80 lead pages on Bitrix, each project unique. Our turnkey landing page development starts from $500 for a simple constructor-based page and from $2,000 for a custom template. You can save up to 30% on development costs by choosing the constructor for simpler projects.
The bitrix:landing module is available from the "Business" edition and provides a library of 150+ ready-made blocks. The CRM form is connected via the crm.site.form component—a lead immediately enters the funnel. There is built-in A/B testing and SEO fields. However, the constructor does not work with composite cache and limits PHP logic.
A bespoke template (folder /bitrix/templates/landing_custom/) gives full control: HTML, CSS, JS, any components (bitrix:form.result.new, bitrix:catalog.section), integration with highload blocks for arbitrary applications, dynamic content based on UTM. Composite cache and CDN are natively supported. Launch time starts from 5 days, but flexibility is unlimited.
Comparison of Approaches
| Parameter | Landing module | Custom template |
|---|---|---|
| Content editing | Visual drag-and-drop | Admin panel (infoblocks/properties) |
| PHP access | No | Full |
| CRM integration | Built-in (crm.site.form) | Via API/webhooks |
| A/B tests | Built-in mechanism | Google Optimize or custom implementation |
| Launch speed | 1–3 days | 5–15 days |
| Custom JS logic | Limited (block sandbox) | Unlimited |
| Scalability | Limited by block library | Unlimited |
| Composite cache | Not supported | Full support |
Performance Comparison
| Metric | Landing module | Custom template |
|---|---|---|
| Response time (TTFB) | 500–800 ms | 100–300 ms |
| LCP (Largest Contentful Paint) | 3–5 s | 1–2 s |
| Speed Index (SI) | 4–7 | 1–3 |
| Caching capability | HTML only | Composite + HTML + CDN |
Custom templates are 5 times faster than the landing module constructor in terms of TTFB (100-300 ms vs 500-800 ms), making them better for conversion and SEO.
What's Included in Turnkey Development
- Analysis of business goals and target audience
- Structure design and prototyping
- Unique design according to brand book
- Layout and integration with Bitrix24 CRM (forms, applications)
- Analytics setup (Yandex.Metrica, Google Analytics)
- SEO optimization: meta tags, microdata, page speed
- 3-month warranty support and staff training
How to Choose Between Constructor and Custom?
The constructor covers 80% of typical tasks: promo campaigns, lead collection, hypothesis testing. But if you need a complex multi-step form with FIAS validation, dynamic content substitution by geo, or high conversion, custom wins. In practice, a custom sales page yields 15–30% higher conversion due to speed optimization and personalization.
What If You Need a Complex Landing Page with 1C Integration?
A typical task is connecting exchange with 1C via CommerceML. In a custom template, we implement an import agent that synchronizes items and prices. Integration with payment gateways (YooKassa, Sber) requires a custom result handler. These scenarios are impossible in the constructor.
How We Develop a Landing Page: Stages
- Briefing and audit — identify goals, audience pain points, study competitors.
- Prototyping — draw block structure and scenario logic.
- Design — create an adaptive layout in Figma.
- Layout and integration — implement the template, connect CRM, configure forms.
- Testing — check cross-browser compatibility, speed (Core Web Vitals), correct form submissions.
- Deployment — place on production server, set up monitoring.
- Post-release — hand over documentation, conduct training, provide warranty.
Technical Details for Developers
For custom development we use PHP 8.1+, components 2.0, infoblock ORM v2.0. For storing applications — highload block with arbitrary structure. Caching — tagged, with composite mode. Integrations via REST API (CRM, amoCRM, telephony). Example block file structure: custom_block/templates/.default/template.php.
According to documentation, the landing module does not support kernel-level caching, so for high-load projects custom templates are preferable.
Why Is a Custom Template More Profitable Than the Constructor?
Custom gives full performance control. Composite cache speeds up page delivery by 5–10 times compared to the constructor. And the absence of PHP restrictions allows implementing any logic: auto-filling data from 1C, integration with payment gateways, complex business process scenarios. See Wikipedia for more about the landing page concept — it's not just a page, but a sales tool.
Contact us for a consultation. We will assess your task and offer the optimal solution. Order a promo page development on 1C-Bitrix — get a working tool for your business.