You should not pay for recruitment in a month you are not hiring
Most HR suites sell you everything and let you use a third of it. Klok is built as modules with a registry: what is off is not billed, not shown in the menu, and not reachable by URL — the gate is enforced in the application, not merely hidden in the navigation.
Off Means Off
A disabled module returns a 403 rather than simply disappearing from the menu. Hiding a link is not access control.
Start With The Spine
Most companies begin with core HR, attendance, leave and payroll, and add recruitment or expenses when the need is real.
Per-employee Pricing
You pay per employee, so the bill follows the size of the company rather than a band you have just crossed by one person.
Change It Monthly
Modules are turned on and off as the year goes — hiring season on, hiring season off.
Modules off are not billed, and not visible
Most HR suites price as a bundle and let you use a third of it. The unused two-thirds are not free: they clutter every menu, they appear in every training session, and they are on the invoice.
In Klok the modules a company has switched on are held in a registry. A module that is off is not billed, does not appear in navigation, and returns a clear refusal if somebody reaches its URL directly — the check sits above the role check, so even an administrator does not see a module the company has not taken.
Start with the spine
Almost everybody needs the same core: employee master, attendance, leave, payroll. Recruitment matters when you are hiring; expenses matter when people travel; CRM matters if you go to events.
Taking those when they become relevant, and dropping them when they stop, is a monthly decision rather than an annual negotiation.
Priced per employee, changed monthly
Headcount moves, and seasonal businesses move a great deal. Pricing follows the people you actually have, and the module mix can change at the next cycle without a renegotiation.
Turning a module on and off
Choose
The spine, plus whatever is relevant this month. Everything else stays off.
It appears
Navigation, permissions and screens follow the registry — no menu items for things you do not have.
You are billed for that
Per employee, for the modules that are on. What is off does not appear on the invoice.
Change it next month
Add recruitment for a hiring push, drop it afterwards. No annual commitment to unwind.
Pay For What You Use FAQs
How is billing actually calculated?
Per active employee, per month, in advance, in rupees — with modules you have switched off not billed at all. Someone added mid-cycle is pro-rated rather than charged as a full month, and someone who exits stops being billed. The number on the invoice should be reconstructable from your own employee count and the published rate; if it ever is not, that is a bug, not a pricing strategy.
Does the price change as we grow?
The per-employee rate is published, so growth is arithmetic you can do in advance rather than a renegotiation trigger. Changes to an existing subscription come with notice and take effect at renewal, never mid-term — and founding customers keep their joining terms. Pricing surprises are how HR software vendors traditionally fund themselves; declining to do that is part of what we are selling.
What happens when we switch a module off?
Billing for it stops, and the data it created stays — switching off expenses does not delete last quarter's claims, it stops new ones and stops the charge. Switch it back on and you continue where you left off. Modules are meant to be tried honestly, which only works if trying is financially reversible.
Is there a minimum bill?
Yes — plans carry a minimum employee count, disclosed on the pricing page next to the rate rather than discovered on the first invoice. Below that size, the arithmetic of supporting a company properly does not work, and we would rather publish the floor than quietly pad small invoices to reach it.
What is deliberately not on the invoice?
Setup fees, implementation charges, per-module platform fees, API access, export fees, and the "annual support" line that is really the licence again. The invoice is employees times rate for the modules you run, plus GST. Everything a vendor can hide in an invoice is something a buyer eventually resents; a reconstructable bill is cheaper to defend than a padded one.
Who counts as an "active employee" for billing?
Someone with a live employment record in the period — not someone who exited last quarter, and not a candidate in your pipeline. Exits stop being billed; seasonal staff are billed for the months they actually exist on the register. If your headcount and the invoice ever disagree, the register is the arbiter, and you can read it yourself.
See it on your own data
Fourteen days, no card. Load a handful of employees and judge it against how you work today.