Bring your worst
payroll month.
No deck, no discovery call before the real call. We ask about your policies and your edge cases first, then show you the parts of the product that handle them — and the parts that do not.
What happens in the 30 min
Questions first, product second.
- 1
First ten minutes: your policies
How leave accrues, what carries forward, which locations have their own holiday calendar, how shifts are set up and what happens when one crosses midnight. We ask; you talk.
- 2
Next ten: your payroll edge cases
The components nobody else models cleanly. Mid-year ceiling crossings, arrears, prorated joiners, full and final settlements, the state where professional tax works differently.
- 3
Last ten: the parts that usually break
We show those specific things in the product, on data shaped like yours. Not a tour of the dashboard — the two or three places your current system loses.
If it becomes obvious in the first ten minutes that we are not the right fit, we will say so and give you back the other twenty.
Who should be on the call
Two people, not a committee.
Whoever runs payroll
The person who knows why last March was painful. They will spot in five minutes what a feature list cannot tell you in an hour.
Whoever will use it daily
HR ops, not just the person signing. If the people who open it every morning do not like it, nothing else matters by month three.
Optionally, someone technical
If isolation, SSO or the audit trail are part of the decision, bring them and we will go into the mechanics rather than the summary.
What you get afterwards
In writing, within a day.
- A written note on what would work, what would need configuring, and what we do not do at all.
- The specific answer to every edge case you raised, including the ones we had to go and check.
- A rough implementation shape and timeline — including the parallel payroll run, which is the part that takes real time.
- A price for your shape: the tier your modules need, at the band your headcount sits in.
The list of what we do not do is part of the note, not something you discover in month four. It is the most useful paragraph in it.
Come prepared
Bring the case that broke the last system.
A demo on invented data proves nothing. These four are the ones that separate HR software that holds up from HR software that needs a spreadsheet next to it — pick whichever is yours.
A night shift that crosses midnight
Which day does the punch belong to, and what does that do to overtime and to the attendance day in payroll?
Someone who crossed the PF wage ceiling mid-year
What happens to the contribution from that month, and what does the variance report say about it?
A leave policy with a carry-forward cap
Accrual, the cap, the encashment at year end, and the balance an employee sees on the day it resets.
A location with its own holiday calendar
One workspace, several states, different lists — and a leave request that spans two of them.
Would rather write than talk? Send us the question — or email hello@zivohr.com and we will answer it in writing.