Where to start before you look at a single system
Write down everything that happens around your people in one month. How many people start, how many contracts and amendments, how many times attendance gets corrected before payday, how many deadlines someone is keeping in their head. That list is the spec. Without it you'll compare features you may never use — and miss the one you're doing this for.
54.4% of HR staff spend three hours or more a day on administration. The area they most often name for digitization is drafting employment contracts and documents — 58.7%.
Seven things HR systems really differ on
Systems don't differ by feature count. They differ on seven things you only find out in daily use: whether they cover your work, whether they connect to payroll, whether you can trial them, how fast they go live, whether you can switch them on in stages, what an employee sees, and how well they fit the law you work under.
| Criterion | Why it matters | How to check it |
|---|---|---|
| Coverage of the work you actually do | A system that handles 60% of your list leaves the other 40% in Excel | Go through your monthly list line by line, not the vendor's feature list |
| Payroll and accounting connections | The most common complaint about the systems people use is a missing connection to other systems — 35.9% | Ask about your payroll system by name, not about an “open API” |
| A trial before you sign | A demo shows the ideal case. A trial shows yours | A trial with no card and no commitment, ideally on your own data |
| Time to first real use | Rollouts that run for months often never finish | Ask for the range, and for what pushes it to the long end |
| Switching it on in stages | Turning everything on at once is the most common reason a system ends up unused | Can you run one module and leave the rest switched off? |
| Employee self-service | Without it, every question comes back to one person | Can an employee see their own vacation, documents and details? |
| Fit with Czech and Slovak law, data in the EU | Foreign systems handle local legislation poorly | Ask about specifics: the labor code, JMHZ filings, RUIAN address data, where the data sits |
What kinds of systems are out there
Local HR systems. Built around local legislation, with integrations to the accounting software Czech companies actually run, and support in the local language. Narrower than the global platforms, but they fit how the work really gets done.
Global HR platforms. Broad functionality, strong analytics, usually more expensive. Local legislation and connections to Czech payroll systems get passing attention, or none.
Payroll and accounting software with an HR module. You already have it, so it looks like the cheapest route. It will usually cover records, but not onboarding, reviews, training or employee self-service.
Spreadsheets and shared drives. These hold up longer than anyone expects — until an audit lands, the person who maintained the files leaves, or headcount outgrows what anyone can keep track of by hand.
Figure out what today is costing you
Take the hours that go into HR routine every week — the ones you wrote down at the start. Multiply them by what an hour of that work really costs you, salary plus employer contributions rather than the gross hourly rate. In the Czech Republic that works out to roughly CZK 370 (the median gross wage for an HR role plus employer contributions of 33.8%, at ~170 hours a month); use your own number if you're somewhere else.
Put the result next to the monthly price of the system. Don't use the savings a vendor promises you. Use the hours you already know about.
Ten questions to ask every vendor
These questions go after what a website and a sales deck won't tell you: what the system does today and what's still a promise, who maintains the connection to your payroll, how much work stays on your side, and how you get your data back out when you're done.
- Which items on my list does the system cover today, and which are on the roadmap?
- Do you have a finished integration with [your payroll system]? Who maintains it?
- Can I try it with no card and no commitment? For how long?
- How long did the rollout take for a client like us — and where did it drag?
- What exactly falls on us during the rollout, and how many hours is that?
- Can I run one module and switch the rest on later?
- What does a regular employee see, and what do they need to know how to do?
- Where does the data sit, and how do I get it out if we part ways?
- What happens to the price if we grow by twenty people?
- Who picks up the phone when something breaks, and in what language?
If the answer to questions 2, 4 and 8 is “I'll show you on the demo”, that's an answer in itself.
Five mistakes that keep coming back
Choosing by the length of the feature list. A feature you never switch on is worth nothing. What counts is the overlap with your list, not the total.
Skipping the trial. The vendor runs the demo. You run the trial — and that's where you find out whether you can use the thing without being walked through every step.
Deciding without the people who will work in it. A system picked by management alone usually ends with the old spreadsheet still running next to it.
Switching everything on at once. Eight modules in one day means eight sources of resistance at once.
Underestimating the migration. Data in five spreadsheets across three places doesn't move itself. Ask who does it and what format each thing has to arrive in.
What to watch on the legal side
Employee data falls under GDPR, so ask where it physically sits and who has access to it. If a system uses AI to recruit or evaluate people, the EU AI Act treats that as a high-risk use (Annex III, point 4), with December 2, 2027 as the deadline for full compliance. That isn't a reason to avoid AI — it's a reason to ask the vendor how they've handled it.
Checklist before you sign
Before you sign, run through the ten items below. Each one maps to a chapter of this guide. If you hesitate on any of them, that's exactly where these decisions tend to break — and asking now costs less than finding out after signing, when the contract is harder to move.
- I have a written monthly list of what our people admin costs us
- The system covers at least what's on that list
- The integration with our payroll system exists and has been verified, not promised
- I have been through a trial with our own data, not just a demo
- I know how long the rollout takes and what falls on us
- I can start with one module
- At least one person who will work in it daily has tried it
- I know where the data sits and how to get it out
- I know what happens to the price as we grow
- I have an answer on how AI is handled and how it fits the EU AI Act
Picked a system? Next up: How to roll out an HR system.
FAQ
The five questions that come up most often while you're choosing — how long it takes, what it costs, whether it pays off without a full-time HR person, whether to go local or international, and whether you can try anything for free.
Speybl is an HR application for all of HR — eight modules from hiring to offboarding in one system: people, recruitment and onboarding, attendance and shifts, performance, data and insight, documents and signatures, assets, training. AI agents take the routine steps off your hands and pass the result back for approval. It connects to Pohoda, Pamica, Money S3, Helios, Abra Flexi, Giriton, Microsoft 365, Google Workspace, Slack, DigiSign and Signi. Your data stays in the EU and support is available in English.
30 days free no credit card up and running in hours to days