This question is usually asked the wrong way round. A promoter decides it is time to “do something about HR”, and the choice presents itself as software or a consultant — a product or a person, a licence fee or a professional fee. But the two are not alternatives. They do different work, and the reason the decision feels difficult is almost always that the underlying problem has not been named yet.
The question behind the question
Software encodes a process. A consultant defines one. If you already know precisely what your appraisal cycle should look like, who owns which outcome, and what each role is measured on, then what you need is somewhere to run it — and that is software. If you cannot answer those questions in a sentence each, software will simply digitise the confusion, at speed and at cost.
The uncomfortable version: buying an HRMS before defining what good performance looks like is paying to automate a decision you have not made. It is also the single most common sequencing error we see in MSMEs, and it is expensive twice over — once for the licence, and again for the year spent concluding that the system did not work.
A test you can apply this afternoon
Take any three roles in your organisation. For each one, write down: the three outcomes that role exists to deliver, how you would know whether each was achieved, and where that evidence lives today.
If you can complete that for all three roles in under an hour, your definitions are sound and your problem is administrative — you need a system. If you find yourself guessing, or discover that two roles both claim the same outcome, or that the evidence lives only in someone’s memory, your problem is definitional. No software resolves that.
Most promoters who run this test are surprised. The exercise sounds trivial and turns out not to be, and that surprise is itself the answer.
What each one is actually for
| Software | A consultant | |
|---|---|---|
| Solves | Administration, record-keeping, workflow, visibility, compliance | Definition, structure, sequencing, difficult conversations |
| Good when | The process is agreed and the pain is manual effort | The process is unclear, contested, or has never been written |
| Fails when | Applied to an undefined process — it hardens the confusion | Applied to a well-defined process — you are paying for what you already know |
| Cost shape | Recurring, predictable, scales with headcount | One-off or project-based, front-loaded |
| What you own afterwards | A system, and a dependency on the vendor | A framework, and the capability to run it |
| Timeline | Weeks to implement | Weeks to design, then a cycle to prove |
Four situations, and the honest answer for each
You have 40 people, everyone reports to the promoter, and payroll is the pain
Buy software. There is no structural problem to solve; you have an administrative load and a founder’s time being consumed by it. A basic HRMS pays for itself quickly here and you do not need a consultant to tell you that.
You have 150 people, appraisals happen, and nothing changes as a result
Consultant first. Appraisal machinery already exists, so more machinery is not the answer. Something is wrong with what is being measured, or with the conversation, or with whether anyone acts on the outcome. Software will make an ineffective process faster.
Promotions cause resentment and you cannot explain the basis
Consultant first, and it is urgent. This is a definitional problem with a retention cost attached, and every cycle you run without fixing it compounds. See rolling out KRAs for what the fix involves.
You know exactly what you measure, but it lives in eleven spreadsheets
Software, without hesitation. Your definitions are sound and your problem is genuinely administrative. The switching thresholds are set out in HRMS vs spreadsheets.
When the answer is neither, yet
There is a fourth answer nobody sells, and it is sometimes the right one.
- The business is mid-restructure. If reporting lines will change within six months, both a framework and a system will encode a structure you are about to abandon. Wait.
- Pay is materially below market. Fix that first. A performance framework will tell a good employee, with evidence, that they deserve more than you are paying them — and they will act on it.
- The real problem is one manager. If most of the difficulty traces to a single person who will not manage, that is a leadership conversation, not a procurement decision.
- Nobody senior has time this quarter. Both routes need genuine attention from the top. Launched into a quarter where nobody can attend, both fail, and the organisation learns that these things do not work.
The sequence that works when you need both
Most organisations above roughly eighty people eventually need both. The order matters more than the choice.
- Define first. Result areas and measures for every role in scope, agreed with the managers who will use them.
- Run one cycle on whatever you have. Even a spreadsheet. This exposes the design errors while they are still cheap to fix.
- Then buy, and configure to the framework — not the other way round. A system configured to your definitions is a different purchase from one you adapt yourself to.
- Automate the administration afterwards, once the process is stable enough to be worth encoding. The selection discipline is in what to automate first.
Inverting steps one and three is the standard failure, and it is understandable: software is a decision you can make in a fortnight, while definition is slow and involves disagreement. The fortnight is why it appeals, and also why it does not work.
Frequently asked questions
Vendors say their system includes best-practice templates. Is that not the definition step?
A template is a starting structure, not a definition. It cannot know which two of your managers both believe they own dispatch, or that your quality measure depends on a record nobody actually maintains. Templates save typing; they do not resolve disagreement, and disagreement is the substance of the work.
Can a consultant not just recommend the software too?
They can, and you should ask directly whether they take commission from the vendors they recommend. It is a common arrangement in India and not automatically wrong — but you are entitled to know before you weigh the advice.
We are 60 people. Is a consultant overkill?
Often yes, for a full engagement. At that size, a short structured piece of work — role definitions and one review cycle designed properly — usually delivers most of the value. Be sceptical of a proposal that arrives at that headcount looking like an enterprise programme.
What if we already bought software and it is not working?
Do not replace it yet. In most cases the system is being asked to run a process nobody defined. Define the framework, reconfigure what you already own, and only then judge whether the tool is genuinely the constraint. Replacing it first usually reproduces the problem at a new vendor.
Where to go from here
If the three-role test earlier gave you an uncomfortable answer, that is the useful outcome and the place to start. For the design work, see KRA and KPI design; for what a full engagement involves, our case study walks through one phase by phase. If your definitions are already sound and you need somewhere to run them, that is the performance management system and the HRMS underneath it.
BPro is based in Kochi, Kerala and works with organisations across India. Call +91 80869 08876, email care@bpropms.com, or use the contact form.