# 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. -- Stewart Brand How Buildings Learn, 1994 Key Takeaways * A CTO transition is not a failure; it is a predictable phase of company growth. The skills that take a company from zero to one are rarely the same skills that take it from one to a hundred, and recognising that is leadership, not defeat. * The CTOs who stay longest do so not by clinging to the role but by continually reinventing it -- treating each era as a new job within the same company. * Reid Hoffman's tour-of-duty framework turns an indefinite, guilt-laden commitment into a time-boxed alliance with clear objectives. When the tour ends, both sides renegotiate openly instead of drifting toward mutual resentment. * When a startup shuts down, the CTO's last job is to help people land well. The technology is gone; the relationships and the reputation you built in the final weeks are what you carry forward. 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."\\] 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."\\] 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."\\] 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."\\] 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."\\] 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.\\] 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).\\] 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."\\] 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."\\] 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.\\] 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."\\] 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.\\] 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.\\] 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.\\] 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.\\] 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."\\] 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."\\] 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."\\] 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).\\] 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."\\] 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."\\] 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.\\] 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."\\] 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.\\] 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.\\] 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."\\] 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.\`"\\] 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."\\] 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."\\] 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."\\] 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."\\] 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."\\] 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 You Are Fired The scenarios above assume the CTO controls the departure. This one does not. Noam Wasserman, studying approximately 10,000 founders across 3,600 startups for _The Founder's Dilemmas_, found that 52% of founders are replaced by the time the startup raises its third round of financing. Of those replacements, 73% are involuntary.\\] The data concerns founder-CEOs, but the pattern applies to founding CTOs with equal force -- and possibly greater frequency. Adelina Chalmers, a consultant who performs technical due diligence for VC firms, estimates that most founding CTOs are fired or moved sideways within three to five years. The causes she identifies are consistent across her engagements: the CTO alienates the board with technical language that makes no business case, treats non-technical executives with visible disdain, or says "you have to trust me" to a room full of people whose fiduciary duty is to verify rather than trust.\\] The firing itself happens in several ways, and only one of them involves the word "fired." The most common is the quiet push-out: the CTO's title remains but their authority is removed. A VP of Engineering is hired to run the team. The CTO's direct reports are reassigned. Decisions that once required the CTO's approval are made in meetings the CTO is not invited to. Gonzalo Fernandez-Victorio describes the trajectory with precision: "What started as an exciting position setting up the whole team, technology and processes for the company, ended up sidelined, micromanaged, with no responsibility over the team, and no decision over the technology."\\] The CTO who is being sidelined will recognise the symptoms before they recognise the diagnosis. The second variant is the "strategic reorganisation" -- the board decides the company needs a different technical leadership structure, and the CTO is offered a lesser role: Distinguished Engineer, Chief Architect, "Founder Emeritus." The title is a face-saving device. The authority is gone. The third variant is direct termination: a board vote, a conversation with the CEO, and an escort to the door. Scott Barstow, writing from the CEO's side, warns that firing a CTO carries more operational risk than firing any other executive: "If you have a bloody ending to the dismissal of your CTO, the damage can be permanent."\\] The legal mechanics are simpler than most CTOs realise. Under Delaware law, officers serve at the board's pleasure and can be removed with or without cause by a board vote. No advance notice is required. A CTO who is also a director presents a different problem -- director removal requires a shareholder vote, not a board vote -- but in practice, a CTO who has been fired from the officer role will not survive long as a board member. The position is untenable.\\] What to negotiate if you see it coming -- or when it arrives: acceleration of unvested equity (double-trigger acceleration is standard; push for it before you need it, not during the severance conversation); extended exercise windows for vested options (the standard 90-day post-termination exercise period is a trap for founders with large ISOs and AMT exposure); continuation of health insurance; a mutual non-disparagement clause; and an agreed reference narrative. The CTO who negotiated these terms in their original employment agreement has leverage. The CTO who did not is negotiating from weakness at the worst possible moment.\\] Katherine Hays, writing in BetaKit, states the point that should appear in bold on every founder's wall: "The company's lawyer is representing the company's interests, not yours."\\] The emotional reality is the part that no negotiation addresses. Yakov Filippenko, co-founder of Intch, called the board vote himself: "We had to choose who would stay, me or my co-founder. The vote didn't go my way." On the aftermath: "When it ended, I filled my calendar with aimless meetings. Five or six a day. Traditional business tools didn't help. OKRs, planning sessions, strategy off-sites -- none of it worked on the inner collapse that comes when your identity and your company split apart."\\] The inner collapse is not weakness. It is the predictable consequence of the identity fusion that [Chapter 15](15-cto-burnout-isolation.html) described -- the inability to separate the self from the company. Jason Cohen of WP Engine names the mechanism: "A startup founder lacks this distinction between personal identity and work identity."\\] When the company fires the CTO, it is not firing an employee. It is amputating part of the CTO's identity. The grief is proportional. The recovery path is the same path the chapter has been describing: peer support, coaching, the willingness to ask Colonna's question ("How have I been complicit in creating the conditions I say I don't want?"), and -- eventually -- the recognition that the role was a stage, not a destination. Noah Glass, who co-founded Twitter, built the first prototype, chose the name, and was fired in 2006, never appeared in the IPO filing. He went on to build OLO, a restaurant technology company that went public in 2021\. The firing was brutal. The career was not over. | | AUTHOR: If you have ever been fired from a role, or witnessed a co-founder firing at close range, the reader needs to hear it. The CTO who is reading this section while suspecting they are about to be pushed out needs to know they are not alone, that the grief is real, and that the career continues. | | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ## 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. Before describing that liminal state, a statistical reality deserves attention: most acquisition conversations go nowhere. Jeff Seibert, who sold Increo to Box and Crashlytics to Twitter, then spent years evaluating acquisitions from the buyer's side as Senior Director of Product at Twitter, offers the clearest data: Twitter evaluated over fifty startups during his tenure, and roughly one in seventeen conversations resulted in a completed deal.\\] Axial, an M&A deal network, reports that a typical PE firm attends 150 management meetings per year and closes five to ten deals -- a conversion rate between 3% and 7%.\\] Even after a Letter of Intent is signed, 10--25% of deals fail to close.\\] Kevin Dykes, a serial founder, went through five failed acquisition processes with a single startup before a partial deal finally closed. His summary captures the asymmetry: for the acquiring company's corporate development team, exploratory conversations are Tuesday; for the startup founder, they are an all-consuming emotional event that pulls focus from product, fundraising, and team morale -- often for months, with nothing to show for it.\\] The CTO's practical takeaway is: do not tell the team until the direction is certain, do not stop building product, and do not believe a deal is real until the money has arrived. A recently exited founder, asked when they knew the acquisition was real, answered with two words: "Cheque cleared." | | AUTHOR: If you have been through exploratory acquisition conversations at CorralData or at previous companies -- the corporate development coffees, the sizing-up meetings that felt like they might be something but weren't -- the reader needs to understand that the default outcome of an acquisition conversation is silence. | | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | 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.\\] 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?"\\] 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."\\] 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?"\\] 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."\\] 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."\\] 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."\\] 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."\\] 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.\\] 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."\\] 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 Money Arrives The acquisition closes. The cheque clears. The CTO is, for the first time in years, not worried about runway. And then a different set of problems begins -- ones that no CTO book discusses, because CTO books assume the hard part is building the company, not surviving its success. Psychologists Stephen Goldbart and Joan DiFuria of the Money, Meaning & Choices Institute coined the term "sudden wealth syndrome" in the 1990s to describe the constellation of anxiety, guilt, isolation, and identity confusion that accompanies rapid wealth acquisition. It is not a formal clinical diagnosis -- it does not appear in the DSM-5 -- but the pattern is documented and consistent: the recipient experiences guilt comparable to survivor guilt, paranoia about losing the wealth, impulsive financial decisions driven by the novelty of having options, and a persistent sense that the money should have produced happiness and has not.\\] Markus Persson -- "Notch" -- sold Minecraft to Microsoft for $2.5 billion in September 2014\. Less than a year later, he posted what became the defining cautionary tale of post-exit wealth: "Hanging out in Ibiza with a bunch of friends and partying with famous people, able to do whatever I want, and I've never felt more isolated." He bought a $70 million Beverly Hills mansion. He described the problem of running out of reasons to keep trying. He noted that the biggest effort in the sale went into ensuring the employees were taken care of, "and they all hate me now."\\] Two days later he partially walked it back -- "I'm sitting here having a nice day" -- but the damage was done. The thread became a reference point for every subsequent conversation about founder mental health after exit. By 2019, Microsoft had distanced Persson from the Minecraft brand entirely, following a series of increasingly controversial social media posts. The trajectory -- isolation, loss of purpose, radicalisation through online discourse -- is not inevitable, but it is common enough to name as a risk. The practical defences are straightforward, if underused. First: hire a fee-only fiduciary financial adviser before the deal closes, not after. The wealth managers who cold-call after an exit are not fiduciaries -- they operate under a suitability standard, meaning they can recommend products that are merely adequate for the client rather than optimal. A fee-only adviser, registered with NAPFA, charges flat fees or AUM percentages, accepts no commissions, and is legally obligated to act in the client's best interest. Firms like Darrow Wealth Management and Secfi specialise in equity compensation for startup founders and executives.\\] Second: understand the tax implications before the deal structure is finalised. Section 1202 (QSBS) can exclude up to 100% of capital gains -- capped at the greater of $10 million or ten times the shareholder's basis -- on qualified small business stock held for five or more years. But the exclusion is federal only. California does not conform to Section 1202; a California founder with a $10 million federally excluded gain would still owe approximately $1.4 million in state tax. Healthcare companies require careful QSBS analysis -- certain service sectors are disqualified.\\] Third: do not make major financial decisions for six months. Susan Bradley of the Sudden Money Institute calls this the "Passage" phase and advises clients to let the new reality settle before committing capital. The subtler risk is the golden handcuffs. Matthew Lyon, an engineer who went through an acquisition, wrote the most honest account of the retention trap: the common-stock options were worthless, but they translated into a retention offer designed to keep him through integration. "I focused so narrowly on the payout that I didn't see the broader emotional cost," he wrote. The burnout during integration was severe enough to resemble clinical depression. When he finally received the payout and resigned, the recovery took seven months.\\] The CTO facing a retention offer should calculate not just the financial value of staying but the opportunity cost -- the career time lost, the emotional toll of working in an organisation they no longer recognise, and the health effects of chronic misalignment between their values and their daily reality. Sometimes the most expensive handcuffs are the ones you do not take off when you can afford to. And the deepest risk: do not mistake a liquidity event for personal validation. The exit was partly skill, partly timing, partly luck, and partly the labour of every person who worked at the company. The CTO who treats the cheque as evidence of personal superiority -- who begins dispensing wisdom on social media, who loses the capacity to listen, who radicalises in the echo chamber of post-exit founders congratulating each other on their brilliance -- has not succeeded. They have begun a different kind of failure. The Haatch VC collective, all exited founders themselves, capture it precisely: "So much effort and focus had been put on the 'deal' that I had very little understanding of what I should think, or feel, afterwards. You suddenly wake up with an empty email inbox and silence."\\] The silence is the test. What you do with it reveals whether the exit was the end of a chapter or the beginning of a decline. | | AUTHOR: Your perspective on what financial and psychological preparation you would want to have in place if CorralData were acquired -- both for yourself and for the team. The reader needs to hear a working CTO thinking about this before it happens, not after. | | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ## 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. It is also, statistically, the most likely scenario. Shikhar Ghosh at Harvard Business School studied 2,000 venture-backed companies that raised at least $1 million between 2004 and 2010 and found that 75% never returned cash to investors; 30--40% liquidated completely, with investors losing everything.\\] Carta's analysis of its 2018 startup cohort, published in early 2025 by Head of Insights Peter Walker, tracked every company on the platform over seven years: 62% shut down entirely, only 15% reached Series B, and approximately 1.3% achieved unicorn status.\\] The post-2021 correction has accelerated these numbers. Carta recorded 966 U.S. startup shutdowns in 2024, a 25% increase over 2023, with Series B shutdowns up 133% year-over-year.\\] CB Insights analysed 431 publicly shut-down VC-backed startups since 2023, representing $17.5 billion in destroyed equity. Nearly a quarter had been "walking dead" for three or more years since their last fundraise -- zombie companies that neither shut down nor grew.\\] The CTO reading this chapter needs to absorb this number: roughly two out of three startups that raise a seed round will not exist in seven years. This is not a worst case. It is the base rate. 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.\\] 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."\\] 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."\\] 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.'"\\] 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."\\] 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?"\\] 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.\\] 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.\\] 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.\\] 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.\\] 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."\\] 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.'"\\] 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.\\] 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."\\] 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."\\] 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.\\] 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."\\] 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?"\\] 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."\\] 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.\\] 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](10-business-acumen-gap.html) 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."\\] The reputation is not built in the good times. It is built in the exit. Kellan Elliott-McCrea's test from [Chapter 11](11-building-engineering-team.html) 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. ## Frequently Asked Questions 1. _When should a startup CTO step down?_ Consider stepping aside when the company's needs have clearly outgrown your skills and interest -- when the role requires capabilities you do not have and do not want to develop. Other signals include sustained stagnation after five or more years, persistent friction with the board or CEO about the direction of technology, or the recognition that a different leader could unlock the next stage of growth. Stepping aside at the right time is a sign of strength and self-awareness, not failure. 2. _Is it normal for founding CTOs to be replaced?_ Yes -- the majority of founding CTOs are no longer in the role by Series B or C. The CTO job at a 5-person startup and the CTO job at a 500-person company are fundamentally different positions with different skill requirements. This is not a reflection of the founding CTO's ability but a structural reality of the role's transformation. The founders who navigate this transition well plan for it in advance rather than being forced out by circumstance. 3. _What is a tour of duty in startup leadership?_ The tour of duty concept, from Reid Hoffman, reframes employment as a series of defined missions rather than indefinite tenure. Applied to the CTO role, it means committing to a specific mission -- build the MVP, scale the team to 50 engineers, achieve SOC 2 compliance -- with a defined timeframe and success criteria. When the mission is complete, both the CTO and the company can honestly assess whether a new tour makes sense or whether it is time for a transition. 4. _How do you plan a CTO leadership transition?_ Start planning 6 to 12 months before the transition. Document institutional knowledge -- architecture decisions, vendor relationships, team dynamics, technical debt inventory. Hire or identify your successor and ensure overlap for knowledge transfer. Define your post-transition role clearly -- advisory, board seat, individual contributor, or clean departure. Communicate the transition to the team with honesty about the reasons. A well-planned transition preserves the team's stability and the departing CTO's reputation. 5. _What happens to founding CTOs after they leave?_ Founding CTOs move into a range of roles -- advisory positions at the company they built, CTO roles at later-stage companies where their experience is a better fit, venture capital where their technical judgment helps evaluate startups, founding new companies with the benefit of hindsight, or returning to individual contributor engineering roles. Many find the advisory path -- helping multiple startups with strategic technology decisions -- to be the most satisfying next chapter. ## References . Hockey, W. (2019, June 18). Transitions. _Medium_. -- Hockey was co-founder, CTO, and President of Plaid. . Cooke, E. (\~2015). This is how effective CTOs embrace change \\\[CTO Summit talk\]. _First Round Review_. -- Cooke was technical co-founder of Twilio. . Carranza, M. (2020, December 6). Evolution of my role as a founder CTO. _miguelcarranza.es_. -- Carranza is CTO of RevenueCat. . Wasserman, N. (2008, February). The founder's dilemma. _Harvard Business Review_. -- Based on study of 212 startups. Expanded in Wasserman, N. (2012). _The Founder's Dilemmas_. Princeton University Press (\~10,000 founders). . Nyblom, V. (2023, March 22). The four stages of a startup CTO. _nyblom.io_. . Wilson, F. (2011, October 31). VP Engineering vs CTO. _AVC_ (MBA Mondays). . Suster, M. (\~2011). Want to know the difference between a CTO and a VP Engineering? _Both Sides of the Table_. . Discord statistics compiled from: Whop, "Ultimate Discord statistics for 2026," ; Discord company blog; podcast interviews (Grit #192, Gaming Founders Podcast). . Vishnevskiy, S. (2017, July 6). How Discord scaled Elixir to 5,000,000 concurrent users. _Discord Blog_. . Vishnevskiy, S. (2020, August 13). Prachi Gupta joins the Discord family. _Discord Blog_. . Vishnevskiy, S. (2026, February 24). Getting global age assurance right: What we got wrong and what's changing. _Discord Blog_. . French-Owen, C. From founder to CTO. _calv.info_. -- French-Owen was co-founder and CTO of Segment. . Aisen, D. (\~2022). Our CTO transition in retrospect. _Proof Reading_ (Medium). . Korn Ferry. (2020, January 21). Age and tenure in the C-Suite. _Business Wire_. -- Based on top 1,000 US companies. CIO/CTO average tenure: \~4.3 years. . Barstow, S. How to survive your CTO leaving. _scottbarstow.com_. . Melhuish, S. (2020, October 15). How to plan a successful leadership succession at a start-up \\\[Interview\]. _McKinsey & Company_. . Cox, S. That time the CTO quit. _Medium_. . Wilson, F. (2018, November 11). What happens when a founder is fully vested? _AVC_ / _Inc._ . Hoffman, R., Casnocha, B., & Yeh, C. (2014). _The Alliance: Managing Talent in the Networked Age_. Harvard Business Review Press. See also: Hoffman, R., Casnocha, B., & Yeh, C. (2013, June). Tours of duty: The new employer-employee compact. _Harvard Business Review_. . Doubrovkine, D. (2019, November 17). Pros and cons of going from management back to individual contributor. _code.dblock.org_. . Hediard, B. (\~2023). A CTO and co-founder journey from startup to scale up, Part 4: What's next for me? _Medium_. . Murati, M. Quoted in Coldewey, D. (2024, October 19). Former OpenAI CTO Mira Murati is reportedly fundraising for a new AI startup. _TechCrunch_. . Singleton, D. (2024, August). LinkedIn post announcing departure from Stripe. Reported in _Silicon Republic_: . Straubel, J. B. Quoted in Kolodny, L. (2019, July 27). JB Straubel wasn't just Tesla's CTO -- he invented the carmaker's core technologies. _CNBC_. . Wasserman, N. (2012). _The Founder's Dilemmas: Anticipating and Avoiding the Pitfalls That Can Sink a Startup_. Princeton University Press. Study of \~10,000 founders across \~3,600 startups. 52% of founders replaced by third financing round; 73% of replacements involuntary. See also HBS Working Knowledge: . Chalmers, A. ("The Geek Whisperer"). Most founding CTOs are fired or moved sideways within 3--5 years. Here's why! _Medium_. . Fernandez-Victorio, G. When the CTO is not management. _HackerNoon_. . Barstow, S. (2017, March). Firing your CTO. _scottbarstow.com_. . Delaware General Corporation Law §142 (officer removal by board, with or without cause) and §141(k) (director removal by shareholder vote). See also Morse Law: -- Morrison & Foerster ScaleUp: . Adelson, R. A. (2019). Negotiating your new CSO or CTO employment agreement. _CEOWORLD Magazine_. -- See also Cooley GO on acceleration triggers: . Hays, K. Ask an investor: How do I fire my co-founder? _BetaKit_. . Filippenko, Y. I was fired from my own startup. Here's what every founder should know about letting go. _Crunchbase News_. . Cohen, J. Startup identity and the sadness of a successful exit. _A Smart Bear_. . Seibert, J. One founder, both sides of the M&A table. _First Round Review_. -- Twitter evaluated 50+ startups; \~1 in 17 conversations resulted in a completed deal. . Axial. Streamlining the M&A funnel. -- Typical PE firm: 150 management meetings/year, 5--10 closed deals, 3--7% conversion. . Surfside Capital Advisors. (2025). What happens after you accept a LOI? -- 10--25% of deals fail to close after LOI. . Dykes, K. 8 lessons from 5 failed acquisitions in 1 startup. . Malikkides, O. (2024, July 26). Inside tech due diligence: Lessons from a startup acquisition. _Medium_. -- Firsthand CTO account; Labstep was acquired \~2024\. . Doubrovkine, D. (2017, October 29). How to do startup technical due diligence. _code.dblock.org_. -- Doubrovkine has conducted due diligence for both VC and acquirer evaluations. . Gil, E. (2018). M&A: Negotiate the acquisition. In _High Growth Handbook_. Stripe Press. -- "$1--3M per engineer, up to $5M for exceptional talent." . Larson, W. (2020, January 2). How to navigate and/or survive your acquihire. _Irrational Exuberance_ (lethain.com). -- Written from experience at the Digg acqui-hire; also covers the SocialCode acqui-hire at Washington Post. . French-Owen, C. (2020, November 11). A new adventure. _calv.info_. -- French-Owen left Segment the day the Twilio acquisition closed ($3.2B, November 2020). . Wagner, K., & Molla, R. (2018, September 24). Instagram's co-founders are leaving amid frustrations with parent company Facebook. _Recode (Vox Media)_. -- Krieger served as CTO/VP Engineering at Instagram from 2010 to 2018\. . Debow, D. (interviewed by First Round Review). How to sell your startup: The complete guide to running an M&A process as a founder. _First Round Review_. -- Debow has been through three acquisitions, including Salesforce. . Goldbart, S. & DiFuria, J. Money, Meaning & Choices Institute (MMCI). Coined "sudden wealth syndrome" in the 1990s. Not a formal DSM-5 diagnosis. See also CAPTRUST: -- Susan Bradley, Sudden Money Institute: . Persson, M. (@notch). Twitter thread, 29 August 2015\. Reported in GameSpot: -- CNN Money: . NAPFA (National Association of Personal Financial Advisors). -- Fee-only advisers accept no commissions and are fiduciaries. Darrow Wealth Management: -- Secfi: . IRC §1202 (QSBS). Wilson Sonsini guide: -- California non-conformity: -- Cross-reference Appendix C for AMT and exercise mechanics. . Lyon, M. (2015, August). Regretting the golden handcuffs. . Haatch (UK VC firm, four exited founders). Life after a major business exit. -- See also Startups.com: . Ghosh, S. Harvard Business School. Study of 2,000+ VC-backed companies that raised at least $1M (2004--2010). 75% never returned cash to investors; 30--40% liquidated completely. Cited in _Wall Street Journal_ (2012, September 19): "The venture capital secret: 3 out of 4 start-ups fail." . Walker, P. / Carta. (2025). Class of 2018 analysis: 62% shut down, 15% reached Series B, \~1.3% achieved unicorn status. . Carta. (2024). Startup shutdowns are accelerating. 966 U.S. shutdowns in 2024, +25% YoY; Series B shutdowns +133% YoY. . CB Insights. (2025). Why startups fail: Top reasons. 431 shut-down VC-backed startups since 2023; $17.5B destroyed equity. Nearly 25% were "walking dead" -- 3+ years since last fundraise. . Aoun, A. (2024, November). Interview on _More or Less from the Morins and the Lessins_, The Information. -- Recorded days after Forward's shutdown; includes 150 phone calls detail, "go cold plan" via Munjal Shah (Hippocratic AI), and Dave Morin's "landing the plane" formulation. Forward raised \~$400M over eight years. . Price, R., & Torrence, R. (2024, November 22). Forward's leaders are already recruiting for a new startup, just a week after the healthcare company shut down. _Business Insider_. . Mathewes, F. (2024, November 20). Patients scramble to retrieve records after startup abruptly closes. _CBS News / Becker's ASC_. -- Illinois requires 30-day closure notice for healthcare providers. . SimpleClosure. (2024). What happens to intellectual property when a company shuts down. _SimpleClosure Blog_. -- "These assets cannot be distributed informally during a shutdown." See also: Pedraza, J. (2025, January 28). Managed wind-down vs ABC vs bankruptcy guide. _SimpleClosure Blog_. . Smith, A. (2022, November). Kite post-mortem and open-source announcement. _kite.com_ (archived). Covered in: Brinker, A. (2022, November 21). Kite AI coding pulled down to earth because our 500K developers would not pay to use it -- now open source. _DevClass_. . Kan, J. (2020). The story of Atrium. _The Quest with Justin Kan (Substack)_. -- Atrium raised $75.5M; shut down March 2020\. Kan previously co-founded Twitch (acquired by Amazon, \~$1B). . Gompers, P., Kovner, A., Lerner, J., & Scharfstein, D. (2010). Performance persistence in entrepreneurship. _Journal of Financial Economics_, 96, 18--32\. NBER Working Paper No. 12592\. -- Previously successful founders: 30% next-venture success rate; first-time founders: 21%; previously failed founders: 22%. . Durkin, N. (2014, June). My startup failed, and this is what it feels like. _Medium_. -- Durkin founded 99dresses; the post has been widely cited as one of the most honest founder failure accounts. . Routledge, J. (2025, February 17). #266: Founder startup grief. _James Routledge Substack_. -- "In a way, grieving a startup that fails is easier than grieving a startup that is sold because it's black and white." . Konrad, A. (2026, February 25). Profile: Meet Column, the most important fintech startup you've never heard of. _Upstarts Media_. -- \~$200M annual revenue, \~110 employees, free cash flow positive at >$100M, entirely bootstrapped. . Majors, C. (2017, May 11; updated 2023, July 14). The engineer/manager pendulum. _charity.wtf_. . Schroepfer, M. Quoted in Rodriguez, S. (2023, May 2). Former Facebook CTO Mike Schroepfer launches climate investment firm. _CNBC_. . Turnbull, J. Interviewed in "How the former CTO of Kickstarter finds meaning in leading." _Shortcut Blog_. . Lee, D. (2012, August 18). Quick thoughts on acquihires/"soft landings." _daslee.me_. -- Lee is a partner at SV Angel; the Ron Conway quote is: "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."