HRMS software for small teams in India · by invitation
Attendance, leave, employee records and payroll for companies from their first two hires to a few hundred people, priced per employee, per month, no minimum. Every punch and approval is written as it happens, so the numbers are live from sign-in and each one shows its because.
because many HRMS plans start at a fixed monthly minimum sized for 25 or 50 people, and a team of five pays all of it.
Good morning, Meenal
4
In now
because 4 of 5 punched in since 08:52
1
Late mark
because Vikram's grace ended at 09:40
1
On leave
because Priya's casual leave was approved
Team todayall 5 shown
Waiting on you2
Leave · 09:48
Asha Rao
Casual leave · Fri 16 – Mon 19 Oct
Regularisation · 09:55
Vikram Nair
Missed punch-out · Mon 28 Sep
if approved: Present, out 18:32
Month close · today
September payroll
Waiting for your approval · payslips Wed 30 Sep
No. 01
The minimum bill
A bill is an entry like any other, so it should say what it pays for. A five-person team should not pay for forty-five empty seats.
Many HRMS plans start at a fixed monthly minimum sized for 25 or 50 people, so a small team pays for people it has not hired. LekhaHR bills the team you have, from two people, with no base fee.
| No. | Plan | Seats on the bill · filled: your 5 people | Monthly bill |
|---|---|---|---|
| 1.1 | LekhaHROperations plan · billed yearly | 5 seats, one for each personbecause the bill counts the people you have: 5 × ₹79. | ₹395a month |
| 1.2 | greytHR · Essential | because it is a flat plan that covers up to 50 employees, so five people pay the same as 50. | ₹2,495a month |
| 1.3 | Zimyo · Basic | because it is ₹80 per user with a 50-user minimum: 50 × ₹80 = ₹4,000, for 5 people or for 50. | ₹4,000a month |
a person in your teama seat the minimum bills for
Competitor figures: each vendor's published price for the named plan, excluding GST, as reviewed on 29 Sep 2026. Prices change.
LekhaHR Operations: ₹79 per employee per month on annual billing for the first 25 employees, then ₹69, ₹59 and ₹49 a person in the higher bands, with no minimum and no base fee; GST extra. Business is ₹119 per employee for the first 25 on the same terms, and monthly billing adds ₹20 per employee in every band.
Per employee, per month, no minimum
LekhaHR has no fixed minimum and no base fee, so a 5-person team pays for 5: ₹395 a month on Operations, billed annually, before GST. Its rates fall in bands as the team grows, the way tax slabs work, and every module runs on one employee record, with no add-ons to buy.
No fixed minimum. Some Indian HRMS plans charge a flat monthly fee or bill a minimum band of 25 to 50 employees, so a small team pays for seats it has not filled. LekhaHR bills only the people you have: 5 employees on Operations cost ₹395 a month on annual billing, before GST.
Rates fall as you grow. LekhaHR's bands work like tax slabs: each rate applies only to the people inside its band, from ₹79 for the first 25 down to ₹49 past 100. Hiring one more person adds one line at that band's rate and never raises the rate for everyone else.
One platform, one record. Employee records, attendance, leave, payroll, onboarding and exits run on one record per person in LekhaHR, with no separate tools to connect and no per-module add-ons. Both plans include all of them.
09:02
The first entry of the day is written by the person it is about.
Your team punches in from a computer or a phone. Works today in the phone's browser; a native mobile app is coming soon. Location is taken once, at the punch, never through the day. By the time you open LekhaHR, the day already knows who is in, who is late and who is on leave.
One tap, stamped with server time.
Late marks follow the rule you set.
Every half day says why.
Fix a missed punch before cutoff.
Good morning, Asha
You're in.
Koramangala office. Taken at the punch, not after.
Shift 09:00–18:00 · grace 10 min
Vikram Nair · September
Design preview · sample data
13:30
Two days, not four. The weekend is already in the policy, so nobody counts it by hand.
A request shows its count, its reason and the balance it will leave before anyone approves it. In a small team the approver is often the founder, so the decision takes one look.
9.0 credited, Jan to Sep, less 3.0 taken
Sat 17 and Sun 18 are weekly offs, and the sandwich rule is off for casual leave
Design preview · sample data
16:10
A dashboard that waits for tonight's batch is a report. This one moves while you read it.
Dashboards move as punches and approvals land, from the first sign-in. Any role, prebuilt or one you write, can be given any module at the scope you choose: self, team or the whole company.
4 of 5 in
because Priya is on approved leave until Thu 1 Oct
Updated 16:10:02
1 away
because Priya Menon took casual leave, 29–30 Sep
Next: Asha · 16–19 Oct
2 to verify
because Rohan's PAN card and Vikram's address proof came in today
1
because Vikram's Mon 28 Sep regularisation is still open
Any role, any module
| Role | Core HR | Attendance | Leave | Payroll |
|---|---|---|---|---|
| Founder | Org | Org | Org | Org |
| Office managercustom role | Org | Org | Org | View |
| Team lead | Team | Team | Team | None |
| Employee | Self | Self | Self | Self |
| Accountantcustom role | None | View | None | Org |
because in a team of five the founder is often HR, and your accountant needs payroll and nothing else.
Design preview · sample data
19:45
When the cycle locks, the record stops moving. Anything later is written as an adjustment, never over the top.
Attendance locks, paid days carry into payroll, and each payslip line shows the rule, the rate and the date behind it. LekhaHR works out PF, ESI, professional tax and TDS, so every return starts from figures you can check.
because 30 days, less 8 weekly offs and 1 holiday (Mon 14 Sep)
LOP 0 · because she was present on every working day in the window
LOP 0 · counted as paid days, because casual leave is paid leave (10–11 Sep)
LOP 0 · because his late mark on 21 Sep is counted, not deducted, under this policy
LOP 0.5 day · because 16 Sep was a half day with no fix before the cutoff; 29 Sep goes to October's run
LOP 0 · her casual leave on 29–30 Sep is paid leave and falls in October's input
29.5 of 30 paid days: LOP 0.5 day, because 16 Sep was a half day with no fix before the cutoff; 29 Sep goes to October's run
basic and special allowance; HRA and conveyance (₹6,490) are within half of pay, so nothing is added back
12% of ₹10,817 wages, below the EPF ceiling all month (₹15,000 to 16 Sep, ₹25,000 from 17 Sep 2026), so PF is on all of it
₹81.13 rounded up. Wages are within the ₹21,000 ceiling, tested on Code wages since 21 Nov 2025. Paiteq adds 3.25%, ₹352
his projected income for tax year 2026-27 is below the basic exemption limit, so no tax is deducted and no Form 130 (earlier Form 16) is due
₹17,307 less EPF and ESI; no professional tax below Paiteq's Karnataka threshold
Design preview · sample data · PF and ESI rates from the Code on Social Security, 2020; TDS under the Income-tax Act, 2025 · checked by the LekhaHR team
How payroll worksThe rest of the suite
Both plans run on one employee record, so a claim at 11:20 and a timesheet at 17:30 land in the same month close. Approvals, reports and an API sit under all of them.
Switching from Keka, greytHR or a spreadsheet
Upload the file, match its columns to LekhaHR once, and decide only the rows that need a decision. Opening balances become the first line of each person's ledger.
because it came from the Keka export of 30 Sep 2026, row 4
employee_master.xlsx · 42 rows
LekhaHR fields
Design preview · sample file · 1 row has a balance below zero, so it waits for you
No. 06 · Privacy
No. 07 · Written for you if
No. 08 · An honest note
No. 09
Questions
Prices carry their working. Statutory answers carry the date the rule took effect.
An HRMS (human resource management system) is software that keeps one record for each employee and runs the routine HR work against it: attendance, leave, payroll, onboarding, exits and approvals. LekhaHR is HRMS software for small teams in India, from two people upward, priced per employee each month with no minimum.
There is no single best; it depends on your headcount and whether you run payroll in-house. Check three things: the monthly bill at your headcount, since some plans charge for a 25- or 50-person band; whether PF, ESI, PT and TDS follow the current rules with dates; and whether every figure explains itself.
LekhaHR is priced per active employee a month, with no base fee and no minimum. On the Operations plan, billed annually, each of the first 25 employees costs ₹79, falling to ₹69, ₹59 and ₹49 in higher bands. Monthly billing is ₹20 more per employee. GST at 18% is added separately.
Because LekhaHR has no minimum and no base fee, so 5 people are billed as 5: ₹395 a month on Operations, billed annually, before GST. A plan with a flat fee covering the first 25 or 50 employees charges for the whole band even with 5 people on it. Free editions with limits exist, so compare the bill at your headcount.
Yes. Both plans include payroll with PF, ESI, professional tax and TDS, payslips, and the figures for Form 130 (earlier Form 16). Each payslip line shows the rule behind it and the date that rule took effect. LekhaHR works out the figures; you or your accountant file the returns and make the deposits.
LekhaHR is available by invitation: request an invite and we reply by email with your setup. There is no self-serve sign-up, free plan or trial. Tell us your team size and the tool you use now, and a person reads every request.
Yes, for small teams. LekhaHR covers the core HR work a small team runs in those tools: employee records, attendance, leave, payroll, onboarding and exits. It is billed per employee with no minimum, and switching starts from your existing export, with one month run side by side before you move.
No. 10 · Invitation
LekhaHR is available by invitation, from teams of two. Each team gets help getting set up from its current tool, and a reply by email to every request.
We read every request ourselves.