"my CTO just quit what should I do"

"Don't hire fast. Do a knowledge transfer inventory immediately, identify who's the de facto technical lead on each active workstream, and stabilize operations before making any permanent decisions. You have more time than you think — and less time than you want to waste on the wrong replacement."

Your CTO Just Quit. Here's What to Do in the Next 30 Days.

You found out this morning. Or maybe yesterday. The CTO sent the email, had the call, and is gone — or leaving in two weeks. Your stomach dropped.

Here’s what I want you to hear first: this is survivable. I’ve walked into this situation more than once. At companies far more technically complex than yours. The immediate crisis is almost never as bad as it feels at 7am when you’re reading that resignation.

What you do in the next 30 days determines whether this is a bump or a catastrophe.

Days 1–3: Stop. Don’t Hire Yet.

The worst thing you can do right now is start calling recruiters. I know the instinct. There’s a hole, you want to fill it. Resist it.

A rushed CTO hire is one of the most expensive mistakes a company can make. You’ll optimize for “available now” instead of “right for this stage.” You’ll skip the evaluation that exposes whether a candidate can actually do the job or just interview well. You’ll bring in someone who inherits a mess they don’t understand and spend their first 90 days getting their footing while you’re paying them $250K.

You have time to do this right. Use it.

Days 1–7: Lock Down Knowledge

Your immediate problem isn’t leadership. It’s knowledge. Where does the critical institutional knowledge live, and is it only in your CTO’s head?

Call a meeting — today if possible — and run through these questions:

Who has the credentials to production systems? All of them?
Who knows how the deployment process actually works, step by step?
Are there vendor or partner relationships that ran through the CTO personally?
What’s in flight right now, and who owns each active project?
Are there contracts, renewals, or commitments in the next 60 days that the CTO was managing?

Get written answers. Have your outgoing CTO document anything they can before their last day. If they’re leaving on good terms, most people will do this — it’s in their professional interest to hand off cleanly.

If they’re leaving badly, escalate your urgency on credentials and access control immediately. The last thing you want is a disgruntled ex-CTO with keys to production.

Days 7–14: Identify Your Interim Technical Lead

You already have a de facto technical leader on your team. You just haven’t named them yet.

Look at who the engineers actually go to when they have questions. Who runs the sprint planning without being asked? Who do you trust to make a judgment call on a technical decision at 2pm on a Wednesday?

That person — or those two people — need to know, explicitly, that they are temporarily accountable for technical continuity. Not permanently. Not with the pressure of a title change. Just: “I need you to be my point of contact on technical questions for the next 60 days while we figure out the path forward. I’ll pay you accordingly and protect your time.”

This person doesn’t need to be your next CTO. They just need to keep things stable while you think clearly.

Days 14–30: Assess Before You Act

Before you write a job description, you need to answer a harder question: what do you actually need?

The CTO who just left was solving the problems of the company 12 months ago. Your company is different now. Your stage is different. Your engineering team has changed. Your product roadmap has changed.

A 12-person startup at $2M ARR needs something very different from a 40-person company at $8M ARR. The person who was great in the first phase often struggles in the second — and the reverse is also true.

Spend this time figuring out what gap you’re actually trying to fill:

Do you need someone to manage and grow the engineering team?
Do you need architecture and technical strategy?
Do you need someone who can talk to the board and investors?
Do you need someone to fix a specific technical problem (scaling, security, technical debt)?

Those are different jobs. And hiring for the wrong one will put you back in this situation in 18 months.

What Not to Do

Don’t promote the most senior engineer unless they’ve demonstrated they want to lead people, not just code. Many great engineers make miserable managers, and you’ll lose a great engineer and get a struggling manager.

Don’t hire a consulting firm to fill the gap unless you have a very specific, bounded project. Consulting firms are not engineering leadership.

Don’t panic-share the news with your board before you have a plan. Have a stabilization plan in hand when you make that call. “Our CTO resigned and here’s our 30-day stabilization plan” lands very differently than “our CTO resigned and we’re figuring it out.”

The Case for a Fractional CTO Right Now

If your next hire is going to take 90–120 days — and a good one should — you have a leadership gap in the interim. A fractional CTO can step in immediately, provide technical continuity, help you evaluate the state of what you’ve got, and then help you write the job description and evaluate candidates for the permanent role.

That’s exactly the kind of situation I work with. If you’re in it and want to talk through what the next 30 days should look like specifically for your company, book a 15-minute call and we’ll figure out the right path together.