Why we publish our limits next to our claims

If you have read more than one page of this site, you will have noticed a pattern. Almost every description of what HRMS does is followed by a plain note about what it does not yet do, or what needs checking first. That is deliberate. This article explains why.

The idea behind the product

Our positioning is a short phrase: people operations you can explain. A final number is only part of payroll. The employee record, the time inputs, the adjustment and the applicable rule matter too. HRMS is built around keeping that history available, so a team can trace a result back to the records and rules behind it.

A product built around explanation creates an obligation. If we ask you to expect a clear answer from your HR records, you should be able to expect the same from us.

The tension in software marketing

Software websites usually describe the finished vision. Features appear without their conditions. A demo looks like a deployment. A partial capability is described in the same words as a complete one. The reader is left to discover the boundary later, often after real data or real money is involved.

For HR and payroll that is a particular problem. These systems hold salaries, personal details and the basis for decisions that affect people's livelihoods. A misread claim is not a minor inconvenience.

What we decided

Our view is that software should explain its purpose in everyday language, the interface should help people understand the next step, and the website should be clear about what is available today. In practice, that means:

• Availability sits next to the claim, not on a separate page you might not read.
• Evidence is described for what it is. The local review started the core platform with 24 seeded employees and 651 recorded events, and exercised supporting AI, geolocation and document services. That is evidence of local evaluation, not a production customer result, and we say so.
• Broader ambitions stay labelled as direction until they are demonstrably available.

The limits we state, and why each matters

Each of these changes a decision. Knowing that login is a demo persona selector tells you not to upload real data yet. Knowing that the rule pack is not statutory validation tells you to involve your payroll adviser. Knowing that the history check is tamper-evident rather than immutable tells you which other controls you still need; our article on tamper-evident vs immutable goes into that.

What we choose not to say

Some things are absent from this site on purpose. There are no customer testimonials or logos, because we do not have verified ones to show. There is no certification badge, because none has been obtained. There is no price, no free trial and no response-time promise. There are no countdowns or invented scarcity. We do not describe payroll as fully compliant, records as certified immutable, salaries as guaranteed accurate, or AI as deciding pay; payroll uses deterministic calculation and rule paths, and AI explanation features are separate.

Why this helps you

Stated limits make evaluation faster. Instead of spending a walkthrough discovering the boundary, you can spend it testing whether the product fits the part of your work that matters. You can ask which steps work today, which depend on setup and which are still product direction, and check the answers against the trust and availability page.

It also makes the conversation more honest in both directions. If HRMS is not the right fit yet, it is better for both sides to know early.

What we want you to judge

Judge the product on the workflow you can see, the records you can inspect and the fit with your own situation. Ask difficult questions. A clear answer is more useful than a broad promise. The FAQs collect the questions we think are most worth asking, and the about page sets out our product point of view.

The takeaway

People operations you can explain is a standard for the product and for how we talk about it. Every claim on this site should be traceable to what was actually reviewed, with its limit beside it. If you find one that is not, we would like to know. And if the limits above still leave a workflow worth exploring, the evaluation page explains how to scope a sample-data walkthrough.