HR Tech Stack: The 5 Layers, What to Buy First, and How to Build by Company Size
What is an HR tech stack? The 5 layers every company needs, how to build yours by company size, and what to prioritize when you do not have an HR team.
HR Tech Stack
The 5 layers of HR technology, what to buy first, and how the stack changes as you grow
An HR tech stack is the set of software tools a company uses to manage its people: employee records, onboarding, payroll, compliance, and (as the company grows) hiring, performance, and analytics. At a 500-person company, this stack might include 8 to 12 specialized tools. At a 15-person company, it should include 2, maybe 3.
The problem with most HR tech stack guides is that they describe the enterprise version: HRIS plus ATS plus payroll plus performance management plus engagement surveys plus learning management plus workforce analytics. That is the right stack for a company with 200 employees and a dedicated HR team. It is the wrong stack for a company with 20 employees where the founder handles HR between product meetings. This guide covers the 5 layers of an HR technology stack, what to buy first, how the stack should evolve as you grow, and the mistakes that lead companies to either under-invest (spreadsheets until something breaks) or over-invest (enterprise tools at startup scale).
What Is an HR Tech Stack?
An HR tech stack (also called an HR technology stack or HR software stack) is the combination of software tools that a company uses to manage its human resources functions. It spans the employee lifecycle: from hiring (applicant tracking) through onboarding (workflows and document collection) to employment (records, payroll, performance) to departure (offboarding, exit documentation).
The stack metaphor comes from software engineering, where a "tech stack" refers to the layers of technology that work together to run an application. In HR, each layer handles a different function, and the layers connect through integrations (data flowing from the HRIS to payroll, from the ATS to onboarding, from performance reviews to analytics). The quality of these integrations matters as much as the quality of the individual tools.
The 5 Layers of an HR Tech Stack
Every HR tech stack, regardless of company size, is built from these five layers. The difference between a 15-person company and a 500-person company is not which layers exist. It is how many layers are active and how sophisticated each one is.
The layers are listed in priority order. Layer 1 (foundation) should be implemented first because every other layer depends on it. You cannot run payroll without employee records. You cannot track performance without knowing who reports to whom. You cannot analyze workforce data without a database to analyze. Start with the foundation. Add layers when the operational pain of not having them exceeds the cost and complexity of adopting them.
Layer 1: The Foundation (and Why It Comes First)
The foundation layer is the non-negotiable. It is the system that stores every employee record, automates onboarding for every new hire, manages compliance documents with e-signature, provides a visual org chart, and gives employees self-service access to their own information. Without it, employee data scatters across spreadsheets, filing cabinets, email, and the founder's memory.
| Function | What It Does | Why It Cannot Wait |
|---|---|---|
| Employee database (HRIS) | Centralized profiles with contact info, role, department, start date, and employment details | Without it, you cannot answer basic questions: how many employees do we have in California? When did this person start? |
| Onboarding workflows | Automated task sequences for every new hire: paperwork, training, check-ins, introductions | Without it, onboarding quality varies by who runs it and what they remember to do |
| Document management with e-signature | Collect and store signed I-9, W-4, offer letters, handbook acknowledgments, and policy updates | Without it, compliance documents are incomplete, unsigned, or lost |
| Org chart | Visual reporting structure connected to the employee database | Without it, new hires do not know who they report to and how the team is organized |
| Employee self-service | Employees update their own address, emergency contact, and tax withholding | Without it, every routine update goes through the founder or office manager |
A platform like FirstHR covers the entire foundation layer: AI-powered onboarding wizard, e-signature, HRIS with employee profiles, visual org chart builder, training modules, and self-service portal. The cost is $98 per month flat for up to 10 employees or $198 per month for up to 50. This is the foundation that everything else builds on.
Organizations with strong onboarding see 82% better new hire retention (Gallup). The foundation layer is where onboarding lives, which makes it the highest-ROI layer in the stack by a wide margin.
What the Five Layers Leave Out
The five-layer model describes the HR functions every company eventually touches. It does not describe every piece of software you may be legally or operationally required to run. Four functions sit outside the core layers, and whether you need them depends on how you employ people rather than on how many people you employ.
| Function | Who Actually Needs It | What Triggers the Purchase |
|---|---|---|
| Time and attendance | Any employer with nonexempt (hourly, overtime-eligible) staff | The FLSA requires accurate records of daily and weekly hours worked for nonexempt employees. It does not prescribe a format, so a paper timesheet is legal. Buy software when you have shift workers, multiple locations, or overtime disputes you cannot reconstruct. |
| Scheduling | Retail, hospitality, healthcare, and anyone running shifts | Multiple shifts per day or predictive scheduling laws in your city or state, which require advance posting of schedules and premium pay for late changes. These laws exist in a handful of jurisdictions, not nationally. |
| Benefits administration | Employers offering health coverage, and every applicable large employer | Once you average 50 or more full-time and full-time-equivalent employees, you are an applicable large employer under the ACA and must file Forms 1094-C and 1095-C. Before that threshold, a broker portal plus your payroll deductions usually covers it. |
| Learning management (LMS) | Regulated industries and companies with required annual training | Mandated training you must prove was completed: harassment prevention training required in several states, safety training, licensure or continuing education. Otherwise the training module inside your foundation platform is enough. |
Time and attendance is the one that most often gets skipped and most often costs money later. Wage and hour claims are decided on records, and when the employer has no reliable record of hours worked, the employee's reasonable estimate tends to carry the day. If your timekeeping is a group text and a manager's memory, that is a liability sitting outside your stack, not a cost you have avoided. Rounding rules deserve the same attention: rounding is permitted under federal law only when it is neutral over time, and some states have narrowed or effectively eliminated it, so a rounding setting your vendor turned on by default is worth checking against your own state's rules.
Sample Stacks by Company Size
| Company Size | Active Layers | Tools | Approximate Monthly Cost |
|---|---|---|---|
| 5-10 employees | Layer 1 (Foundation) + Layer 2 (Payroll) | HRIS with onboarding and documents ($98 flat) + Payroll provider ($100-200) | $200-300/month total |
| 10-25 employees | Layers 1-2 + Light Layer 3 | Foundation ($98 flat) + Payroll ($150-300) + Simple ATS or job board ($0-100) | $250-500/month total |
| 25-50 employees | Layers 1-3 + Light Layer 4 | Foundation ($198 flat) + Payroll ($200-400) + Dedicated ATS ($100-300) + Basic performance tools ($50-200) | $550-1,100/month total |
| 50-100 employees | All 5 layers | Foundation + Payroll + ATS + Performance platform + Basic analytics | $1,000-3,000/month total |
| 100+ employees | All 5 layers (enterprise) | Enterprise HRIS + Payroll + ATS + Performance + Engagement + LMS + Analytics + Comp benchmarking | $5,000-15,000+/month |
Notice the pattern: the foundation layer and payroll are constant across every size. Payroll is the one layer almost nobody builds themselves. What changes is how many additional layers are active and how sophisticated each tool is within a layer. A 15-person company does not need a $500 per month ATS. A spreadsheet or free job board handles 3 to 5 hires per year. The ATS becomes worth its cost when hiring volume exceeds 10 positions per year, and the cost of manual tracking (lost candidates, inconsistent screening, slow response times) exceeds the tool cost.
How to Build Your HR Tech Stack
| Step | What to Do | Common Mistake to Avoid |
|---|---|---|
| 1. Start with the foundation | Choose an HRIS with onboarding, document management, e-signature, and org chart. This is your single source of truth. | Skipping this and starting with payroll or an ATS. Payroll needs employee data. The ATS needs somewhere to send accepted candidates. |
| 2. Add payroll separately | Choose a dedicated payroll provider. This is a specialized function that deserves a specialized tool. | Expecting your HRIS to handle payroll. Most HRIS platforms designed for small businesses do not include payroll, and that is fine. |
| 3. Use free tools for early hiring | Post on 2-3 job boards. Track candidates in a spreadsheet or use a free ATS. This works for fewer than 10 hires per year. | Buying a $300/month ATS when you hire 4 people per year. The tool costs more than the problem. |
| 4. Formalize performance at 25+ | When informal quarterly conversations are no longer enough, add a lightweight performance tool. | Adding performance management at 10 employees. Quarterly 1-on-1s with written notes accomplish the same thing at that scale. |
| 5. Add analytics when the data exists | Workforce analytics requires at least 50+ employees and 2-3 years of data to produce actionable insights. | Buying analytics dashboards at 20 employees. The sample size is too small for statistical significance. |
The principle: add layers when the pain of not having them is greater than the cost of adding them. If you have never missed a compliance deadline, your document management is working. If candidates are not falling through the cracks, your hiring process is working. Do not fix what is not broken. Invest where it hurts. Research from the Work Institute shows that 20% of turnover happens within the first 45 days. If early turnover is your pain point, invest in the foundation layer (onboarding), not analytics.
What a Digital HR Strategy Means at This Size
A digital HR strategy is the decision about which HR work stops being manual, in what order, and how you will know it worked. At enterprise scale that becomes a multi-year transformation program with a budget and a steering committee. In a company with no HR department, it is the sequence above plus two things that sequence does not cover.
The first is adoption. A platform that managers never open leaves the founder doing the work by hand anyway, so every tool needs one named owner, a date the old process stops, and a plan for retiring the spreadsheet it replaced. Running the manual process alongside the new one indefinitely is the most common way a rollout quietly fails.
The second is measurement. Pick two numbers before you buy: the hours per week the process consumes today, and one outcome the tool is supposed to move, such as paperwork completed before day one or turnover inside the first 90 days. Look at both a quarter after launch. If neither moved, the tool was not the fix.
How Data Actually Moves Between Tools
"Integrates with payroll" is a sentence that hides five very different things. Before you accept it from a vendor, ask what kind of connection it is, which direction data travels, and how often it runs. Those three answers determine whether the integration saves you work or just relocates it.
| Connection Type | How It Works | What to Expect |
|---|---|---|
| Native integration | The two vendors built and maintain the connection. You authorize it once in the settings. | The only kind that reliably runs without attention. Ask which fields it syncs, not just whether it exists: many native connectors move name and hire date but not compensation or department. |
| API integration | One system calls the other programmatically, usually built by you or a contractor. | Flexible and fragile. Someone has to own it when a vendor changes an endpoint. Reasonable at 100 employees with an IT team, rarely worth it at 20. |
| Unified API middleware | A third-party service normalizes many HR systems behind one connector. | Common in the vendor's own plumbing rather than something a small business buys directly. Adds a party that holds your employee data, so it belongs in your vendor security review. |
| Scheduled file transfer | A CSV is exported on a schedule and imported by the other system. | Standard for benefits carriers and 401(k) providers. Works well, but errors surface a cycle late, so someone has to read the exception report. |
| Manual re-entry | A person types the same information into both systems. | Not an integration. Budget the hours honestly: at 30 employees, new hires plus address, rate, and status changes is a recurring administrative task, not a rounding error. |
The rule that keeps a multi-tool stack coherent is one field, one owner. Decide, field by field, which system is authoritative, and make every other system a copy. In practice: the HRIS owns identity data (legal name, hire date, department, manager, employment status), payroll owns compensation history, tax withholding, and bank details, the benefits carrier or broker owns enrollment elections, and the ATS owns nothing after the offer is accepted. When two systems both claim to own pay rate, you will eventually pay someone the wrong amount and spend a day working out which record was right.
Direction matters as much as ownership. A termination entered in the HRIS should stop the next payroll run and trigger a benefits termination that starts the COBRA notice clock. A raise entered directly in payroll, bypassing the HRIS, leaves your records showing the old number the next time you benchmark compensation or defend a pay equity question. Pick the entry point for each event type, write it down, and hold to it. Most stack failures are not integration failures. They are two people entering the same change in two different places.
Write it down here, before the next tool goes in. The first tab settles ownership field by field and how each copy is kept current; the second settles where each event gets entered and what it has to set off downstream. The seeded rows are the split described above, and the blank ones are the fields your own stack argues about.
| A | B | C | D | E | F | G | |
|---|---|---|---|---|---|---|---|
| 1 | Data field | System of record | Systems that hold a copy | How the copy is updated: native, API, file transfer, or manual | Who enters the change | How often it syncs | Last verified |
| 2 | Legal name | HRIS | Payroll, benefits carrier | ||||
| 3 | Hire date | HRIS | Payroll, benefits carrier | ||||
| 4 | Department and manager | HRIS | |||||
| 5 | Employment status | HRIS | Payroll, benefits carrier | ||||
| 6 | Pay rate and compensation history | Payroll | HRIS holds a copy only | ||||
| 7 | Tax withholding elections | Payroll | |||||
| 8 | Bank details for direct deposit | Payroll | |||||
| 9 | Benefit enrollment elections | Benefits carrier or broker | Payroll takes the deduction amount | ||||
| 10 | Candidate and offer history | ATS until the offer is accepted, then nothing | |||||
| 11 | Home address | ||||||
| 12 | Emergency contact | ||||||
| 13 | Time off balances |
HCM Integration in a Small Stack
HCM integration is the same question one tier up. A human capital management suite bundles the HRIS, payroll, benefits, and talent layers under one vendor, so the connections that matter point outward: to accounting for labor cost, to benefits carriers for enrollment, and to identity management for provisioning and shutoff on the last day.
A suite is sold as the end of the integration problem, and it relocates that problem rather than removing it. Ask a suite what you would ask a connector: which fields the modules genuinely share, which ones still move by file transfer, and whether accounting can pull labor cost without someone exporting it by hand every month.
The difference between an HRIS and an HCM is worth settling before a demo settles it for you, because for most companies under fifty people a full suite is more platform than the work actually requires.
Migrating Off Spreadsheets Without Losing Records
The move from spreadsheets to a real foundation layer is usually described as a one-day import. It is closer to a two-week project at 20 employees, and most of the work is cleanup rather than data entry. The spreadsheet has three versions, two of them on someone's desktop; job titles do not match what is in the offer letters; four people have no recorded start date. Migration is the moment all of that surfaces.
A sequence that works: first, freeze the spreadsheet and declare a single version authoritative so changes stop landing in the copy nobody is migrating. Second, reconcile the employee list against payroll, because payroll is the one system that is definitionally complete. Anyone being paid is an employee, and anyone in the spreadsheet who is not in payroll needs an explanation. Third, migrate active employees only, and archive terminated employees as records rather than trying to reconstruct their full profiles. Fourth, run one full pay cycle with both systems in view before you retire the old process.
The reconciliation is the step worth doing on paper rather than in your head, because every mismatch it surfaces needs an explanation and a name against it before anything gets imported. Work it one row per person, from the payroll list down, and record two things against each row: why the person appears in one list and not the other, and where the old file went. The employee directory guide has a reconciliation worksheet built for exactly this pass, and it works the same whether the destination is a directory or the whole foundation layer.
Retention is the part people get wrong. Migrating systems does not reset any clock and does not let you discard the old files. I-9s must be kept for three years after the date of hire or one year after employment ends, whichever is later, and they are best kept separately from the personnel file so an audit does not expose everything else. Under the FLSA, payroll records are kept three years, and the records that wage computations are based on, including time cards, are kept two. Several other rules run longer or shorter, and some states impose their own periods, so the practical answer is to keep the old records for the longest applicable period rather than deleting anything at migration.
If you store I-9s electronically in the new system, the electronic storage has requirements of its own: controls that maintain the integrity and accuracy of the record, indexing that lets you retrieve a specific form, an audit trail showing when a record was created or changed, and the ability to produce a legible copy on request. What you do not need to do is re-collect I-9s from existing employees because you changed software. Completing a new form when none is required creates its own problems, including the appearance of re-verifying employees you had no basis to re-verify.
When a PEO Replaces Most of the Stack
There is an alternative to assembling layers, and small employers should price it before they build: a professional employer organization. A PEO enters a co-employment relationship with you. It becomes the employer of record for payroll tax purposes, runs payroll, files employment taxes, sponsors or administers benefits, and usually carries workers' compensation under a master policy. You keep day-to-day direction of the work, hiring and firing decisions, and the business itself. In stack terms, a PEO collapses layers 1, 2, and most of benefits administration into one relationship, and gives you its platform whether or not you like its platform.
| Consideration | PEO | Your Own Stack |
|---|---|---|
| Pricing model | Quoted either as a percentage of gross payroll or a flat fee per employee per month. Cost scales with wages under the first model, so raises increase the bill. | Mostly flat or per-employee software fees. Cost tracks headcount, not payroll dollars. |
| Health benefits | Access to the PEO's larger risk pool, which is the strongest argument for a small employer that cannot get competitive rates on its own. | You buy through a broker on your own census, which at 10 employees can be expensive or limited. |
| Multi-state employment | The PEO handles state registrations, withholding accounts, and unemployment filings in states you have not entered before. | You register in each state yourself. Manageable for two or three states, a real burden past that. |
| Control and switching | The PEO's systems are your systems. Leaving means re-registering for your own tax accounts and rebuilding benefits, usually timed to a plan year. | You can replace one layer at a time without touching the others. |
| Tax liability | With an IRS-certified PEO (a CPEO), the customer is generally not liable for federal employment taxes on wages the CPEO pays. Certification is a specific IRS status, so confirm it rather than assuming it. | Liability for employment tax deposits and filings stays with you, wherever the software sits. |
Run the comparison in one unit before deciding. A percentage-of-payroll quote and a per-employee quote are not comparable until you convert both to annual dollars at your actual wage levels. A quote of five percent of gross payroll on a $2 million annual payroll is $100,000 a year; the same headcount on a software stack plus a broker is a different order of magnitude, but it does not include the benefits pricing advantage, the workers' compensation policy, or the state registrations. Compare what is inside each number, not the headline.
One thing a PEO does not do is take your legal status away. If you average 50 or more full-time-equivalent employees, you are the applicable large employer under the ACA employer mandate, not the PEO, and the responsibility for offering compliant coverage rests with you even when the PEO prepares and files the forms. The same logic applies broadly: a PEO changes who performs the work, not who ultimately owns the obligation.
Common HR Tech Stack Mistakes
| Mistake | Why It Happens | What to Do Instead |
|---|---|---|
| Too many tools too early | Each tool seemed like a good idea individually | Start with 2 tools (foundation + payroll). Add one at a time when the need is clear and measurable. |
| No integration between tools | Tools were chosen independently without considering data flow | Before adding a new tool, verify it integrates with your HRIS. Employee data should flow, not be re-entered. |
| Per-employee pricing across the stack | Each tool charges $5-$15 per employee. At 5 tools and 40 employees, that is $1,000-$3,000/month. | Choose flat-fee pricing on the foundation layer. Per-employee pricing on payroll is standard, but everywhere else, flat is better. |
| Enterprise tools at startup scale | The demo impressed you. The features seemed important. | Buy for your current size, not your aspiration. You can upgrade when you outgrow the tool. |
| Spreadsheet until crisis | Spreadsheets work until they do not. The transition happens during a compliance issue. | Move to a dedicated HRIS at 10 employees. The migration is easy when you have 10 records. It is painful at 40. |
| Ignoring the foundation layer | Payroll gets set up first (legal deadline). ATS gets set up second (hiring pressure). HRIS comes last, if ever. | The HRIS is the central record. Payroll pulls from it. The ATS feeds into it. Set it up first, not last. |
The most expensive mistake is not choosing the wrong tool. It is using too many tools with no integration. Every disconnected tool creates a data silo where employee information lives in isolation. When data is scattered across 5 tools, no single tool has a complete picture, and the founder spends hours reconciling information that should flow automatically. Stack consolidation is one of the defining trends in the industry for exactly this reason. Research from Gallup shows that approximately 42% of employee turnover is preventable, much of it through better systems and processes that the right tech stack enables.
Frequently Asked Questions
What is an HR tech stack?
An HR tech stack is the collection of software tools a company uses to manage its people operations: hiring, onboarding, employee records, payroll, benefits, performance, and compliance. The stack can range from a single all-in-one platform to a set of specialized tools connected through integrations. For small businesses, a minimal stack includes an HRIS with onboarding and document management plus a separate payroll provider. Enterprise stacks typically add an ATS, performance management, engagement surveys, learning management, and workforce analytics.
What are the components of an HR tech stack?
The five core components (layers) are: (1) Foundation: HRIS, onboarding, document management, e-signature, org chart, and employee self-service. (2) Payroll and compliance: payroll processing, tax filing, and regulatory compliance. (3) Talent acquisition: job posting, applicant tracking, and candidate management. (4) Performance and engagement: reviews, goal tracking, surveys, and recognition. (5) Analytics and planning: workforce metrics, headcount planning, and compensation benchmarking. Not every company needs all five layers. Most businesses under 25 employees operate effectively with layers 1 and 2.
What is the difference between HRIS and an HR tech stack?
An HRIS (Human Resource Information System) is one component of the HR tech stack, specifically the foundation layer that stores employee data, manages profiles, and tracks employment information. The HR tech stack is the broader collection of all HR tools: HRIS plus payroll, plus ATS, plus performance management, plus any other tools the company uses. Think of the HRIS as the database layer and the HR tech stack as the entire technology ecosystem built on top of it.
How do I build an HR tech stack?
Start with the foundation layer: an HRIS with onboarding, document management, and e-signature. Add a payroll provider (this is almost always a separate, specialized tool). Stop there if you have fewer than 25 employees. Add an ATS when you are hiring more than 10 people per year. Add performance management when informal quarterly conversations are no longer sufficient (usually around 25-30 employees). Add analytics when you have enough data to analyze meaningfully (50+ employees). The key principle: add layers when the pain of not having them exceeds the cost and complexity of adding them.
Do I need all five layers if I have fewer than 50 employees?
No. Most businesses under 50 employees need only two layers: the foundation (HRIS, onboarding, documents, e-signature) and payroll. The talent acquisition, performance, and analytics layers become valuable as you grow past 25-50 employees. Building the full enterprise stack at 15 employees creates complexity without proportional benefit. The foundation layer is the one non-negotiable: every company with employees needs a centralized place to store records, onboard new hires, and manage compliance documents.
How much should an HR tech stack cost?
For a company with 5-50 employees, the minimum viable stack costs $200-500 per month total: $98-200 for the foundation layer (HRIS, onboarding, documents) plus $100-300 for payroll. Per-employee pricing models can push costs much higher: a $10 per employee per month platform costs $500 at 50 employees versus $98 flat. As you add layers (ATS, performance, analytics), costs increase. Enterprise stacks can reach $50-150 per employee per month across all tools. For small businesses, flat-fee pricing on the foundation layer is the most cost-effective approach.
Can I run HR with just a spreadsheet?
Yes, until you reach about 10 employees. A spreadsheet can track employee information, store start dates, and maintain a basic directory. It breaks down when you need signed compliance documents (I-9, W-4, handbook acknowledgments), onboarding consistency across hires, access controls for sensitive data (SSN, compensation), or audit trails for when records were created and modified. The transition from spreadsheet to dedicated HRIS typically happens between 8 and 15 employees, when the manual effort and compliance risk exceed the software cost.