Custom HR Systems: When to Build, When to Buy — and When to Do Both

The Mid-Market HR Trap

Every organisation between 50 and 5,000 employees eventually hits the same wall. The spreadsheets and shared drives that worked at 30 people are now a compliance risk. The enterprise suites — Workday, SAP SuccessFactors, Oracle HCM — quote implementation programmes that cost more than your entire technology budget. And the mid-market tools in between force your processes into their model: their approval chains, their leave rules, their appraisal cycles.

The result is what we call the HR trap: paying licence fees for a system your team works around rather than with. HR exports to Excel, managers keep shadow spreadsheets, and the "single source of truth" is anything but.

What "Custom" Actually Costs in 2026

The build-vs-buy calculation changed materially in the last three years. AI-accelerated delivery means a custom HR core — people records, onboarding workflows, leave and absence, document management, reporting — that would have been a £250K, 9-month programme in 2022 is now a £40-80K, 8-12 week build. That doesn't make building right for everyone, but it moves the break-even point dramatically.

Run the maths honestly over five years:

• SaaS HRIS: per-employee-per-month fees (typically £4-12 PEPM), implementation costs, plus the hidden cost of process workarounds and integrations that never quite work.
• Custom build: one fixed build cost, modest hosting (usually under £500/month), and support. No per-seat fees as you grow — the economics improve with headcount rather than worsening.
• The crossover: for most 200+ employee organisations with any process complexity, custom breaks even between year two and year three — and everything after that is margin.

When Buying Is Still Right

We tell roughly a third of the organisations who ask us about custom HR systems not to build one. Buy off the shelf when:

• Your processes are genuinely standard. If vanilla onboarding, standard UK statutory leave, and annual appraisals describe you, a good mid-market tool will serve you well.
• Payroll is the core need. Never build payroll. Tax tables, RTI submissions, and pension auto-enrolment are a regulatory treadmill best left to specialists.
• You have no one to own it. A custom system needs an internal owner who cares about it — not a developer, just a decision-maker.

The Hybrid Pattern That Wins

The strongest architecture we deploy is neither pure build nor pure buy. Keep a specialist payroll provider at the centre of the compliance-heavy work, then build the custom layer where your competitive difference actually lives:

• Onboarding workflows that mirror how your organisation really inducts people — kit ordering, access provisioning, buddy assignment, probation checkpoints — triggered automatically from a signed offer.
• Manager self-service designed around your approval reality, not a vendor's org-chart assumptions.
• An AI assistant over your policies, so "how much paternity leave do I get?" is answered instantly from your handbook rather than a ticket to HR. (See our guide to RAG in production for how to do this without hallucinations.)
• Reporting that answers your board's questions — attrition by team, time-to-hire, absence patterns — without a data analyst spending every month-end in Excel.

The question isn't "build or buy?" It's "which 20% of HR is where our organisation is genuinely different?" Build that. Buy the rest.

A Realistic Delivery Shape

A typical custom HR build with us follows our standard delivery process: week 1 scoping with HR and line managers, week 2 architecture and data model (including migration from whatever spreadsheets hold the truth today), weeks 3-8 building in two-week sprints with HR seeing working software every Friday, and real users onboarding real starters by week 5. Data migration, GDPR-compliant retention rules, and integration with payroll and identity (Okta, Entra, Google Workspace) are part of the fixed scope, not change requests.

You own the code, the data model, and the roadmap. When employment law changes or your organisation restructures, you change the system — you don't file a feature request and hope.