We build one thing, for companies that already know what they need

The usual way to build this is one database with a company column on every row, and a filter that has to be applied correctly in every query, forever. It works right up until somebody forgets one.

We give every customer their own database and their own deployment instead. It is more work for us — each new customer is a real deployment rather than a row — and it means there is no query anywhere that could return two companies’ data, because there is no connection that can see both.

If a payment fails you get seven days and three reminders. After that the workspace becomes read-only: everyone can still sign in, look things up and export everything.

What does not happen, at any point, is deletion. Attendance history is a legal record belonging to the company that created it, and an unpaid invoice is a commercial disagreement — not a reason for that record to disappear.

Built in India, for Indian working patterns: regional holidays, GST on the invoice, and the shift and half-day conventions that imported HR software tends to get subtly wrong.