Put the first reliable record in place
Bring people details, documents, leave, sickness and starter work into one dependable system.
HollyHR · CharlieHR · BreatheCompare six products for the jobs that appear as a startup grows: keeping the first reliable record, onboarding regularly, giving managers access, connecting payroll and devices, and employing people internationally.
Start with the work that has become difficult. HollyHR, CharlieHR and Breathe cover different versions of the first dependable HR core. PeopleHR adds a tiered path into workflows and wider modules. Zelt and Humaans become more relevant when payroll, devices, integrations and detailed permissions need to work together.
Headcount is only a clue. Regular hiring, more managers, the first HR hire, connected payroll or devices, and the first international employee can each change the products worth considering.
Bring people details, documents, leave, sickness and starter work into one dependable system.
HollyHR · CharlieHR · BreatheStandardise onboarding and decide whether recruitment, engagement or workflow depth belongs in the same product.
CharlieHR · PeopleHR · HumaansTest approvals, private records and permission roles as people decisions spread beyond the founders.
PeopleHR · Humaans · ZeltBring HR data closer to payroll, devices, apps and the integrations your operating model now depends on.
Zelt · Humaans · PeopleHRMove people details, documents, leave and starter records into one system with clear ownership.
Test tasks, reminders, documents and ownership across several starters, not only one polished demo.
Check exactly what each manager can view, change and approve before responsibility spreads.
When the first HR hire arrives, automation, analytics, performance and reliable integrations may justify a broader system.
Decide which system owns each record and how corrections move between HR, payroll, finance and IT.
An employer-of-record or global employment platform may become a separate decision from the domestic HR system.
Free covers up to 10 active employees counted for billing. Standard costs £2 per active employee counted for billing per month or £20 per active employee counted for billing each year, before tax.
A UK startup wants a focused HR core, clear public pricing, free access through 10 active employees, API and MCP access, and a documented export route.
Choose a broader or longer-established product when native payroll, recruitment, devices, performance, mobile apps or an established customer history matter now.
Charlie costs £45 a month for 5 to 14 people, £105 for 15 to 29 and £180 for 30 to 49. Recruit and Advice are separate products.
Founders or operations teams want onboarding, time off, engagement and performance together, with recruitment or HR advice available separately.
Model the normal headcount band. If you need Recruit or Advice, confirm its current price and billing terms.
Core HR costs £24 for 1 to 10 people, £44 for 11 to 20, £99 for 21 to 50 and £175 for 51 to 100. Optional modules cost extra.
A UK startup wants an established self-serve HR core with mobile access, performance and optional workforce modules.
Price the next headcount band and every required add-on. A banded package can change sharply before the underlying work changes.
Published prices start at £3 for Starter, £5.50 for Core, £8 for Pro and £9.50 for Elite+ per employee each month.
A growing team wants a tiered route from records and absence into onboarding, performance, workflows, learning, analytics or UK payroll options.
Confirm which tier contains each workflow shown in the demo, then price that tier and any optional module rather than Starter by default.
Pricing is quote-led. The public plan table shows a 20-seat minimum and separates People, Money, Tech, Growth, Attendance and Talent modules.
A team of at least 20 wants People, Money and Tech modules in one connected platform, including payroll, devices and application access.
Ask for the exact quote, module scope, implementation and subscription terms. The public plan table applies a 20-seat minimum.
Pricing is quote-led. Growth and Enterprise have different permission, integration, security and support boundaries, with optional products shown separately as add-ons.
An HR team wants workflow automation, analytics, integrations and API access around one employee database.
Ask which permissions, integrations, security controls and support sit in Growth or Enterprise, then include every needed add-on in the quote.
Use a starter, a working-pattern change and historic information. Check what imports cleanly and what must be rebuilt.
Run one new starter through tasks, documents, reminders and ownership. Then do it again with a different manager.
Sign in with founder, manager and employee access. Check private files, unrelated teams and approval boundaries.
Write down where payroll, recruitment, devices and identity data begin, who fixes errors and how updates travel.
Include hiring, module changes, implementation, tax, contract terms and the trigger that would move you into another category.
There is no universal best product. HollyHR, CharlieHR and Breathe cover different versions of a dependable HR core. PeopleHR offers a broader tiered route. Zelt and Humaans are more relevant when payroll, devices, integrations and detailed permissions need to work together. Shortlist against the hiring, management or systems change you need to handle next, then run the same practical tests with each supplier.
Move when one reliable people record, manager access, leave calculation, starter ownership or exit evidence is becoming difficult to maintain. The right moment is an operating problem, not a fixed employee number.
Onboarding belongs in the same buying decision when starters arrive regularly and ownership is hard to coordinate. Recruitment only needs to be included when candidate workflow is an active problem. A separate applicant tracking system can be better than replacing a sound HR core.
Permission design and approval workflow become more important. Test what each manager can view, change and approve, including private files and people outside their team. Product breadth does not make a weak access model safer.
Only when one connected platform solves a real operating problem. Compare a native module, an integration and an export-led handoff separately. Ask which system owns each record and who fixes discrepancies between HR, payroll, finance and IT.
Local payroll, tax, employment law and benefits can change the buying category. Compare an employer-of-record or global employment platform for that work, then decide whether the domestic HR system should remain separate or connect to it.
Bring your team over from a spreadsheet. There is no card, no sales call and no lock-in. For up to 10 active employees, everyday HR is free.