Lead distribution automation is a logical stage in the development of any sales department implementing an ERP system (CRM). However, in practice, this functionality often becomes a "bottleneck" that creates administrative barriers instead of accelerating work.
Often, a commercial director dreams of "fairness." For some, this is a kind of "commercial socialism" in distribution, although the absolute majority is still guided by reasonable criteria. However, such oddities occur periodically.
The Problem: The Trap of "Smart" Distribution.
When a company outgrows Excel, it wants the CRM system to decide for itself exactly whom to hand a client to. A typical scenario involves implementing complex distribution criteria (by traffic channels, regions, or industry specifics). The goal is to direct the client to the most appropriate specialist. However, later, an accumulation of requirements begins: "If a client from the IT sector with a turnover of over 100 million came on Thursday afternoon and their request contains the word 'server', give it only to Oleksiy; but if Oleksiy is busy — then to Dmytro, provided that Dmytro's KPI is above 90%".
Mostly, requirements are simpler, for example: we give all new leads from social media to Oleksiy, and leads from another site and incoming emails to Olga. Immediately, proposals arise to distribute leads by customer countries.
To prevent managers from being jealous of their colleagues' work, a requirement appears — to hide all leads from other employees so that everyone is happy, no one feels offended, and everyone sees only their own inquiries. Everything looks logical, the system works, and everyone is satisfied.
On paper, this seemed like an orderly structure that excluded errors. However, in real-world sales conditions, it turns out that an individual manager still needs to be granted the right to redistribute leads.
Eventually, it turns out that all leads should be accessible to everyone, because in practice, managers often pass them to each other. If they do not have the appropriate rights, this forces them to perform unnecessary actions and ask the administrator to grant access to a specific lead.
As a result, the lead distribution system, which consisted of 5 rules, was reduced to zero in practice. The company decided to completely cancel the settings: open access for everyone and return to the "general queue" model with the possibility of manual distribution. Of course, the question arises: why spend effort on forming a distribution system if, in practice, no one used it?
This is a typical situation where a leader's vision of an ideal system diverges from the realities of the team's work. Of course, all this could have been clarified during the Discovery stage, but it is not the developers who decide exactly how the company should work, so the customer's wish is law. Additionally, at the start, the customer's main question often concerns how to preserve the database so that a manager does not steal clients, rather than how to simplify the sales process.
The best approach in such a situation is minimalism at the start. It is worth copying the system in its current form without complex rules and introducing complications only when manual management truly starts to slow down sales.
It is important to verify every rule, for example, with the following questions:
- "What will we do if the responsible manager is unavailable for 4 hours?".
- "What happens if a lead arrives on Sunday (during non-working hours or on Easter)?".
- "What happens if a lead writes to another communication channel (for example, sends an email instead of Telegram)?".
- "Are there exceptions for VIP clients or repeat inquiries that should bypass the general distribution logic?".
- "What is the acceptable 'fairness' error: are you ready for the fact that due to different quality of inquiries, one manager will receive 10 target leads, while another — 10 spam calls with the same quantitative distribution?".
Analysis of various scenarios will help the client orient themselves and consider alternatives or even refuse unnecessary automation.
In turn, the Odoo system allows you to test different scenarios, for example, lead distribution, and not dive into deep development. Odoo supports the "Fail Fast" strategy ("fail fast and cheap"). Thanks to basic functionality, a company can test different versions of sales department settings just a week after starting. If a new scheme turns out to be ineffective or too complex, it can be turned off with one click, saving the budget for more significant tasks.
Odoo provides an evolutionary approach, and its modularity allows a business to grow organically. You can start with manual lead distribution, later set up automation by source (social media, email, calls), and even later — implement distribution by manager workload. The system does not require a complete rebuild: you simply add new levels of complexity as your business develops.
Automation should remove obstacles, not create new ones. Sometimes the best decision in IT is a conscious refusal of unnecessary functions in favor of the team's work speed.