Insights · 12 min read
A practical guide to building HR software: the modules you actually need, why payroll and compliance drive the cost, and what to build first.
By GGP Editorial
HR software looks simple from the outside. A list of employees, a place to request time off, a payroll run at the end of the month. The demo always looks clean. The hard parts live where the demo never looks: local payroll tax rules that change every year, permissions that stop one manager from seeing another team's salaries, onboarding that actually collects the documents you need, and the audit trail you will be glad to have when a dispute or a regulator shows up.
I write this from the vendor side. GlobeSoft is a software company founded in 2018 with 40-plus engineers and more than 300 delivered projects, and we have built enough internal business systems to know where HR projects stall. This guide covers what HR software actually needs, what it costs, how long it takes, and what you should build first.
If you are still deciding whether to build at all, our piece on custom software vs SaaS covers the build-versus-buy question in more depth.
The phrase covers three different products, and they have different scopes and different buyers.
An HRMS, or human resource management system, is the internal tool. A company builds or buys it to run its own people operations: employee records, onboarding, leave, attendance, payroll, and reporting. The buyer is an HR or operations leader who cares about accuracy, compliance, and how much manual work the team is doing. Some people call this an HRIS or an HCM; the naming differences matter more to analysts than to the build.
An HR SaaS product is the platform you sell. You build it once and sell it to many companies, which means multi-tenant architecture, per-tenant branding and configuration, and a different bar for security and support. The buyer is a founder who wants to run the product business itself.
A point HR tool is the focused version. A standalone applicant tracking system, a time-off tracker, a shift scheduler, or a payroll calculator. Smaller scope, one job done well.
The three overlap, but they are not the same build. An internal HRMS and a multi-tenant HR SaaS product have almost nothing in common after the employee record. Decide which one you are before you write a line of code.
Before you budget a custom build, check whether an off-the-shelf tool already covers you.
BambooHR and HiBob serve small and mid-size companies. Workday and SAP SuccessFactors serve large enterprises. Rippling bundles HR with payroll and IT provisioning. Gusto and ADP handle US payroll. Personio serves European SMBs. Deel handles global contractors and cross-border payroll.
You should build when one of these is true. Your workflows will not bend to the product, like a specific leave policy, a union agreement, a shift pattern, or a bonus scheme. Your HR data has to live in a system you control for security or compliance reasons. Or the HR product is the business you are selling, not a tool you use.
The middle path also exists. Buy the commodity modules and build a thin custom layer for the parts that differentiate you. Many companies run a commercial HRMS for records and payroll, then build a small custom portal for scheduling or a specific approval flow.
The visible features are the easy ones. Here is a realistic split between what you need on day one and what can wait.
| Must have in v1 | Can wait |
|---|---|
| Employee records and profiles | Performance reviews |
| Onboarding and document collection | Learning and development |
| Leave and time-off requests | Benefits enrollment |
| Manager approval flows | Recruitment and ATS |
| Employee self-service portal | Shift scheduling |
| Basic reporting | Org chart and headcount planning |
| Role-based permissions | Surveys and engagement |
| Audit log | Mobile app |
Employee self-service is the module that quietly saves the most time. Most HR teams drown in questions: how many days off do I have left, what is my parental leave policy, where is my payslip. A self-service portal that answers those without a human is where a good HR system pays for itself.
Payroll is where HR projects stall, and it is rarely the first thing founders think about.
The record-keeping side is easy. The tax side is not. Withholding rules, employer contributions, and filing deadlines differ by country and change every year. In the US you deal with federal, state, and sometimes local taxes. In Brazil you deal with INSS, FGTS, and a specific eSocial filing format. In the UK it is PAYE and auto-enrolment pensions. In Singapore it is CPF contributions. None of this is a nice-to-have you can skip.
There are two honest approaches. You integrate with a payroll provider that owns the tax calculation and filing for the countries you operate in, and your system passes the data over. Or you build the payroll engine yourself, which is only worth it when payroll itself is the product you sell, or when you operate in one country with rules you can maintain.
Most internal HR systems should integrate, not build. Hand the tax risk to a provider and keep your system focused on records, workflows, and reporting. The same logic applies to anything regulated: do not build your own e-signature or background-check engine when a mature service already exists.
HR data is personal data with extra weight. You are storing salaries, ID numbers, bank details, health information, and performance notes. That means a few things from day one.
Role-based access control. A manager sees their own team, not the whole company. HR admins see more. Nobody sees salaries who should not.
An audit trail. Who changed a record, when, and from what to what. You will want this for disputes, and some jurisdictions require it.
Data retention and deletion. Employment records usually have a retention period, and people have a right to have their data deleted in some regions. GDPR in Europe is the most familiar example, but it is not the only one.
Localization. Leave balances, public holidays, currency, and date formats differ by country. If you operate in more than one country, plan for it in the data model, not as an afterthought.
None of this is exciting, and all of it is where HR software either holds up or falls apart. We wrote about the same boring-but-necessary logic in enterprise software development.
Cost in an HR system is driven by four things, in rough order of impact.
Team. A small senior team of a product manager, a designer, two backend engineers, and one or two frontend or mobile engineers is the typical shape. Where the team sits changes the bill a lot: a senior engineer through a China-based team runs roughly $5,000 to $8,000 a month, against around $12,000 to $16,000 for the same role on a US salary. We cover those numbers in what software development costs in China.
Modules. An internal HRMS for one company with records, leave, and approvals is a smaller build than a multi-tenant HR SaaS product with payroll, which is smaller than a full HCM suite.
Payroll and compliance. This is the biggest hidden cost. Integration with a payroll provider, plus the work to keep leave policies and local rules correct, adds real time and real risk.
Integrations. Single sign-on, Slack or Teams, your accounting system, and e-signature each add time, and each is a place where scope quietly grows.
As a rough guide, a focused first version built by a small senior team typically lands between $40,000 and $120,000 depending on scope. An internal HRMS with records, leave, approvals, and reporting sits at the low end. A multi-tenant HR SaaS product with payroll integrations and per-tenant configuration runs well past that. Those are ranges, not quotes; the only number that matters is the one from a scoped proposal. We wrote a walk-through on getting a real estimate in how to estimate a custom software project.
A scoped first version usually runs three to six months from kickoff to launch. An internal HRMS can land in that window. A multi-tenant HR SaaS product with payroll integrations runs longer, often six to nine months. The spread comes from scope and third-party work, not typing speed. Plan for a discovery phase before anyone writes code, and a soft launch with a real department or a handful of pilot customers before you open the doors.
The way the system will be used shapes the data model early, so decide it up front.
Internal tool. One company, one set of rules, users are your own employees. Simpler permissions, no billing, no tenant isolation.
HR SaaS product. Many companies, each with its own data and configuration. This needs a multi-tenant design from the start, with tenant isolation, per-tenant settings, and a subscription and billing layer. It is expensive to bolt on later. We cover the trade-offs in multi-tenant SaaS architecture.
A point tool you sell. The smallest scope, but you still need accounts, billing, and support from day one.
AI has real uses in HR software, but they are narrower than the pitch decks suggest.
The useful ones are text work: screening and summarizing resumes, drafting job descriptions, answering routine policy questions through a chatbot, and summarizing performance notes into a review draft. These are genuine time savers, and they fit the "assistant, not decision maker" role that keeps you out of trouble. An AI should surface and summarize, not decide who gets hired or fired.
The risky ones are any place an algorithm makes a consequential people decision, like automated candidate ranking without a human in the loop. That is a compliance and fairness problem, not a feature. Keep the human in the loop and the AI on the drafting side. If you want to understand where AI actually pays for itself in business software, start with how to add AI to existing business software.
Scope the first version down to the shortest path an employee and a manager can walk end to end: the employee checks their leave balance and requests time off, the manager approves it, and both can see the record afterwards. If that loop works with the right permissions and an audit trail, everything else can follow.
Cut these from v1: performance reviews, learning modules, a mobile app, surveys, org-chart planning, and most of the analytics. None of them remove the manual work HR teams actually drown in. The self-service loop does. Our guide on how to build a SaaS MVP walks through the same trimming logic.
Building payroll before the workflows. Founders often start with payroll because it feels like the point. It is usually the last thing you should build yourself. Wire the approval flows and self-service first, then integrate payroll.
Ignoring permissions until the end. Access control is painful to bolt on after the fact. Decide who sees what before the data model is set.
Under-scoping the admin side. The employee-facing portal is what everyone demos. The admin side, where HR configures policies and runs reports, is where the team actually lives.
Treating localization as an afterthought. Adding a second country later is real work if the data model assumed one currency and one set of leave rules.
A focused first version from a small senior team typically lands between $40,000 and $120,000. An internal HRMS sits at the low end; a multi-tenant HR SaaS product with payroll integrations runs higher. See where the money goes in a custom build for the full breakdown.
Three to six months for a scoped first version is typical. Multi-tenant HR SaaS products with payroll integrations often run six to nine months.
If an off-the-shelf tool covers you, use it. Build when your workflows will not bend to the product, when you need to control HR data, or when the HR product is the business you are selling. See custom software vs SaaS for the fuller decision.
Usually not. Integrate with a payroll provider that owns tax calculation and filing for your countries, unless payroll itself is the product you sell.
Usually not. A responsive web portal covers most employees in the first year. Build the mobile app when employees tell you they need it, not before.
Internal tool, single tenant. HR SaaS product, multi-tenant, and design it that way from day one. See multi-tenant SaaS architecture.
GlobeSoft is a software development company founded in 2018, with 40-plus engineers and more than 300 delivered projects for over 100 clients across the US, Brazil, South Africa, and Singapore. We build custom software, mobile apps, SaaS platforms, FinTech systems, ERP and CRM, and AI products on a stack that includes Java, Spring Boot, Go, Python, React, Vue, and Node.
If you are planning an internal HR system, an HR SaaS product, or a focused HR tool, talk to us about your project. Send us the rough idea and we will help you scope the first version, estimate the budget, and figure out what to build first.
Tell us what you are building and where you are today. We typically reply within 24 hours.
