deeptechcleantechexecutive searchCTO hiringco-founder transitionuniversity spinoutleadershipB2B SaaS
The Tech Co-Founder Transition in Deeptech
Here's a story that plays out more often than the industry admits. A PhD student spends years solving a problem the industry hasn't named yet — and builds a real company around it. Then the job changes completely. This is the moment we get called in.
Here's a story that plays out more often than the industry admits.
A PhD student spends four years in a university lab solving a problem most of the industry hasn't even named yet. They publish. They iterate. They get it to work. The kind of breakthrough that doesn't just make a good business case, it actually changes something about how the world operates. Then comes the spinout, the seed round, the first hires, the first pilots. Five years after defending their thesis, they've built something real: a technology that works, customers willing to test it, and investors who believe in it.
That's not a small thing. Most scientists never get this far.
But somewhere between the last pilot and the first serious commercial contract, the job changes completely. The founding CTO, who in most cases is also the person who invented the core technology, is suddenly staring at a set of problems that have nothing to do with science.
How do you industrialize this? How do you go from a working prototype to a repeatable product? How do you manage a 20-person engineering team when you've never managed anyone before? How do you negotiate a scale contract with a procurement committee at a large chemical company?
These aren't science problems. And the founder knows it.
This is the moment we get called in. And it's one of the most delicate searches we run.
This Isn't a Succession. It's an Addition.
The first thing to get right is the framing, and most companies get it wrong.
The instinct, especially from investors who've seen this pattern before, is to treat this as a leadership gap that needs to be filled. "The technical founder isn't the right person to scale the company." True, maybe. But the way you act on that belief makes all the difference.
In most deeptech transitions we've been part of, the founding CTO isn't going anywhere. Nor should they. The technology is still evolving. The R&D pipeline is what makes the company defensible. The scientific founder's deep knowledge of chemistry, materials, the edge cases, and the things that almost broke the process is genuinely irreplaceable, and pretending otherwise to make an org chart look cleaner is a mistake.
What the company actually needs isn't a replacement. It's a counterpart. Someone who has taken a complex technical product from working prototype to industrial deployment before. Who understands the gap between "it works in controlled conditions" and "it works at a customer site, installed by a third-party contractor, maintained by someone who didn't build it."
That's a very specific kind of person. And finding them requires understanding what you're actually looking for, which is not a slightly more commercial version of the founder.
The Real Profile
When we start a search like this, we often push back on the brief we're given. Founders and boards tend to write job descriptions that describe a unicorn: deep scientific knowledge, commercial acumen, people leadership, international experience, startup DNA, and ideally someone who's already done this exact thing in this exact vertical.
That person is rare. Finding them requires precise market mapping and real depth, not a blind search across LinkedIn. It means knowing which adjacent industries produce this profile, which companies have actually been through this transition, and who specifically has the track record to prove it. That's exactly the kind of work our methodology is built around.
But before the search even starts, the more important conversation is about the profile itself. Because what this role actually calls for is someone with a different but complementary shape to the founder. They don't need to be the smartest person in the room on the science. The company already has that. What they need is:
Industrialization experience. They've taken something technically complex and turned it into something repeatable. Not necessarily in cleantech. Sometimes the best candidates come from adjacent industries where the engineering and operational challenges are structurally similar: specialty chemicals, advanced manufacturing, energy infrastructure, industrial biotech.
Comfort with ambiguity at scale. Early-stage deeptech is not a clean environment. The product is still being defined while it's being sold. Requirements change mid-deployment. The founding CTO will make a technical call that invalidates three months of work. The incoming CTO needs to absorb this without falling apart, and without creating a crisis of confidence in the team.
The ability to build around a founder, not instead of one. This is probably the hardest thing to assess in an interview process. The best candidates for this role are people who are genuinely energized by working alongside someone who invented the technology, not threatened by it. They understand that their job is to build the machine that delivers what the founder created. That requires a specific kind of ego: confident enough to lead, secure enough not to compete.
Commercial translation. They can take what the scientific founder understands intuitively about the technology and translate it into something a customer, a project manager, or a procurement team can actually evaluate and buy. This isn't about dumbing it down. It's about building the bridge.
Why Young Founders Make This Harder (And More Important)
There's a specific dynamic in university spinouts that makes this transition more loaded than it would be at a more mature company.
The founding CTO is often in their late twenties or early thirties. This is their first company. They've never hired a senior person before, let alone someone who is technically their peer or superior in certain dimensions. They've built the team themselves, usually from their lab group or their network. The culture is informal, scientific, and built on mutual trust with people who've worked alongside them for years.
Bringing in a CTO, especially one who is older, more experienced in industry, and explicitly hired to do things the founder doesn't know how to do yet, introduces a power dynamic that nobody quite knows how to navigate.
We've seen this go wrong in quiet ways. The new CTO is officially in charge of engineering. But the team still goes to the founder for technical decisions, because that's what they've always done. The founder, not wanting to undermine anyone, tries to redirect but does it inconsistently. The new CTO starts to feel like a figurehead. Within six months they're looking for the exit.
Nobody did anything wrong exactly. The setup was just never thought through carefully enough.
The transition works when the founder and the incoming CTO have built enough of a real relationship, before the hire is made, that the boundaries are clear and both people trust each other to operate within them. This takes time. It takes honest conversations. And it's one of the reasons we spend as much time working with the founding team through the process as we do sourcing candidates.
The Three Conversations That Make or Break the Hire
Before we write a brief, we make sure three conversations have happened, or we help make them happen.
Between the CEO and the founding CTO. What is the founding CTO's role going to look like after this hire, in practice, not just on paper? Where does their authority end and the new person's begin? Is the founding CTO genuinely at peace with this, or are they agreeing to it because the board wants it? A reluctant handover is not a handover.
Between the board and the CEO. What does success look like for this hire, and on what timeline? Is the expectation that the new CTO turns pilots into contracts within 12 months? Takes the company to Series B? Builds the team to 50 engineers? Vague mandates produce the wrong candidates and set up the right candidates to fail.
Between the founding CTO and the candidate. This one is the most underrated. The best transitions we've been part of had the founding CTO deeply involved in the final stages of the search, not just signing off, but doing real technical deep-dives with candidates, sharing context about the technology that no brief could capture, and beginning to build the working relationship before day one. It gives the founder ownership. It gives candidates a real picture of what they're walking into. And it surfaces chemistry, or the absence of it, before it becomes a six-month problem.
What This Looks Like When It Works
When it goes well, the founding CTO exhales.
Not because they've been relieved of something, but because they finally have someone to share the weight with. Someone who takes the industrialization problem off their desk so they can go back to the thing they're actually brilliant at. The R&D roadmap. The next generation of technology. The scientific conversations with customers that nobody else in the company can have.
The new CTO, meanwhile, gets to do what they're built for: taking a technology that genuinely works and building the operational infrastructure around it. That's a compelling challenge for the right person. The cleantech and deeptech space is full of real, working technologies that are stuck at exactly this stage. For an experienced operator who's done it before, it's one of the most interesting jobs out there right now.
Done well, the transition doesn't weaken the company. It doubles it. Two people, complementary skills, both motivated, both clear on their lane. That's when things start to move.
The Human Side of the Transition
I'll end with this, because it matters.
The founding CTO of a deeptech spinout has usually given years of their life to this technology before the company even existed. The PhD. The late nights in the lab. The presentations that didn't land. The experiments that failed. By the time they're sitting across from us talking about bringing in a CTO, they've already done something extraordinary. They turned a scientific insight into a company that investors believe in, and customers are willing to test.
That deserves respect. Not the performative kind, but the kind that shows up in how you design the process. How do you involve them? How do you talk about the role with candidates? How you handle the moments when the transition gets uncomfortable, because it always does.
Done right, everyone wins. The founder gets to focus on what they're brilliant at. The company gets someone who knows how to deliver. And the technology, which was always good enough, finally gets the chance to prove it at scale.
Frequently Asked Questions
When is the right time to bring in a CTO in a deeptech or cleantech company?
The clearest signal is when the company has proven the technology works, has at least one or two pilots behind it, and is starting to have real conversations about scale contracts. At that point, the founding CTO is being pulled in too many directions and the cost of not having an operator in place starts to compound quickly.
Should the scientific founder stay involved after a new CTO joins?
In almost every case, yes. The founding CTO's knowledge of the technology is a core asset of the company, not a role that gets replaced. The goal is to create a clean division where the founder owns the science and the incoming CTO owns delivery. That only works if both people are clear on the boundaries and genuinely trust each other, which is why how you run the transition matters as much as who you hire.
What makes a CTO search in deeptech different from a standard tech search?
The candidate pool is completely different. You're not looking for someone who has scaled a SaaS platform or managed a distributed engineering team. You're looking for someone who has taken a physically complex product through industrialization, managed the gap between R&D and real-world deployment, and done it in an environment where the product was still evolving while it was being sold. That profile rarely shows up in the obvious places, which is why the search requires precise market mapping rather than broad outreach.
How long does a search like this typically take?
It depends, and the biggest variable is rarely the search itself. It's how quickly the key stakeholders — the CEO, the founding CTO, and the board — can align on what they're actually looking for and what the incoming person is walking into. When that groundwork is done properly upfront, the search moves fast. We've closed searches like this in three months. When there's internal misalignment going into the process, no amount of good candidates fixes that, and timelines stretch accordingly.
What should a founding CTO expect from this process?
Honest conversations, early. About what their role looks like after the hire. About what they're genuinely handing over and what they're keeping. About the kind of person they can actually work alongside. The founding CTO shouldn't be a passive observer in this search. The best outcomes happen when they're an active part of it, and when they feel ownership over who comes in rather than having someone handed to them.
Key Search
Key Search specializes in expansion hires across Europe, the US, and transatlantic searches. To find out more about our US and North American hiring capability, visit us below.