One hire, then the whole team
A growing services company needed to replace the leader who held its operations together, quietly, before the team knew it was happening. We ran the search, made the hire, and he worked out. Then he brought us back to build the rest of his team. This is how one confidential search became a hiring partnership across the org chart.
Start
A function that ran on one person's memory
A services company of around forty people, profitable and growing, running a billing-intensive operation for a few hundred business clients on a month-to-month model. No long-term contracts. Clients stay while the service delivers and leave the moment it slips, which makes operations the function the entire business rides on: fulfillment, repairs, help desk, and the billing and audit work that keeps clients' costs honest.
They had a problem they could not post publicly. The leader running operations needed to be replaced, and the search had to stay confidential. The incumbent did not know. The team did not know. No job board, no company name in outreach, referrals limited to a trusted few. On top of the discretion, the bar was high. Operations ran on tribal knowledge, with documentation missing, service levels inconsistent, a ticket backlog, and an offshore team without clean escalation. They did not need a body in a seat. They needed an operator who could systematize all of it, found quietly, and gotten right the first time, because everything downstream depended on it.
Needed
A partner for the part of hiring that's hardest to outsource
A confidential replacement is the kind of search that exposes whether a recruiter can actually do the job. You cannot advertise, so you have to go find people directly. You cannot lean on the company's name to open a conversation, so the pitch has to carry itself. And the cost of a miss is higher than usual, because you are quietly swapping out the person a function depends on while that function keeps running.
What they needed, though they framed it as one hire, was a partner they could trust with the part of hiring that is hardest to outsource: judgment about who can actually carry a function, applied discreetly and repeatedly. That is the thing this engagement turned out to be. The first search was the test. Everything after it was the result of passing.
Built
One search became three roles, in sequence
What started as one confidential search became three roles across the operation, in sequence. Here is each one, and how the first opened the door to the rest.
The confidential leadership search
We built the role around what the business actually needed an operator to do, not a generic operations job post: take four teams running on instinct and turn them into documented, measured functions with clear ownership and escalation, onshore and offshore. The placemat set what good looks like at thirty, sixty, ninety days and twelve months, translated into the outcomes the CEO cared about, margins, ticket resolution, a function that could scale without scaling headcount in lockstep. The screen was performance-based, every question tied to a specific competency and the evidence that proves it, run discreetly against a directly sourced pool because nothing could be posted.
Operations ran on one person's memory, and the search had to stay invisible.
A documented function with clear owners and targets, led by someone who came in a level above the original spec, as a director.
The revenue leader they trusted us to find next
The hire worked, and a hire that works changes the relationship. The leader we had placed became the reason the company brought us back, this time for a Customer Success Director, the revenue-owning leader for the existing client base. This was its own hard search: a rare intersection of deep domain knowledge of a billing-heavy industry, the ability to build process from scratch rather than inherit it, real accountability for retention and expansion revenue, and offshore team management. The account-management function was reactive, controllable churn sat in the high single digits and needed to come down by a third or more, and there was no satisfaction program at all. We defined the role as a turnaround and built a multi-stakeholder final-round scorecard to assess it, with each interviewer evaluating only what they were positioned to judge: a panel reading cross-functional fit, with the operations leader we had just placed sitting on it, and the CEO reading closing conviction.
A reactive function with churn bleeding and no system to bend it.
A revenue-owning leader vetted across every stakeholder who would work with them.
The frontline team for the new leader
Then the operations leader needed to staff his own team, starting with a Fulfillment Technician, an hourly, on-site role. Two things made it more than a simple req. The pay sat in an awkward band, above local warehouse rates but at the floor for entry-level IT, so we sized the market and set the rate against real benchmarks, with a ninety-day performance bump built in as a closing tool. And the obvious sourcing pool was the wrong one: new college graduates were easy to reach but treated the role as a stepping stone and would be gone in months. We pivoted the search to people with high-volume warehouse and fulfillment backgrounds who saw the work as a launchpad and wanted to grow with the company. Different pool, right motivation.
An hourly role priced by guess and sourced from a pool that would churn out in months.
A market-set rate and a pipeline of people who wanted to grow into the work.
Work
Anonymized snapshots, across all three roles
Anonymized snapshots of the actual deliverables, across all three roles. Generic content, real method.
Frontline technician: pay and pipeline
RateSet against real market benchmarks, with a ninety-day performance bump as a closing tool.
PipelinePivoted from college grads, who treat the role as a stepping stone, to warehouse-experienced candidates who want to grow into it.
An hourly role nobody knew how to price or where to fill. We set the rate against the market and pivoted the search from people who would leave in months to people who saw the work as a launchpad. It got filled by someone who wanted to stay and grow.
Operations leader
Take four teams running on instinct and turn them into documented, measured functions with clear ownership and escalation, onshore and offshore.
Assess every team, map the processes, find the bottlenecks.
KPIs and accountability cadence in place; fix the highest-impact gaps.
Documented operation with owners and SLAs; the CEO trusts the function is owned.
Operations is a competitive advantage, not a constraint.
A critical function held together by one person's memory, and a search that had to stay quiet. We defined the role around the outcomes the CEO cared about and screened on evidence, not resumes. The person we placed came in a level above the original spec, as a director.
Customer Success Director
Revenue accountability, retention and churn, offshore management, domain billing knowledge.
Cross-functional fit. How handoffs between teams would actually run.
Closing conviction. Do they want this, and can the CEO trust them to own it.
A revenue-owning leadership hire to fix a reactive, churn-bleeding function. We split the assessment across the people who would work with this person, including the operations leader we had just placed, with the CEO owning the close. Each interviewer judged only what they were positioned to judge.
Fulfillment technician
On-site, full-time, reliable commute. Logistics before anything else.
Detail orientation, process discipline, reliability, coachability.
Low ego, ownership, and the drive to grow. Sees the role as a launchpad, not a dead end.
High-volume hiring still needs a real bar. Must-pass logistics first, then a screen for the traits that actually predict success in the work. The same discipline as the executive search, scaled to the frontline.
Results
How the relationship compounded
Operations Director
Confidential replacement
Customer Success Director
Revenue leader
Fulfillment Technician
Frontline hire
Operations Director
Confidential replacement
Customer Success Director
Revenue leader
Fulfillment Technician
Frontline hire
One confidential search became three roles, top to bottom of the operation.
from defining the role to the right person in seat
and counting, the operations leader still in the role
It started as a single confidential replacement. The hire worked, came in a level above the original spec, and is still in the role six months on. That turned a one-off search into the company's hiring partner across the org chart, from the leader who runs operations to the people on the floor. The strongest proof a search worked is the client coming back to run the next one with you.
Kept
A way of hiring they can rerun
The company did not just get three hires. They got a way of hiring they can rerun. Every role came with the same apparatus: the role defined in the terms of the business, the screen built to catch the specific failures that matter, the market sized before sourcing, the interview built to assess what actually predicts success. That is theirs now, at every level of the company.
And the relationship is the point. Hiring done well compounds. Get one right, and the next is easier to trust, easier to define, easier to fill. A confidential, high-stakes replacement became a partnership because the work held up under the highest-stakes version of the test. That is what compounding looks like, and it is the same thing we build for every founder we work with: not a hire, but a reason to never worry about the next one.
Build the system behind the hire.
If your next hires matter and you want a partner who earns the right to the ones after that, we build the role, the screen, the market read, and the search, in a way your team keeps.