Start a Search
We place across every leadership function in PE-backed essential services. Select a function to see how we recruit for it and the roles we fill.
Start a SearchNine functions, each one mapped by INC'D from real placements in PE-backed essential services platforms across North America.
The operator who built a loyal 10-branch business is rarely the operator who can run a 40-branch PE-backed platform. These are different people. Get the hire right and management depth becomes the lever for multiple expansion at exit. Get it wrong and the hold runs on the wrong engine.
General management in this market is not a single seat. It is a spectrum of operators, every one of them owning a P&L.
General management in a PE-backed field services platform covers the full operational spectrum. A single-branch GM with $5M in revenue and one operating P&L. A Regional Director with eight branches and $80M underneath. A Market Director running a metro across multiple brands. A Platform CEO with 40+ locations and $500M across the platform. The seats look different, but they share one trait. Every one of them owns the operational outcome of the business they sit on top of. The single-branch GM owns dispatch and the local customer book. The Platform CEO owns the value-creation plan and the exit narrative. Both are operators.
The org structure in a fully-built multi-brand platform is layered. Platform CEO at the top. A General Manager or President beneath them owning operations across all brands. A layer of Regional or Market Directors managing 5 to 15 locations across a state or metro. Branch Managers running the day-to-day operating P&L of one location. Area Managers and lead technicians owning the productivity metrics underneath. At smaller platforms, several of these layers compress into a single seat. The single-branch GM is essentially Branch Manager and Regional Director and Market Director and CEO in one person, just at a smaller P&L.
We map that org two to three years before the seats are hireable. The Regional Director who is going to run a third of the platform in 2027 is a Branch Manager today, somewhere we already know. The Market Director who will integrate the next bolt-on is a Regional Director today, in a peer platform we have been tracking. This is the pre-GM layer that the best operators in field services build deliberately, and that most platforms reach for too late.
A bad GM hire does not just cost a search fee and lost months. It costs the value-creation plan itself. Targets get pushed. Add-ons stall. The exit story has a hole in it where management depth was supposed to be.
The data on PE-backed CEO turnover tells the rest of the story.
The right GM in year one is rarely the right GM in year four. The job changes shape with the platform.
The platform GM is one hire. The org that makes them effective is six.
The pedigree gets the interview. The operating reps decide the outcome.
We have placed enough GMs in this market to know two things matter more than the resume.
The right operators at every level do not just run the business. They become the reason it earns a multiple at exit.
Field operations in a field services platform is not a logistics function. It is the margin engine. The difference between a 28% EBITDA platform and a 19% one is almost always an operations problem.
Field operations in a field services platform is the only function where every single decision either creates margin or destroys it. There is no neutral.
The VP of Operations or COO in a PE-backed field services platform owns the operational P&L across every brand, every market, and every truck. Same-day service delivery. Technician productivity per labor hour. Dispatch efficiency. SLA compliance. First-time fix rate. The customer relationship that determines whether the platform's revenue base compounds or churns. The seat where field credibility and PE-fluent operating discipline have to live in one person, and most search firms cannot map that combination.
We draw a hard line between residential and commercial operations profiles. The residential operator has run high-volume, same-day, consumer-facing field operations where the technician is the brand and dispatch is the lever. The commercial operator has managed long-cycle B2B accounts, account-based pricing, and project work alongside recurring service. Operations leaders from outside the trades have never encountered either reality. The functions look similar from the outside; they run on completely different operational physics.
There is a clear pattern in the operators who compound EBITDA through the hold, and an even clearer one in those who do not. They have run a multi-site service business through a roll-up. They speak in technician productivity, first-time fix rate, route density, and revenue per truck hour as fluently as they speak in EBITDA bridges. They built a Director of Field Operations and a Director of Dispatch underneath them in the first six months. The ones who do not share a very different profile.
A bad operations hire is the most expensive hire on the platform. Service quality drops. Technicians leave. Customers churn. The EBITDA bridge that the value-creation plan is built on starts to sag, quietly, for two quarters before anyone in the boardroom realizes what is happening.
The data on field service economics tells the rest of the story.
The operations role does not stay the same through the hold. The job changes shape with the platform.
The operations leader is one hire. The team that turns operational discipline into EBITDA is six.
The pedigree gets you in the room. The dispatch board decides whether you stay in it.
After enough operations placements across this market, the signal has narrowed to a small set.
The right operations leader does not just run the platform. They turn field discipline into the EBITDA story buyers pay for at exit.
The CFO is the most visible finance hire in a PE-backed platform. It is rarely the most urgent one. Finance either runs at the speed of the business, or the business runs at the speed of finance.
A PE-grade CFO in this sector is not a better bookkeeper. It is a different job entirely.
The finance seat inside a PE-backed field services platform is one of the most demanding hires in the middle market. Cash is daily, not monthly. Covenants are a weekly flash. The chart of accounts arrives founder-built on QuickBooks and needs to run 15 to 40 entities within the year. Every add-on brings a purchase price allocation, a working capital true-up against a negotiated peg, and an integration into the platform stack, often on a six-to-eight-week cadence.
The default technology stack in PE-backed field services is ServiceTitan for field operations, and NetSuite or Sage Intacct for the general ledger. The founder-built QuickBooks environment does not survive the first acquisition.
The incumbent CFO is retained roughly a quarter of the time post-close. The rest are replaced, usually inside the first twelve months. Not because the incumbent was bad. Because the job is no longer the one they were hired to do.
The wrong finance hire does not cost a search fee. It costs covenant cushion, integration tempo, and the diligence the next buyer runs against you.
Two patterns separate the CFOs who clear the hold from the ones the board replaces 18 months in. The ones who do not share a very different one.
The CFO who is perfect for platform formation rarely makes it to exit. The CFO who can run a pre-exit QofE sprint would suffocate in a founder-run business with a box of receipts. Matching the finance hire to the stage of the platform is the single most common mistake in a PE-backed build.
The finance org is built in rings. Not one hire. The right sequence of them.
The CV tells you very little. The track record tells you everything.
We have seen every pattern. We know which ones hold up inside a roll-up and which ones collapse by month nine.
The right finance hire does not just close the books. They underwrite the exit.
In a field services business, the revenue leader is not closing deals. They are building the recurring revenue base that determines what the platform is worth at exit.
Revenue in this sector is not a sales number. It is the contractual certainty that compounds into enterprise value.
Recurring revenue sits at the heart of field services, but the end customer changes the motion completely. When the customer is a property group, whether an apartment owner, REIT, facility manager, or installer partner, the sale is a bulk-contract motion: multi-year terms, account-based management, RFP responses, installer enablement, and the relationship infrastructure that wins recurring agreements. When the customer is a household, the sale is a high-volume, membership-driven, repair-attached motion priced per booked call. Almost every vertical we cover runs both at the same time, and the revenue leader has to lead both.
We look for operators who have built revenue engines from the ground up, not inherited books, and who know which motion fits which side. On the household side, the difference between a 30% and a 70% service agreement attachment rate determines what the platform is worth at exit. On the property-group side, one multi-year account can represent 15% of platform revenue and has to be retained through an integration, a pricing reset, and a service incident without the account manager walking to a competitor.
The operators who build this properly share a pattern. They track agreement attachment at the technician level, not the branch level. They instrument membership retention by month and by cohort. They know which customer types retain at 85% and which retain at 55% and price accordingly. They hold the sales-to-service interface tight enough that a repair call becomes an agreement conversation and an agreement call becomes a replacement conversation. The operators who do not share a very different pattern.
A bad revenue hire does not show up as missed sales targets. It shows up two years later when the platform cannot prove a defensible recurring revenue base to an exit buyer, and the multiple moves a turn. The damage compounds silently until the Q of Earnings team surfaces it in the last weeks of a process.
The industry data on recurring revenue in field services is unambiguous.
The revenue role does not stay the same through the hold. The job changes shape with the platform.
The revenue leader is one hire. The team that turns one-transaction customers into compounding revenue is six.
The CV tells you the books they closed. The dashboard tells you which books will still be there in 24 months.
Across the revenue leaders we have placed in this sector, the signals split cleanly.
The right revenue leader does not just hit the plan. They build the contractual base that turns the hold into a story buyers compete to own.
Marketing in field services is two motions, not one. Channel-driven account management to property groups. Local demand generation priced per booked call to households. Almost every vertical we cover runs both. The CMO who has only run one is a half-hire. Half-hires show up in CAC-to-LTV math at exit, not before.
Marketing in field services is the only function where a bad hire does not look expensive for two years. And by then the hold is half over.
The motion tracks the end customer, not the vertical. When the customer is a property group, marketing is channel-based: account management, RFP response, partner enablement, installer-channel programs, and the relationship infrastructure that wins bulk agreements. When the customer is a household, marketing is demand-gen: Google Local Services Ads, paid search, local SEO, branded vehicle impressions, direct mail, retargeting, and the call-center economics that convert a booked call into a tuned-up agreement customer. Different skill sets, different metrics, different failure modes.
We place marketing leaders who have run one motion or both. The CMO who has built a demand-gen engine serving 50 residential branches does not automatically translate to the channel side of the same platform. The CMO running penetration campaigns into property groups does not translate to a direct-response motion the next morning. In a multi-vertical platform, the CMO has to be able to lead both or know precisely which deputy leads which side, and we have watched half-hires get through hiring processes that did not test for the distinction.
We see two profiles of marketing leader in this market: the ones who compound value, and the ones who present really well in interviews. They can produce a CAC number by channel, by market, and by vintage inside fifteen minutes. They have rebuilt the call-to-agreement conversion funnel at least once. They know which brand investments pay back inside the hold and which ones are lifestyle spend. They understand that the Director of Demand Generation and the Director of Channel Marketing run completely different P&Ls and hire accordingly. The operators who do not have a pattern too, and it is one we have watched collapse more than once.
A bad CMO hire looks fine until exit. The CAC-to-LTV math shows up in Quality of Earnings. Revenue has grown, brand has grown, and yet the buyer model discounts recurring revenue on retention risk. A turn of multiple evaporates in the last 90 days of a process because the marketing function never instrumented the unit economics that the buyer was going to run on it.
The marketing economics of this sector are well understood by the operators who have lived inside them.
The CMO role changes through the hold. The job at platform formation is not the job at exit.
The CMO is one hire. The team that turns marketing spend into defensible enterprise value is six.
The pitch deck tells you how they think. The attribution model tells you whether they can operate.
The signal that predicts the outcome on a marketing hire is rarely the one that wins the interview.
The right CMO does not just grow the pipeline. They build the marketing story that defends the exit multiple when the diligence team starts asking questions.
In a trades business running 35%+ annual technician turnover, HR is not a support function. It is an operational constraint that determines whether the platform can grow at all.
The most underwritten assumption in a PE-backed field services platform is that the labor exists to staff the growth plan. Half the time it does not, and nobody finds out until Year Two.
People leadership in PE-backed field services carries a scope most HR professionals have not encountered. Field labor recruitment in tight markets. Compliance exposure across multiple employment models and states. Workforce integration during acquisitions closing every six to eight weeks. Retention strategies for technicians earning $25 an hour who can leave for a competitor across town tomorrow. Total rewards architecture that has to balance equity, base, and performance variable across very different workforce categories.
The regulatory complexity alone: immigration compliance, worker classification risk, licensing requirements by trade and by state. This puts the VP of People in this sector at a level most corporate HR functions never reach. We look for leaders who have built HR infrastructure in high-turnover, multi-location, multi-state environments. Anyone whose experience comes from professional services, financial services, or technology does not survive the first peak season.
We see two patterns in the people leaders we place: the ones who clear the hold, and the ones who get quietly replaced at month 18. They have stood in the parking lot at 6am and watched the technicians arrive. They know the local labor market in the three or four metros that matter to the platform by name and by competitor. They have built an in-house apprenticeship pipeline that is not a marketing claim. They treat the General Managers and Branch Managers as their primary internal customers, not the C-Suite. The ones who do not share a very different profile: HR business partners with no field exposure who treat the function as a compliance layer and watch the platform's turnover numbers degrade quarter after quarter.
A bad people hire in this sector does not look bad for 18 months. The hiring miss compounds as the integration lag, the over-reliance on contract labor, the EBITDA drag of running 38% turnover instead of 28%. By the time the data is clear, two acquisitions have already landed inside a workforce that cannot absorb them, and the value-creation plan has slipped a year.
The macro data on the trades workforce explains why this seat is so hard to staff well.
The people role does not stay the same through the hold. The job changes shape with the platform.
The people leader is one hire. The team that turns workforce constraint into platform capacity is six.
The HR pedigree gets you in the room. The 6am parking lot tells you whether you can do the job.
Two signals separate the people leaders who clear the hold from the ones who do not, and we have seen both repeatedly.
The right people leader does not just fill the org chart. They build the workforce engine that decides whether the value-creation plan can actually be executed.
Every platform that has closed 20 acquisitions in three years is managing integration debt. The question is not whether the debt exists. It is how fast it compounds before exit.
Most of the multiple expansion in a roll-up is not paid for at acquisition. It is earned in the integration function or destroyed there.
Integration leadership has become one of the most critical and least well-filled functions in PE-backed field services. System migrations, brand consolidation, workforce absorption, pricing harmonization, and ERP implementation running on a six-to-eight-week cadence per deal. In infrastructure and field services platforms, integration is the function that determines whether 20 acquisitions become a $200M platform or a $200M mess.
The best integration operators combine project management precision with enough operational credibility to hold the trust of acquired management teams through a transition that threatens everything they built. That combination is rare. We have placed this function into platforms ranging from five to forty acquisitions deep, and the same pattern shows up: the platforms that got it right hired the integration function ahead of the cadence; the ones that got it wrong are still trying to catch up two years in.
Two profiles show up in the integration function: the one that compounds value through the cadence, and the one the platform spends a year cleaning up after. They have run integration as a real function inside a PE-backed platform, not as an internal consultancy or a one-deal SWAT team. They keep an integration playbook that updates every quarter from actual failures, not a document that lives on SharePoint. They have rebuilt an ERP migration plan after the first one collapsed and learned the right lesson. They sit beside the deal team during diligence and call out the integration debt before close. The ones who do not share a different profile, and the platforms find out the same way every time.
A bad integration hire is the most expensive seat to miss on a PE-backed roll-up. The deal team keeps closing. The cadence keeps accelerating. The integration function falls behind. By Year Three, the platform is carrying duplicate ERP instances, fragmented dispatch systems, three competing pricing models, and a workforce that has churned out the institutional knowledge of every acquired brand. The exit story falls apart in diligence and the multiple compresses by a turn or two.
The data on post-merger integration in this sector is unforgiving.
The integration role does not stay the same through the hold. The job changes shape with the cadence.
The integration leader is one hire. The team that turns 20 acquisitions into a coherent platform is six.
The deal pipeline tells you what they have closed. The integration retros tell you what they have actually absorbed.
Pattern recognition matters here. Across enough integration placements, two signals consistently predict the outcome.
The right integration leader does not just close the gap between deal close and platform reality. They turn 20 acquisitions into a single story that commands a premium at exit.
The technology leader in a field services platform is not building product. They are building the operational infrastructure that makes a 40-branch platform run like one business instead of forty. A unified platform story at exit earns a multiple. A fragmented one earns a discount.
The CTO's job in this market is not innovation. It is unification, and most CTOs from the SaaS world have never been hired to do that.
Technology leadership in a PE-backed field services platform is a defined and specific discipline. Field service management platforms, dispatch systems, customer portals, and the ERP consolidation that underpins multi-entity financial reporting. The right leader understands the trades-specific software ecosystem: ServiceTitan, FieldEdge, BuildOps, NetSuite, Sage Intacct. The wrong leader spends 18 months trying to build what should have been bought.
The most common mistake is hiring a CTO from SaaS or enterprise technology who brings strong product and engineering credentials into an environment where the job is operational unification, not product development. The platform does not need a better app. It needs its 35 acquired businesses running on one set of books, one dispatch system, and one data model. That is a different job and it requires a different operator.
We see two CTO profiles in this market. One earns the buyout. The other is the reason the next CTO gets hired. They have run a system migration in a multi-brand PE-backed environment and either nailed it or learned the hard way and rebuilt the playbook. They negotiate with vendors as operators, not as buyers. They sit beside the CFO during board meetings and translate the data architecture into EBITDA implications. They know which battles to win first: chart of accounts, then dispatch, then everything else. The ones who do not share a different profile, and the platform finds out when the data room opens.
A bad technology hire on a PE-backed roll-up does not show up as a missed go-live. It shows up as the platform paying for three CRMs, four FSM systems, and seven ERP instances at the same time, with no single source of truth for the board pack. The exit story breaks during data room because nobody can produce a clean cohort retention curve across the platform.
The base rates on platform technology in this sector are unforgiving.
The technology role does not stay the same through the hold. The job changes shape with the platform.
The CTO is one hire. The team that turns seven acquired tech stacks into one operating platform is six.
The architecture diagram tells you what they have built. The dashboard the CFO trusts tells you whether it works.
From the technology placements we have run in this sector, the signal cuts cleanly between two profiles.
The right CTO does not just modernize the stack. They build the operating platform that turns 35 acquired businesses into one defensible story at exit.
Several of the most active PE-backed essential services verticals run two businesses simultaneously: a recurring service operation and a project delivery engine. Platforms hire well for one and badly for the other. Exit underwriting looks at both revenue streams. The weaker one sets the multiple.
Project delivery in field services is not a different lane of operations. It is a fundamentally different business model running alongside the service operation, with its own P&L, its own workforce, and its own failure modes.
Project and infrastructure delivery leadership sits inside the field services world but operates on a different economic model. Revenue is milestone-based, not recurring. Workforce is project-deployed, not route-managed. The P&L runs on margin per project, not agreement penetration. In several of the verticals we cover, where project delivery runs alongside recurring service, the project side can be 30 to 60 percent of platform revenue and is often the lever that determines whether the platform earns the multiple expansion or absorbs the margin compression.
The platforms that get this wrong conflate the two. They promote a strong service operations leader into a project delivery mandate, or hire a construction executive who cannot adapt to the PE reporting cadence and recurring service culture around them. We have placed this function across verticals where the project side is the larger revenue stream and across verticals where it is the smaller. The operating model is the same. The leader profile is the same. The platforms that hire it correctly compound value. The platforms that do not absorb the project losses inside the service-side EBITDA and pretend the math works.
Two profiles separate the project delivery leaders who turn a second P&L into multiple expansion from the ones who let it become a drag. They have run capital projects against a stage-gate process inside a PE reporting cadence. They build a separate PMO and project controls function inside 90 days because they know what happens when project delivery runs on the service operations dashboard. They speak in margin per project, change-order capture, and backlog conversion as fluently as they speak in EBITDA. They know which projects to chase and which ones to walk away from at the bid stage. The ones who do not share a different profile, and the project P&L bleeds quietly until exit diligence finds it.
A bad project delivery hire on a multi-revenue-stream platform does not look bad until the second large project goes 30% over budget and the platform has to write down the backlog. By then, the service-side margins have to absorb the project shortfall, the EBITDA misses two consecutive quarters, and the value-creation plan slips a year. Exit underwriting sees both businesses on the same P&L and prices the platform at the weaker multiple.
The base rates on capital project delivery are unforgiving and have been for decades.
The role does not stay the same through the hold. The job changes shape with the platform.
The project delivery leader is one hire. The team that turns capital projects into a defensible second P&L is six.
The bid pipeline tells you what they hope to win. The change-order log tells you what they actually deliver.
On the project delivery side, the signal is unforgiving and it shows up early.
The right project delivery leader does not just close out the backlog. They build the second P&L the platform needs to defend the multiple at exit.
We place across every function and level in PE-backed essential services. If the role matters to your platform, we have a view on the market.