Why we built this

The problem with suites

A company that needs attendance today does not need payroll today. But HR suites are sold whole, so the buyer pays for six modules, configures two, and spends the next year explaining to staff why the menu is full of things nobody uses.

When payroll finally does become urgent, the suite has usually been half-abandoned, and the project starts again — often on different software, because nobody trusts the abandoned configuration.

Licence what you run

Here a licence names modules and limits, and the application obeys it everywhere: the menu, the permissions, the reports, the API. Buy Attendance and that is what the product is. Add Payroll in April and it appears, against the same employees, the same branches and the same history — no reinstall, no migration, no second login.

It also means a licence can be reduced without anything being destroyed. Downgrading stops new records beyond the limit; it never deletes the ones already there.

Payroll has to be defensible

Payroll is not a feature, it is a legal record. So salary components are expressions you can read back rather than formulas buried in code, a run locks once processed, and every consequential change — a revision, an approval, a licence edit — lands in an immutable trail with its before-and-after values.

When somebody asks in September why a number changed in April, that question has an answer.

Leaving should be easy

Every register and every report exports to CSV from the screen you are on, for anyone on your team holding the export permission — no request to us, no waiting. Software that keeps customers by making departure painful is not software we want to build, and the discipline of being easy to leave keeps us honest about being worth staying with.