Payroll stays quiet. That’s the whole product.
Payroll operations and oversight on the engine you already run. Not payroll software, and not a comparison against one.
Depending on who you want holding the cycle.
The cycle is the same either way. The tiers differ in who holds the marks.
Cut-off
Changes close: starters, leavers, timesheets, deductions.
ownerChecks
Reviewed against the record. Exceptions surface here — still corrections, not phone calls.
ownerApproval
Sign-off with a name against it, not whoever is nearest.
owner- The mark
Submission
Nothing crosses this line unchecked.
owner Funding
Money moves on a date somebody owns.
ownerFilings
Deadlines on the calendar, not in one person's memory.
owner
Oversight
You run it — we check itYour team submits payroll and we check it first. New starters, leavers, changes, timesheets and deductions reviewed against the record before anything is sent, and the exceptions come to us rather than to whoever is nearest.
Managed processing
We run it end to end — you approveEnd to end, including the parts that are only hard when they go wrong: off-cycles, corrections, terminations mid-period, and the entity differences that nobody wrote down. You approve, we run it.
Both are flat monthly, on top of Managed people ops or on their own. Every tier and every number, shared in full on our first call. Managed people ops
Three habits, and none of them are software.
Exceptions surface before submission
The difference between an hour and an afternoon is almost always when a problem is found. A classification mismatch caught the day before is a correction; caught during submission it is a phone call with a deadline attached.
Entity rules are written down
Multi-entity payroll goes wrong in the gaps between entities, where the rule exists only as something the long-serving person knows. We configure and document it, so the cycle does not depend on one person's memory.
Somebody owns the calendar
Cut-offs, approvals, funding dates and filing deadlines belong on a calendar with a name against each one. Most payroll problems are scheduling problems wearing a different coat.
What finance asks first.
Is this payroll software?
No, and we do not sell any. You keep whatever payroll engine you run — Rippling, ADP, Gusto, something else — and we provide the operating discipline around it. Comparing us to a payroll platform is comparing a pilot to an aircraft.
How do you charge for exceptions?
We do not publish a per-exception fee, because charging by the thing going wrong creates an incentive nobody should want. Exceptions are inside the monthly scope. If volume is genuinely unusual we say so and re-scope rather than invoice the surprise.
Which platforms do you work on?
Rippling and HiBob most often, ADP Workforce Now regularly, and others where the decision was already made before we arrived. The payroll rescue case study on this site is an ADP consolidation rather than one of our two lead platforms, which is the honest evidence for that claim.
Do you replace our payroll person?
Usually we make their week smaller rather than their job unnecessary. Oversight suits a team that wants a second pair of eyes before submission. Managed processing suits a company where payroll keeps landing on somebody whose actual job is finance, or operations, or founding the company.
What does the PE audit trail look like?
Every cycle leaves a record of what was checked, what was flagged and who approved it. That is the artefact a diligence process asks for, and building it after the fact is considerably harder than producing it as you go.
20 minutes. No deck. No pitch.
You talk. We map what you’re running and where to start. The fixed quote follows the call, in writing.