Guides, read 8 Nov 2026
Twelve guides to the people tech stack
- How many people tools a company needs at each sizeFive at 50, nine at 150, eleven at 500, fourteen at 1,000, and which of them were chosen on purpose
- When to consolidate and when not toThree reasons to merge, three reasons to keep, and the one test that settles each category
- What you lose when you drop a point toolThe depth, the history, the benchmark and the champion, category by category
- The integrations to keepPayroll, the ATS and the identity tool, and the direction the data should flow
- How to price a stackPer seat, per month, times 36, plus the three lines the pricing page hides
- Performance reviews inside an HRIS versus a specialistOne cycle a year on a template, or calibration as the People team's main product
- Engagement surveys inside an HRIS versus a specialistResults by manager on the record, or benchmarks and people science from a panel
- Compensation cycles inside an HRIS versus a specialistThe cycle belongs on the record; the benchmark belongs to whoever has the data
- The IT side of the people stackWhich half of IT belongs in the people system, and which stays with the IT team
- How to run a consolidation in a quarterThirteen weeks: inventory, decide, migrate the record, move the modules, cancel
- What to tell the vendors you are cancelingThe notice, the export, the read-only month and the renewal clause
- The people stack at 50, 150, 500 and 1,000Four sizes, four worked consolidations, and the category that changes at each step
- Best of breed versus all-in-one in 2026The old argument was module depth; the new one is whether the system builds what the tool sold
Last reviewed 10 Nov 2026.