Choosing a CRM when you have no IT department
The feature list is not the decision. What matters is whether you can change stages, rules and permissions without filing a ticket.
Most CRM evaluations end in a spreadsheet comparing features, and that spreadsheet almost never decides anything useful. Every mid-market CRM captures leads, stores contacts, shows a pipeline and sends email. If you are a fifteen-person company without a systems administrator, the feature list tells you what the software does on day one. What you actually need to know is what it costs to change on day ninety.
The default pipeline is somebody else’s sales cycle
Open any CRM and you will find stages named Lead, Qualified, Proposal, Negotiation, Closed Won. That sequence describes how software is sold. It does not describe a tool exporter who ships a sample, waits five weeks for a factory trial, and only then talks price. Forced into the vendor’s stages, your reps will park every live deal in “Negotiation” for a month, and your pipeline report becomes fiction.
OneHash lets you define the stages, which is a small thing until the day you need a sixth one. The same applies to fields: the two or three pieces of information that actually predict whether your deals close — plant capacity, tender deadline, the distributor who introduced you — belong on the record, not in the notes box.
Routing rules matter more than routing
Most CRMs offer round-robin lead assignment, and for most Indian SMBs round-robin is the wrong answer. Accounts have history. The rep who lost this buyer eighteen months ago on delivery time is the one person who knows what to say now. OneHash assigns leads automatically by rule, and by hand when it matters — and the second half of that sentence is the part that keeps sales managers using it rather than working around it.
The real test: who builds the report
Ask the vendor how a sales manager gets a number that nobody anticipated — margin by territory for the last two quarters, excluding one distributor. If the honest answer involves a support ticket, a consultant, or a paid professional-services day, you have not bought a reporting system. You have bought a request queue.
OneHash builds reports and dashboards without a developer. That constraint is worth more than any individual feature, because the questions a growing business asks change faster than any vendor ships.
Permissions are an operational problem, not a security badge
At ten people everyone sees everything and it is fine. At forty it is not: you have interns, contractors and a rep who is quietly interviewing elsewhere. OneHash gives you roles, permissions and approval chains you set yourself, so people see the records they work on and not the rest. What happens to the data itself is set out in the privacy policy rather than claimed here.
Buy the one you could leave
OneHash is built on ERPNext and Frappe, which are open source, so your data is exportable and the schema is readable. This sounds like a philosophical point and is a practical one: the CRM you can walk away from is the one you will not spend three years quietly resenting. It also means the customisations you make are yours, not a proprietary scripting language nobody else hires for.
Work through what to check before you commit, then open the live demo and try to break your own process in it. Change a stage. Add a field. Build a report nobody asked for. Whatever takes ten minutes there will take ten minutes in a year. Plans are on pricing.