Practical guide

CRM Use Cases: How Companies Sell More and Work More Efficiently

A working guide rather than a sales page: what a CRM actually fixes in sales, marketing, support and operations, how it plays out across 13 industries, what results real companies have reported — and, just as importantly, what a CRM does not fix.

Written by the Bsmart team, which implements Bitrix24 and custom CRM systems for companies in the Republic of Moldova.

Full read: ~35 minutes. Industry sections are collapsed — read only what applies to you.Content and sources last reviewed:

What a CRM use case is, and what problems a CRM solves

A CRM use case is a specific working situation where a CRM replaces a manual process: capturing an enquiry, tracking a quote, following up with a customer, or reporting on sales. A CRM mainly solves lost information and lost follow-up — it does not solve a weak product, an uncompetitive price, or a team without a sales process.

What a CRM solves

  • Customer knowledge lives in one employee's head, personal phone, or local file.
  • Enquiries arrive on five different channels and nobody holds the full list.
  • Follow-ups happen from memory, so they happen inconsistently or not at all.
  • Reporting is assembled by hand at month end, from data that is already stale.
  • When a colleague leaves, the relationship with their customers leaves too.

When a company needs a CRM

  • More than one person talks to the same customer.
  • The sales cycle has several steps and runs over days or weeks.
  • Enquiry volume exceeds what one person can hold in mind.
  • Management needs a view of the pipeline without interrupting the team.
  • Repeatable procedures already exist, written or not, and can be automated.

What a CRM cannot solve on its own

  • A sales process the company has never defined. A CRM digitises the existing process, flaws included.
  • Absent demand. A CRM does not create customers; it organises the relationships you already have.
  • A team that refuses to log its work. With no data entered, reports look fine and lie.
  • Old, duplicated or wrong data. Migrating a dirty database produces a dirty CRM.
  • Management decisions. The CRM shows you reality; what you do about it stays a human call.
Open contents

CRM use cases by department

The same system solves different problems for different teams. For each one below: the real problem, what the process looks like beforehand, what the CRM does, one concrete automation, the useful integrations, a KPI you can measure, and the limitation to keep in mind.

Sales

Business problem
Opportunities slip away between the first conversation and the signature, and nobody can say exactly how many deals are actually in play.
The process before CRM
Every rep keeps their own file or notebook. Quotes go out from personal email. Status is discovered at the weekly meeting, by asking.
What the CRM does
Every enquiry becomes a deal with a stage, an owner, a value and a deadline. The pipeline is visible in real time and the full history sits on the customer record.
Example automation · Measurable KPI · Important limitation
Example automation
When a deal sits in the same stage for more than 5 days, the system creates a task for the owner and notifies the manager.
Relevant integrations
  • VoIP telephony
  • Corporate email
  • Website forms
  • WhatsApp, Telegram, Viber
Measurable KPI
Stage-by-stage conversion, average cycle length, number of deals with no activity.
What improves
Fewer forgotten opportunities, and a forecast built on logged data rather than the team's verbal estimates.
Important limitation
If the pipeline stages do not match how the team really sells, people will drag deals along mechanically and the report will be worthless.

Marketing

Business problem
Budget goes into campaigns, but nobody knows which source brings customers who actually buy.
The process before CRM
Leads from ads, the website and social media land in different inboxes. Attribution is done from memory, or not at all.
What the CRM does
Each lead's source is captured automatically and stays attached through to the sale, so reports show revenue per channel, not just clicks.
Example automation · Measurable KPI · Important limitation
Example automation
Leads who downloaded a resource but went quiet for 7 days automatically enter an email sequence with a relevant case study.
Relevant integrations
  • Google Ads and Meta Ads
  • Web forms
  • Email marketing
  • Analytics
Measurable KPI
Cost per qualified lead, lead-to-customer rate per source, revenue attributed per campaign.
What improves
Budget shifts away from channels that produce volume towards those that produce contracts.
Important limitation
Attribution stays approximate: someone who sees an ad and calls a week later from another device cannot be tied cleanly to a source.

Customer support

Business problem
Customers repeat the same problem on every call, because the agent cannot see what was discussed before.
The process before CRM
Complaints arrive by phone, email and messaging, and get handled by whoever is free. Nothing records what was promised.
What the CRM does
Each request becomes a ticket linked to the customer, with an owner and a deadline. Whoever picks it up sees the full history.
Example automation · Measurable KPI · Important limitation
Example automation
A ticket past its deadline escalates automatically to the coordinator and flags the customer for a check-in call.
Relevant integrations
  • Telephony with call recording
  • Website chat
  • WhatsApp, Telegram, Viber
  • Support email
Measurable KPI
Average first-response time, time to resolution, share of reopened tickets.
What improves
Consistent answers no matter who takes the case, and fewer dropped promises.
Important limitation
Escalation rules do not add people. If the team is understaffed, the CRM simply makes the delay visible.

Management

Business problem
Decisions rest on reports prepared by the same team those reports are used to evaluate.
The process before CRM
Spreadsheets are requested at month end. They arrive late, in different formats, and cannot be compared across periods.
What the CRM does
Dashboards for pipeline, activity and results, refreshed with every action logged in the system.
Example automation · Measurable KPI · Important limitation
Example automation
A weekly report of high-value deals with no recent activity is sent to management automatically on Monday morning.
Relevant integrations
  • CRM reporting
  • Accounting / invoicing
  • Business intelligence tools
Measurable KPI
Pipeline value per stage, forecast vs actual, activity per owner.
What improves
Problems become visible mid-month, while they can still be fixed, not after the books close.
Important limitation
Dashboards only show what was entered. Partial adoption produces optimistic, misleading reports.

Operations

Business problem
Information gets lost between the signed contract and delivery, and the customer hears about the delay before the team does.
The process before CRM
Handover from sales to delivery happens in a chat message or a corridor conversation. Agreed details stay in that conversation.
What the CRM does
A won deal automatically opens a delivery workflow with stages, owners and deadlines, tied to the same customer record.
Example automation · Measurable KPI · Important limitation
Example automation
When a deal moves to "Won", the system creates the delivery checklist and notifies the fulfilment team.
Relevant integrations
  • Task and project management
  • Inventory / ERP
  • Shipping and courier systems
Measurable KPI
Contract-to-delivery time, share of on-time orders, overdue tasks.
What improves
One source of truth for what was sold, what was promised and what was delivered.
Important limitation
Inventory or ERP integration is the most expensive part of the project, and it needs clean data on both sides.

Finance and invoicing

Business problem
Invoices go out late, and chasing overdue payments depends on somebody remembering.
The process before CRM
Customer details are retyped from the quote into the accounting software, with transcription errors along the way.
What the CRM does
Billing details live on the customer record, and payment status is visible next to the deal.
Example automation · Measurable KPI · Important limitation
Example automation
Three days past the due date, the system creates a collections task and notifies the account owner.
Relevant integrations
  • Accounting software (including 1C, where technically feasible)
  • E-invoicing
  • Bank statements
Measurable KPI
Average days to payment, overdue balance by ageing bucket, invoices issued on time.
What improves
Less manual re-entry, and a clear picture of cash locked up in receivables.
Important limitation
A CRM is not accounting software. Integration with the accounting system must be assessed technically before it is promised.

Human resources

Business problem
Recruitment runs on email and spreadsheets, and good candidates are left without an answer.
The process before CRM
CVs pile up in an inbox. Interview stages are remembered. Rejected candidates are never revisited for later roles.
What the CRM does
A separate recruitment pipeline with the candidate as an entity, plus internal onboarding workflows for new hires.
Example automation · Measurable KPI · Important limitation
Example automation
A candidate who clears the technical interview automatically triggers onboarding tasks and access requests, assigned to their owners.
Relevant integrations
  • Job boards
  • Email
  • Electronic document signing
Measurable KPI
Time to hire, share of candidates left unanswered, onboarding duration.
What improves
A reusable candidate history and a predictable first week for new colleagues.
Important limitation
Candidate data is personal data: it needs a lawful basis, a retention period and restricted access, exactly like customer data.

Field teams

Business problem
Field reps report in the evening, from memory, and the information arrives incomplete.
The process before CRM
Visits are noted on paper or in a phone and typed up back at the office, sometimes the next day.
What the CRM does
The mobile app lets reps log the visit, the order and the next step at the customer's site, with full history to hand.
Example automation · Measurable KPI · Important limitation
Example automation
After a visit marked complete with no order, the system schedules a follow-up at the agreed interval.
Relevant integrations
  • CRM mobile app
  • Maps and routing
  • Product and price catalogue
Measurable KPI
Visits per rep, visit-to-order rate, delay between visit and logging.
What improves
Data entered at the moment it happens, so it is more accurate, and route planning grounded in reality.
Important limitation
It depends on connectivity and mobile discipline; an overlong mobile form simply gets abandoned.

Call centre teams

Business problem
Call volume makes it impossible to track the outcome of each conversation by hand.
The process before CRM
Call lists are split across spreadsheets. Outcomes are noted inconsistently, and callbacks fall through.
What the CRM does
The call is linked automatically to the customer record, with a recording, a structured outcome and the next action scheduled.
Example automation · Measurable KPI · Important limitation
Example automation
An unanswered call schedules a callback automatically; after three attempts the contact moves into a separate workflow.
Relevant integrations
  • VoIP telephony with recording
  • Call scripts
  • Dialer systems, where present
Measurable KPI
Calls per agent, contact rate, call-to-appointment rate, average handling time.
What improves
Callbacks stop depending on memory, and call quality can be reviewed against recordings.
Important limitation
Recording calls requires informing the other party in advance and a defined retention policy for the files.

CRM use cases by industry

What separates industries is not the buttons, but what gets tracked: the thing being sold, the entities that matter, and the moment where deals are lost. Pick a sector to see its pipeline, entities, automations and specific risks.

Real estate

Typical operational problem: The same property is pitched by two agents to two buyers, and incoming requests are never matched against available stock.

Example pipeline

  1. Enquiry received
  2. Budget and area qualified
  3. Viewing booked
  4. Offer / negotiation
  5. Preliminary contract
  6. Deal closed

Core CRM entities

  • Buyer
  • Owner
  • Property (as its own object)
  • Viewing
  • Deal

Recommended integrations

  • Telephony
  • WhatsApp and Viber
  • Listing portals
  • Electronic signing

Useful automations

  • Automatic matching of a new request against the portfolio
  • Follow-up reminder after each viewing
  • Alerting buyers when a matching property is listed

Example dashboard / KPIs

  • Viewings per agent
  • Viewing-to-offer rate
  • Average time to sell by area
  • Properties with no activity for 30 days

Implementation risk or challenge: Exclusivity and portfolio-access rules must be settled before configuration, or agents will keep their best leads out of the system.

Logistics and transport

Typical operational problem: Transport requests, quotes and confirmations travel over messaging apps, and the price given to a customer cannot be reconstructed later.

Example pipeline

  1. Transport request
  2. Cost and route calculated
  3. Quote sent
  4. Order confirmed
  5. In transit
  6. Delivered and invoiced

Core CRM entities

  • Shipper
  • Transport order
  • Route
  • Vehicle / carrier
  • Invoice

Recommended integrations

  • Telephony
  • Email and messaging
  • GPS tracking systems
  • Invoicing software

Useful automations

  • Automatic acknowledgement of a request, with a response deadline
  • Alert on orders past the estimated delivery date
  • Automatic dispatch of transport documents on completion

Example dashboard / KPIs

  • Requests to confirmed orders
  • Margin per order
  • On-time deliveries
  • Response time to a request

Implementation risk or challenge: Telematics and invoicing integration is the hard part; without it the CRM stays a parallel ledger that somebody fills in by hand.

Retail and e-commerce

Typical operational problem: Orders from the online shop, social media and the physical store are handled in separate places, with stock levels that never see each other.

Example pipeline

  1. Order received
  2. Confirmed and stock checked
  3. Payment
  4. Picked and shipped
  5. Delivered
  6. Post-purchase

Core CRM entities

  • Customer
  • Order
  • Product
  • Return
  • Loyalty programme

Recommended integrations

  • E-commerce platform
  • Chat and messaging
  • Courier services
  • POS / till system

Useful automations

  • Abandoned-cart recovery via a scheduled message
  • Review request a few days after delivery
  • Automatic segmentation by purchase frequency

Example dashboard / KPIs

  • Average order value
  • Repeat customer rate
  • Cancelled orders
  • Order-to-dispatch time

Implementation risk or challenge: A high volume of small orders can flood the CRM with low-value records; you need clear rules on what enters the CRM and what stays in the shop platform.

Distribution

Typical operational problem: The outlet portfolio is large, and reps have no record of who was visited, when, and with what result.

Example pipeline

  1. Outlet identified
  2. First visit
  3. Trial order
  4. Active recurring customer
  5. Declining customer
  6. Reactivation

Core CRM entities

  • Outlet
  • Sales rep
  • Visit
  • Recurring order
  • Product range

Recommended integrations

  • Mobile app for reps
  • Stock and pricing
  • Invoicing
  • Maps and routing

Useful automations

  • Visit plan generated from route and call frequency
  • Alert on customers who have not ordered in N weeks
  • Blocking orders for customers past their credit limit

Example dashboard / KPIs

  • Active vs dormant outlets
  • Orders per visit
  • Average range per customer
  • Overdue balances per rep

Implementation risk or challenge: Without price and stock synchronisation, reps will take orders that cannot be fulfilled, and trust in the system evaporates fast.

Professional services

Typical operational problem: Projects are sold on trust, but the hours worked, the decisions taken and the deliverables stay in email and in people's heads.

Example pipeline

  1. Enquiry
  2. Needs conversation
  3. Proposal
  4. Contract
  5. Delivery
  6. Referral / next project

Core CRM entities

  • Client
  • Project
  • Proposal
  • Deliverable
  • Contract

Recommended integrations

  • Email and calendar
  • Project management
  • Electronic signing
  • Invoicing

Useful automations

  • Standard task set generated on contract signature
  • Reminder on proposals unanswered for 5 days
  • Feedback request at project close

Example dashboard / KPIs

  • Proposal-to-contract rate
  • Average project value
  • Projects running past deadline
  • Revenue from repeat clients

Implementation risk or challenge: An over-rigid system fits consulting work badly; over-configuration creates pointless admin for small teams.

Medical clinics

Typical operational problem: Appointments are booked by phone, no-shows are frequent, and follow-up check-ups are never tracked systematically.

Example pipeline

  1. Booking request
  2. Appointment confirmed
  3. Consultation
  4. Treatment plan
  5. Check-up scheduled
  6. Returning patient

Core CRM entities

  • Patient
  • Appointment
  • Medical service
  • Practitioner
  • Treatment plan

Recommended integrations

  • Telephony
  • SMS and messaging
  • Appointment calendar
  • Till system

Useful automations

  • Automatic reminder 24 hours before the appointment
  • Rebooking offered automatically after a no-show
  • Check-up reminder at the recommended interval

Example dashboard / KPIs

  • No-show rate
  • Utilisation per practitioner
  • Check-up return rate
  • Waiting time to an appointment

Implementation risk or challenge: Health data is a special category. What is stored in the CRM and who can see it needs careful thought; diagnoses do not belong in a commercial CRM without prior legal review.

Automotive and servicing

Typical operational problem: Customers come in once and are never contacted again, even though the service interval is entirely predictable.

Example pipeline

  1. Enquiry
  2. Booking
  3. Diagnosis and estimate
  4. Customer approval
  5. Repair
  6. Handover and warranty

Core CRM entities

  • Customer
  • Vehicle (a separate entity)
  • Work order
  • Estimate
  • Service history

Recommended integrations

  • Telephony
  • SMS and messaging
  • Parts catalogue
  • Invoicing

Useful automations

  • Service reminder based on mileage or elapsed time
  • Notification when an estimate is approved
  • Review request after handover

Example dashboard / KPIs

  • Customer return rate
  • Average work-order value
  • Estimate-to-approval time
  • Bay utilisation

Implementation risk or challenge: The vehicle, not the customer, is what you track. A contact-only CRM cannot keep the history straight when a car changes owner.

Construction

Typical operational problem: Quoting takes time, several versions of the estimate are in play, and nobody can tell which one was actually sent.

Example pipeline

  1. Enquiry
  2. Site visit
  3. Estimate
  4. Negotiation
  5. Contract
  6. Staged delivery

Core CRM entities

  • Client
  • Site / project
  • Estimate and its versions
  • Contract
  • Delivery stage

Recommended integrations

  • Email
  • Document management
  • Staged invoicing
  • Electronic signing

Useful automations

  • Automatic versioning of estimates tied to the same enquiry
  • Follow-up reminder after an estimate is sent
  • Stage tasks generated on contract signature

Example dashboard / KPIs

  • Estimate-to-contract rate
  • Enquiry-to-estimate time
  • Deviation from stage deadlines
  • Contracted value per period

Implementation risk or challenge: Long decision cycles make the pipeline look stalled; stages have to be realistic or the reports say nothing useful.

Education and training

Typical operational problem: Interest in a course comes from ads and social media, but many prospects are lost between the question and the enrolment.

Example pipeline

  1. Interest expressed
  2. Consultation
  3. Course offer
  4. Enrolment
  5. Payment
  6. Graduation and next course

Core CRM entities

  • Applicant
  • Course / cohort
  • Enrolment
  • Payment
  • Graduate

Recommended integrations

  • Website forms
  • Facebook and Instagram ads
  • WhatsApp and Telegram
  • Payment platform

Useful automations

  • Immediate reply on the channel the question came from
  • Payment reminders before the cohort starts
  • Next-course offer at graduation

Example dashboard / KPIs

  • Enquiry-to-enrolment rate
  • Cohorts filled on time
  • First-response time
  • Rate of return for a second course

Implementation risk or challenge: Strong seasonality can make month-on-month reports look catastrophic; comparisons need to be year-on-year.

Hospitality and events

Typical operational problem: Group bookings and events are negotiated over messaging apps, and the agreed details are lost by the time the date arrives.

Example pipeline

  1. Event enquiry
  2. Quote and availability
  3. Venue viewing
  4. Contract and deposit
  5. Planning
  6. Event and feedback

Core CRM entities

  • Client
  • Event
  • Venue / date
  • Menu and services
  • Deposit

Recommended integrations

  • Telephony and messaging
  • Availability calendar
  • Payments
  • Social media

Useful automations

  • Date blocked automatically when the deposit is confirmed
  • Reminder to confirm the final guest count
  • Review request after the event

Example dashboard / KPIs

  • Enquiry-to-contract rate
  • Date occupancy
  • Average event value
  • Repeat events

Implementation risk or challenge: Many decisions are made verbally, on site. If the team has no habit of logging, the CRM stays empty exactly during the busiest weeks.

Call centres and telesales

Typical operational problem: Large contact lists are worked through, but call outcomes and the reasons for refusal cannot be analysed.

Example pipeline

  1. Contact in the database
  2. First call
  3. Interest confirmed
  4. Appointment / offer
  5. Sale
  6. Scheduled callback

Core CRM entities

  • Contact
  • Calling campaign
  • Call
  • Structured outcome
  • Agent

Recommended integrations

  • VoIP telephony with recording
  • Dialer
  • Call scripts
  • SMS

Useful automations

  • Automatic distribution of lists across agents
  • Callback scheduled automatically after an unanswered call
  • Moving a contact to a separate list after N attempts

Example dashboard / KPIs

  • Contact rate
  • Call-to-positive-outcome rate
  • Refusal reasons by category
  • Calls per hour per agent

Implementation risk or challenge: Cold calling and call recording carry notification and consent requirements that must be cleared before the campaign launches.

Insurance

Typical operational problem: Policies expire without the customer being contacted, and the renewal goes to another broker.

Example pipeline

  1. Quote request
  2. Comparing offers
  3. Policy issued
  4. Policy active
  5. Renewal
  6. Claim / assistance

Core CRM entities

  • Client
  • Policy (with expiry date)
  • Insurance product
  • Renewal
  • Claim file

Recommended integrations

  • Telephony
  • Email and SMS
  • Insurer systems, where available
  • Electronic signing

Useful automations

  • Contact task created 30 days before expiry
  • Notification when a claim is registered
  • Complementary product offer after the first policy

Example dashboard / KPIs

  • Renewal rate
  • Policies per client
  • Response time to a quote request
  • Average premium

Implementation risk or challenge: Policy data is personal and sometimes sensitive; access rights and retention periods must be configured from the start, not bolted on later.

Complex B2B sales

Typical operational problem: Several people at the client company are involved in the decision, and the rep spends months talking to the one who does not sign.

Example pipeline

  1. Company identified
  2. First contact
  3. Needs analysis
  4. Proposal
  5. Negotiation and approvals
  6. Contract

Core CRM entities

  • Company
  • Contacts with roles
  • Opportunity
  • Proposal
  • Contract and annexes

Recommended integrations

  • Email and calendar
  • Telephony
  • Electronic signing
  • Accounting

Useful automations

  • Alert on opportunities where no decision-maker has been identified
  • Reminders per person involved in the decision
  • Preparation tasks before each scheduled meeting

Example dashboard / KPIs

  • Sales cycle length
  • Contacts involved per opportunity
  • Win rate by segment
  • Average contract value

Implementation risk or challenge: B2B selling carries a lot of unquantifiable information. Asking the team to fill in dozens of fields lowers data quality instead of raising it.

Real case studies, with verifiable sources

The examples below are other companies' implementations, published by CRM vendors or by the organisations themselves. We use them because they are checkable — each card links to the original source, not to a retelling.

Results are reported by the original organisations or CRM vendors and are not Bsmart projects. Individual results depend on company size, processes, data quality, implementation and team adoption.

Vitaquest International

USA·Manufacturing (nutraceuticals and functional foods), 600+ employees

Platform: Zoho CRMResult with published figures

Initial challenge
Customer communication and order processing ran on fragmented email threads, across departments that never saw the same data.
What was implemented
Zoho CRM as the central system: unified customer data, structured quoting and standardised onboarding, with automation replacing email ping-pong.
Reported result
Quote turnaround cut by 50%, quote volume up 33%, roughly 6,500 emails a month eliminated, and 65 working days a year recovered in the sales department.
Context
Relevant to Moldovan distributors and manufacturers who still quote dozens of requests a week by hand, over email.

Lexmark

global·Manufacturing and printing technology

Platform: Microsoft Dynamics 365 + Experlogix CPQResult with published figures

Initial challenge
The sales and reporting process was cumbersome, and complex quotes kept coming back for revision.
What was implemented
Integrating the CRM with a configure-price-quote (CPQ) system, so quotes are generated from validated data rather than separate files.
Reported result
A 43% drop in quote revisions and a significant reduction in time-to-quote.
Context
Shows what integrating the CRM with pricing actually buys you — versus a CRM plus a separate price spreadsheet.

Sticos

Norway·Compliance software for accountants and auditors, 25–200 employees

Platform: HubSpot Service HubResult with published figures

Initial challenge
Support was drowning in repetitive requests (password resets, login problems) arriving by email, and an acquisition was about to add some 15,000 tickets.
What was implemented
A well-written knowledge base, chat embedded in the product, and automated workflows for the most common phrasings — deflection before a human is involved.
Reported result
41% of tickets handled automatically, a 91% chat deflection rate and a 75% chat resolution rate; the acquisition was absorbed without extra hires.
Context
The result rests on the quality of the knowledge base, not on automation itself — without good content, nothing gets deflected.

Motorola Solutions

global·Technology and mission-critical communications, 1,000+ employees

Platform: HubSpotPartial figures

Initial challenge
Customer data was scattered across several systems, and marketing had no unified, real-time view.
What was implemented
Consolidating records into a single trusted base, and campaigns triggered by how customers actually use the product.
Reported result
Over 123,000 customer records unified. The company also reports a multi-million cross-sell opportunity surfaced by one campaign — a figure the source does not break down.
Context
The scale is enterprise, but the principle holds at any size: useful campaigns start from clean data, not from the sending tool.

Fine & Country South Africa

South Africa·Premium residential real estate, 200+ employees

Platform: Bitrix24Qualitative result, no figures

Initial challenge
Market data, agent activity and transactions were dispersed; there was no single view for reporting.
What was implemented
Bitrix24 CRM plus its collaboration tools as a single point for data and reporting, with a local implementation partner.
Reported result
The source publishes no figures. The customer describes a major improvement in data availability and a comprehensive view of operations.
Context
An example of a real but unquantified outcome — exactly the kind of testimonial you should not read as a percentage promise.

IMTS Institute

India·Education and training, 80+ employees

Platform: Bitrix24Qualitative result, no figures

Initial challenge
Leads arrived from multiple sources, conversations were scattered across tools, and replies lagged — with enquiries getting lost.
What was implemented
Contact Center + CRM: enquiries from Google Ads, Facebook/Instagram forms, website forms, WhatsApp and phone all land in one flow.
Reported result
The source publishes no figures. The customer reports less lead leakage and faster response, tracking each applicant through to enrolment.
Context
The closest scenario to Moldovan reality: many messaging channels, a small team, and leads falling between them.

Vicasa International

Vietnam·Manufacturing and export (brewery by-products), 15+ employees

Platform: Bitrix24Qualitative result, no figures

Initial challenge
Data fragmented across time zones and regions, manual processes, and a previous system that could not keep up with growth.
What was implemented
CRM for customers and deals, plus workflow automation, in a single environment for an international customer network.
Reported result
The source publishes no figures. The customer describes full control over complex workflows and managing customers across several markets at once.
Context
A small company (15+ people) running export operations — a common profile in Moldova.

Easy CIP (Infinite-Data LLC)

USA·SaaS for the public sector (startup)

Platform: Bitrix24Qualitative result, no figures

Initial challenge
Long public-sector sales cycles, plus the need to avoid the compounding cost of several separate tools.
What was implemented
One environment for opportunities, calls with automatic logging, email campaigns, website chat and internal communication.
Reported result
The source publishes no figures. The founder describes strong value for money from consolidating tools into one configurable platform.
Context
The argument here is cost consolidation, not sales growth — a legitimate and very common motivation.

The benefits of a CRM, with the day-to-day example

A benefit stated in the abstract ("better efficiency") helps nobody decide anything. For each advantage below, here is the concrete moment where you see it.

Customer information in one place

Every conversation, quote, order and document sits on the same record, whichever channel it arrived on.

What it looks like in practice: A customer calls about an order from three months ago. The person who answers, having never spoken to them, sees in five seconds what was ordered, who handled it and what was promised.

Consistent lead follow-up

Every enquiry gets an owner and a next step with a deadline, so it stops depending on who remembers.

What it looks like in practice: Out of 40 enquiries in a month, the 12 who never replied to the first quote appear automatically on a follow-up list instead of quietly disappearing.

Pipeline visibility

At any moment you can see how many opportunities exist, at which stage, and worth how much.

What it looks like in practice: Mid-month it becomes obvious that "quote sent" is clogging up, and the team can act then rather than at the month-end review.

Automating repetitive work

Predictable tasks — reminders, notifications, document generation — run without anyone doing them.

What it looks like in practice: The contract is generated from data already on the record, instead of being typed into a Word template with the previous customer's details still in it.

Better coordination between teams

Handover from sales to delivery happens through the system, with full context, not through a chat message.

What it looks like in practice: The delivery team reads the negotiated terms directly in the deal and stops asking the salesperson what exactly was promised.

More consistent customer service

The quality of the answer depends much less on who happens to pick up the case.

What it looks like in practice: A customer writing on Telegram gets the same answer and the same timeframe as if they had phoned, because both channels land in one flow.

Reporting and forecasting

Reports are generated from activity already logged rather than assembled by hand.

What it looks like in practice: The monthly forecast is calculated from deal values by stage, and the gap against actuals can be analysed by cause instead of debated as an impression.

Less dependence on one person

The customer relationship stays with the company when the employee leaves.

What it looks like in practice: When a rep departs, their portfolio is reassigned with its full history, instead of being rebuilt through "hello, I'll be looking after you from now on" calls.

Integrated communication channels

Email, phone, chat and messaging arrive in the same place, tied to the customer.

What it looks like in practice: A conversation that started on WhatsApp and continued by phone shows up as a single thread on the customer record.

Mobile access

People working away from the office have the same data as those in it.

What it looks like in practice: A rep checks the customer history in the car before walking into the meeting, and logs the outcome immediately afterwards.

Control over the process

You can define what must be filled in, who is allowed to change what, and what happens at each stage.

What it looks like in practice: A discount above a set threshold requires the manager's approval before the quote can be sent.

Decisions based on data

Choices about budget, headcount and priorities can be checked against your own numbers.

What it looks like in practice: You notice that one channel delivers half the leads but under 10% of contracts — and move the budget accordingly.

Limitations and drawbacks worth knowing beforehand

This section exists because most failed CRM projects do not fail because of the software. If any of the points below describes your company, it is worth resolving before buying licences.

The upfront cost is not just the licence

On top of the subscription come process analysis, configuration, migration, integrations and training. A realistic budget includes all of it, not the per-user price alone.

It requires process analysis, not just installation

A CRM configured without understanding how the company actually sells will faithfully reproduce a process that does not work.

Team resistance is real and predictable

The system makes work visible, and that is experienced as control. Without explaining the benefit for each role, adoption stays nominal.

Training is not optional

A user who does not know where a call outcome is recorded will put everything in the comments field, and reporting becomes impossible.

Bad data stays bad after migration

Duplicates, contacts with no phone number and companies spelled three different ways transfer exactly as they are. Cleanup belongs before the import.

Over-customisation has a monthly price

Every extra mandatory field and every exotic automation adds entry time, maintenance cost and upgrade risk.

The outcome depends on configuration quality

The same platform can be excellent or unusable in two similar companies. The difference is how the structure was thought through.

Integrations are the least predictable part

A legacy system with no API, an outdated version or an on-premise install can make an integration far more expensive than it looks in the first conversation.

The system needs maintenance

Processes change, people change, and a CRM left untouched for two years becomes a collection of fields nobody fills in any more.

Responsibility for personal data stays with you

Centralising customer data also centralises obligations: lawful basis, access rights, retention periods, audit trails. The platform vendor does not take those on for you.

The risk of buying more than you need

Many features go unused for years. A smaller plan used fully is usually more valuable than a large plan used at a quarter of its capacity.

When a CRM is the right call

  • Several people work with the same customers and need shared context.
  • Enquiry volume exceeds what can be tracked manually.
  • The sales process has repeatable steps that can be described.
  • Management needs to see the situation without interrupting the team.
  • There is genuine intent to change how work is done, not just the tool.

When something simpler is enough

  • One person handles all customer relationships.
  • The number of active customers is small and stable, and deals are infrequent.
  • Selling happens in a single step, with no follow-up over time.
  • The company has no defined process yet — in which case the first step is the process, not the software.

Technology does not repair a broken sales process. If it is not clear who picks up an enquiry, how fast it must be answered, or what counts as a qualified lead, the CRM will make those ambiguities visible — which is useful — but it will not resolve them for you.

CRM vs Excel and manual work

Excel is not the wrong choice. It is an excellent tool for calculation and analysis and a weak one for tracking relationships over time, with multiple users. The comparison below shows where each one breaks.

CRM vs Excel and manual work
CriterionExcel / manual workCRM
Customer recordsOne row per customer, in files that multiply into versionsOne record with full history, shared across the company
Follow-up trackingDepends on memory, or a date column that notifies nobodyTasks with deadlines, assigned to an owner, with notifications
CollaborationOne file edited in turn or sent by emailSimultaneous access, with a trace of who changed what
AutomationFormulas and macros, dependent on whoever wrote themConfigured rules that run without anyone opening a file
PermissionsIn practice, whoever has the file sees everythingRights by role, department and data type
ReportingRebuilt by hand every periodGenerated from current data, at any time
Change historyUsually none; nobody knows who changed a priceA change log per record
IntegrationsManual copying between systemsConnections to telephony, email, messaging, invoicing
ScalabilityGets unwieldy past a few thousand rows and several editorsDesigned for volume and multiple users
Mobile useAwkward and error-proneA dedicated app with forms built for it
Error riskHigh: deleted rows, forgotten filters, partial sortsReduced by validation and structured fields
When an employee leavesThe personal file leaves with them, or stays without contextData stays with the company and can be reassigned

The honest verdict

If one person tracks a few dozen customers, a well-built spreadsheet is enough and cheaper. The difference appears with the second person, the second communication channel, and the need to know what happened three months ago. From there, the cost of manual work grows faster than the cost of a CRM.

What a CRM implementation looks like at Bsmart

The stages below map to the services we actually provide: audit and analysis, configuration and customisation, data migration, integrations, training and ongoing support. The order matters — skipping the first two is the single most common cause of failed projects.

  1. Business process audit

    We go through how an enquiry reaches the company, who picks it up, what happens at each step, and where time or information is lost.

    Output of this stage: A map of the current process, with the problem points identified.

  2. Requirements gathering

    We separate what is necessary from what is merely wanted, and agree what goes into the first phase.

    Output of this stage: A prioritised requirements list, with what is deferred clearly marked.

  3. CRM architecture

    We define the entities, the relationships between them and the data structure, so that the reports you want are actually possible.

    Output of this stage: An agreed system structure, before anything gets configured.

  4. Pipeline and field configuration

    We build the real sales stages and only the fields that are genuinely needed, in the company's own vocabulary.

    Output of this stage: A usable CRM in which the team recognises its own way of working.

  5. Automation

    We add the rules that remove repetitive work: tasks, notifications, escalations, document generation.

    Output of this stage: Live automations, documented and reversible.

  6. Integrations

    We connect telephony, email, messaging and website forms, and where technically feasible the invoicing or accounting systems.

    Output of this stage: Communication channels reach the CRM without manual entry.

  7. Data migration

    We clean, deduplicate and import the existing data from Excel or the previous system, and validate it after import.

    Output of this stage: A verified database, not merely a transferred one.

  8. Permissions and security

    We set who can see and who can change each type of data, including from a personal-data standpoint.

    Output of this stage: Roles and rights configured, with least-privilege access.

  9. Testing

    We run the real scenarios, with real users, before go-live.

    Output of this stage: Configuration errors are fixed before they reach customers.

  10. Team training

    We train by role: a salesperson needs something different from a manager or a support agent.

    Output of this stage: The team knows exactly what to do in the system, daily.

  11. Launch

    We move into real use, with close support during the first weeks, when most questions surface.

    Output of this stage: The system becomes where work happens, not a parallel ledger.

  12. Post-launch optimisation

    We revisit the configuration based on how it is really used and on processes that have changed since.

    Output of this stage: A system that stays useful past the first year.

Do you need a CRM? An 8-question assessment

An indicative assessment that can absolutely come out as "you do not need a CRM right now". Nothing is sent anywhere: the calculation runs in your browser and the result appears immediately, with no form to fill in.

Question 1 of 8

How many new enquiries or leads do you receive per month?

Estimator: what manual work costs, in your own numbers

A simple arithmetic calculation on your data. It is not a forecast and it uses no "industry averages" — we have no verified source for one, so we do not invent one.

Gross salary plus contributions, divided by hours worked.

Hunting for information, copying between files, manual reporting, re-entering data.

Margin may be more relevant than gross revenue — use whatever helps you decide.

Estimate

86.7 hours of manual work per month, in total · 1.5 leads recovered per month

Value of recovered time
3,467 MDL per month41,600 MDL per year
Value of recovered leads
1,800 MDL per month21,600 MDL per year
Estimated total
5,267 MDL per month63,200 MDL per year

Assumptions and formulas used

  • A month has 52/12 ≈ 4.33 weeks.
  • We assume automation can remove 50% of the manual hours you entered — not 100%, because some manual work remains.
  • We assume 10% of leads are currently lost to missed follow-up, and that a tracking system would recover a quarter of those.
  • Recovered leads convert to sales at 20%.
  • Costs are excluded: licences, implementation, training, maintenance. The figure is gross, not profit.

Formulas

  • Recovered time = employees × hours/week × 4.33 × 50% × hourly cost
  • Recovered leads = monthly leads × 10% × 25%; revenue = recovered leads × 20% × average value

The figures above are an arithmetic estimate from the data you entered, not a promise of financial results and not financial advice. The percentages in the assumptions are deliberately conservative working values, not statistics.

Frequently asked questions about CRM use cases

Questions strictly about applying a CRM in practice. For costs, timelines, platform comparisons and Bitrix24 specifics, the detailed answers are on the FAQ page.

Which businesses gain the most from a CRM?

Those where several people work with the same customers, the sale takes several steps, and customers come back over time. If a sale closes in a single interaction with no follow-up, the gain is far smaller.

Is a CRM useful for a five-person company?

It can be, if those five talk to the same customers across different channels. It largely is not, if one person handles sales and keeps tidy records. Team size matters less than the number of places where information can be lost.

How do I know the problem is the lack of a CRM and not something else?

A practical test: take five customers you lost in recent months and try to reconstruct what was discussed with each. If you cannot, the problem is record-keeping. If you can and still lost them, the problem is in the offer, the price or the process — and a CRM will not fix that.

Can a CRM work in Romanian and Russian at the same time?

Major platforms, Bitrix24 included, offer multilingual interfaces, and each user can work in their own language. Email templates and documents are built per language, so this requirement belongs in the configuration from the start.

Can the CRM be connected to telephony?

Yes, and it is usually one of the first worthwhile integrations: the call is linked to the customer record, can be recorded, and the outcome is logged in a structured way. Actual feasibility depends on your provider and PBX type, so it is verified technically before it is promised.

Can data be migrated from Excel?

Yes, but a useful migration means cleaning before importing: removing duplicates, standardising names and filling required fields. Importing straight over a messy database moves the problem rather than solving it.

What are the biggest risks in a CRM implementation?

In order of frequency: no defined process before configuration, no involvement from the team that will use it, migrating poor-quality data, and over-customisation that makes daily use burdensome.

What is the difference between buying a CRM and implementing one?

Buying gives you access to the platform. Implementation means process analysis, data structure, configuration, integrations, migration and training. An account that is opened but not configured is, in practice, an expensive spreadsheet.

Can a CRM be adapted to a specific industry?

Yes, through custom entities and pipelines: the property for real estate, the vehicle for a garage, the policy for insurance. That kind of adaptation changes how the team understands the system more than any additional feature.

Does a CRM replace employees?

Not in relationship work. It removes repetitive work — hunting for information, copying between files, manual reporting — and moves that time towards talking to customers. Expecting to cut headcount right after implementation is generally unrealistic.

How does AI work inside a CRM?

In practice: transcribing and summarising calls, suggesting the next step, drafting replies and classifying requests. The output depends on the quality of the existing data, and its suggestions need a human check before they reach a customer.

How much of the result depends on the team versus the platform?

Mostly the team. The right platform, badly configured and unused, produces nothing. An average platform configured around the process and used daily does. That is why training and adoption are project stages, not formalities.

Sources and methodology

How the case studies were selected

  • We only included examples published by the original source: the CRM vendor or the organisation that ran the implementation.
  • We excluded aggregators, reseller blog posts, and "top CRM results" listicles with no primary source.
  • We kept the figures exactly as they appear in the source. Where the source publishes no figures, we say so explicitly rather than estimating.
  • We noted who reports the result. Most are case studies published by the platform vendor, so they are that vendor's marketing material.
  • We removed market statistics we could not trace to a verifiable primary source, even where they are widely quoted online.

Why results vary

The same features produce different results in different companies. Team size, initial data quality, usage discipline, integration complexity and management support influence the outcome more than the choice of platform. None of the examples on this page should be read as an expected result for your company.

Author and review

Written and reviewed by the Bsmart team, which implements Bitrix24 and custom CRM solutions for companies in the Republic of Moldova.

Content and sources last reviewed:

Continue with

Talk through your company's processes with a specialist

A first consultation at no cost, where we look at how enquiries reach you and where they get lost. If the conversation shows you do not need a CRM right now, we will tell you so.

What happens after you send the form

  1. Bsmart receives and reviews your request.
  2. A specialist contacts you to arrange a conversation.
  3. Together we look at your current process: where enquiries come from, who picks them up, where they are lost.
  4. You receive a recommended implementation direction, with the stages and what each involves.
  • Free initial consultation, no obligation.
  • Conversation in Romanian or Russian, your choice.
  • An honest recommendation, including "you do not need this yet".
  • A local team, based in Chișinău.

+373 790 239 00info@bsmart.md

Request the consultation

B
Bsmart Assistant
Online