There is a gap between buying a CRM system and actually using one, and most companies in Turkey lose years without ever noticing. They install the software, run user training sessions, and enter the entire customer list. A few months later you walk in and the sales team is back to their notebooks, the owner is still making decisions from memory, and the software is running in the background untouched. I call this ‘showroom CRM’: it looks present, but it does nothing. That is precisely the problem this article addresses. CRM localization in Turkey is not about translating menus. The real work is embedding Turkey’s specific customer relationship logic — the credit culture, the holiday visit tradition, the owner-to-owner meeting habit — directly into the system. Projects that skip this step turn into shelf decoration within months.Last year I worked with a wholesale distribution company in Izmir with around 378 employees. The firm supplied raw materials to the textile and garment sector, with a customer base of small and medium workshops in Bursa, Denizli, and Kahramanmaras. The owner had purchased a Turkified version of a foreign CRM package. The interface was clean: customer cards, visit logs, quote tracking. But more than half the sales team had effectively stopped using the program within the first three months. Why? Because the software asked for ‘visit’ records, but this company’s customer relationships did not begin when an invoice was issued. They began a month earlier, when someone called to ask ‘how are things, how does the season look?’ Where were they supposed to enter that phone call? There was no field for it. The program did not know the language of that relationship.At that point most consultants say ‘increase user training.’ I have been seeing the opposite for years: it is not a training problem, it is a design problem. Customer relationships in Turkey do not resemble what Western software designers call ‘account management.’ In Turkey, a customer relationship runs like a network built on continuity and trust. That network has its own rhythm: a check-in call before Ramadan, a holiday visit, a conversation about advance payment at the start of the season, a message during a crisis saying ‘please hold on, do not close your account with us.’ A CRM system that does not recognize this rhythm becomes a meaningless bureaucratic burden for the sales team. Nobody carries that burden willingly. If they do carry it, the data they enter is unreliable. Unreliable data means the reports coming out of the CRM give the owner a false picture.So what does CRM localization for the Turkish market actually mean in practice? I see three essential axes. The first is the data model. A customer record in Turkey is not just ‘company name plus tax number.’ Knowing the owner, recognizing his wife, noting where he holidays — these are part of the relationship. The system must have fields where this information can be entered. At the Izmir firm we solved this by expanding the ‘customer note’ field and allowing free-text input. The sales team started using it immediately. Having the field was the first step. The second axis is communication type. Standard foreign CRM software recognizes ‘meeting, email, phone call’ as interaction types. In Turkey you need to add ‘coffee invitation, holiday greeting, workplace visit, referral conversation.’ Without these additions, the bulk of what the sales team actually does remains invisible in the system. The third axis is payment and credit tracking. Credit sales are still a relationship tool in Turkey. Does the customer buy on credit, for how long, has payment been late — this information must be connected to the accounting module inside the CRM. If it is not, the sales person is building the relationship forward while the finance department is raising alarms, and a manager has to step in to resolve the confusion. The process breaks.That said, this localization has limits, and it is worth naming them clearly. Putting everything into a system is not always right. In a small sales team — say eight or ten people — where the owner already holds every customer in his head, the extra data-entry workload can easily outweigh the real benefit. In that case the CRM’s function should be narrowed: it should handle quote tracking and collection reminders, not the entire relationship. Trying to put everything in often ends with nothing going in at all. At the Izmir firm we struck exactly this balance: we left sales notes free-form, made quote and order tracking mandatory, and kept everything else optional. That trade-off was the reason the project survived past the six-month mark.The owner-led decision structure is a separate localization challenge. In foreign CRM software, the sales representative manages his own customers and the manager only sees reports. In Turkey, the owner frequently takes over conversations with key customers directly, or at minimum expects to be informed at every step. The system must be configured for this: a ‘critical customer’ flag, a notification path (in 2004 this usually meant a printed alert or a phone call rather than any automated push notification inside the software), and two separate views — one for the sales team, one for the owner. Projects that skip this setup slide into chaos where the owner tries to use the system in his own way, edits records the sales team entered, and nobody knows who logged what. The data falls apart.Before starting a CRM project in Turkey, three questions must be answered. Who currently manages customer relationships, and how — in a notebook, in someone’s memory, or in a separate accounting program? What information will the sales team refuse to enter into the system, and why? What does the owner want to see, and how does he access that information today? Answering these three questions before selecting software is not optional. Starting without them is like ordering shoes without measuring the foot: they might fit, but the odds are against it. CRM localization for the Turkish market is not a technical matter. It is a matter of understanding how relationships are actually built here. Projects that grasp this move forward. Projects that skip it become shelf decoration.
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 29, 2004. The English edition has been reviewed and edited by the author.