Picture a mid-sized factoring company in Istanbul: 287 employees, a portfolio of roughly four hundred active SME clients — most of them suppliers in the textile and food sectors transferring receivables — and a client management team that cannot agree on where the notes from the last customer meeting are stored. Getting a single client’s limit history means sending separate e-mails to credit risk, operations and accounting. Management’s instinct is to buy a CRM system and fix the problem. The reasoning sounds solid. But the problem here is not the software — it is the process itself. Buying a CRM accelerates a disorganised workflow; it does not correct it. That is the central argument of this article: CRM projects in factoring companies are routinely executed in the wrong order, and that wrong order produces systems that work technically but deliver nothing operationally.Factoring is, at its core, a business of trust and information. Taking over a client’s receivables and advancing funds against them requires knowing that client’s commercial behaviour, sector dynamics, and the payment habits of their debtors. Unlike corporate banking, the factoring relationship is typically shorter in tenor, more repetitive in rhythm, and far denser in operational contact: from limit requests and collection follow-ups to dispute resolution and renewal conversations, a client manager touches the same company on different topics several times a week. That contact density explains why centralising information is so critical. But centralisation is a software problem only after the question of what information needs to exist has been answered — and that question belongs to process design. Most factoring companies conflate the two and launch projects before the distinction is clear.Before any CRM project begins, three foundational questions must be answered honestly. First: what information does the client manager record, when, and for what purpose? Second: where does that information currently live — in a spreadsheet, an e-mail archive, or a handwritten notebook? Third: do risk, operations and sales generate this information independently, or do they read the same data set from different angles? Without answering these questions, the CRM implementation does nothing more than move existing disorder onto a screen. Consider a representative scenario: a factoring company based in Ankara, serving predominantly construction-sector clients, discovers that its sales team logs meeting notes into the CRM consistently while the credit risk team never updates client limits in the same system. The result is that a client manager looks at the system, quotes against an outdated limit, and gives the client inaccurate terms. The failure is not in the software — it is in the absence of a process that defines who owns which data point.The most critical integration point in factoring CRM is the connection to limit and risk data. What a client manager genuinely needs to see in a CRM is not just meeting dates and proposal notes, but the client’s utilised limit, overdue receivables, debtor concentration, and sector-level risk score. All of this typically lives in separate systems: accounting software, risk modelling tools, and operational tracking sheets. Without integrating those sources, the client manager still has to open four different screens before walking into a meeting — which is exactly the problem the CRM was supposed to eliminate. This integration challenge is as much a political problem as a technical one. The credit risk team is reluctant to expose its data; the sales team wants real-time access to limits; operations prefers to work independently of both. A CRM project launched without resolving these conflicts divides as much as it unifies. Addressing the ownership and sharing questions before defining the integration architecture substantially improves the probability that the project will actually be used.User adoption deserves its own discussion in the factoring context. Client managers typically spend their most productive hours in the field or on the phone — they tend to view data entry as a bureaucratic obligation that competes with billable relationship time. This is CRM’s natural enemy, because the value of any CRM is a direct function of data quality, and data quality is a direct function of input discipline. The pattern I have observed repeatedly: entry frequency is high during the first six weeks of a CRM rollout, sustained by project-team pressure and management attention. By the seventh week it begins to fall. By the fourteenth week, the system is being used regularly by fewer than a third of the people who were entering data at launch. This pattern is not unique to factoring, but the consequences are sharper here: a client manager who stops entering data makes their entire portfolio invisible to colleagues, and client handovers become chaotic. The solution is not a better interface — it is making the entry of a meeting note a mandatory step in a defined process. That requires management discipline and measurement, not software configuration.Management expectations belong in this equation too. A general manager or sales director typically wants two things from a CRM: visibility into what client managers are doing in the field, and a way to measure the opportunity size within the portfolio. Both are legitimate. But the sequence matters enormously. Visibility only becomes meaningful once data discipline is in place; data discipline is only achievable once process design is complete. If management wants CRM reports to be accurate, the prior questions — who enters what data, on what schedule, validated by what criterion — must be settled first. Skipping those questions produces a situation where, six months into the project, the dashboards are empty. The software is running. The data is not there. Factoring companies reach this point more often than most would admit, largely because software selection happens before process mapping. The vendor runs a demo, a decision is made, and the process questions surface in week two of implementation — when it is already late to change direction.For a manager preparing to launch a CRM project in a factoring company, the practical starting point is this: spend one week observing what one of your client managers actually does in the field. Watch what information they collect, where they record it, and what data drives their decisions. Draw that information flow on paper. Complete that map before selecting a system. The software should be the digital expression of that map — and you are the one who builds the map, not the vendor. Concretely: run a three-day workshop with your client managers and ask each person to write down, step by step, what they do in the 48 hours following first contact with a new client. If the answers differ significantly from one person to the next, standardise the process first. Then buy the CRM. When companies reverse that order — and most do — the system goes live and sits unused. That looks like progress from the outside. It is not. In factoring, that outcome is far more common than the industry cares to acknowledge.
This article was originally published in Turkish by Gökhan MERCANOĞLU on January 20, 2009. The English edition has been reviewed and edited by the author.