How to Set Up an HR Department in a Startup: 2026 Guide

Most startups set up an HR department the same way: not at all, then all at once. For the first twenty hires, the founder does HR from a laptop — offer letters copied from a friend's template, salaries paid through a spreadsheet, leave tracked in memory. Then something forces the issue: a compliance notice, a messy exit, an investor's due diligence checklist, or simply the fortieth employee asking who approves their leave. Knowing how to set up an HR department in a startup — deliberately, in stages, before the forcing event — is one of the highest-leverage operational moves a founder can make.

This guide lays out the full playbook for India-based startups and SMBs: what HR must cover at each headcount stage, when to hire your first HR person and what profile to choose, the compliance registrations you cannot skip, the policies and documents to create first, the technology stack that keeps a small team sane, budgets, metrics, and the mistakes that cost the most. Similar principles apply in most emerging markets, with local compliance swapped in.

What "HR" Actually Has to Cover

Before designing the department, inventory the work. HR in a startup spans six functions, whether or not anyone has the title:

1. Talent acquisition — sourcing, interviewing, offers, and onboarding.
2. Payroll and compensation — salary structures, monthly payroll, reimbursements, increments, ESOPs.
3. Compliance — statutory registrations, PF/ESI/PT/TDS filings, labour law obligations, POSH, registers and records.
4. Employee lifecycle operations — records, letters, attendance, leave, confirmations, transfers, exits.
5. Performance and development — goals, reviews, feedback, training.
6. Culture and employee experience — engagement, grievances, communication, wellbeing.

At ten employees, the founder can genuinely cover most of this with good tools. At fifty, the six functions generate daily work. At a hundred and fifty, each function needs an owner. The art is adding structure just ahead of the breakage point, not after.

Stage 1: Founder-Led HR (Roughly 1–20 Employees)

At this stage you should not hire an HR manager. You should build the system that an HR manager would later inherit.

Get legally clean

• Registrations. Depending on your entity, states, and headcount: Shops and Establishments registration for each office location, PF registration (mandatory generally at 20 employees, voluntary earlier), ESI (generally at 10 employees in covered areas, wage-linked), professional tax registration in applicable states, and Labour Welfare Fund where applicable. TAN for TDS on salaries. Thresholds and applicability vary — verify with a compliance professional; missing a registration is the most common startup HR failure.
• POSH compliance. If you have ten or more employees, constitute an Internal Committee under the POSH Act, adopt a policy, and run awareness sessions. This is frequently ignored by startups and carries real liability.
• Employment contracts. A solid offer letter and employment agreement template: role, compensation structure, probation, notice, confidentiality, IP assignment (critical for product startups), and code of conduct reference. Have a lawyer review the template once; reuse it forever.

Set up the payroll foundation

• Define a standard salary structure (basic, HRA, allowances) rather than negotiating structure per hire. Keep basic pay at a defensible share of gross with the labour codes' wage definition in mind.
• Run payroll through software, not spreadsheets, from as early as possible. Manual payroll works until the first month it doesn't — a missed TDS deposit or a wrong PF computation costs more than a year of software subscription.
• Open the statutory calendar: PF and ESI monthly deposit dates, TDS deposit and quarterly return dates, PT deposit dates. Automate reminders.

Create the minimum policy set

Resist writing a fifty-page handbook. Five one-pagers cover ninety percent of early needs:

1. Leave policy (types, accrual, carry-forward, encashment)
2. Attendance and work hours (including remote/hybrid expectations)
3. Expense reimbursement
4. Code of conduct + POSH summary
5. Exit process (notice, FnF timeline, asset return)

Put them in a shared drive or, better, an HRMS employees can actually search.

Start the employee file habit

One folder (digital) per employee from day one: signed offer, agreement, KYC, PF nomination, gratuity nomination, tax declarations. Retro-fitting files for forty employees later is a miserable quarter.

Stage 2: The First HR Hire (Roughly 20–50 Employees)

Somewhere in this band, founder-led HR stops scaling. The signals: hiring is slowing because nobody owns the pipeline, payroll eats two founder-days a month, employees don't know whom to ask about policies, and compliance is running on hope.

Whom to hire first

The classic mistake is hiring either a pure recruiter (leaves payroll and compliance orphaned) or a senior CHRO (overkill and they'll leave). The right first profile for most startups is an HR generalist with payroll-and-operations strength — someone from a 3–8 year experience band who has personally run payroll, handled statutory filings with a consultant, hired across functions, and written policies. Culture-building instincts matter, but operational hygiene is the survival skill at this stage.

A common and effective pattern:

• First HR hire: generalist (people ops + payroll + compliance coordination)
• Recruitment: founders + hiring managers still own closing; the generalist owns process and pipeline
• Compliance depth: outsourced to a CA/CS or compliance firm, coordinated by the generalist

What the first HR hire should deliver in 90 days

• Payroll transitioned fully to software with statutory computations configured
• Employee files complete and digital for all staff
• The five core policies refreshed and published
• Onboarding standardised: pre-joining documents, day-one setup, 30/60/90 check-ins
• Statutory compliance calendar owned, with a filing tracker
• A basic HR dashboard: headcount, attrition, hiring pipeline, leave liability

Introduce structure without bureaucracy

This is also the stage to formalise probation confirmations, a light performance check-in cycle (quarterly conversations beat annual paperwork), and a grievance channel that isn't "message the founder."

Stage 3: Building the Function (Roughly 50–150 Employees)

Now HR becomes a small team with specialisation:

• Talent acquisition gets a dedicated owner once you're making 2+ hires per month consistently. An applicant tracking process (even inside your HRMS) replaces the shared-inbox pipeline.
• HR operations & payroll remains one owner, now supported properly by software — attendance devices or geo-tracked mobile check-ins if you have field staff, automated leave workflows, employee self-service for payslips and declarations.
• HR business partnering starts informally: HR sits with function heads on org design, performance issues, and retention risks rather than just processing transactions.

Governance that becomes necessary in this band

• A real performance management cycle with goals (OKRs or KPIs), documented reviews, and a calibration step
• Compensation bands per role/level, so offers and increments stop being ad hoc
• A promotion and increment cycle with a budget
• Manager training — first-time managers are now most of your management layer
• An engagement pulse (quarterly eNPS or similar) with visible follow-up
• Attrition analysis by team, tenure, and manager

The compliance step-up

Multi-state expansion multiplies registrations (S&E per state, PT per state, LWF where applicable). Contract staff bring CLRA considerations. Headcount growth can trigger standing orders applicability in some sectors and states. This is the stage to move from "our CA handles it" to a compliance tracker the HR team owns, with the consultant as executor rather than memory.

Stage 4: Head of HR and Strategic HR (150+ Employees)

Past ~150 employees, hire a genuine Head of HR/CHRO profile — someone who has scaled a function before. The centre of gravity shifts from administration to strategy: workforce planning tied to the business plan, leadership development, succession, culture codification, compensation philosophy, HR analytics, and organisational design. The operations you built in stages 1–3 become the platform this leader runs on; if those foundations are missing, the new head spends their first year doing archaeology instead of strategy.

The Startup HR Tech Stack

The right stack at each stage, with the principle "one system of record, adopted early, beats five point tools stitched later":

Selection principles for the core HRMS:

• India-compliant payroll is non-negotiable: PF, ESI, PT, TDS, LWF computations and challan-ready outputs, with multi-state support.
• Employee self-service reduces HR load more than any other feature — payslips, leave, attendance regularisation, tax declarations, letters on demand.
• Configurable workflows (onboarding, exits, confirmations) let one HR generalist run processes that would otherwise need a team.
• Reports you'll actually use: headcount, attrition, leave liability, payroll cost, compliance status.
• Pricing that scales with you, not enterprise minimums.

Adopting the system of record at stage 1 is the single cheapest decision in this whole playbook — data cleanliness compounds exactly like technical architecture does.

Budgeting for HR

Rules of thumb for planning (calibrate to your market and stage):

• HR headcount ratio: roughly one HR person per 40–60 employees in the growth stages; the first hire lands around employee 25–35.
• HR software: typically a small per-employee-per-month cost — almost always cheaper than the errors and hours it removes.
• Compliance retainer: a monthly CS/CA retainer for filings and advisory is standard until you internalise the capability.
• Recruitment costs: agency fees (commonly a percentage of CTC) versus building sourcing capability — most startups blend both, shifting inward as employer brand grows.
• Training and engagement: small but non-zero from stage 2; a budget line signals seriousness.

The honest framing for founders: HR spend is not overhead competing with product; it is the maintenance cost of the machine that builds the product. Underfunding it doesn't save money — it defers cost into attrition, compliance penalties, and founder time.

Metrics: How to Know Your HR Function Works

Track a small set from the start and review monthly:

• Time-to-hire and offer acceptance rate (talent acquisition health)
• Regretted attrition by team and tenure band (retention health)
• Payroll accuracy (errors per cycle) and payroll timeliness (operations health)
• Compliance filing timeliness — a simple green/amber/red tracker (risk health)
• Onboarding completion and 90-day new-hire retention (intake quality)
• eNPS or pulse score trend (culture temperature)
• HR ticket resolution time once self-service exists (service health)

Five minutes of dashboard beats fifty pages of policy. What leadership inspects, the organisation respects.

The Ten Most Expensive Early HR Mistakes

1. Skipping registrations until "we're bigger." Penalties and retroactive dues cost multiples of doing it on time.
2. Spreadsheet payroll past 15 employees. One wrong TDS cycle erases years of "savings."
3. No IP assignment clauses. Discovered during investor due diligence, fixed under duress.
4. Hiring a recruiter as the first HR person. Pipeline improves; payroll and compliance rot.
5. No POSH committee at 10+ employees. Legal exposure plus a terrible first test when a complaint arrives.
6. Unstructured compensation. Every offer negotiated from scratch creates internal inequity that surfaces painfully later.
7. No employee files. Every audit, dispute, and due diligence becomes an excavation.
8. Copy-pasted policies that don't match reality. A policy you don't follow is worse than none in a dispute.
9. Annual-only performance conversations. Problems age badly; feedback debt compounds.
10. Treating exits casually. Delayed FnF and withheld letters generate the reviews future candidates read.

A 90-Day Action Plan to Stand Up HR

Days 1–30: Foundations. Audit registrations against thresholds and fix gaps; move payroll to software; create the five core policies; open employee files for all staff; set up the statutory calendar; constitute the POSH IC if applicable.

Days 31–60: Process. Standardise onboarding end to end; configure leave and attendance workflows with self-service; standardise the offer-to-joining document flow with e-signatures; publish the exit/FnF process; complete PF and gratuity nominations for everyone.

Days 61–90: Rhythm. Launch the HR dashboard; run the first engagement pulse; start quarterly performance check-ins; brief managers on their responsibilities (leave approvals, feedback, escalation); decide the first HR hire timeline based on load.

A founder plus a good HRMS can complete this plan without any HR staff — and the startup that does it will onboard its future HR team into a working system instead of a crisis.

Remote, Hybrid, and Field Teams: HR Design Choices That Changed

If your startup is distributed — and most now are, at least partially — several playbook items need explicit design rather than office-era defaults:

• Attendance philosophy. Decide early whether you track presence (check-ins, geo-tagged for field staff) or only outcomes (no attendance capture for knowledge roles, leave still tracked). Mixed models are fine; undocumented ones are not. Field and operations staff generally need real attendance capture for payroll accuracy and statutory records; forcing the same regime on engineers mostly generates resentment.
• State-wise compliance mapping. Every remote employee's work state matters for professional tax, S&E rules, and LWF. Tag work location on the employee record from day one and let payroll apply state rules automatically — retro-mapping fifty remote employees is painful.
• Documentation becomes the culture carrier. In distributed teams, the handbook, policy pages, and onboarding materials do the transmission that hallway osmosis used to do. Budget real effort for written clarity; it is a retention tool disguised as admin.
• Equipment and expense policy. Who buys the laptop, what internet reimbursement applies, how assets are recovered at exit across cities — decide once, write it down, wire it into onboarding and offboarding checklists.
• Time zones and meeting norms if you hire across regions: core hours, async defaults, and response-time expectations belong in the work-hours policy, not tribal knowledge.

None of this requires more headcount — it requires the decisions to be made explicitly and encoded in your HRMS so the system, not memory, enforces them.

Building the Recruitment Engine Inside the New Department

Recruitment deserves its own operating system, because it is the HR activity founders feel most acutely. The elements to standardise as the department forms:

• Role scorecards before sourcing. For every opening, write what the person must accomplish in 12 months and the competencies that predict it — before a single résumé is screened. This one artifact aligns founders, hiring managers, and interviewers, and cuts time-to-hire more than any sourcing tactic.
• A structured interview loop. Assign each interviewer specific competencies, use consistent questions, and collect written feedback on a scale before any group discussion. Unstructured "chat and vibe" interviews feel fast but produce noisy hires and legal risk.
• A single pipeline of record. Whether a lightweight ATS or your HRMS's recruitment module, every candidate, stage, and feedback note lives in one place. The shared-inbox pipeline dies at roughly two simultaneous openings.
• Candidate experience SLAs. Acknowledge every application, decide within a stated number of days per stage, and always close the loop with rejected candidates. In tight talent markets, your process is your employer brand.
• Offer discipline. Offers come from compensation bands, are approved through one route, and go out through a standard template with e-signature. Off-band offers need explicit sign-off, and each one is recorded with its rationale — this is what keeps internal equity intact at fifty employees.
• Source tracking. Tag every hire by source (referral, agency, inbound, outbound) and review cost and quality by source quarterly. Referral programs usually win on both once measured, which justifies funding them properly.

An Onboarding Blueprint Worth Copying

Onboarding is where recruitment promises meet operational reality, and it is the process new HR departments most visibly own. A strong default:

Pre-joining (offer to day 0). Document collection and verification through a portal, not email attachments; background verification initiated; equipment and access provisioned; a welcome note from the manager; payroll and PF/gratuity nomination forms completed digitally so day one is not paperwork day.

Day one. Working equipment, working access, a planned schedule, lunch arranged, and a manager who blocked the day. Nothing else signals "we were expecting you" as clearly.

Week one. Product and business orientation, tool setup, policy walkthrough (search-able, not read-aloud), and the first small deliverable shipped — momentum beats immersion.

Days 30/60/90. Structured check-ins against the role scorecard: expectations aligned at 30, feedback exchanged at 60, confirmation trajectory clear by 90. HR audits completion; managers own content. Probation confirmation letters generate automatically from the workflow rather than being remembered into existence.

Measure it: onboarding task completion rate, time-to-productivity as the manager assesses it, and 90-day retention. Early attrition is nearly always an onboarding or expectation-setting failure, and it is the cheapest attrition to fix.

Culture: The Part You Cannot Delegate to the Department

A warning for founders reading this as a delegation manual: the HR department institutionalises culture, but it cannot originate it. Culture is set by what founders reward, tolerate, and model. What HR can do as it forms:

• Codify what already works. Write down the behaviours behind your best decisions and hires — as concrete do/don't statements, not poster values.
• Wire values into mechanisms. Interview loops that test for them, review criteria that weight them, recognition that cites them. A value that appears in no mechanism is decoration.
• Create honest feedback channels. Pulse surveys with published follow-ups, skip-level conversations, and a grievance path that visibly works. Trust compounds when the first complaint is handled well.
• Protect rituals through scale. Weekly all-hands, demo days, celebration habits — the department's job is to keep these alive when calendars get crowded, adapting format without losing function.

The healthiest sign at 100 employees is when managers, not HR, are heard explaining "how we do things here." That is culture successfully institutionalised.

ESOPs: The HR Side of Equity

Most Indian startups use ESOPs, and the new HR department inherits their administration even though the scheme design sits with founders, counsel, and the board. HR's checklist:

• Maintain the grant register: who was granted what, when, at what vesting schedule and exercise price, against board approvals.
• Ensure every grant is papered — grant letters issued and acknowledged, scheme document accessible to holders.
• Track vesting events and cliff dates; communicate them proactively rather than letting employees discover them at exit.
• Build ESOP handling into the exit process: what is vested, the exercise window and process, what lapses — stated clearly in the FnF communication.
• Coordinate the tax touchpoints (perquisite taxation at exercise runs through payroll) with your finance team and advisors.

Equity disputes at exit are among the most corrosive startup conflicts, and nearly all of them trace to informal grants and undocumented promises. The department's contribution is unglamorous rigour.

Working Rhythm: HR and the Leadership Team

Finally, wire the new department into how the company runs, or it becomes a service desk:

• A monthly people review with founders: dashboard walk-through (hiring, attrition, engagement, compliance status), one deep dive, and decisions logged.
• Quarterly workforce planning tied to the business plan: which roles, when, at what cost — so recruitment executes a plan instead of reacting to panics.
• An annual calendar every manager can see: increment cycle, review windows, engagement surveys, compliance renewals, holiday list publication. Predictability is half of perceived fairness.
• Clear decision rights. What managers decide (leave, small spot awards), what HR decides (policy interpretation, process), what founders decide (bands, exceptions, senior hires). Ambiguity here generates most early HR friction.

A Note on Sequencing: What to Do When Everything Feels Urgent

If you are reading this at forty employees with none of it in place, resist the instinct to do everything at once. The triage order that minimises risk: first, statutory registrations and payroll correctness — this is where penalties and personal liability live. Second, employment paperwork and IP assignment — this is what due diligence will examine. Third, the exit and FnF process — this is where reputational damage accumulates fastest. Fourth, onboarding and performance rhythm — this is where retention is won. Culture and engagement programs come last not because they matter least, but because they are the least recoverable from a position of operational chaos: an engagement survey run by a team that pays salaries late is an irony employees will not forgive. Fix the plumbing, then decorate.

Frequently Asked Questions

1. At what headcount should a startup hire its first HR person? Most startups feel the pain between 20 and 35 employees and should hire around then. If hiring velocity is unusually high or the workforce is field-heavy, earlier. The hire should be an operations-strong generalist, not a specialist.

2. Can we outsource HR entirely instead of building a department? You can outsource payroll processing and compliance filings effectively, and many startups should. You cannot outsource culture, hiring judgment, performance conversations, or employee trust. The durable model is: software for operations, consultants for compliance execution, and in-house ownership of people decisions.

3. Which HR registrations are mandatory for a small startup in India? It depends on state, sector, and headcount, but the usual set is Shops & Establishments registration, TAN and TDS compliance from the first salaried employee, ESI upon crossing the applicable threshold in covered areas, PF at the statutory threshold (commonly 20), professional tax per state, and POSH IC at ten employees. Verify current thresholds with a professional — they change and vary.

4. Do we need an HR department if we use good HR software? Software collapses the operational workload dramatically — one person can run what used to need three. But software executes decisions; it doesn't make them. You still need human ownership of hiring, performance, grievances, and culture. The right statement is: good software lets you delay the department, not the function.

5. What HR policies should a startup write first? Leave, attendance/work hours, expense reimbursement, code of conduct with POSH, and exit process. Add remote-work, IT/security, and travel policies as the realities demand. Keep each to a page or two and review annually.

6. How much should a startup budget for HR software? Entry-level India-compliant HRMS platforms are priced per employee per month at rates that almost any funded or revenue-generating startup can absorb. The comparison to make is not against zero but against the founder-hours, error costs, and penalty risks of manual operation.

7. When should performance reviews start? Lightweight quarterly check-ins from roughly employee 15–20, formalising into a documented cycle with goals and calibration by 50. Starting the habit early is much easier than imposing it on a culture that grew without feedback.

8. What does an investor's HR due diligence actually check? Typically: employment agreements with IP assignment for all staff, cap table/ESOP hygiene, statutory registrations and filing proofs, PF/ESI/TDS compliance, POSH compliance, pending disputes, key-person dependencies, and attrition data. A startup that followed this guide's stages passes by default.

Conclusion

One final reframe for founders who still see this as overhead: your competitors for talent are running this playbook. In a market where candidates check review sites before interviews, compare offer processes, and ask pointed questions about ESOP paperwork and FnF timelines, the quality of your HR operations is part of your recruiting pitch whether you designed it or not. The startups that win senior hires are rarely the ones with the biggest budgets — they are the ones whose offer arrived in a day, whose onboarding worked on day one, and whose ex-employees say they were treated fairly. That reputation is built by exactly the unglamorous systems this guide describes, one clean process at a time.

Setting up an HR department in a startup is not about hiring HR people early — it is about sequencing: legal cleanliness and payroll discipline first, a systems-minded generalist when load demands, specialisation as scale arrives, and strategy leadership once there is an organisation to lead. At every stage, the multiplier is infrastructure: one system where employee records, attendance, leave, payroll, and compliance already live together, so each new HR hire starts with leverage instead of archaeology.

CozyHR is built to be that first system — India-ready payroll, statutory compliance support, self-service, and lifecycle workflows that one founder or one generalist can run. If you're building your HR function this year, start it on rails: try CozyHR.

This article is general guidance, not legal advice. Registration thresholds and statutory requirements vary by state and change over time — verify current rules with a qualified professional.