Payroll work needs the right person close to the work.
Large PeopleSoft Payroll engagements often separate senior judgment from hands-on execution. One person scopes the work, another designs it, another builds it, and the internal team inherits whatever made it through that chain. Payroll is too exacting for that much distance between decision and delivery.
This is not a value problem. It's a structural one. The economics of large consulting firms require leverage — many hours billed by junior staff, fewer by senior. Payroll work resists that model because the consequences of getting it wrong are concrete and recurring. A bad interface fails every two weeks. A misconfigured earnings code shows up on every pay stub until someone notices. A garnishment rule that's almost-right generates legal exposure on day one.
J.H. Randolph & Co. exists for the segment of work where senior judgment and hands-on execution need to live in the same person. The pricing reflects that reality. The engagement model does too.
Direct, end to end, documented.
Every engagement is run start-to-finish by the senior practitioner. There's no "we'll have someone reach out" hand-off, no Tuesday status call with three people who weren't in the kickoff. The person who scopes the work is the person who builds it, validates it, and writes the documentation.
That model has obvious limits. Capacity is finite — typically three to four concurrent clients, depending on intensity. Engagements get scheduled, not slotted in. Year-end retainers fill quickly. The trade-off is that what gets delivered is genuinely what was promised, by the person who promised it.
The work itself is concentrated where PeopleSoft Payroll work is most concentrated: interface development, report writing, processing support, year-end engagements, tax updates, customization cleanup, optimization reviews, and training. Eight services, all run the same way.
Teams that take payroll seriously.
The clients who get the most out of this model are organizations where payroll is treated as the strategic function it actually is — not a back-office utility. They have an existing PeopleSoft instance, an experienced internal team, and a specific problem that needs an experienced second pair of hands.
Sometimes that's a one-time build: a new interface, a complex BI Publisher template, an off-cycle that's outgrown its current logic. Sometimes it's run-state support during a leave or a hiring gap. Sometimes it's the year-end engagement that turns a fire drill into a process.
Less common, but valuable: organizations weighing whether to migrate off PeopleSoft to a cloud HCM platform, who want a clear-eyed read on the option of staying — and what staying would actually require to do well.
A short list of real things.
You can expect that the first call will be a working conversation, not a sales pitch. You can expect that the written summary that follows will be specific — scope, timeline, fee, validation criteria — and that nothing in it will be aspirational.
You can expect that during the engagement, the person you're talking to is the person doing the work. You can expect documentation that the team can actually use after the engagement closes. You can expect that scope creep is discussed, not absorbed silently.
You should not expect glossy decks, junior-staff deliverables, or pricing structures designed to maximize hours. None of those are part of the model.