I run PE technology leadership searches where the preferred candidate gets to offer stage, has been engaged and enthusiastic throughout, and then turns it down. It happens more often than most clients expect. Not because the offer was wrong or the process failed, but because they got to the point where the decision was real and found they didn’t have the risk appetite they thought they did.
The idea of the exit is exciting. The equity upside, the transformation mandate, the chance to build something with real commercial consequences. Most candidates mean it when they say they want that. But wanting it in theory and committing to it when your name is on the line are different things, and the gap between those two moments is where a lot of PE searches lose their preferred hire.
What actually happens at the decision point
The pattern is consistent enough to call out. A strong exec enters the process with genuine enthusiasm. They talk well about transformation, about operating under pressure, about being accountable for commercial outcomes. They engage seriously with the brief, they impress in interviews, and they’re clearly capable of doing the job.
Then the offer arrives, and the conversation changes.
The concerns that come up at this stage are often very rational. The equity structure is complex. The notice period at their current employer is long. Their partner has questions about the stability and security. The current employer, who had shown no interest in retention until now, suddenly finds budget for a promotion or a counter. Each of these is a real factor. But underneath most of them is something simpler: the person is confronting the reality that this role carries genuine risk, and they’re not sure they want it.
This isn’t a character flaw. Some people genuinely prefer security and predictability, and that’s a valid choice. But those people typically don’t suit PE-backed ventures, and the time to work that out is not at offer stage.
Why candidates talk themselves out of it
The hardest version of this to spot is when someone talks themselves out of it using logic that sounds careful but is really just fear of loss with a business case attached.
“The equity structure doesn’t give me enough certainty.” Equity is different in every deal. The payout depends on so many factors that certainty is never on the table. When things go right, the wealth creation is real. When they go wrong, the exec has taken a pay cut for harder work with less return. That’s the deal. Someone who needs the equity to be predictable before they commit is telling you they want the upside without the exposure, and that’s not how PE works.
“I need to think about what my current employer might offer.” A counter is a retention play, not a career decision. The reasons they were looking in the first place haven’t changed because someone found a budget line to keep them.
“My partner isn’t comfortable with the risk.” This one is real and needs to be respected. But it often surfaces late in the process because the candidate hasn’t had a proper conversation at home about what this move actually involves. The earlier that conversation happens, the less likely it is to derail an offer. And it needs to address a worst case scenario.
The underlying question is whether the candidate actually has the risk tolerance for what PE demands. And the answer, when it comes out at offer stage, is expensive for everyone.
What it means for the process
When the preferred hire turns down the offer, the search has usually lost four to six weeks. The client has invested time and conviction in them. The second choice, if there is one, knows they were second choice. The momentum of the process takes a hit that’s hard to come back from.
The instinct at this point is often to push harder on the candidate, improve the offer, make the case more compelling. There’s a place for that, and I’ll always work with the CEO to make sure the offer is right and the benefits are clear. But there comes a point where pushing harder than you should is a warning sign, not a solution. If you have to twist someone’s arm to get them to accept, they’ll typically fail or disengage at some point after they join. The commitment has to be their choice, with both feet in.
What I do in practice is run both tracks at once. Work on closing the preferred hire with the right offer and the right clarity, while preparing for the scenario that they won’t go for it. That means keeping other strong options engaged throughout the process, not as consolation options but as a genuine alternative. The searches that survive a late dropout are the ones that planned for it. The ones that didn’t have to restart from scratch and lose months.
What this tells you about risk appetite
The exec who turns down the equity play is giving you useful information. Not about whether they’re a good operator (they often are) but about whether they’re the right operator for this specific context. PE-backed technology leadership is a risk environment. The mandate is harder, the timeline is compressed, the accountability is more personal, and the financial structure reflects that. Some of the best technology leaders in the market aren’t suited to it, and that’s fine.
The more honest both sides are about this early in the process, the better. As a search partner, a large part of my job is testing for it before the offer stage, not after. The questions I ask throughout the process are designed to confront whether someone genuinely has the appetite for what this involves, or whether they’re drawn to the idea of it without fully contemplating the reality. That’s not something you can assess from a CV. It comes out in how someone talks about decisions they’ve made under real pressure, and whether their version of risk has ever actually cost them something.
The people who close well in PE processes tend to have one thing in common. They’ve already decided before the offer arrives. The offer is a formality, not a decision point. The ones who wobble at offer stage were often never fully committed, and the process didn’t catch it early enough. I’ve been through this enough times to treat it as a default rather than an exception.