We don’t build HR software. We build your HR architecture.
An HR system architect, not a software house, not the usual implementation partner. We start with your organisation, its countries, entities and people processes, and get the base right, so you can build the exciting things on top later. A solid global base, made yours.
Most HR projects fail before a line is configured.
They don’t fail on features. They fail in how the project is framed. The trap is a loop, and almost everyone runs it.
HRIS treated as one-off
A project, not an architecture.
Budget → cram in everything
The full suite, all departments, all domains, all functions, squeezed into the best-negotiated price.
Focus on what’s missing
Attention goes to the gaps; everything that already works is forgotten or taken for granted.
Fixed scope, price, timeline
Locked before anyone has touched the system, so the requirements are guesses.
Delivered, goals missed
On time or not, the reason you started has slipped out of view.
The root cause is the one-off framing. Treat an HR system as a one-time project and every step that follows is set up to disappoint: a system nobody has used yet can’t be fully specified up front, and once it’s fixed there’s no partner left to correct course.
So we do it differently.
We stay engaged so the system corrects as you learn it. We start with what you already have, not what’s missing. And we’d rather deliver fewer processes that run completely than a full suite that half-works.
We’ll tell you honestly when an RFP is set up to disappoint you, and help you reshape it, even if that means we don’t bid. We’re looking for the customers we can actually make happy.
Five principles. Each breaks a link in that loop.
We’re an HR system architect, not a software house, not the usual implementation partner. These have held across twenty years and every release.
Built for organisations that cross borders.
Before any principle, there’s the platform: built from the ground up for organisations that run across countries, entities, currencies and languages. Not a feature, the prerequisite that makes everything else possible.
HR and payroll as one.
The most common point of failure isn’t a missing feature: it’s the boundary between HR and payroll. Different data, different timing, different ownership; that’s where things get lost and reconciled by hand the night before the deadline. We design that connection as the requirement everything else is built around.
End-to-end, or not at all.
A half-automated process has a return of zero. Automate the request but not the approval, and cost doesn’t fall. It shifts. We’d rather deliver fewer processes that run completely, hire-to-retire on one data model, than many that stall.
The system adapts to you, not the other way around.
Every HR team has a shadow system, leave in Excel, appraisals in Word, because their software forced them to fit it. If 80% of your HR already works, we don’t touch it; we complete the picture. The standard vendor says “adapt to our system.” Our response: we adapt the system to your processes, built in through our RAD methodology, faster than the change management a standard tool would demand.
An architecture partnership, not a project.
The most dangerous phrase in any HRIS engagement is “we’re going live”, because it implies the work is done. Your organisation grows, legislation changes, entities are added. An HR system is never finished. Most vendors scope, deliver, invoice, close, and five years later a new HR director inherits the mess. We stay engaged as your architecture partner.
Built for the AI era.
AI doesn’t fix bad data. It amplifies it. The organisations that get the most from AI are the ones with a clean, structured, connected people record it can actually use. Popay was built API-first, with field-level data classification and purpose-aware access, so every AI interaction is scoped, logged and GDPR-defensible.
One record. Everything reads from it.
Talent & development
Workforce & time
Payroll
Popay Core HR
One record for every employee, contracts, people, org, that the whole platform reads from and writes to.
That’s what “architecture” means in practice, not a stack of tools, but one record the whole platform reads from and writes to.
See your landscape, and where Popay fits.
Map your HR systems in a few clicks and see, independently, what stays, what connects, and where a solid base begins. Start where it hurts most; phase the rest.
A steady base. Then the exciting part.
With the foundation solid, you can finally move, automate, add, expand, without everything coming loose. That’s the point of steady and reliable: not to stand still, but to give you a base worth building on.
Let’s get your base right.
Steady and reliable, so you can do the exciting things.