Chapter 16: Knowing When to Step Aside — and Making It a Strength
A building is not something you finish. A building is something you start.
How Buildings Learn, 1994
William Hockey, co-founder and CTO of Plaid, published a blog post in June 2019 titled "Transitions" that began with an admission most founding CTOs would never make publicly: he was leaving the company he had built. Plaid had just raised at a $2.65 billion valuation. The team was 300 people. The product was becoming critical infrastructure for the fintech industry. And Hockey was stepping into a board-only role — not because he had been pushed out, but because he had spent two years planning for this moment.
"This conclusion was neither a rash nor a recent decision," Hockey wrote. "Over the past couple of years I have known that there would come a point at which I would choose to move to a purely strategic and advisorial role. And during the past year, I have started to work towards this goal."[1] His method was deliberate: he removed himself from day-to-day projects, tested whether teams could function without him, and stepped in only when necessary to guide and level up. When the transition was complete, his assessment was simple: "It is a testament to what we’ve all built together that I’m able to transition out of direct management without doubting for a moment the certainty of Plaid’s future."[1]
Hockey did something else that mattered as much as the transition itself: he made it public. "In tech, it has historically been taboo to talk about founders or executives transitioning to different roles inside companies," he wrote. "Leadership transitions need to become a bedrock of any company that desires to endure across decades."[1]
This chapter is about that transition — when to make it, how to make it well, and why making it is a sign of strategic maturity rather than failure. It is also about the alternative: the CTO who grows with the role rather than out of it. Both paths require intentionality. Neither is the default.
The Stage Mismatch
Evan Cooke, technical co-founder of Twilio, describes the CTO’s evolution in terms that make the stage problem visceral: "Chief technology officers at high-growth tech startups typically have three completely different careers in the span of only a few years: Engineer, Manager, Executive."[2] The skills that make a CTO effective at each stage are not just different — they are often in tension. The engineer who builds the prototype values depth, flow state, and hands-on problem-solving. The manager who hires the team values communication, delegation, and process. The executive who represents the company to the board and the market values strategy, narrative, and political judgment. Few people are good at all three. Fewer still enjoy all three.
Miguel Carranza, CTO of RevenueCat, documented his own evolution year by year and noticed a pattern in the broader data: "After reading a bunch of S-1 forms, it was hard to find first-time CTOs going all the way from MVP to IPO, as opposed to founding CEOs."[3] The founding CTO who takes a company from zero to exit without being replaced is the exception, not the rule.
Noam Wasserman’s research on founder transitions, based on a study of more than 10,000 founders, provides the quantitative foundation. By the third financing round, 52% of founder-CEOs have been replaced — and nearly three-quarters of those replacements were involuntary.[4] No equivalent data exists specifically for founding CTOs, but the structural logic is the same: the skills that got the company started are not the skills that scale it.
Viktor Nyblom, a CTO coach, defines four stages that map roughly to the 0→1 / 1→10 / 10→100 framework: Coder (the CTO writes most of the code), Manager (the CTO manages the people who write the code), Director (the CTO manages managers and owns process), and Strategist (the CTO owns technical vision and executive communication).[5] Each transition requires the CTO to let go of the activities that defined the previous stage. Each transition involves grief — the subject of Chapter 13. And each transition is a point at which the CTO must honestly assess whether they want to make the next jump.
Cooke captures the emotional difficulty of the later stages: "Board meetings that used to involve hours of product and engineering discussions instead start to focus on sales and marketing or strategy. It can feel like technology issues aren’t being prioritized or that you’re being marginalized. The reality is that the important problems faced by the company have changed."[2] The CTO who interprets this shift as a demotion — rather than as evidence that they succeeded in building a technology organisation that no longer requires constant executive attention — will resist the transition rather than embrace it.
Fred Wilson, co-founder of Union Square Ventures, frames the mismatch from the investor’s perspective: "It is very rare to find a person who can do both the VP Eng and CTO jobs at the same time. They require very different skills and very different time allocations."[6] Mark Suster, a venture capitalist who was twice a founder, provides the timing: "CTO’s max out at about 3 direct reports." When the team grows past five developers, the CTO needs either to evolve into a people leader or to hire one.[7] The question the CTO must answer at each stage is not "am I good at this?" but "is this what the company needs, and am I the person who can provide it?"
The honest answer — the one that most CTOs avoid — requires separating identity from role. The CTO who built the system from nothing has every right to feel proud of that achievement. But pride in what you built is not the same as fitness for what comes next. Cooke’s observation is worth sitting with: "I don’t think the huge amount of change in the CTO role gets enough recognition. Almost every founding CTO starts out wearing many, many hats — engineer, product manager, salesperson, customer service — but eventually you hire great people to fill those roles. That’s when it gets hard."[2] The difficulty is not in letting go of the hats. It is in discovering who you are without them.
|
AUTHOR: Where you see yourself in the stage framework — Coder, Manager, Director, or Strategist — and whether the stage you are in matches the stage CorralData needs. The reader at your company’s size is approaching the Manager-to-Director transition. How does the mismatch feel from the inside? |
The CTO Who Stayed
Not every founding CTO leaves. Stanislav Vishnevskiy, co-founder and CTO of Discord, has held the role since the company’s founding in 2015. As of early 2026, Discord has more than 200 million monthly active users and roughly 900 employees. Vishnevskiy remains CTO — more than a decade into the company’s life, through every stage of growth.[8]
His evolution is traceable through the company’s public record. In 2017, he was personally authoring technical blog posts about scaling Discord’s Elixir infrastructure to five million concurrent users — deep, hands-on architecture work that only the founding engineer could write.[9] By 2020, he was hiring Prachi Gupta from LinkedIn as Head of Engineering — the kind of delegation that signals a CTO who has moved from doing the work to building the organisation that does the work.[10] By 2026, he was writing public-facing blog posts on age verification policy and representing Discord at industry conferences — executive work that has nothing to do with code and everything to do with the company’s relationship with the world.[11]
Several factors made Vishnevskiy’s survival possible. His foundational architectural decision — building on Elixir and the Erlang VM — proved durable enough to serve the platform at massive scale, giving him sustained technical credibility even as he stepped away from daily implementation. He was willing to hire people who were better than him at specific functions, rather than clinging to responsibilities he had outgrown. And his relationship with co-founder Jason Citron remained stable across a decade — the co-founder dynamic that Chapter 10 identified as the most common point of failure held, giving both founders room to evolve their roles without threatening the other.
Calvin French-Owen, co-founder and CTO of Segment, provides the analytical framework for Vishnevskiy’s survival: "Think of yourself as a founder first, and CTO second. You can always hire someone to fill any one of these archetypes. But you can’t hire more founders."[12] The founder-CTO who stays is not staying because they are the best possible CTO at every stage. They are staying because the combination of founder context, institutional knowledge, and company vision they carry is irreplaceable — and they are willing to reinvent their role at each stage to remain useful.
French-Owen also names the attitude that makes survival possible: "The best founders I know don’t run away from this constant series of mini-games. They embrace it."[12] The "mini-games" are the stage transitions — each one requiring the CTO to learn a new set of skills, let go of the old ones, and tolerate the discomfort of being a beginner again. The CTO who stays must do this three or four times over a decade. The CTO who leaves is choosing to play a different game rather than start the next level.
Neither choice is wrong. The choice that is wrong is the one made by default — the CTO who stays without evolving, or the CTO who leaves without planning.
|
AUTHOR: Your assessment of your own trajectory — do you see yourself as a CTO who will stay and evolve, or one who is building toward a transition? The reader needs to see the self-assessment being done honestly, not the answer being predetermined. |
The Mechanics of Leaving Well
Daniel Aisen, CEO of Proof Trading, published a retrospective on his company’s CTO transition that provides the most practical account available of what the departure actually looks like from the inside. His first observation: the reaction was milder than expected. "At least to our face, the reaction we got was far milder than expected. Our investors in particular seemed totally unphased. Whereas for us this was major, scary news, our investors gave us the impression it was par for the course. It is apparently very common for co-founder/CTOs to leave early stage startups around the 3–4 year mark."[13]
This normalisation from the investor side is itself significant. The founding CTO who agonises for months about how the board will react is often carrying a fear that the board does not share. Korn Ferry data on the top 1,000 US companies shows CIO/CTO average tenure at approximately 4.3 years — shorter than CEOs (6.9 years) and only slightly longer than CMOs (3.5 years).[14] The CTO who leaves after four years is not failing. They are operating within the normal range of executive tenure.
Aisen’s practical advice centres on speed and candour: "We told the rest of the team within 24 hours, and made a public announcement within about a week."[13] His rationale: "Communicate quickly and candidly, internally and externally. It’s easy to fall into the trap of trying to control the message. In our experience, this is an impossible needle to thread."[13] Scott Barstow, a startup advisor, reinforces this: people tend to know what is happening even when you try to keep it quiet, and the attempt at secrecy induces more worry than the news itself.[15]
The timeline question has no single right answer. Hockey’s transition took two years. The PropertyGuru co-founder, interviewed by McKinsey, described a three-year succession process that included presenting to the board by framing succession as something "every leader needs to plan for."[16] Proof Trading moved within weeks. Steve Cox, a VP who managed the aftermath of a sudden CTO departure, argues that extended transitions can cause more harm than short ones: his CTO stayed for three months plus one month of consulting, but in retrospect, Cox believes the timeline should have been compressed to two to three weeks because the extended transition produced delayed decisions and competitive damage.[17]
The equity dimension is specific and consequential. Fred Wilson provides the investor’s perspective: founding CTOs four years in typically own between 10% and 40% of the company. When a founder is fully vested, Wilson recommends a new grant — "some percentage of what a market grant to a new CEO would be, ranging from 20% to 50%" — to maintain alignment.[18] The standard vesting structure (four years with a one-year cliff) means that a CTO who leaves before vesting is complete forfeits unvested shares. The CTO who is considering departure should understand their vesting schedule, any acceleration clauses, and the tax implications of option exercise — the financial literacy from Chapter 15 applied to the specific context of exit.
|
AUTHOR: If there is anything you can share about how you think about your own vesting, equity position, and the financial dimension of staying vs. leaving — even in general terms — it would ground this section. The reader at your stage is thinking about these questions even if they are not asking them aloud. |
Departure as Strategy
Reid Hoffman, co-founder of LinkedIn, provides the framework that reframes departure from failure to strategy. In The Alliance, written with Ben Casnocha and Chris Yeh, Hoffman proposes the "tour of duty" — a model in which employer and employee commit to a specific mission of finite duration. The paradox, Hoffman argues, is that "acknowledging the fact that an employee can and might leave your company in the future improves your ability to construct a tour of duty that convinces him or her to stay."[19]
Applied to the CTO role: the founding CTO’s initial tour might be to build the MVP and achieve product-market fit. The second tour might be to scale the engineering team from five to fifty. The third might be to establish the technical strategy that carries the company through its next phase. Each tour has a defined mission and an endpoint. When the mission is complete, both parties should discuss the next tour — which may be at the same company in a different role, or at a different company entirely.
Daniel Doubrovkine, former CTO of Artsy, provides the most honest articulation of what this looks like from the inside: "`In my last year as CTO I began to feel like I was dangerously hanging over the ‘organizationally important, but useless’ line, where many very senior managers typically sit and vest. I don’t ever want to be that kind of ballast.`"[20] Doubrovkine left to take an IC role at AWS — a move that, by traditional career logic, looks like a step backward. By Doubrovkine’s logic, it extended his "technical relevance by a decade."[20]
Benoit Hediard, co-founder and CTO of Agorapulse, frames the self-knowledge even more directly: "I’m a startup builder, not a scale up manager. I’m a craftsman, not an industrialist."[21] The sentence reads as a limitation. It is, in fact, a superpower — the clarity to know what you are good at, what you enjoy, and where your contribution is highest. The CTO who tries to be both the craftsman and the industrialist will be mediocre at both. The CTO who knows which one they are can make the transition at the right time, to the right role, with the right framing.
The industry is normalising this understanding. Mira Murati, departing as CTO of OpenAI, said: "I’m stepping away because I want to create the time and space to do my own exploration."[22] David Singleton, after seven years as CTO of Stripe, wrote: "It’s time for me to pick up my startup dreams again and start something new on my own."[23] JB Straubel, after fifteen years as CTO of Tesla, emphasised: "I’m not disappearing. This was not some lack of confidence in the company or the team."[24] Each of these departures was covered as news. None was covered as failure. The narrative has shifted.
|
AUTHOR: How you think about your own "tour of duty" at CorralData — is there a specific mission that, once accomplished, would signal the end of your current tour? Or is the mission still evolving? The reader needs to see this framework applied to a real, ongoing decision. |
When the Company Is Acquired
Not every departure is voluntary, and not every exit is a departure. When a startup is acquired, the CTO enters a liminal state — no longer a founder in any real sense, not yet an employee of the acquiring company, and uncertain about which version of themselves will survive the integration.
The process begins with due diligence, and for the CTO, due diligence is personal. Onoufrios Malikkides, CTO of Labstep, described a two-stage technical evaluation during his company’s acquisition: first, a spreadsheet containing hundreds of questions covering architecture, data schemas, IP ownership, security posture, test coverage, CI/CD maturity, and disaster recovery documentation. Second, a four-hour deep dive with external evaluators examining the codebase and the team.[25] The CTO is not merely answering questions about the system. They are defending every decision they have ever made — every shortcut, every piece of technical debt, every architectural bet. Doubrovkine, writing from the evaluator’s side, reduces the assessment to three questions: "Would I trust this CTO with my own company? Do I respect the technical and organisational abilities of the technology leadership? Would I want to hire any of the technical people into my own team?"[26] The CTO who has invested in code quality, documentation, and team development will find due diligence uncomfortable but survivable. The CTO who has accumulated years of undocumented debt will find it existential.
Elad Gil’s High Growth Handbook provides the financial mechanics most founders miss. In acqui-hire scenarios, the typical valuation is between one and three million dollars per engineer, rising to five million for exceptional talent. But the headline number disguises a critical split: a portion goes to the cap table (shareholders), and a portion goes to the retention pool (employees who stay). "Many corporate development teams quote total deal value without mentioning what part goes to the cap table versus retention," Gil writes. "This can materially impact value to founders."[27] The CTO who negotiates without understanding this distinction is negotiating blindly.
Will Larson, who went through the Digg acqui-hire, identifies the question that defines the acqui-hire experience: "Am I the product?"[28] In a product acquisition, the company’s technology is the asset. In an acqui-hire, the people are the asset. The distinction matters because in an acqui-hire, the CTO’s negotiating power comes from their ability to deliver the team — and that power evaporates the moment the deal closes. Larson is blunt about the compensation reality: "Even the best of the acquihire compensation packages were less than you would have made working as a senior software engineer at Google for the same period of time."[28] Senior leaders face additional pressure: "Because acquihires are 'star' oriented, if you’re a senior leader who doesn’t explicitly refuse to move forward, pressure will converge on you from all sides: investors, the team wanting to return to stable employment, and the non-participating leadership team who all want you to commit so they can move on."[28]
Then comes integration — the part nobody prepares for. Doubrovkine’s description of his post-CTO experience at a large company captures the identity loss with precision: "I did lose significant amounts of organisational power. I no longer know all the secrets. Many decisions that affect me are made by others, by design. As CTO I made all decisions for my team and for company-wide technology. I had access to detailed financial information, and knew when someone important was quitting or being fired. This is all gone."[20] The CTO who was the most important technical person in a fifty-person company becomes a mid-level leader in a five-thousand-person company. The title may survive the acquisition. The authority does not.
The departure pattern is well-documented if statistically imprecise. French-Owen left Segment the day the Twilio acquisition closed — zero days of integration. "On Oct 30th, my co-founder Ilya and I said our last goodbyes to the company. In that moment, I felt a sudden wave of sadness. I fully realised I was parting with the teammates who I’d spent the better part of my 20’s with."[29] Mike Krieger and Kevin Systrom lasted six years at Facebook after the Instagram acquisition before departing in 2018 over what multiple outlets reported as growing tensions with Zuckerberg over Facebook’s increasing control of Instagram’s product direction.[30] Jan Koum lasted four years at Facebook after the WhatsApp acquisition. The pattern is consistent: the CTO who stays through integration watches their company’s identity dissolve into the acquirer’s culture, and at some point — whether it is day one or year six — they decide they have mourned long enough.
Daniel Debow, who has been through three acquisitions, offers the most practical advice: "Psychologically, you should prepare yourself for some sort of turmoil. You are operating in a different environment now." And the hardest sentence: "Remind yourself: you are not CEO anymore."[31] For the CTO, the equivalent is: you are not the person who built this system from nothing. You are the person who maintains a system that now belongs to someone else.
|
AUTHOR: If you have any experience with acquisition conversations at CorralData or at previous companies — even exploratory ones — the reader needs to see how this feels from the inside. The due diligence stress, the identity questions, the "what happens to my team" anxiety. Even if no acquisition has happened, the anticipation of one is worth describing. |
When the Company Shuts Down
The scenarios covered so far — voluntary departure, stage mismatch, acquisition — all assume the company survives. The scenario nobody wants to discuss is the one in which it does not.
Adrian Aoun spent eight years building Forward, a healthcare startup that raised $400 million to reimagine primary care through technology. The company built AI-powered doctor’s offices, then pivoted to "CarePods" — self-contained AI diagnostic stations designed to scale globally without requiring a doctor on site. The market turned against them. The 2021 fundraising boom that had enabled a $225 million round corrected violently. Amazon bought One Medical for four billion; Walgreens bought Village MD for nearly six billion; CVS bought Oak Street for eleven billion. Then, within eighteen months, nearly every one of those acquisitions failed — write-downs, shuttered clinics, fired CEOs. The growth-stage investors Aoun needed saw "$25 billion worth of failures" in primary care and closed their chequebooks.[32]
Aoun’s account of the shutdown decision, given on the "More or Less" podcast days after it happened, is the most honest public description of the moment available. "As early as last week, we had a round on the table," he said. "And the reality is that we kind of said, look, is this round going to get us to the other side of this market? And the reality is no, it’s not."[32] What happened next was immediate: "I felt a moral and ethical obligation to do it. When you’re asking investors, when you’re asking customers, when you’re asking employees to follow you and believe in you, the second you don’t believe that you have a chance of success, you’re being unethical."[32] Four hours later, he told the employees.
He then made 150 phone calls to investors. "One of the most shocking responses was, 'I can’t believe you actually called. Nobody else calls.'"[32] Dave Morin, co-founder of Offline Ventures and co-host of the podcast, framed this credibility distinction: "A lot of entrepreneurs can lift off the plane, but not all entrepreneurs can land the plane. And landing the plane could be an exit, it could be returning partial money back, or it could just be following through to shut down the right way. Just finish the job. Don’t abandon the ship."[32] One of Aoun’s largest investors — a board member as recently as the week before — called the next day and said: "We’re done with that. So what are you doing next? Can I cut you a term sheet?"[32]
The employees' reaction was equally striking. Zero came forward with anger. The most common response: "I know you said you’re not doing something for six months, but that doesn’t work for me because I need a job. Will you start your next company today and hire me next week?" By Wednesday — the day after the Tuesday shutdown — Aoun was starting a new company. Within a week, he was cofounding a venture with former Forward executives.[33]
Aoun’s story is the version with investor goodwill and a soft landing. The version without goodwill is uglier. Forward’s patients lost access to their medical records. The company’s website posted a notice that its clinical email support would be available only until December 13, 2024. Patients reported on social media that they could not get medication refills or access their own health data weeks after the closure.[34] For a CTO in healthcare — which is to say, for a CTO whose systems hold data protected by HIPAA — the technical wind-down is not optional. Customer data must be migrated, exported, or securely deleted according to regulatory requirements. Infrastructure must be decommissioned. IP must be disposed of according to board-approved processes — it cannot be informally distributed, even to the founders.[35]
The "go cold plan" — a concept Aoun attributed to Munjal Shah of Hippocratic AI — is the structural defence against this scenario. Shah’s approach: ensure that at any point, the company can scale its burn down to a level that provides thirty-six months of cash runway. The mechanism is not just headcount reduction — it is contractual flexibility across leases, cloud infrastructure, vendor commitments, and service agreements.[32] The CTO who signs a three-year AWS commitment without a termination clause has reduced the company’s ability to go cold. The CTO who negotiates month-to-month terms at a slightly higher unit cost has bought the company an option — and in a startup, optionality is worth more than optimisation.
Adam Smith, founder of Kite — an AI code completion tool that raised venture funding and accumulated 500,000 developers before shutting down in 2022 — chose a different kind of closure. He open-sourced the entire codebase under a BSD-3-Clause licence: the Python type inference engine, package analyser, desktop software, editor integrations, and GitHub crawler. "We failed to deliver our vision of AI-assisted programming because we were ten-plus years too early to market," Smith wrote. "I’m sorry it did not work out. We took a chance. We ran the experiment, and despite great efforts, the experiment did not work."[36] The open-source decision was an act of generosity — the technology that did not make money could still make a contribution — but it was also an act of narrative control. Smith defined the failure on his own terms before anyone else could define it for him.
Justin Kan’s Atrium — a tech-enabled law firm that raised $75 million — provides the serial founder’s perspective on shutdown. Kan, who had co-founded Twitch and sold it to Amazon for a billion dollars, could not make legal services work as a technology business. His conclusion was characteristically direct: "Adding more money to a situation of lack of product-market fit rarely works." And his observation about the experience: "My friends see me and they’re like, 'Wow, you are so much happier than you were going through the startup experience.'"[37]
The research on what happens to founders after failure tells a more complex story than the Silicon Valley narrative suggests. Gompers, Kovner, Lerner, and Scharfstein’s study of venture-backed entrepreneurship found that previously successful founders have a 30% chance of succeeding in their next venture — substantially higher than the 21% base rate for first-time founders. But previously failed founders? Their success rate is 22% — barely above the first-time rate.[38] The "investors prefer second-time founders" story is true in a narrow sense — failed founders receive funding faster than first-timers, at 21 months versus 37 months from founding to first VC round — but the performance improvement is marginal. What investors are buying is not a higher probability of success. It is a lower probability of the specific failure modes that kill first-time companies: cofounder disputes, inability to hire, failure to communicate with the board.
Nikki Durkin, who shut down her startup 99dresses, wrote the rawest account of the emotional reality: "Failure f—ing sucks. Failing is lonely and isolating. Every time I’d scroll through my Facebook feed, all my startup friends were launching new products, announcing their new fundraising rounds or acquisition, and posting photos of their happy teams."[39] The CTO who goes through a shutdown will experience some version of this — the grief of losing the thing you built with your hands, compounded by the public nature of the loss. James Routledge, founder of Sanctus, draws a distinction that matters: "In a way, grieving a startup that fails is easier than grieving a startup that is sold, because it’s black and white. The startup is dead. You must mourn it and move on."[40] The clarity of failure, as brutal as it is, at least allows clean grief. The ambiguity of acquisition — your company lives on, but without you — does not.
|
AUTHOR: This section needs your honest reflection on what shutdown would look like at CorralData — not because you expect it, but because the reader at a healthcare startup needs to see a CTO thinking about the obligations. What would happen to patient data? What contracts would need to be unwound? What would you owe to the team? The reader who has never thought about this needs to start thinking about it now, while there is time to plan rather than react. |
What Comes After
The CTO career does not end when the CTO role ends. It changes shape.
Hockey left Plaid and spent three years in stealth building Column, a nationally chartered bank for developers. By early 2026, Column was generating roughly $200 million in annual revenue with approximately 110 employees, entirely bootstrapped and free-cash-flow positive.[41] The founding CTO’s operational experience — building systems, hiring engineers, translating between technical and business audiences — turned out to be the foundation for a different kind of company.
Charity Majors’ "engineer/manager pendulum" provides the intellectual framework for the most counterintuitive post-CTO path: going back to building. "The best frontline eng managers in the world are the ones that are never more than 2-3 years removed from hands-on work," Majors writes. "The best individual contributors are the ones who have done time in management. And the best technical leaders in the world are often the ones who do both. Back and forth. Like a pendulum."[42] Doubrovkine’s move from Artsy CTO to AWS IC is the pendulum in action. The management experience does not disappear. It becomes context — the understanding of systems, teams, and trade-offs that makes the former CTO a more effective builder than they were before they led.
Other paths are equally valid. Mike Schroepfer left the CTO role at Facebook after a decade to launch Gigascale Capital, a climate-focused venture fund: "I always had a passion for the climate crisis. I have some little kids at home. I think about the future, and I said, what am I doing about this problem?"[43] James Turnbull, former CTO of Kickstarter, moved to Empatico, an education startup: "There is a growing pool of folks like me who want to do something they can feel proud of."[44] The CTO career arc that starts with building a product and ends with building something that matters beyond the product is not a retreat. It is the completion of a trajectory that the startup phase, with its urgency and financial pressure, did not allow.
There is also the serial CTO — the person who does the founding CTO role at multiple companies, deliberately choosing to operate in the 0→1 or 1→10 stage where their skills are strongest. Hediard’s self-assessment — "I’m a startup builder, not a scale up manager" — is the serial CTO’s self-knowledge made explicit.[21] Rather than trying to become a strategist when their strength is craftsmanship, the serial CTO leaves when the company outgrows the stage, carries the lessons to the next company, and starts the cycle again. The industry increasingly supports this path: fractional CTO roles, advisory positions, and portfolio careers allow the former CTO to apply their experience across multiple companies simultaneously rather than committing to one organisation for the next decade.
The common thread across every post-CTO path — founding a new company, returning to IC work, moving into investing, pursuing mission-driven work, or operating as a serial CTO — is that the skills the CTO developed in the role do not expire. The architectural judgment, the ability to translate between technical and business audiences, the experience of building and leading teams, the pattern recognition for what works and what does not at startup scale — these are transferable to every subsequent role. The CTO who leaves is not starting over. They are carrying forward everything the role taught them into a context where it can be applied differently.
The question this chapter asks is not "should you leave?" It is "are you making the decision, or is the decision being made for you?" The CTO who plans a two-year transition, builds the team that can function without them, and leaves on their own terms — as Hockey did — is exercising the same strategic judgment that made them effective in the role. The CTO who stays and evolves through every stage — as Vishnevskiy has done — is exercising a different kind of strategic judgment, one that requires continuous reinvention and the willingness to be a beginner again and again. The CTO whose company is acquired must navigate the hardest identity question of all: who am I when the system I built belongs to someone else? And the CTO whose company shuts down must answer the question that Aoun answered in four hours: do I have the integrity to act the moment I stop believing?
Chapter 10 addressed what happens when the CTO is pushed out. This chapter addresses what happens when the CTO chooses — and what happens when circumstances choose for them. The difference is not always in the outcome. In every case, the CTO leaves the role. The difference is in how they leave, what they leave behind, and whether the people who trusted them — the team, the investors, the customers — are better off for having been led by someone who knew when to act. David Lee of SV Angel, citing Ron Conway, put it simply: "How a founder conducts herself during either an acqui-hire or soft landing can determine if they get funding from their prior investors for their next venture."[45] The reputation is not built in the good times. It is built in the exit.
Kellan Elliott-McCrea’s test from Chapter 11 applies one final time: can you hand the work off to people you trust, and will they run the thing without you and make it better than you could have imagined? If the answer is yes, you are ready — whether what follows is a new tour, a new company, or a clean goodbye.