HRMS
Attendance, leave, payroll and approvals, in production today. Graduated pricing means the rate per employee drops as your headcount grows.
See pricingPeople ops & custom engineering
Most tools make you change how you work to match them. We built the opposite: a live people-operations product you can run on today, and the engineering behind it to reshape whatever genuinely does not fit.
What we build
Most clients start on the live HRMS below. When a workflow genuinely doesn't fit — an approval chain, a report, an integration — that becomes a build discussion with the engineers who wrote the product, not a support ticket that goes nowhere.
Attendance, leave, payroll and approvals, in production today. Graduated pricing means the rate per employee drops as your headcount grows.
See pricingAn approval chain, report or workflow the HRMS genuinely can't cover becomes a build discussion — not a closed door. Quoted directly, not a published rate.
Discuss a projectThe pattern
Everything works fine on paper at ten people. Somewhere past twenty it stops — and the spreadsheet becomes the thing your team argues about.
Check-ins in a group chat, corrections over phone calls, and a spreadsheet someone rebuilds at month end. It works until somebody disputes a day and nobody can prove what happened.
Requests approved over email or in person, balances tracked in one person’s file, and an argument every time an employee thinks the number is wrong.
The same salary structures re-entered, the same pro-rations recalculated by hand, and payslips assembled one document at a time.
Systems designed for a thousand employees, priced and configured accordingly — so a forty-person company spends a quarter setting up features it will never use.
How we work
How the organisation works today — people, processes, tools and constraints — before recommending a product or a build.
Use what already fits. Only scope custom work for gaps that genuinely need it.
Help with launch, training and ongoing support so the software becomes part of how the team works.
Why us
Every statutory number on a payslip carries a government source, a check date, and a status — verified, disputed or unverified. Where we have not verified a schedule, the engine refuses to run rather than guess. Your team can supply the schedule; the payslip marks it as employer-supplied. We calculate. We do not file.
No ticket queue, no account manager relaying questions to an engineering team in another city. When something breaks or you need a change, you speak directly to the people who wrote the software.
If an approval chain, report or workflow is missing, that is the start of a build discussion — not a closed door. Large vendors rarely justify that for a company of forty people.
Every company runs in its own tenant, enforced in the application and again with row-level security in the database. Role-based access means people see only what their role requires.
Pricing
No free tier — every employee is billed from the first one. The rate drops in three graduated bands as headcount grows, with no feature gates at any band.
₹129/emp/mo
₹99/emp/mo
₹79/emp/mo
Custom
Full plan comparison and billing details are on the pricing page. Custom software is scoped and quoted per project, separately from the HRMS plan — see contact.
About
We run a production people-operations product and take on custom builds when a catalogue tool cannot cover the process.
We are deliberately small. That means we cannot match a large vendor on feature count or marketing — and it also means the person who answers your question is the person who wrote the code. For a system holding payroll data, we think that trade is worth making.
Contact
Exploring the product, planning a custom system, or asking a direct question? Write or call. You'll hear from the people who build the software.