Internal hr system: what is a hr system, what is hr system, and when building one inside the business is still the right answer

Deciding between building and buying

1. Name the process no product supports. Building is defensible when one central process is genuinely unusual and central to how the organisation works. Write that process down. If it fits in a paragraph and three vendors say they support it, the case for building has already gone.
2. Price the second year, not the first. A build is cheap in year one because the work is enthusiasm. Price the second year: statutory changes, a leaver who was the only person who understood the schema, and the report somebody needs urgently in December.
3. Decide who answers at two in the morning. Payroll runs on a date. If the system that feeds it is yours, the recovery plan is yours too. Name the person, write the runbook, and if neither exists, that is the answer.
4. Keep the record separate from the workflow. Where a build does make sense, build the workflow and buy the record, not the other way round. Workflows change every couple of years. A record has to survive a decade and prove itself to an auditor.

What is a hr system, in the sense that matters here

What is a hr system is usually answered with a module list, which is the least useful answer available. A more honest one: it is the place the organisation has agreed to keep the facts about employment, plus whatever software makes keeping them bearable. The agreement is the important half, and it is the half a build cannot buy.

That framing explains why internal builds so often stall. The build delivers the software and leaves the agreement unmade, so two departments carry on with their own spreadsheets and the new system becomes a third place to look.

The things internal builds get right

Fit, first. An internal team can model a secondment structure, a shift premium or an approval chain exactly as the organisation works, without the compromises a general product forces. Second, integration: an internal build sits inside your own identity and reporting estate, and the data does not have to leave it.

Third, and least discussed, is the absence of a renewal conversation. Organisations with long procurement cycles sometimes build simply to stop having the same negotiation every three years, and that is a rational motive as long as the maintenance cost is honestly booked.

The things they get wrong

Statutory change is the usual failure. Rates, thresholds and reporting formats move, and a bought product absorbs that as part of the subscription while a build absorbs it as a project nobody planned. The second failure is permissions, which are boring to build and catastrophic to get wrong.

The third is documentation. Internal systems are documented in the heads of the people who built them, and the departure of one person can turn a working system into a black box that nobody dares change.

Common questions

Is an internal hr system cheaper than a subscription?

Almost never once maintenance is counted honestly, including the statutory changes and the staff time to make them. It can still be the right choice, but the argument should be about fit and control rather than price.

Can we build the workflow and buy the record?

Yes, and it is usually the best version of the idea. Buy a product with a documented API for the employment facts, build the unusual process on top, and keep the obligations that come with a record on the vendor.

What happens to an internal build when the developer leaves?

That is the question to answer before starting. If the answer is not a written schema, a test suite and a second person who has actually changed the code, the system has a single point of failure that has nothing to do with software.

Does a build change our data protection position?

It moves more of the responsibility to you. You become the party that has to demonstrate the security of the processing rather than relying on a processor to demonstrate it, so the security review is yours to fund.

Coverage by country

• Employer of record vendors covering Singapore
• Employer of record vendors covering Mexico
• Employer of record vendors covering Spain
• Employer of record vendors covering Colombia
• Employer of record vendors covering United Kingdom
• Employer of record vendors covering France
• Employer of record vendors covering Hungary
• Employer of record vendors covering New Zealand