When a customer's latest quote sits in a sales representative's email, their complaint in a call center's spreadsheet and their payment status in accounting, answering a single question about that customer means asking three people. The question "What is CRM, and what is it for?" usually comes up once this fragmentation is noticed.
In this article, we explain CRM through the vendors' own definitions, outline which tasks it brings together, report the current usage rate in Türkiye, cover CRM system examples by type, and focus on how process, data and ownership can be handled during setup.
What is CRM?
CRM is the abbreviation of Customer Relationship Management and is rendered in Turkish as müşteri ilişkileri yönetimi. According to Microsoft's definition, CRM is the combination of the strategy, processes and technology that organizations use to manage relationships with customers and prospects across marketing, sales and service.
The same source makes an important distinction: CRM is the name of the overall approach, while a CRM system is the software platform that puts that approach into practice. In short, a "CRM program" is a tool, but CRM itself is a decision about how to work with customers.
What is CRM used for, and which tasks does it bring together?
According to Oracle's explanation, a CRM system brings together, links and analyzes all the customer data it collects, such as contact details, conversations with representatives, purchases and service requests. Zoho likewise describes CRM software as a data repository that unites sales, marketing and customer support activities.
In practice, a CRM system usually brings together the following tasks:
- Customer and prospect records: company, contact person, contact details and past conversations.
- Sales tracking: opportunities, quotes, stages and reminders.
- Marketing: campaigns, lists and the inquiries that come in from campaigns.
- Service and support: requests, complaints and resolution times.
- Reporting: views of the sales funnel, conversion and team performance.
Its relationship with ERP should also be noted. As covered in the "What Is ERP?" article, ERP keeps the organization's internal record from the order through to accounting, while CRM focuses on the customer relationship before and after the order. When the two systems share the same customer record, data does not have to be entered twice.
CRM usage rate in Türkiye
According to the ERP, CRM and BI dynamic table within the Information Technology Usage in Enterprises Survey, 2026 that TÜİK (the Turkish Statistical Institute) published on September 10, 2026, the 2026 figures for enterprises with at least 10 employees are as follows:
- Overall: 13.6% of enterprises use CRM software.
- By size: the rate is 11.4% among enterprises with 10–49 employees, 20.3% among those with 50–249 employees and 46.2% among those with 250 or more employees.
- By activity (examples): 48.4% in finance and insurance, 44.4% in information and communication services, 16.0% in wholesale and retail trade, 13.6% in manufacturing and 6.0% in construction.
In the same table, the ERP usage rate is 32.3%. In other words, the number of enterprises using CRM in Türkiye is, proportionally, less than half of those using ERP. The fact that the rate does not reach half even among large enterprises indicates that a significant share of customer information is still kept in email, spreadsheets and personal notes.
CRM system examples by type
Understanding the type before the product name makes the choice easier. The product names below are given only to illustrate the type and in the vendor's own description; they are not a ranking, a comparison or a recommendation.
By function. Both Microsoft and Oracle commonly group CRM systems into three types: operational CRM (the day-to-day running of sales, marketing and service work), analytical CRM (reporting on and interpreting customer data) and collaborative CRM (sharing customer information across teams). Most products offer these three functions together, with different emphasis.
By focus area. Some products focus on a specific team. For example, Microsoft positions Dynamics 365 Sales as a CRM for sales teams. Others serve several teams under one roof: HubSpot describes its CRM as a product that supports customer support, sales and marketing together, and Zoho CRM presents itself as an online CRM solution that brings customer operations together on a single platform.
By licensing and package model. Odoo describes its CRM app as an open-source sales tool. With products of this kind, CRM can also be used as part of the same package as the same vendor's ERP, accounting or inventory apps; building an integration between a separate CRM and an ERP is the other option.
Which type is suitable depends on the number of customers, the length of the sales cycle, how the teams work and the existing systems.
Proper setup: process, data, ownership
The same Microsoft page also emphasizes that successful CRM implementations depend on data quality, governance and employee adoption. Oracle, for its part, lists typing errors, duplicate customer records and information that changes over time among the sources of bad data. From Orient Global's perspective, these findings can be turned into four preparations:
- Write down the process first. Define together with the teams where a request comes from, which stages it passes through and when it will be counted as "won" or "lost." A sales process with unclear stages stays unclear in the CRM, too.
- Clean the data before migrating it. When merging customer lists from scattered spreadsheets, weed out duplicate records, missing fields and variant spellings. Decide up front which fields will be mandatory.
- Assign ownership. Every customer record, every opportunity and every shared field (such as industry, region or customer type) should have someone responsible for it. Put in writing who will create a record and who will change it; this habit does not last without data governance.
- Think about personal data from the start. Information about individuals in a CRM is personal data. Article 4 of Law No. 6698 (Türkiye's Personal Data Protection Law) lists as principles that personal data be accurate and, where necessary, up to date, that it be processed for specified purposes, and that it be kept limited to those purposes. Which fields are kept and why, and for how long they will be stored, should be part of the setup.
A few simple indicators are also enough to measure adoption: what share of the records is up to date, what share of the opportunities is tracked through the CRM, and whether reports are still prepared from separate spreadsheets.
Frequently asked questions
Is a CRM program only for the sales team? No. According to Microsoft's definition, CRM brings marketing, sales and service teams together around the same view of the customer. Sales tracking is often the starting point, but it is not the only use.
Are CRM and ERP the same thing? No. ERP manages an organization's internal processes (finance, inventory, purchasing, production) with shared data, whereas CRM focuses on the relationship with the customer. The two systems complement each other and are usually integrated so that they share the same customer record.
Does a small business need a CRM? According to TÜİK's 2026 data, 11.4% of enterprises with 10–49 employees use CRM. What matters is not size but how many people and how many channels the customer information is spread across.
What is AI useful for in CRM? Vendors are increasingly adding AI features to their CRM products. Taking an inventory of these features in existing systems before buying a new tool is covered in the article on embedded AI; measuring results in sales and marketing is the subject of a separate article.
Conclusion
CRM is an approach that moves customer-related information out of individuals' email and spreadsheets and into the organization's shared record. The TÜİK data shows that usage in Türkiye lags behind ERP and rises markedly with company size. Choosing a product matters, but the success of a setup is most often determined by a defined sales process, clean data, clear ownership and care shown for personal data from the start.
Why logistics experience matters here. The scattered-record problem this article opens with is familiar in logistics and distribution, where a single customer's quote, delivery exception, service request and payment status can sit with sales, warehouse, transport, technical service and finance at once. Requests, complaints and resolution times, the service-and-support item in the list above, are daily business in a warehouse or technical-service operation, and the four preparations are ordinary operations discipline there: agreed stage definitions, clean master data before anything is moved, a named owner for every record and hand-off, and care over the recipient names, addresses and phone numbers that delivery work puts on file. One of our consultants brings more than 30 years in operations, logistics and supply chain: at a technology distribution company of roughly one billion dollars in scale, he ran logistics, warehousing, technical service and administrative operations end to end, building and leading teams of 100+ people and delivering lasting gains in operational performance through KPI-driven programs. He has also managed nationwide warehouse and transport operations at leading retail, logistics and distribution organizations. An industrial engineer, he now brings that supply-chain discipline to SMEs through AI and automation. Meet our consultants.
This article is for general information only; product names are given solely as examples and do not constitute a recommendation.
#interimmanagement #forwarddeployedengineering