Picture this: it's a Friday evening and Ravi says he applied for three days of leave last month. Your spreadsheet says he has one day left. He's certain you approved it. You're fairly sure you did too, but the chat is buried somewhere in a WhatsApp thread from six weeks ago. So you spend the next 40 minutes scrolling back through messages, trying to settle a dispute over something that should have taken 10 seconds to look up.
That's not a compliance problem. That's just friction — the kind that doesn't show up as a line item anywhere, but quietly takes up more of your time than it should.
If your team is between 5 and 20 people, this article is for you. Not to tell you that you're doing it wrong — the spreadsheet works, and a good CA handles the numbers. But to be honest about what it's actually costing you, and why starting with a proper system earlier than you think is worth it.
The reasons you haven't — and why they make sense
Let's be honest about the objections, because they're not bad reasoning.
"We're too small for this." You probably picture HR software as something large companies use — with implementation consultants and a six-month onboarding project. That reputation exists because the platforms that show up first in search are genuinely built for companies with full HR departments. Keka, Darwinbox, Zoho People — these are solid products, but they're designed for 100-person teams, not a 10-person office where the founder or admin is also doing HR. So the "too small" instinct is a fair read of those products. It's just not true of the whole category.
"PF and ESI don't even apply to us." Also correct. PF is mandatory only at 20 employees. ESI kicks in at 10. If you're at 8 people, your actual compliance obligation is TDS and Professional Tax — real, but manageable. The compliance case for HR software is weak at your size, and we're not going to pretend otherwise.
"Our CA handles it." They do. A reliable CA is worth keeping. But there's something a CA structurally can't do: give Priya access to her own payslip at 11pm when she needs it for a loan application. Or tell Suresh his leave balance without you forwarding a spreadsheet. That's not a gap in your CA's skills — it's just a different kind of problem.
"It's an extra expense we don't need right now." This is the most honest objection. And the answer depends entirely on which plan you're looking at. We'll get to that.
What's actually happening in the meantime
The thing about running HR on spreadsheets at 12 people is that the problems are small. None of them are crises. But they stack.
Every month, someone messages asking for their payslip. Not every employee — just the ones who need it for something. A rental agreement, a bank loan, a visa. You open the spreadsheet, find the right month, export a PDF, send it. Takes 15 minutes. Four employees across 12 months is 12 hours a year you spent generating documents your team should be able to get themselves.
Someone applies for leave over WhatsApp. You approve it in the chat. Three months later, the spreadsheet says they have 2 days left. They say 5. You go back through the thread. The approval is there but the balance was never updated. Now you're in an awkward conversation about a number neither of you fully trusts.
A person joins on the 16th. You do the prorated salary — basic divided by 30, times 15 days, then check whether ESI applies this month, then recalculate TDS. You do this right, but you double-check it twice because you're not completely sure the formula is correct. This happens every time someone joins mid-month.
And then March arrives. Every employee needs Form 16 for their tax filing. If you've been running payroll in a spreadsheet, generating accurate Form 16s means either your CA billing hours to reconcile 12 months of TDS data, or you spending days doing it yourself. It lands when everyone is already asking for their documents.
None of this is dramatic. It's just friction — small, recurring, invisible in any single month. Visible when you add it up.
What your team actually feels
There's a side to this that doesn't come up in the cost-benefit analysis.
When someone joins a small team, they're betting on you. They trust that you'll pay them correctly, track their leave fairly, and treat their employment records with some care. Getting a payslip as an Excel attachment forwarded over WhatsApp isn't a crisis. But it tells them something — not intentionally, just as a signal. 'We haven't quite sorted that yet.'
Contrast that with being able to log into a portal any time and see their salary breakdown, their leave history, their payslip for any month. That's the experience employees at larger companies take for granted. There's genuinely no reason an 8-person team can't offer the same thing. And when you do, it tells your team something different: we're organised, we take you seriously, we're building something properly.
For a small company competing with bigger names for good people, how you treat your team on the inside matters as much as anything you say in a hiring post.
"We'll set it up when we're bigger" — what that actually looks like
This is the one that sounds like good resource management but tends to backfire.
You hire your 20th employee. PF just became mandatory. You need to register on the EPFO portal, generate UAN numbers for all 20 people, and start filing ECR monthly from this payroll cycle. At the same time, you're trying to move everyone into an HRMS — reconciling leave balances that employees have been tracking in their own notes, importing payroll history with minor discrepancies that need sorting, handling the mid-month joiner who triggered the count. All of this while running payroll on deadline.
Starting at 8 employees means none of that backlog exists. You add people one at a time. Leave builds correctly from day one. When ESI kicks in at 10 people, it's a toggle you turn on. When PF kicks in at 20, it's a configuration change. You're not managing a migration project — you're just flipping a switch.
Starting clean is always easier than cleaning up.
What actually changes when you use a system
Concretely, not in terms of 'streamlined operations':
Priya needs a payslip at 11pm for a home loan application. She logs into the portal and downloads it herself. You're not involved.
Rajan applies for three days of leave. It goes through the system. You approve or decline with a click. The balance updates automatically. In October, if there's a question, the full history is right there — request, approval, timestamp.
Someone joins on the 14th. You add their details. The system shows you the prorated salary breakdown. You review it, confirm, done.
March arrives. Form 16 for all your employees is generated from the TDS data the system has been tracking all year. Your CA reviews, signs off. You send the link to your team.
None of this is revolutionary. It's just things that used to take time no longer taking time.
The cost, honestly
This is where MedleyHR comes in — and we'll be specific rather than vague about it.
If you have up to 10 employees in India, MedleyHR is free. Permanently. Not a 30-day trial, not a free tier with the useful things locked behind a paywall. Employee database, payroll recording, leave management, and a self-service portal where your team can view their payslips and check leave balances. ₹0 per month, no credit card required, no expiry date.
We built it this way because we didn't want cost to be the reason a small team skips having a proper system. If you're at 7 people, there is no cost argument against starting. You get a better experience for your team, you remove the friction from your month, and you build from a clean foundation — for free.
If you're between 11 and 25 employees, the Growth plan is ₹1,999 per month. That gets you full payroll with TDS, ESI, Form 16, payslip downloads, reimbursements, leave approvals — everything you need to run HR properly. To put it in context: ₹1,999/month is less than one day's salary for most employees at that team size. No setup fee, no implementation project, no consultant. You configure your salary structure, add your team, and run a test payroll. Most teams are doing their first real payroll within a day of signing up.
MedleyHR is free for up to 10 employees in India — employee database, payroll recording, leave management, and a self-service portal. No credit card, no expiry. For 11–25 employees, the Growth plan is ₹1,999/month: full payroll, TDS, ESI, Form 16, payslip downloads, and approval workflows. Start free →
The honest answer to whether you need this
There's no regulation that forces a 7-person company to use HR software. The spreadsheet works. Many teams run on it for years.
But the question isn't really whether you need it. It's whether the manual process is actually cheaper once you count your time, your team's experience, and the cleanup project that's waiting for you when you finally do have to switch.
If you're under 10 people, the math is simple: the free plan costs nothing, and it removes a real category of friction from every month. The only reason not to start is inertia.
If you're at 10–20 people, ₹1,999 is a real number and only you know if it's worth it at your stage. But if March is stressful, if payslip requests take time, if you've had a leave dispute you couldn't cleanly resolve — it probably pays for itself faster than you'd expect.
Either way: the best time to start is before you feel like you have to.