Simple pricing, per active employee.
KES 200 per active employee per month. One rate, stated publicly.
PiPO HRIS is priced at KES 200 per active employee per month. An enterprise option is available for larger or more complex deployments, and is priced against scope rather than from a list. Implementation — scoping, configuration, data migration and training — is quoted separately after scoping, because it genuinely depends on your data and your structure and any number published here would be fiction.
What the rate covers
| Standard | Enterprise | |
|---|---|---|
| Rate | KES 200 per active employee per month | Priced against scope |
| Platform modules | The platform, configured to your scope | The platform, configured to your scope |
| Permanent and casual workers | Both, on one record | Both, on one record |
| Employee and manager self-service | Included | Included |
| Support | Standard support | Agreed in the engagement |
| Implementation | Quoted after scoping | Quoted after scoping |
| Integration scope | Confirmed during scoping | Confirmed during scoping |
“Active employee” means a person on the platform in the month — a casual worker engaged for part of a month counts once, not per engagement. Exactly how that is measured for your organisation is confirmed in the agreement.
What we do not do on price
There is no per-module pricing, because splitting a single record into billable modules would work against the whole design. There is no charge per payslip or per transaction, which in a casual workforce would penalise you for the exact thing the platform is best at.
Implementation is quoted after scoping rather than bundled into a headline rate. That is less convenient for comparison and more honest: the work depends on the state of your data and the number of decisions your organisation still has to make.
Common questions
A person on the platform during that month. A casual worker engaged for part of a month counts once rather than per engagement. The precise measure for your organisation is set out in the agreement.
No. Implementation is quoted separately after scoping, because it depends on your data quality, your structure and the integration scope.
It is for larger or more complex deployments — multiple entities, more complex integration scope, or specific support arrangements. It is priced against scope, so it is agreed rather than listed.
No. The platform is priced per active employee, not per module.
Want a number for your organisation?
Tell us your workforce size and shape and we will give you the platform cost and an implementation estimate after scoping.