What breaks at forty people that didn't at ten
Lead routing, pricing history and pipeline visibility all fail quietly between ten and forty people. What to fix, and in what order.
At ten people, the company runs on overhearing. You know which deals are live because you sit near the person working them. Nobody needs a system, and anyone who tells you otherwise is selling one.
The reason to install one anyway is that the failure comes late and all at once: somewhere past twenty-five people the overhearing stops working, and by the time it is obviously broken you are fixing it while also hiring. Here is what breaks, roughly in the order it does.
Routing stops working before anyone notices
Ten people: an enquiry lands, someone says “I’ll take it”, the room hears. Forty people across two offices: two reps work the same account for a week, or nobody does. There is no moment when this changes — it degrades.
OneHash CRM puts leads from web forms, email, calls and campaigns into one queue and assigns them by rule, or by hand when the account has history. The point is not automation. It is that ownership is written down somewhere other than in the memory of whoever was in the room.
The person who remembers the pricing leaves
Every small company has someone who knows what you quoted a given buyer in 2023 and why they said no. Nobody has put a value on that knowledge, and it leaves with a resignation letter.
Once quotes and orders live on the customer record, the history survives the person: a new rep opens the account and sees the sample sent, the price rejected, and the order that came through eighteen months later.
Your forecast starts describing the past
The Friday spreadsheet works while the person filling it in has touched every deal himself. With four reps it becomes a summary of what four people remembered on Friday afternoon, reviewed on Monday, about a week that ended three days ago.
Targets by territory, product, partner or rep only mean something when the numbers move with the deals. A manager should see who is behind plan mid-month, while there is still a month to act.
Everyone seeing everything stops being fine
At ten people, open access is a feature: it is faster and nobody abuses it. At forty you have contractors, interns, a new hire on probation and a rep who is interviewing elsewhere, and your cost prices are in the same file as your customer list.
Roles, permissions and approval chains you configure yourself are what make growth survivable here — not because your people are untrustworthy, but because “who signs off on a discount” becomes a real question the moment the founder is no longer in every conversation.
The processes you invented at ten do not fit at forty
This is the argument for configurability over features. The stages that described your sales cycle at ten people will be wrong at forty, once you have added a channel, a second product line or a pre-sales step. A CRM whose stages, fields and approval chains you cannot change yourself gets worked around instead — in spreadsheets, on WhatsApp, exactly where you started.
Keep the exit open
OneHash is built on ERPNext and Frappe, which are open source, so the data is exportable and the schema is readable — worth comparing against a closed alternative like Odoo. Webhooks and a REST API connect it to whatever else you run, and the integration library covers mail, calendars and payments without custom work.
That matters more at forty people than at ten, because by then a migration is not a weekend.
What to do first
Not a phased rollout plan. One thing: put lead capture and ownership in one place before you next hire two salespeople. Reporting, permissions and automation can follow, and are easier once the records exist. The mistake is waiting until the system is obviously needed — that is the same quarter you are least able to install one.
Try the live demo with your own pipeline, or talk to us about what a move from spreadsheets actually involves.