Event Website as a Sales Tool
An event agency receives dozens of repetitive questions: "How much does a corporate event for 100 people cost?" "Show me wedding examples." Without a website with a portfolio and calculator, managers spend hours on manual matching. We create websites on 1C-Bitrix that automate these processes. Over 30 projects for agencies confirm: a custom site with a cost calculator and CRM integration generates three times more qualified leads compared to a typical WordPress solution. Managers save an average of 40 hours per month on lead processing — at $12.5/hour, that's $500 monthly. The average development budget ranges from $3,000 to $7,000 depending on calculator complexity and integration scope.
Event Portfolio
The portfolio is the main sales block. We use an infoblock with sections by event type: corporate events, weddings, conferences, festivals, private parties. Element properties: type, guest count, venue, date, photo gallery (20–50 photos), video, client review, services (linked to the "Services" infoblock), and tags for filtering.
The detail page of a case is a longread: cover image, facts, masonry gallery (CSS Grid + Lightbox), video, review. At the bottom, a "Similar Events" block via bitrix:news.list filtered by section. The catalog uses a tile layout with AJAX filter bitrix:catalog.smart.filter.
Services Catalog
An infoblock with sections: organization, decor, catering, tech support, entertainment program, photo and video. Each service is an element with a description, icon, and link to event types. On the service page, an automatic selection of cases that used it.
Brief Form for Requests
A detailed form with a step-by-step interface (wizard) on bitrix:form.result.new or a custom component. Steps: event type, date, guests, city; details (venue, catering, entertainment, decor); budget and contact (name, phone, email, messenger, files up to 20 MB). Data is saved to a Highload-block "Requests" and duplicated via email. When integrated with Bitrix24 via REST API, a lead is created with filled fields.
How the Cost Calculator Works
The calculator balances "leave a request" and a public price list. The visitor gets an estimated budget range, the agency gets a warm lead. Our calculator boosts conversion to request by 2–3 times — confirmed by data from 15 projects.
Principle of Operation
The calculator does not show an exact amount (services are variable). It outputs a range: "from X to Y" — the lower bound for basic configuration, the upper for premium. The user sequentially selects parameters: event type, guest count, venue, services (decor, catering, entertainment, photo/video). Each step affects the final range.
Technical Implementation
Calculation data is stored in the Highload-block CalcParamsTable. Fields: UF_EVENT_TYPE (list), UF_SERVICE (list), UF_GUESTS_MIN, UF_GUESTS_MAX, UF_PRICE_MIN, UF_PRICE_MAX, UF_IS_PER_GUEST, UF_COEFFICIENT. Calculation is performed on the server: with each parameter change, the frontend sends an AJAX request. D7 controller selects rows from the Highload-block and sums ranges:
- For services with
UF_IS_PER_GUEST = true: (UF_PRICE_MIN * guests) – (UF_PRICE_MAX * guests)
- For fixed:
UF_PRICE_MIN – UF_PRICE_MAX
Server-side calculation is chosen deliberately: client-side JavaScript with prices is a public price list that could reach competitors. The server returns only the final range.
Example of CalcParamsTable Structure
| Field |
Type |
Example |
| UF_EVENT_TYPE |
List |
Corporate |
| UF_SERVICE |
List |
Catering — banquet |
| UF_GUESTS_MIN |
Number |
50 |
| UF_GUESTS_MAX |
Number |
100 |
| UF_PRICE_MIN |
Number |
2500 |
| UF_PRICE_MAX |
Number |
5000 |
| UF_IS_PER_GUEST |
Boolean |
Yes |
| UF_COEFFICIENT |
Number |
1.0 |
Result and Conversion
The result page shows the total budget range in large font, a breakdown by items (table), suitable cases from the portfolio, and a form "Get an exact estimate". When the form is submitted, a lead with the full set of parameters enters the CRM. The manager calls with a ready-made proposal. Parameters are saved in cookies and, for authorized users, in a Highload-block.
Why 1C-Bitrix?
The platform provides ready-made tools for catalogs, infoblocks, forms, and CRM. The REST API integrates with external services. Highload-blocks are convenient for storing calculator reference data. It's a proven technology for complex sites.
What's Included in Development?
The scope of work includes: project documentation (technical specifications, infoblock structure, calculator logic description), hosting setup and deployment, portfolio filling up to 15 cases (content provided by client), administrator training (1–2 hours), and 1-month warranty support. All accesses and source code are transferred to the client.
Stages and Timelines
| Stage |
What We Do |
Timeline |
| Analytics |
Service catalog, event types, calculator logic |
5–7 days |
| Design |
Prototypes, infoblock structure, calculation formulas |
7–10 days |
| Design |
Layouts (portfolio, calculator, brief), animations |
10–14 days |
| Portfolio and catalog |
Infoblocks, detail pages, filtering |
10–12 days |
| Calculator |
Highload, calculation controller, front-end wizard |
10–14 days |
| Brief form and integrations |
Step-by-step form, CRM, email notifications |
5–7 days |
| Content and launch |
Portfolio filling, testing, deployment |
7–10 days |
Total timeline: 8–11 weeks. Portfolio filling is done in parallel with development. The more cases ready at launch, the higher the conversion. Contact us to discuss your project details. Order website development and get a consultation on functionality.
How to properly design infoblocks?
When developing a 1C-Bitrix website, we see dozens of projects where poor infoblock structure slows down the site. Typical scenario: the client asks for a "product catalog." The developer creates one infoblock catalog, puts 15 properties in it. Six months later – 40 properties, 8 of which are used only for one category. The filter lags, the b_iblock_element_property table grows to millions of rows, CIBlockElement::GetList runs for 3 seconds. Consequences – conversion drop, loss of customers, additional optimization costs. In one project after catalog refactoring, page generation time dropped from 4.2 to 0.8 seconds, and annual support costs were reduced by over $10,000 through eliminated redundant queries and agents.
Our approach: design infoblocks before writing a single line of code. Separate infoblocks for entities (products, categories, brands), dictionary properties via highload blocks, trade offers for SKUs. This builds performance for years. If you want a preliminary audit of your infoblock schema, contact us for a free review of common mistakes and recommendations.
Why 1C-Bitrix outperforms most CMS for business
The choice of CMS is dictated by business needs, not preferences. Native 1C exchange via catalog.import.1c provides two-way synchronization of products, prices, balances, and orders through CommerceML without third-party modules — five times faster than developing custom exchange on OpenCart or WordPress, saving hundreds of thousands of rubles. Proactive security module includes WAF, file integrity control, SQL injection protection, and two-factor authentication; it's certified for FSTEK requirements. Modular architecture lets you enable only needed modules — iblock, catalog, sale, search — reducing DB queries per hit. Regular patches close vulnerabilities faster than open-source projects (average CVE fix time two weeks). Official documentation is maintained on the vendor's site.
What highload blocks are and how they speed up the catalog
Highload blocks are an alternative to extended infoblock properties when the list of values can grow to thousands of entries. Typical example: manufacturers, countries, colors. If stored as list properties in an infoblock, each filter triggers a full scan of b_iblock_property_enum table. With HL-blocks, selection uses indexes – filter response time drops from 1–2 seconds to 50 ms. We use HLB component and custom queries via Bitrix\Highloadblock\DataManager. This is critical for catalogs with 100,000+ items.
From our practice: an online store with 500,000 items. Standard filter by brand took 4 seconds. The server couldn't handle 50 concurrent requests – pages crashed. We moved the brand directory to an HL-block, added tagged caching for 15 minutes, and set up an agent to clear cache on change. After optimization, filter time was 120 ms, average LCP was 1.8 seconds. The project runs stable without failures.
What integrations are critical for 1C-Bitrix stores
Each e‑commerce project requires reliable connections with payments, fiscalization, logistics, and CRM. We integrate YooKassa, CloudPayments, Tinkoff, Apple Pay, Google Pay for payments; ATOL and OrangeData for 54-FZ compliance via sale.cashbox; CDEK, Boxberry, PEC, Russian Post, Yandex.Delivery for logistics; Bitrix24, amoCRM, Roistat, Calltouch, Mindbox for analytics and CRM. All integrations are configured with proper error handling and fallback logic.
What's included in 1C-Bitrix website development
Each project includes a full set of documentation and artifacts to prevent knowledge loss after handover.
- Technical specification – user stories, infoblock diagrams, integration schemas.
- Source code in Git – with commit history, release tags, branching rules.
- Administrative documentation – description of custom components, deployment instructions, list of agents and events.
- Staff training – up to a 3-hour webinar: admin panel, order management, price settings. Recorded for later review.
- Access to staging during development – test before production deployment.
- Warranty support – bug fixes for 30 days after launch. Post-warranty support packages with SLA (response 2 hours, resolution 8 hours).
Our process and technologies
| Project type |
Timeline |
Complexity |
Key features |
| Corporate website |
from 1 month |
Medium |
Catalog, news, forms, CRM integration |
| Online store |
from 2 months |
High |
54-FZ, marketplaces, 1C exchange, SKU |
| B2B portal |
from 3 months |
Very high |
Personal prices, document flow, Bizproc |
| Landing page |
from 2 weeks |
Low |
LCP < 2s, composite cache, static |
| Multisite structure |
from 1.5 months |
High |
Separate content, shared catalog, hreflang |
Tech stack: mobile-first markup, tested on physical devices (iPhone, iPad, Android). Use BrowserStack for Safari on iOS. Performance goals: LCP < 2.5 s, FID < 100 ms, CLS < 0.1. Enable composite site (composite module), CDN, tagged caching, WebP/AVIF, lazy loading. SEO: Schema.org via JSON-LD, auto-generation of sitemap.xml via seo module, canonical and hreflang for multilingual versions. robots.txt blocks /bitrix/ from indexing. CI/CD: Git, auto-deploy via GitLab CI, staging. DB migrations: sprint.migration module with versioning.
Process:
-
Analytics – study competitors, gather requirements, create prototypes in Figma. Output: technical specification with user stories.
-
Design – UI/UX with design system. Components are reusable.
-
Development – write components with custom templates in
local/templates/. Business logic in local/modules/.
-
Testing – functional, cross-browser, load testing (up to 1000 requests). Critical bugs fixed before launch.
-
Launch – deploy to production, monitoring via UptimeRobot, alerts in Telegram. Fixes for first 48 hours.
Multilingual support and redesign
Full localization via language files lang/ and SITE_ID mechanism. hreflang for each version. Regional versions with different prices and content – IP detection (main.geo) or manual selection. Multidomain – unified management of multiple domains.
Redesign without losing rankings: performance audit (PageSpeed, WebPageTest), SEO (Screaming Frog). New template in local/templates/ with preserved URL structure. 301 redirects only if URL changes significantly. Kernel update, migration to D7 ORM, infoblock restructuring, migration via sprint.migration with Git.
Guarantee and support
We have been working with 1C-Bitrix for 12+ years, completed 500+ projects. Certified developers on staff. Fixed price in contract – no surprises. Warranty period covers code errors. After warranty, subscription packages with SLA (response time 2 hours, resolution 8 hours). 24/7 availability monitoring, alerts in Telegram. Get a consultation and preliminary estimate: contact us via the form on the website or chat – we'll respond within an hour. Order turnkey development – we'll design infoblocks, integrate 1C, and speed up the catalog. If you already have a site on another CMS, order a performance audit and migration to Bitrix.
