Home / About VRS / Why we rebuilt

A decade of scars,
engineered in.

Everyone in this industry knows a nightmare story: the time-and-attendance rollout that dragged for two years, the payroll run that silently paid people wrong, the system nobody on the floor would touch. We know those stories from the inside – because we ran a workforce platform for live industrial customers for ten years. The new VRS is not version one of a guess. It is version two of a lesson.

"Most workforce systems are built in a boardroom and then meet reality. Ours met reality first – for ten years – and then we rebuilt it on everything reality taught us."
Rune Sleire Torblå · Founder & CEO, VRS
  • The old VRS still runs today. Real companies clock in on it every morning. We did not abandon a failure – we outgrew a foundation.
  • Every rule in the new engine exists because a customer's payroll needed it. Shift supplements, rotations that start on different days for different crews, offshore release rhythms, retroactive corrections – none of it is speculative.
  • We rebuilt because we refused to bolt year eleven onto year one's assumptions. The hardest thing a software company can do is start over while the old product still pays the bills. We did it anyway – deliberately, with the scars as the spec.
What ten years taught us

The scars – and what each one changed

These are the categories of pain every buyer in this industry recognises. We did not read about them in a report. We answered the support calls.

Scar 01 · Silent wrong pay

A number that looks right is worse than an error

The most expensive failures were never crashes. They were days that calculated plausibly wrong – a supplement missed, a rounding rule misapplied – discovered months later by an angry employee or an auditor.

Rebuilt: every calculated line carries a traceable lineage – tap any value and see exactly which rule produced it, from raw punch to payroll figure. Failures are loud, named blockers – never silent zeros.
Scar 02 · The two-year rollout

Big-bang implementations kill trust before go-live

We watched competitors' projects – and some of our own early ones – stall for quarters because the whole company had to move at once, and nobody could prove the numbers matched until everyone was already committed.

Rebuilt: pilot-first onboarding is the product's default motion – one location, one month, running in parallel with your existing system, numbers compared line by line before anyone commits. See how the pilot works.
Scar 03 · Corrections as an afterthought

Real operations live in the exceptions

Demos show the happy path. Reality is the forgotten clock-out, the retroactive department transfer, the shift that crossed midnight, the manager who must fix a day after payroll ran. Systems that treat corrections as edge cases collapse in month two.

Rebuilt: corrections are a first-class workflow with a full audit trail – workers propose, managers respond with reasons, every version of every day is preserved. Backdated changes recalculate and re-route automatically.
Scar 04 · Rules frozen in code

Every customer's agreement is different – and changes

Norwegian collective agreements, German working-time law, local plant deals – we spent years hard-coding variants and paying for it with every change request. The rule engine could not keep up with the negotiating table.

Rebuilt: rules are versioned configuration, not code – published with an effective date, replayable against history, testable before they touch a payslip. When your agreement changes, the system changes with it.
How we de-risk it for you

You never have to take our word for it

Because we lived the nightmare-rollout era, we designed the buying process so you can't have one. Svalen in Bergen started exactly this way – one location, one month, double-entry against their old system – before rolling out.

THE PILOT PATTERN
01

One location, live data

Pick one site or crew. They clock in on VRS from day one – real shifts, real supplements, real people.

02

One month, in parallel

Your existing system keeps running. At month-end we compare the numbers line by line – ours must match or beat yours, provably.

03

Then – and only then – rollout

You expand on evidence, not promises. If the pilot doesn't convince you, you've lost a month and gained a free audit of your current payroll.

Start with a pilot Read customer stories