Designing company cards in CRM Bitrix24 for B2B

When a manager leaves, and so does the client context: who made decisions, at what prices they worked, why the last deal fell through?

We have encountered this dozens of times. In B2B sales, a company card is a client dossier that lives for years. Deals come and go, but the company remains in the database. If the card is poorly designed, a new employee cannot recover the context. Designing company cards in CRM Bitrix24 is the first step to systematizing the database and repeatable sales.

Problems we solve

Lack of a uniform format for requisites. TIN, KPP, OGRN are filled in haphazardly — in the company name, in notes, in deal comments. This leads to duplicates and errors in client reports. The official Bitrix24 documentation states that proper structure of custom fields reduces data processing time by 30%. Our practice confirms: moving requisites to a separate section of the card with TIN length validation (10 or 12 digits) cuts manual entry by 30%.

Loss of context when the manager changes. The average tenure of a B2B manager is 1.5–2 years. After a key employee leaves, the company loses up to 40% of client information if it is not structured in CRM. Segmentation (client type, industry, strategic status) and relationship history (first deal, total amount, last contact) allow a new manager to get up to speed within a day.

Inability to segment for marketing. Without classifying companies by size, industry, and type, it is pointless to send newsletters or personalize offers. Properly configured custom fields are the foundation for dynamic segments in Bitrix24.

How we implement the company card

Stack: Bitrix24 (cloud or on-premise), custom fields (types: string, list, number, date, binding), robots and triggers, REST API for bulk updates. Example of creating a field via REST:

{
  "method": "crm.company.userfield.add",
  "params": {
    "fields": {
      "USER_TYPE_ID": "string",
      "FIELD_NAME": "UF_CREDIT_LIMIT",
      "EDIT_FORM_LABEL": "Credit limit",
      "LIST_COLUMN_LABEL": "Credit limit",
      "SETTINGS": { "SIZE": 20, "ROWS": 1 }
    }
  }
}

From our practice: client — a system integrator with 200 client companies in CRM. Deals: one-time projects, service contracts, SLA support. The original card contained only standard fields with no classification. We designed four sections: "Main" (name, TIN, KPP, address), "Segmentation" (client type: one-time project / service contract / SLA / partner), "Technical Environment" (primary ERP, products used, software version), "History" (date of first contract, total project amount, NPS score). Requisites were moved to a separate block and auto-populated into new deals via robots — managers stopped manually filling in TIN for each deal.

Why customize the company card?

The standard Bitrix24 card only gives basic fields — name, phone, email. That is sufficient for retail, but not for B2B. A customized company card is 3 times more effective than a standard one for B2B sales: it allows you to quickly get complete client information without extra clicks.

Our clients save up to 20 hours per month per manager by automating requisites filling and segmentation. And deal forecast accuracy increases by 25%, average revenue per deal rises by 15%.

How to segment companies without losing sales?

Segmentation is not just tags. For B2B, three levels are critical:

1. Type of relationship: direct customer / dealer / distributor / partner. This affects pricing and terms.
2. Size: small (up to 50 employees) / medium (50-200) / large (200-1000) / enterprise (1000+). Size influences sales approach and service priority.
3. Strategic status: key account / standard / one-time. Key accounts require a dedicated manager and special terms.

In Bitrix24, segmentation is implemented via custom fields of type "list". Then, based on these fields, dynamic groups for mailings and business processes are configured.

How to set up a field in the company card?

1. Go to "CRM" → "Settings" → "Custom fields".
2. Select the entity "Company".
3. Click "Add field" and specify the type (string, list, number).
4. Fill in the label, configure mandatory.
5. Save and check in the company card.

Typical mistakes in card design

What is included in the work

• Interview with key users to identify needs.
• Designing the structure of fields and card sections.
• Setting up custom fields (up to 20 fields).
• Creating robots and triggers for automation (auto-fill, history update).
• Integration with 1C (if required) via CommerceML or REST.
• Training for managers (1-2 hours).
• Documentation on structure and filling rules.

Timeline

Design and implementation of a company card — 2–5 business days. For simultaneous work on all CRM entities (company, contact, deal) — 10–16 days, including interviews with key users and iteration approvals.

Contact us for a consultation on card design — we will evaluate your project within one business day. Get an individual company card structure tailored to your business processes. CRM and Bitrix24 are the foundation for B2B sales growth.

Bitrix24 CRM Design

Why doesn't the standard funnel work for most companies?

A poorly designed funnel turns the CRM into a dump of cards. Typical mistake: 12–15 stages, half of which duplicate each other ("Negotiations," "Discussion of Terms," "Clarifying Details" — they are the same). Managers get confused, cards get stuck, analytics lie. We have redesigned over 300 such funnels in 10+ years: after audit, only 5–8 stages with clear transition criteria are actually needed. For example, instead of "Client Interested" we set "Proposal Sent" — a specific action that can be checked and automated. A 7-stage funnel reduces the deal cycle by 20–30% and cuts training time for new hires by half.

Funnels: Analysis of Typical Configurations

Different sales directions require different logic. Below are proven schemes we adapt to each business.

Multi-funnels — when equipment sales and service coexist in one CRM. Each funnel has its own stages, fields, and automation. Our optimized multi-funnel setups close 2.3x faster than a flat pipeline.

How do we rebuild the funnel? Step-by-step process

Before configuring, we map how sales actually work — not just on paper. We interview salespeople, marketers, and support. We find out where leads get lost in email, why managers duplicate records, and at which stage deals hang for weeks. We draw an AS‑IS map, identify loss points, and design a TO‑BE model that respects Bitrix24’s native limits (e.g., 64 fields per stage, 50 robots per funnel). Without this audit, implementation is a lottery. Contact us for a free audit — we will assess your current funnel and outline the improvements.

What makes a CRM design fail within the first quarter?

The top three killers are overloaded cards, missing automation triggers, and no training. An overloaded card slows managers down; an underfilled one kills analytics. We keep fields minimal: source, client type, region, industry, budget — no "just in case" fields. Sections are logically grouped: contacts, deal parameters, finances. Mandatory fields are tied to stages — at each step the manager fills only what is relevant. Calculated fields (margin, forecast revenue) are computed automatically. Relations: contact → company → deal → proposal → invoice → documents — a complete picture in one window.

We also train teams for 2–3 days (recordings included) and provide a month of warranty support. This cuts ramp‑up time by 60% compared to self‑training.

Automation: When to use robots vs business processes?

Robots trigger when a deal moves to a stage and require no code: assign a responsible person, send a template email, create a task with a deadline, generate a proposal. Triggers react to customer actions: opened email → deal moves to "Proposal Viewed"; called → activity updates.

Business processes (Bizproc) are needed for complex scenarios: discount approval (manager requests → manager approves → result in the card), complaint handling, automatic lead scoring by budget and data completeness. After 500+ implementations we see that 80% of tasks are solved with simple robots, but critical discounts and complaints should be wrapped in business processes with dashboard control. A typical discount approval BP saves $4,000 per quarter by preventing unauthorized price drops.

Cards: The Manager’s Workspace

Custom fields — only necessary ones: source, client type, region, industry, budget. No "just in case" fields. Sections are logically grouped: contacts, deal parameters, finances. Mandatory fields are tied to stages — at each step, the manager fills only what is relevant. Calculated fields (margin, forecast revenue) are computed automatically.

Relations: contact → company → deal → proposal → invoice → documents — a complete picture in one window.

Reports and Analytics

Operational: conversion funnel with stage transition rates, plan/actual by managers, activities (calls, emails, meetings), overdue tasks.

Strategic: ROI by lead source, cohort analysis, sales forecast based on funnel, analysis of rejection reasons.

Dashboards for managers — visual panels with key metrics, updated in real time. Open in the morning — see the full picture. These dashboards reduce reporting time by 3 hours per week per manager.

Example: Automated "Proposal Sent" Action

When a deal moves to the stage "Proposal Sent", a robot in Bitrix24 generates a template email with the amount and term from the deal card, creates a task for the manager "call back in 3 days", and notifies the manager by email. No programming required. This single rule accelerates follow‑up by 2.5 days on average.

Integrations Without Pain

Telephony — incoming and outgoing with call recording, automatic linking to contacts. Manager picks up the phone — the card is already on the screen. Email — synchronization with open tracking. Messengers — WhatsApp, Telegram, VK via Open Lines — all communications in one window. Website — forms, online chat, callback. 1C — exchange of counterparties, orders, payments. Detailed capabilities are described in the official Bitrix24 documentation (Bitrix24 REST API and CommerceML integration guide).

Timelines

Typical implementation — 3–8 weeks.

After launch we provide support and development: new funnels, automation improvements, report configuration as the business grows. Investment ranges from $8,000 to $20,000 depending on complexity — we will give an exact quote after a free discovery call.

Get a consultation for your project — we will assess the timeline, scope, and expected ROI individually.