The platform

Not twenty tools.
One system with twenty rooms.

Point solutions each keep their own copy of your people, and the copies drift. Kuzhu keeps one record and builds every module on it — which is why a transfer, a resignation or a missed punch shows up everywhere it matters, immediately.

No sync jobs and no CSV round-trips — the modules share a record, not an importer
One approval engine and one login across everything
Switch a module on later and it already knows your people

Walk the twenty rooms Book a demo

One employee record

one approval engine

Foundations

Built the way you would want it built

A database per company

Your data is not a slice of a shared table — it is a database of its own. Exports are complete, deletion is final, and one customer’s mistake can never become yours.

Permissions with edges

Role-based access decides who sees salaries, who approves purchases, who can even find a person. HR sees HR; a manager sees their team; an employee sees themselves.

An audit trail by default

Who changed the salary, who approved the claim, who issued the letter — recorded as it happens, exportable when the auditor visits.

Open at the edges

A documented REST API and webhooks over the same objects the product uses. Kuzhu joins your systems instead of becoming another island.

The architecture, honestly

One record, three engines

Strip the twenty modules away and this is what is left — the three pieces each of them is built from, and the reason none of them can disagree with another.

The employee record

One profile per person — identity, job, structure, statutory details, documents — created once and read by every module. When recruitment converts an offer, payroll already knows the salary; when a transfer changes a manager, every approval chain that referenced them updates the same minute. There is no sync job because there is nothing to sync: the modules are not integrated with each other, they are built on the same table.

A promotion is one entry. Attendance, approvals, payroll and reports all follow from it.

The approval engine

Leave, expenses, purchases, asset requests, salary revisions and document sign-offs all route through one workflow engine. Chains are configuration — by amount, category or department — so your delegation-of-authority matrix stops being a PDF nobody reads and becomes behaviour the system enforces. Approvers get one inbox across everything, on the phone, and every decision keeps its who and when.

Set a vacation delegation once and it covers every module, because there is only one engine to tell.

The reporting layer

Reports read the live records the modules write — not exports, not snapshots, not a warehouse that was current on Thursday. The salary register, the muster roll and the cost analytics are the same numbers the payslips carry, wearing different layouts. That is why the HR deck and the finance deck cannot disagree here: there is exactly one set of numbers for them to be made from.

Drill from any total to the people behind it in one click, because the total was never detached from them.

In practice

A month on the platform

The same thirty days every HR team lives — told as the moments that used to hurt, and what happens to each of them here.

Day 1, 9:04 am

A punch becomes a judged day

The biometric machine at the gate pushes punches; field staff punch from the app with GPS. At midnight each day is judged against the person’s rostered shift — present, late by seven minutes, half day — with the arithmetic on display. Nobody transcribes anything.

Day 6

Leave asks, the ledger answers

An employee applies from the phone and sees the balance impact before submitting. The manager approves with the team calendar in view. The approved days flow to attendance and, if unpaid, to payroll as LOP — untouched by human hands in between.

Day 14

A claim carries its own receipt

Client-visit expenses are photographed at the taxi stand, checked against policy at submission, and approved in the same inbox as everything else. Come month end they are already sitting inside the payroll run as reimbursement lines.

Day 28

The run is a review, not a rebuild

Payroll opens with payable days, approved leave, claims and loan EMIs already in place. PF, ESI, professional tax and TDS compute inside the run. The team reviews the flagged deltas — joiners, exits, unusual movements — approves, and exports the bank file.

Day 30

Everyone is told, nothing is asked

Payslips publish to self-service and the app notifies. The challans and registers come out of the same run. The question “when is salary coming” does not get asked, because the answer is already on every phone.

How Kuzhu works

One system. Everything connected.

Kuzhu connects the people, processes and compliance work that normally live across separate HR systems.

One record

Everything reads and writes the same employee

A transfer updates payroll. A resignation opens exit clearance and lists the laptop to collect. A punch missed on Tuesday shows in Friday’s payroll preview. Modules that share one record cannot drift apart — that is the whole trick.

One profile, twenty modules deep
Career events flow everywhere at once
No exports between your own systems

One approval engine

Policy that enforces itself

Leave, expense claims, purchase orders and salary revisions all route through chains you configure once — by amount, by department, by role. Delegation covers absences. The audit trail writes itself.

Multi-level chains with conditions
Approve from phone or email
Every decision on the record

Compliance built in

Indian payroll, not a translation

PF, ESI, professional tax and TDS are computed inside the payroll run, on the attendance and leave the system already holds. Registers, challans and returns come out ready for filing — not as a spreadsheet project.

PF · ESI · PT (state-wise) · TDS
Returns-ready registers every month
Payslips your staff can actually read

Kuzhu at a glance

One system. A lot less friction.

modules on one platform

employee record shared by all of them

statutory regimes in payroll — PF, ESI, PT, TDS

0.0%

monthly uptime target, an SLA on Enterprise

Built to work quietly in the background.

Security