Buddy Punch vs Deputy for a Newly Acquired Portfolio Company

A typical post-close plan puts payroll and HR systems integration somewhere in months three through six, behind ERP consolidation and banking changes. Hourly labor visibility should not wait that long, because it's the one data set that directly funds or undermines the thesis. If a portfolio company's labor cost turns out to be materially different from underwriting once real clock data exists, that's a finding you want in week four, not discovered alongside a disappointing first quarterly close.

The instinct at close is to wait for a fully configured, integrated solution before rolling anything out. Resist it. In week one, get every hourly employee clocking in and out through a single system, even with default settings and no custom overtime rules yet. A new owner needs a clean, complete data feed running before anything else, so a quick setup matters here, and a partially configured rollout that drags on delays the thing that matters most, which is simply having the numbers.

A practical first hundred days sequence looks like this:

1. In week one, get every hourly employee clocking in and out through a single system, even with default settings and no custom overtime rules yet.
2. In weeks two through four, look for managers who approve their own hours or places where nobody approves anything, and assign approval to someone else.
3. Choose Buddy Punch for a single legal entity with a handful of locations, and consider Deputy once add-on acquisitions bring their own hourly staff.
4. Turn findings on overtime concentration, schedule versus labor budget and approval gaps into a line in the 100-day plan.
5. Involve the site managers whose habits are changing in the rollout, not just whoever manages payroll systems.

Founder-run and family-owned businesses selling into a PE deal often ran on trust: a site manager approved his own hours, or nobody approved anything at all because the owner knew everyone personally. That control gap is invisible until someone looks for it. Pull every site's approval chain and confirm no one is both clocking hours and approving them. This single check tends to surface the most consequential finding in the first month, more often than any line-item cost review, because self-approved overtime compounds quietly and rarely shows up until someone finally cross-checks the totals against the schedule.

A portfolio company that operates as one legal entity with a handful of locations gets most of its value from Buddy Punch's speed and simplicity, and adding Deputy's heavier scheduling and multi-entity reporting on top of that is often more platform than the situation calls for. A roll-up strategy is different: once the fund starts stacking add-on acquisitions under one holding structure, each with its own hourly workforce and its own historical approval habits, Deputy's ability to segment reporting and enforce consistent rules across entities earns its added cost, and the earlier you standardize on it, the less rework each add-on requires.

Once accurate labor data exists, three findings typically surface: overtime concentrated in a handful of roles or shifts, a scheduling pattern that doesn't match the labor budget in the deal model, and at least one location where the old approval process had a real gap. Each of those belongs as its own line item in the 100-day plan, with an owner and a date, rather than as a general note that timekeeping is now under control. A finding that isn't assigned to someone tends to still be open at the next board meeting.

Many post-close plans call for a dedicated operations or general manager hire to own exactly this kind of cleanup, and getting the compensation range wrong slows that hire down. General and operations managers earn a median annual wage of $105,770 nationally, with the middle half of the role spanning roughly $72,320 to $167,280 depending on company size and region¹. Use that range as a sanity check against whatever the seller's org chart implied the role was worth, since a portfolio company hiring below market for this specific position tends to struggle to attract someone capable of actually running the cleanup.

Handing the rollout to whoever manages payroll systems, without involving the site managers whose habits are actually changing, is a common way for a technically successful rollout to fail operationally. A site manager who is told to stop self-approving hours without any explanation of why tends to find workarounds, like having a peer rubber-stamp approvals without real review. Pair the technical rollout with a short, direct conversation at each site about why the control exists now and what specifically changed since close.

Buyers who ran a thorough quality of earnings process before close often already flagged labor as an area of uncertainty in the target's financials, since sellers rarely have strong incentive to surface their own control gaps during a sale process. Treat the post-close timekeeping rollout as the direct follow-through on that diligence flag rather than a separate initiative, and loop the deal team in on what the first month of real data actually shows. A gap between what diligence assumed and what the real clock data reveals is exactly the kind of finding worth surfacing to the investment committee early, while there's still time to adjust the operating plan rather than explain a variance after the fact.