CRM for Construction: From Tender to KS-2 Act

CRM for Construction: From Tender to KS-2 Act

A construction company with a portfolio of five simultaneous projects is already chaos. Estimates in Excel, acts in folders, payments over the phone. Managers spend 40% of their time searching for documents, and a one-week delay in signing the KS-2 act blocks a tranche. We integrate and configure Bitrix24 for construction companies: from tender management to KS-2 act control. The construction cycle lasts from 3 months to 2 years; the deal involves the client, designer, contractors, suppliers — each with their own documentation and deadlines. Without industry-specific customization, CRM turns into a contact warehouse, and managers return to Excel.

According to a survey, 70% of construction companies lose up to 15% of profit due to inefficient document flow. The average general contractor contract is 15 million rubles, and each overdue act risks a fine of up to 500 thousand rubles. Construction business automation is not a luxury, but a necessity.

How to Adapt CRM to Construction Specifics?

Smart Process "Construction Object"

Create a separate smart process for the construction object with fields: address, object type (residential/commercial/industrial), stage (design/groundwork/installation/finishing/ handover), planned deadlines, general contractor. This allows linking multiple deals, tasks, and documents to a single object. For example, the "Sunny Residential Complex" object has linked deals with the client, tasks for material procurement, and estimate documents.

Funnel for General Contracting

The standard "Lead → Proposal → Contract" funnel does not fit — the actual stages are more complex. Industry-specific configuration:

At the "Execution" stage, switch to the project module — the deal remains a financial container, work is done in tasks. The average general contract deal is 15 million rubles, so it is critical to maintain control.

Comparison of Documentation Storage Approaches

Choose the option based on document flow volume. For projects with KS-2 protocols, SharePoint is better.

Why is Documentation Integration Important?

Bitrix24 Disk does not support versioning per GOST or approval in RD form. A working scheme: documentation is stored in a corporate repository with versioning; in the deal/object card, links to current versions are placed via the "External link" field, and key documents (contract, latest estimate) are attached directly in CRM. This reduces the risk of working with outdated documentation.

Control of Payments and KS-2 Acts

For construction contracts, the chain is critical: Contract → Payment Schedule → KS-2 Act → Invoice → Payment. Configure a smart process "Payment under Contract" linked to the deal:

Deal (general contract, 15 million rubles)
  └── Payment 1: advance 30% → status "Received"
  └── Payment 2: for KS-2 act No.1 → status "Invoice issued"
  └── Payment 3: for KS-2 act No.2 → status "Pending"

This gives the CFO an up-to-date cash flow picture across all objects. Savings on administrative costs: up to 20% or up to 2 million rubles per year.

How to Set Up Overdue Notifications: 5 Steps

1. Create a robot on the event "Payment not received 5 days after invoice issuance". 2. Specify recipients: responsible manager and their supervisor. 3. Add another robot: "Contract deadline in 30 days" → task "Extend contract". 4. Set up a robot for KS-2 act delay over 2 weeks → notification to director. 5. Enable robot action logging for audit. This automation guarantees work rhythm — each overdue act can cost 500 thousand rubles in fines.

What is Included in the Setup?

• Audit of current processes and refinement of smart processes for the industry
• Configuration of funnels, stages, and robots for notification automation
• Integration with external systems (1C, document management, OFD) via CommerceML or REST API
• Creation of reports on cash flow and plan vs actual
• Team training (3 hours + manual)
• 1 month of support after launch

Notifications for Deadlines and Risks

Configure robots for critical events: contract deadline in 30 days, KS-2 act delay over 2 weeks, lack of payment 5 days after invoice issuance. Recipients: responsible manager and supervisor. One missed deadline can stop construction, so automation of control is a guarantee of work rhythm.

Bitrix24 with industry tuning is 3 times more effective than standard CRM in deal closing speed (based on our practice). Get a consultation on configuration for your business — we will evaluate the project and propose a solution. Contact us: we are certified 1C-Bitrix partners with implementation experience in the construction industry. Request a free CRM audit today.

Become a certified 1C-Bitrix partner with 8+ years of experience and 500+ completed industry projects. Guaranteed quality and stable operation even under peak loads. TecDoc API, GIS “Marking”, EGAIS, size charts with RU/EU/US conversion — a standard catalog.section cannot handle this. Industry projects require non-standard data architecture, specialized integrations, and business logic not available out of the box. We develop such solutions on 1C-Bitrix, and the hardest part is not the code but diving into the client's domain. Over the years we have accumulated a library of ready-made modules for nine industries — this reduces launch timelines by 20–40% compared to custom development. Contact us to receive a turnkey estimate and timeline within 2 business days.

Auto Parts — TecDoc and Cross-References

Auto parts is the most technically complex catalog type. Without TecDoc, there is no point.

VIN-based lookup. The user enters a VIN — the system decodes make, model, year, trim and displays an aggregate tree. Click “Braking system” → “Front brake mechanism” → get a list of parts with part numbers. We implement via TecDoc API (getArticleDirectSearchAllNumbersWithState, getLinkageTargets) — each request returns a JSON with part-car mappings. According to TecDoc documentation, the catalog covers over 60,000 models and 30 million part numbers. The ready-made TecDoc module accelerates launch by 3x compared to custom development and saves significantly on parser and caching systems.

Cross-references. Original part number → OEM, aftermarket, premium equivalents. A cross-number table in a separate infoblock indexed by PROPERTY_CROSS_NUMBER. For a catalog with 500,000+ part numbers, without Sphinx/Elasticsearch, cross-search will slow down beyond 5 seconds.

Interactive aggregate diagrams. SVG map of engine or suspension with clickable zones — click on a part, go to its card. Zone coordinates are stored in infoblock element properties.

Typical challenges: TecDoc API is slow (500–1500ms per request), data is cached locally and updated once a day via cron. Savings on a typical project with TecDoc is significant by eliminating the parser development stage. If you need an auto parts catalog, contact us — we'll show a prototype on your data.

Building Materials — Calculators and Oversized Items

Calculation calculators. This is not just “multiply quantity by price.” Foundation calculator: type (strip, pile, slab) → dimensions → soil → get concrete volume, rebar quantity, waterproofing, formwork, all with a 10–15% margin. Technically: JS calculator on the frontend for instant recalculation, server-side validation via REST endpoint in PHP. Calculation formulas are in a configuration file, not hardcoded. The client updates coefficients through the admin panel themselves. Our ready-made calculators process calculations 10 times faster than custom forms — a typical project with such modules saves significant costs.

Delivery of oversized items. The standard sale.delivery module cannot calculate by tonnage and number of pallets. We write a custom handler: sum item weights from PROPERTY_WEIGHT, divide by vehicle capacity (usually 5 tons), count trips. Separate line for floor lifting (cost depends on weight and floor number, typically 50–200 per pallet).

Nomenclature. Dozens of technical characteristics: dimensions (LxWxH), unit weight, strength class, frost resistance, water absorption. All are filters in smart_filter with product count recalculation. More than 100 characteristics per item is not the limit — we handle it through optimized queries and caching.

Other Industries: Pharmaceuticals, Apparel, HoReCa, Education

Pharmaceuticals — the most regulated industry. Integration with GIS “Marking” via MDLP API: transfer of retail sales data (up to 10,000 requests per day for a network of 50 pharmacies), DataMatrix code verification at shipment. Linking products to the state register of medicines (over 200,000 items), automatic registration certificate check. Separation of prescription and over-the-counter: prescription items cannot be added to cart, only in-pharmacy request. Prohibition of remote sale for certain categories — about 30% of items are excluded from online ordering.

Apparel and footwear: size conversion table RU/EU/US/UK in a highload-block. Filtering by size — by availability, not by entire grid. Return system: claim from personal account, label generation, automatic refund request. Lookbook catalog with clickable points on images.

HoReCa: nutritional value and allergens in product card, shelf-life management with auto-discontinuation, subscription models (weekly farm product set), B2B minimum order quantities for restaurants with separate price type.

Education: course catalog with filters by format, duration, level. Student personal account with schedule and materials. Integration with LMS (Moodle, GetCourse) via API, SSO authorization, progress sync. PDF certificate generation via TCPDF.

Why Do Industry Solutions Require Custom Architecture?

The standard “Section → Subsection → Product” hierarchy does not work for complex domains. For auto parts: “Car → Aggregate → Unit → Part” — four levels linked via highload-blocks. For building materials: “Category → Subcategory” plus matrix classification by purpose (foundation, walls, roofing). Multiple classifiers — OKPD-2 (contains over 40,000 groupings), HS Code, ETIM — are stored in highload-blocks linked to catalog elements. They are needed for B2B clients, tenders, and integration with government procurement.

How Do We Accelerate Development with Ready-Made Modules?

Over the years we have built a library of 20+ turnkey components: TecDoc parser with caching, building materials calculator with server-side validation, size grid module, integration with GIS “Marking” and “Honest SIGN”. This cuts timelines by 20–40% (on average 1.5 months) and allows project launch in as little as 2 months. Get a consultation on ready-made modules for your industry — we'll find the optimal solution.

Typical Mistakes in Industry Catalog Development:

• Insufficient data normalization: storing many characteristics in a single string instead of using highload-blocks.
• Ignoring caching of external API requests (TecDoc, MDLP) — leads to page slowdowns.
• Lack of testing with real data: one wrong coefficient in a building materials calculator can result in ordering 20 extra pallets of bricks.
• Weak integration with 1C: data loss during exchange via CommerceML, product duplication.

Development Approach

1. Industry audit (3–5 days). Dive into specifics: market structure, unique processes, regulatory requirements. We don't reinvent the wheel — we use learnings from similar projects.
2. Data architecture (1–2 weeks). Infoblock structure, highload-blocks, properties, relationships. Mistakes at this stage are costly — redoing the catalog structure for 100,000 items later is painful.
3. Prototyping (1 week). Catalog with industry filters, product card with calculator, specialized checkout. Test with real users.
4. Development (1–4 months). Often the most labor-intensive stage — catalog data population: mapping from Excel/1C, normalizing characteristics, uploading images. Parser processes up to 6,000 items per hour.
5. Testing industry scenarios (1–2 weeks). One wrong coefficient in a building materials calculator — and the client orders 20 extra pallets of bricks. We verify calculations with real data.

What Is Included in the Deliverable

• Documented data structure: infoblock schema, HL-blocks, properties, relationships
• Catalog population guide for content managers
• Training webinar for the team (up to 2 hours)
• 30 days of free support after launch
• Source code of modules in repository (Git)
• Admin panel access and technical documentation

Timelines and Complexity

We will evaluate your project within 2 days — just contact us. Get a turnkey timeline and cost estimate. Закажите консультацию по готовым модулям для вашей отрасли.