Case studies·Security
Paystubs that can't go out unlocked
Before, paystubs went out as plain email attachments — with all the personal details they carry. Now every paystub is matched to its employee, locked with bank-grade encryption before it's sent, and double-checked before it leaves the office. If the lock fails, nothing goes out.
RJ Bruno Inc.·Commercial plumbing contractor · Staten Island, NY
(est.)Hours saved are estimates based on how much work the system handles each week, not stopwatch measurements.
The problem
Every week, payroll produced one big PDF with everyone's paystubs in it. Someone in the office split it up by hand, one employee at a time, and emailed each stub as an attachment.
Those stubs carry the kind of personal details that should never sit unprotected in an inbox. And splitting them by hand was a weekly chance to send one person's stub to someone else — the kind of mistake you hear about from the employee, not from the system.
What we built
The combined PDF goes in. Individually locked, double-checked paystubs come out — and nothing else. Here's what the office sees:
- It splits the combined PDF into individual stubs and matches each page to exactly one employee on the roster.
- If a page matches nobody, or more than one person, it's set aside instead of guessed.
- Every paystub is locked with bank-grade encryption, using a password that belongs to that one employee, before it's sent. If the lock fails, nothing goes out.
- The system double-checks each file before sending: the right password opens it, a wrong password doesn't, and the page count matches the original.
- It won't mix weeks. The output folder has to be empty before a run starts, so a half-finished run can't be mistaken for a complete one.
- When it's done, it deletes every unlocked working copy.
What it means for the business
An estimated 52–143 hours a year (est.) back in the office — but the hours are the smaller win. The bigger one is that the company's most sensitive weekly document now leaves the office only when it's locked, checked, and addressed to one person.
Payroll, invoices, paystubs — that used to eat our week, and I always worried something would go out wrong. Now it runs on its own, it flags what it isn't sure about, and the sensitive stuff is locked down. I got my office back.
Have a process like this eating your week?
Tell us what it is. The first step is a working call — no prepared pitch, no commitment — to figure out whether it's the kind of repetitive, rule-following work that belongs in a system instead of on someone's desk.