Case Studies
-
My instincts was the trigger, before any of this was a career.
When I started working as an Assistant Comptroller, I was told they needed me to find $50k that somehow went missing. The Comptroller had accused one of the founding owners of having stolen the money. It had led to a court case.
Since I was tasked to find the money and to help build the evidence. So, I dug in. Two months later, I found the “missing” funds. It wasn’t stolen. The Comptroller had misallocated the funds and, rather than admit she was unable to do this particular project, she made the assumption and let someone else take the blame.
After I had resigned, they said they would pay me to keep investigating. So, after my regular 8am-5pm job , I worked with them from 6pm-closing. No one else could untangle it.
Numbers don't lie, even when people do. Someone just has to be willing to actually look.
-
A company had years of payroll tax filings and payments across multiple states, and nobody had ever stepped back to look at the whole picture at once.
She ran a full prior-period reconciliation, jurisdiction by jurisdiction, and found over-remittances sitting across several states. Money the company had already overpaid and never noticed.
Result: a six-figure refund, recovered within nine months.
No one flagged this as a problem before she looked. That's usually how it goes. The money isn't missing because someone did something wrong. It's missing because nobody ever checked.
-
A company needed to move from one PEO to another. That kind of transition is exactly where payroll disasters happen. Tax settings get lost, employee data gets mangled, and year-to-date limits reset when they shouldn't.
I went in as independent contractor to provide oversight for the entire migration. Every configuration, every tax setting, every employee record, reviewed and validated before and after the switch.
Result: zero data loss. Full tax-limit continuity across all 24,600 employees. No mid-year resets, no disruption, no configuration failures.
For a transition that size, the win isn't something dramatic. It's that nothing went wrong, for over twenty thousand people, during a process where almost everything could have.
-
A four-person payroll team was stuck processing payroll manually, all day, every day. That included a Systems Specialist and a 1099 Processor. Two people hired for specialized work who'd been folded into generic processing instead. Meanwhile, the company's PEO transition was falling apart under one manager trying to run it alone.
Then that manager went on leave.
Instinctively, I redesigned the entire payroll operations structure. I redefined the Payroll Systems Specialist’s and the 1099 Payroll Specialist’s roles. The roles they were actually hired for, not add unnecessary hands to processing the payroll run. Systems back to systems. 1099s back to compliance.
The "chaos" that supposedly required all hands on deck didn't happen. Things ran fine. Better, actually.
With people freed up, I got the PEO transition spread across Legal, Finance, IT, HR, and Benefits, where it belonged instead of sitting on one desk.
I rebuilt the reporting so the accountant could pull his own numbers instead of depending on payroll for everything. I repaired the relationship with field staff, who'd stopped trusting payroll altogether.
No one told me to do any of this. I just did it, because instinctively it was the right way to run the department.
By the time the manager came back from leave, the founder and Finance Director had already seen the results. The restructuring stayed. Unfortunately, the manager didn't.
The lesson: most operational chaos isn't a headcount problem. It's a "the wrong people are doing the wrong things" problem.
-
At a PEO, new clients went through two separate teams. Implementation handled the technical setup. Then payroll took over for regular processing. The transition and handoff was never actually taught to the client on how to use the system in between.
New clients were left to figure it out alone. Support tickets piled up.
I didn't wait for someone else to fix it or give me instructions. I heard the complaints from clients, so I took the initiative.
I met with the Implementation Manager and our department manager and explained what I was hearing and seeing. They said let’s beta test it and I started training clients. There was no complications, just sitting with people and showing them how the client-facing system actually worked.
The regular processing side never changed. This was purely about closing a gap that existed and that no one owned.
Here's the tell that it actually mattered: whenever I covered for someone on vacation, their clients started asking to make me their permanent Payroll Specialist. Once I realized that they didn’t know the capabilities & features of the system, I would give them the same training as my regular assigned clients.
The lesson: Clients don't leave because the backend processing was wrong. They leave because no one took the time to walk them through the transitional piece of the process.
-
A payroll tax mess had already chewed through my two predecessors. One quit because it was too much. The other left for the same and then came back later as manager because, in their words, “Managing the mess was easier.”
My Payroll & Benefits director's first instruction was to just call state agencies and have them move the money between accounts.
So, I did exactly that for one month, then brought him the notices still coming in to show him that wasn’t the fix.
After that, I pivoted to what should be done. Research. Pulling Reports. Getting agencies to pause accruals so I could actually reconcile what was owed against what had already been paid.
In the middle of it, I found that the PEO had been sitting on tax cases for months, marking some "closed" without ever touching them, and lying about others, claiming payments and amendments were submitted when they weren't.
I pushed and escalated until the PEO finally admitted to what they were doing (not doing). Due to this, the PEO assigned an entire payroll tax remediation team just to clean up with my supervision.
By the end of my contract, I recovered over $700k in refunds due to overpayments. This included having to close tax accounts in states that no longer had employees, and registered only the new jurisdictions that the system flagged as “New”.
Here's the strange part. My director wanted to micromanage me, sighting, "I can't see your work. I don't know what's actually happening." He never understood that the invisibility was the process at work. When payroll tax work is going right, the evidence is not visible because the work is going on behind the scenes… quietly. No notices, no penalties, no fires. The manager who'd lived through the mess herself, though, was genuinely impressed, because she knew exactly what it took to get there.
The lesson in this work, silence isn't a red flag. It's the Outcome.
-
A fast-growing company had outgrown its payroll tax processes. There was no evidence that anything had broken… yet. However, their growth was outpacing the systems meant to support it, and that gap only gets more expensive with time.
I was brought on as a fractional payroll specialist. I assessed the compliance exposure, identified the structural weak points, and built a remediation plan the company could actually grow into.
Result: A real payroll tax compliance foundation, corrected vulnerabilities, and an ongoing advisory relationship instead of a one-time fix.
This is the story for the founder who reads the others and thinks, "We're not on fire yet, so we're fine." Fine is temporary. The companies that call before the fire are the ones that never have one.