TL;DR: Payroll software calculates the present correctly and is silent about the past. When a labour rule is reinterpreted, the employer's problem is not the new calculation — it is the retroactive liability accumulated in a period where the relevant hours were never recorded as their own category. The product is an exposure meter and an evidence trail, sitting beside the payroll system rather than replacing it.
The evidence
PainHunt's HR and payroll domains hold 117 posts above the 10/15 threshold, averaging 11.4, with pain intensity 7.2/10 and willingness-to-pay 6.9/10 across 721 extracted pain points. The mix of sources is worth noting — Reddit, Mastodon, Medium, Bluesky, and remote job boards — because it means this signal comes from practitioners discussing their work, not consumers complaining about an app.
Two clusters in the current window show the same shape from opposite ends of the market. In the German and EU cluster, employers must now treat travel time in a company vehicle as working time. The consequences described are concrete: existing time-tracking systems do not capture travel time separately from regular hours, proving travel time against personal commuting is difficult in a wage audit, and the resulting back-payment claims are quantified at up to 400 EUR per employee per month. For a company of two hundred, that is a liability question, not an HR question.
In the North American agricultural cluster, the same structure appears with different variables: an hourly rate moving from $16.16 to $12.69, new housing-deduction rules to apply and evidence, compliance with state agricultural labour regulations, and payroll spanning more than twenty thousand temporary workers across multiple farms on varying rates. The manual work described is the tracking and reconciliation, not the arithmetic.
The feature requests point at the same missing layer from both directions: automatic travel-time tracking integrated with existing time-management or fleet systems, a payroll module that calculates the compensation the new interpretation requires, automated alerts when a wage rate changes, a housing-deduction module, and consolidated payroll across sites.
Why now
Labour rules are being reinterpreted faster than payroll configurations are being revisited, and the reinterpretations are increasingly retroactive in effect. A court decision or agency guidance does not create a rule on a future date — it clarifies what the rule always meant, which is precisely what converts a compliance task into a liability.
Work also stopped happening in one place. Travel between sites, vehicle time, remote hours, and multi-site temporary labour all sit at the boundary of what counts as working time, and that boundary is where the current wave of reinterpretation lands. The time systems in the field were designed for a clock-in at a fixed location.
And the mid-market has no one to catch this. Large employers have employment counsel who read the guidance the week it appears. A two-hundred-person company with a bookkeeper and an off-the-shelf payroll product finds out from an employee's lawyer, by which point the exposure has been compounding for a year.
The wedge
Do not build payroll. Build the meter that tells an employer what a rule change already cost them.
- Track rule changes for one jurisdiction and one worker category. German or Austrian travel-time rules for companies with vehicle fleets is a complete, defensible starting scope. Depth in one jurisdiction is credible; a global compliance feed is not.
- Quantify exposure against the employer's own history. Ingest the last twenty-four months of time and payroll data, apply the new interpretation retroactively, and produce a number with its assumptions shown. "You are likely exposed to roughly X, here is the calculation" is the entire sales pitch, and it is delivered before anyone signs anything.
- Close the capture gap going forward. Once the exposure is visible, the employer needs the hours recorded as their own category from now on — via fleet telematics, existing time systems, or a lightweight mobile capture. This is the recurring product; the exposure report is the wedge that gets you in.
- Produce the audit file, not the opinion. What survives a wage audit is a dated, sourced trail showing which rule was applied from when and on what evidence. Generate that artifact; leave the legal conclusion to the employer's counsel and say so in writing.
Distribution follows the rule change itself. Every reinterpretation creates a cohort of exposed employers who all learn about it in the same quarter, through the same accountants, trade associations, and payroll bureaus. Partner with the bureaus rather than competing with them.
Risks and honest caveats
- You are one step from giving legal advice. Producing a number that an employer acts on carries real liability if the interpretation is wrong. Keep the output evidential rather than advisory, involve local employment counsel in the rule model, and never let the interface imply a determination.
- Jurisdiction depth does not transfer. The German travel-time model teaches you almost nothing about North Carolina agricultural housing deductions. Each new market is close to a fresh build, so the business scales by depth and partnership rather than by feature.
- The buyer only exists when a rule changes. Demand is event-driven and lumpy. Without a durable second act — the ongoing capture layer, or a broader monitoring subscription — the revenue looks like consulting with a login.
- Payroll data is among the most sensitive there is. Individual wage records, housing deductions, and vehicle location traces together are a privacy problem before they are a product. In the EU, a works-council conversation about telematics-based tracking is not optional.
- The incumbent may ship the module. When a change is large enough, major payroll vendors eventually add it. Assume twelve to eighteen months, and make the retroactive exposure analysis — which they will not touch, because it implicates their own prior configuration — the durable part.
How to validate this further
Browse the HR, payroll, and compliance threads in the Pain Point Browser, then pressure-test the exposure-meter framing with the Idea Validator. Related reading: verifying contractor skills and credentials and when SaaS companies actually hire leadership.