Should we force every acquired brand onto one ATS?

Not always. One ATS is the goal for firms that share candidates, clients, or delivery models. But if a brand serves a totally different market (perm executive search versus high-volume light industrial), forcing one system can slow both down. Standardize the data layer and reporting first. Consolidate the front-end tools only where the workflows actually match.

How do we consolidate systems without losing recruiter productivity?

Migrate in waves, not all at once. Pick the smallest brand or one office as your first cut, run the new system in parallel for two weeks, and fix the breaks before you touch the biggest revenue producer. Never migrate during your busiest hiring season. Tie recruiter comp or reporting to the new system on day one so adoption is not optional.

What does a portfolio tech stack audit actually cost?

The audit itself is cheap compared to the mistake it prevents. Most portfolios spend 30 to 60 days of internal time or hire an advisor for a fixed fee. The real cost sits in the consolidation that follows, which ranges widely based on how many systems you kill and how dirty the data is. The audit exists to size that number before you sign a migration contract.

PE Portfolio Tech Stack Audit: 90-Day Playbook

Most PE portfolio ops leaders inherit five ATS systems and no plan to unify them. Here is the 90-day audit that tells you what to keep, what to kill, and how to sequence the work without disrupting billing.

PE returns in staffing no longer come from buying cheap and selling high. They come from making the platform run better. That shift lands on the desk of the portfolio operations leader, who usually inherits four or five staffing brands running four or five different ATS and CRM systems that do not talk to each other.

The board wants one number, one dashboard, and one story about how the platform performs. What they have is a mess of spreadsheets stitched together by an analyst who leaves at 9pm. Consolidating that mess is the job. Doing it without breaking billing is the hard part.

Most leaders skip the audit and jump straight to picking a winning system. That is backwards. You cannot pick the right stack until you know what each brand actually uses, what data lives where, and where revenue would break if you moved too fast. Here is the 90-day audit that gives you that picture.

Days 1 to 30: Map what you actually have

You cannot standardize what you have not counted. Start by building a single inventory of every system each brand runs. Not the systems the CFO thinks they run. The ones recruiters open every morning.

For each brand, write down four things:

The system of record. Which ATS or CRM holds the candidate and client data that runs the business?
The shadow tools. The spreadsheets, the standalone sourcing tools, the texting app someone bought on a corporate card. These break migrations more than the main system does.
The contract terms. Renewal dates, auto-renew clauses, and per-seat costs. A system with 14 months left on a contract changes your sequencing.
The data quality. Pull a sample of 200 candidate records from each system and check for duplicates, missing fields, and stale records. Dirty data is the number one reason consolidations run over.

By day 30 you should have one document that shows every system, its cost, its contract clock, and how clean its data is. Most portfolios have never had this in one place. That document alone changes the board conversation.

Days 31 to 60: Score and sequence

Now you decide what to keep and what to kill. Score each system on three things: how well it fits the brand's delivery model, how clean its data is, and how much it costs to run per recruiter per year.

A high-volume light industrial brand and a perm executive search brand do not need the same tools. Do not force them together just because one logo looks cleaner on a slide. Standardize the reporting layer so the board gets one number. Consolidate the front-end systems only where the workflows truly match.

Then sequence the work by risk, not by size. The instinct is to fix the biggest brand first because it drives the most revenue. That is exactly the brand you touch last. If your migration breaks, you want it to break on the smallest office, not the one carrying 40 percent of platform billing.

Build your sequence like this:

Wave one: the smallest brand or a single office. This is your test. Expect to find problems here.
Wave two: mid-size brands with clean data and matching workflows.
Wave three: the largest revenue producer and any brand with a different delivery model.

Never schedule a migration during a brand's busiest hiring season. If light industrial peaks in Q4, you move them in Q2. Recruiters will not learn a new system and hit their numbers at the same time.

Days 61 to 90: Prove it before you scale it

Run wave one in parallel for two weeks. That means recruiters use the new system while the old one stays live as a backup. Yes, it is double work for two weeks. It is also the cheapest insurance you will ever buy.

Watch three numbers during the parallel run: time to submit a candidate, number of open reqs touched per day, and data errors flagged. If any of those go the wrong way, you found a problem before it hit your biggest brand.

Fix the breaks. Document the fixes. Then write the playbook you will hand to wave two and wave three. That playbook is the real deliverable of the whole audit. It turns a one-time scramble into a repeatable process the next acquisition can plug into.

Tie the new system to something recruiters care about on day one. If comp reporting, req assignment, and commission tracking only live in the new system, adoption stops being a suggestion. People use the tool that pays them.

The mistake that kills these projects

The most common failure is treating this as a technology project. It is not. It is a change project with technology attached. The system swap is 30 percent of the work. Getting 200 recruiters across five brands to actually use it is the other 70 percent.

Recruiters who have used the same ATS for eight years will not switch because a slide told them to. They switch when the new system makes their day easier or their check bigger. Build that into the plan or watch adoption stall at 40 percent while your old systems keep billing you.

The audit gives you the map. The sequencing gives you the safe path. The parallel run proves it works. And the playbook lets you do it again the next time the fund buys another brand.

Your next step this week

Pull the contract renewal dates and per-seat costs for every ATS and CRM across your portfolio and put them in one spreadsheet. Just that. You will likely find a system on auto-renew that you meant to kill, or two brands paying for the same tool under different names. That single spreadsheet tells you where to start and gives you the first real number to bring to your board.

The PE Portfolio Tech Stack Audit: Standardizing Recruiting Technology Across Multiple Brands in 90 Days