Most founders run HR out of a spreadsheet and a WhatsApp group until it breaks. Here are the compliance triggers and systems every startup needs in place before growth outpaces the paperwork.
For the first few hires, HR at a startup is a founder, a spreadsheet, and a WhatsApp group. It works — offer letters go out, salaries get paid, leave requests get a thumbs-up emoji. Then headcount crosses into double digits and the informal system starts producing the exact problems it was never built to handle: missed statutory registrations, inconsistent leave approvals, and a founder spending Friday afternoons reconciling attendance instead of building product.
The Founder-as-HR-Department Phase
This phase isn't a mistake — it's the right amount of process for 5 people. The problem is that most founders don't know where the line is, so they keep running HR informally well past the point where it stops being efficient and starts being risky. Compliance obligations in India don't wait for a startup to "feel ready" — they kick in automatically at specific headcount thresholds, regardless of whether HR has been set up to handle them.
The Compliance Triggers Nobody Warns You About
- ESI applies automatically once you have 10 or more employees earning ₹21,000/month or less — many founders miss this because they're only watching total headcount, not eligible headcount
- PF registration becomes mandatory at 20 employees, with contributions due retroactively from the date of applicability, not the date you registered
- POSH (Prevention of Sexual Harassment) Internal Committee formation is mandatory for any organisation with 10 or more employees — this is frequently missed entirely by early-stage companies
- TDS on salary under Section 192 applies from your very first hire, regardless of company size
- Gratuity liability starts accruing from an employee's first day, even though it's only payable after 5 years of service — untracked accrual becomes a nasty surprise at exit time
It's the most commonly overlooked compliance item at startups because it doesn't involve money changing hands. But it's a legal requirement at 10 employees, and its absence is one of the first things auditors and investors flag during due diligence.
What to Set Up Before Employee #10 and #20
- 1A single source of truth for employee records — names, salary structures, bank details, documents — instead of scattered folders and forms
- 2A structured leave policy with defined types, balances, and an approval workflow that isn't a chat message
- 3Automated attendance tracking, even if it's just a mobile check-in — so LOP and payroll never depend on memory
- 4Payroll that calculates PF, ESI, and PT automatically the moment you cross the applicability threshold, rather than retrofitting it after a notice arrives
- 5A basic onboarding checklist so new hires get consistent documentation, System access, and policy sign-off from day one
Why "We'll Deal With It Later" Backfires
The cost of setting up proper HR systems at 8 employees is a few hours of configuration. The cost of doing it at 40 employees, after a statutory notice, after an investor due-diligence flag, or after a disgruntled ex-employee escalation, is measured in weeks of cleanup and real financial penalties. Startups that wait for a problem to force the issue almost always pay more than the ones that set up lightweight systems early.
HRORA is built to grow with a company from its first hire to its five-hundredth — statutory modules switch on automatically as you cross each applicability threshold, so compliance never depends on a founder remembering a headcount number.
Building People Processes That Scale
The goal at this stage isn't enterprise-grade HR — it's lightweight, correct, and automatic. A startup that gets attendance, leave, payroll, and statutory compliance right from the start spends its energy on hiring and product, not on retroactively fixing HR debt during its next funding round.