The 15-25% Margin Leak No One Is Talking About

Staffing firms are losing 15 to 25 percent of their margin to their own software. Not to bad recruiters. Not to a soft market. To CRM, ATS, payroll, and compliance tools that do not talk to each other.

This is the leak nobody puts on a board slide. It does not show up as one line item. It hides inside a hundred small tasks that eat time and create errors every single day.

If you run a staffing firm or a PE-backed portfolio, this is the operations conversation you need to have before your next review. Here is where the money goes.

Where the 15 to 25 Percent Actually Leaks

The margin does not vanish all at once. It bleeds out in four places.

Manual re-entry. A recruiter finds a candidate in the ATS. Then types the same name, rate, and start date into payroll. Then again into a compliance tracker. Three systems, three chances to fatfinger a bill rate. One wrong number on a spread and you have worked that placement for free.

Lost sourcing days. This is the big one. When your CRM and ATS are separate, recruiters spend hours moving records, chasing status, and reconciling lists instead of talking to candidates. A recruiter who loses 90 minutes a day to system-hopping loses roughly one full sourcing day a week. Multiply that across 50 desks and you are staffing a phantom team that produces nothing.

Bad data and bad decisions. When your numbers live in four places, none of them agree. Your CRM says one revenue figure. Payroll says another. Nobody trusts the dashboard, so leaders make calls on gut instead of fact. That is how you keep a losing account for six months longer than you should.

Compliance and billing errors. Disconnected systems miss overtime rules, expired credentials, and rate mismatches. Every miss is a clawback, a fine, or a client dispute. Each one is pure margin gone.

Add those up and 15 to 25 percent is not a scary headline. It is a conservative number.

Why Firms Finally Switch (It Is Not About Features)

Here is what surprises most leaders. Agencies do not leave legacy platforms because a feature is missing. They leave for two reasons.

Lost sourcing days. Recruiters get sick of fighting the tools. Producers threaten to walk. Time-to-fill climbs and clients notice. The pain becomes loud enough that someone finally counts the cost.

Pricing opacity. Firms cannot tell what they are actually paying or what they are getting for it. Fees stack up across four vendors. Renewal quotes arrive with numbers nobody can explain. When you cannot see the price, you cannot manage the spend.

Notice what is not on that list. Nobody switches because they wanted one more report or a prettier button. They switch because the fragmented stack is slowing their people and hiding their money.

That matters for how you make the case internally. If you go to your CFO or your PE sponsor with a feature wish list, you lose. If you go with lost sourcing days and unexplained spend, you win. Those two numbers are board language.

What to Do Before Your Next Board Review

You do not need a two-year transformation. You need to find the leak and prove it. Start with a simple audit you can run in a week.

• Count the re-entry. Pick one placement. Track every system a recruiter touches from first contact to first paycheck. Count how many times the same data gets typed. Anything over two is money.
• Measure sourcing time. Ask five recruiters to log how much of their day goes to admin and system-hopping versus talking to candidates. Most firms find 20 to 30 percent going to the wrong side.
• Add up your real tech spend. List every CRM, ATS, payroll, and compliance tool. Put the annual cost next to each. Most leaders have never seen this on one page. The number is usually bigger than they think.
• Check where the numbers disagree. Pull revenue from your CRM and from payroll for the same month. If they do not match, that gap is your data problem in one clean example.

That audit gives you the story. Now you decide the fix.

Sometimes the answer is connecting the systems you have with clean integrations so data flows once and updates everywhere. Sometimes it is consolidating onto fewer platforms. The right call depends on where your data actually breaks, not on which vendor buys the best lunch.

My framework here is simple. Build the connected data layer so a placement gets entered once. Change the workflow so recruiters stop doing manual reconciliation. Adopt it for real, because a connected stack that nobody uses is just a new invoice.

The adoption piece is where most projects die. You can wire up perfect integrations and still lose the margin back if recruiters keep their old spreadsheets. Plan for that on day one, not month six.

The Cost of Waiting

Every quarter you sit on a fragmented stack, you pay the leak again. A firm doing 30 million in revenue at a 20 percent leak is handing back real profit that should be dropping to the bottom line.

For PE-backed portfolios the math is sharper. That leaked margin is EBITDA. It is multiple. Fixing the stack is one of the few operational moves that raises enterprise value without adding a single new client.

The firms that scale cleanly are not the ones with the most tools. They are the ones whose tools talk to each other so people can sell and recruit instead of babysitting software.

Your move this week: run the re-entry count on one placement. Track every system, count every keystroke of duplicate data, and put the number in front of your leadership team. That single fact starts the conversation your board needs to have. Once you can see the leak, you can stop it.