ServiceNow is the platform enterprises buy, and it is genuinely capable of modelling almost any process an organisation could want — which is exactly the problem for a mid-market buyer. The implementation effort and licensing cost are built around large, complex estates with dedicated administrators, and a fifty-person company adopting it is usually paying for capability it will never configure, let alone use.
Freshservice sits at the other end: fast to deploy, priced per agent in a way that a mid-market IT team can justify, and covering incident, request, asset and change management out of the box without needing a consultant to configure it. Its limitation is depth — organisations with genuinely complex, multi-tier approval chains or heavy integration requirements will eventually find its configurability runs out.
Jira Service Management is the natural choice for a company already running Jira for engineering, because tickets can flow between development and support without a separate integration project, and the same people managing your software backlog can administer the service desk. Its weakness is that it was built as an extension of a software development tool, and processes that don't map naturally onto that model — physical asset tracking, for instance — feel bolted on.
The honest selection criterion for most Indian mid-market companies is not features, it is who will administer the tool. If nobody has time to become a ServiceNow administrator, ServiceNow is the wrong choice regardless of what it can theoretically do. Pick the tool whose complexity matches the person who will actually configure and maintain it, and revisit the decision when that person's capacity changes rather than before.
