Case Studies

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.

Nobody 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, year-to-date limits reset when they shouldn't.

She came in as independent 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.

She made the call herself: pull three of the four people back into the roles they were actually hired for. 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, she got the PEO transition spread across Legal, Finance, IT, HR, and Benefits, where it belonged instead of sitting on one desk. She rebuilt the reporting so the accountant could pull his own numbers instead of depending on payroll for everything. She repaired the relationship with field staff, who'd stopped trusting payroll altogether.

Nobody told her to do any of this. She just did it, because it was the obvious right way to run the department.

By the time the manager came back from leave, the founder had already seen the results. The restructuring stayed. 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. Nobody ever actually showed the client how to use the system in between.

New clients were left to figure it out alone. Support tickets piled up. First impressions were rough.

She didn't wait for someone else to fix it. She started training clients herself, in the gap between implementation handing off and payroll taking over. Nothing complicated, just sitting with people and showing them how the system actually worked.

The regular processing side never changed. This was purely about closing a gap that existed and that nobody owned.

Here's the tell that it actually mattered: whenever she covered for someone on vacation, clients she trained started asking to stay with her permanently. Every one of them.

The lesson: people don't leave because the backend processing was wrong. They leave because nobody walked them through it.

A payroll tax mess had already chewed through two people before her. One quit because it was too much. The other came back later as manager because, in their words, managing the mess was easier than fixing it.

Her director's first instruction was to just call state agencies and move money between accounts whenever something looked off. She did exactly that for one month, then brought him the notices still coming in to show him it wasn't working.

After that, she did it properly. Research. Investigation. Getting agencies to pause accruals so she could actually reconcile what was owed against what had already been paid. In the middle of it, she found something worse: 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.

She pushed until they admitted it. The PEO ended up assigning an entire team just to clean up what they'd caused.

By the end, she'd recovered over $700,000 in refunds and overpayments. She closed tax accounts in states where the company had no business being registered, and made sure new ones only opened when the system actually required it.

Here's the strange part. Her director started micromanaging her during this, saying, "I can't see her work. I don't know what's actually happening." He never understood that quiet was the whole point. When tax work is going right, nothing happens. No notices, no penalties, no fires. The manager who'd lived through the mess himself, though, was genuinely impressed, because he knew exactly what it took to get there.

The lesson: in this work, silence isn't a red flag. It's the goal.

A fast-growing company had outgrown its payroll tax processes. Nothing had broken yet, but growth was outpacing the systems meant to support it, and that gap only gets more expensive with time.

Brought on as a fractional advisor, she 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.