People & Workforce
HR operations that fit how you actually work
Your policies, your approval chains, your countries — composed from components that already exist, in weeks rather than a configuration project measured in quarters.
The problem today
HR suites model a generic employee. You do not employ generic people.
An HR platform ships with one opinion about the employee lifecycle. Where your organisation agrees with that opinion, it works well. Everywhere else, the gap becomes a project.
Every local rule is a customisation
A secondment policy, a union agreement, a country-specific allowance, a role that reports into two places at once. Each one is scoped, quoted and built by a partner — then re-tested at every platform upgrade, forever.
The work between the modules is yours to solve
Onboarding is not one module. It is HR, IT, facilities, payroll and a manager, in sequence, with approvals. Suites hand you the records and leave the coordination in email and spreadsheets.
You pay for the whole suite to get two modules right
Licensing is per-employee across a bundle, whether or not you use performance, learning or recruiting. The modules you do not use subsidise the two you needed.
What Ciphus composes
Composed from pre-built components — and a new one in days when needed
These are assembled, not written. The components exist; what changes per customer is how they are arranged and which of your rules they enforce. When something genuinely is not in the library, adding it is a matter of days, not a roadmap conversation.
Employee record
One record across employment, contract, compensation and history — with the fields your organisation actually uses.
Onboarding & offboarding
The full cross-team sequence, with approvals and access provisioning, tracked to completion rather than assumed.
Leave & absence
Your accrual rules and entitlements, including the ones that differ by country, contract or agreement.
Time & attendance
Capture that reflects how your people work — shifts, projects, sites or a mix of all three.
Org structure
Reporting lines, cost-centre alignment and dotted-line relationships that survive a reorganisation.
HR case management
Employee requests and cases handled with a record of what was asked, decided and by whom.
Why that matters
Composed, not extended
Weeks, not quarters
Composed from components that already exist. When one is genuinely missing it is added in days, not deferred to a roadmap.
A fraction of the cost
No multi-year implementation, and no partner-billed change request every time a policy moves.
No lock-in — and leverage
It runs on your infrastructure and your data model stays yours. Keeping the option to move is what changes the conversation at renewal.
Clara in people & workforce
Ask a question. Get the breakdown behind it.
Which onboardings are behind schedule, and what is holding them up?
7 of 23 April starters are behind, all at the same stage.
Broken down by driver:
IT provisioning
5
Awaiting hardware approval
Manager sign-off
2
Overdue by 4+ days
On track
16
No action needed
Illustrative example. Figures are not customer data.
Governed by default
Every action inside your own rules
Permissions, approval thresholds and delegation are part of the application, not a layer bolted on afterwards. Every action carries a record of what changed, who approved it and when — so an audit is a report rather than an investigation. What Clara can reach is exactly what the person asking can reach.