Your CTO Just Left. Here's the Triage Sequence for the Next 30 Days.

The CTO departure is rarely just a people problem. It's an information problem. The departing CTO carried knowledge about why the system is built the way it is, which parts are fragile, which technical decisions are reversible, and which aren't.

The First 72 Hours

• Document the known fragility points. Ask directly: "What are the three things most likely to break in the next 90 days?"
• Get access to everything. Every repository, cloud account, and third-party service. You should not need the CTO's personal credentials for anything.
• Identify the informal technical leaders. Who did engineers actually go to for guidance? That person is your stabilizer.
• Freeze major technical decisions. Architecture choices, cloud migrations, and new framework adoptions wait 30 days without explicit review.

The First 30 Days

Week 1 — Stabilize.

• Rotate credentials the CTO had access to.
• Identify all systems that require active management: cron jobs, renewal dates, alert thresholds.
• Brief the team: acknowledge the departure, name an interim technical decision-maker.

Week 2 — Audit.

• Map the current architecture, even as a rough diagram.
• Identify ongoing technical commitments: vendor contracts, migration projects, debt programs.
• Assess the team's technical depth — who can make which decisions independently?

Week 3–4 — Plan.

• Decide: interim fractional CTO, internal promotion, or full-time hire?
• If interim: brief them comprehensively in Week 1's findings.
• If internal promotion: give them explicit authority and a support structure.
• If full-time hire: start the search and plan for 3–6 months to close.

What Not to Do

• Don't give engineering decisions to the product manager. Product managers optimize for features. CTOs optimize for systems.
• Don't rush to hire. A bad CTO hire is worse than a temporary gap.
• Don't let the departing CTO's architectural decisions become sacred. New context may require different choices.

FAQ

Should I try to hire an interim CTO or promote internally?

It depends on the team's depth. If you have a senior engineer with architecture experience and leadership credibility, promote internally with fractional advisory support. If not, bring in a fractional CTO for 3–6 months while hiring full-time.

How long should the full-time CTO search take?

Budget 3–6 months for a thorough search. Rushing produces a bad hire. A bad CTO hire typically costs $500k–$1M+ to unwind through severance, knowledge loss, architectural reversals, and team attrition.

What should I look for in the next CTO?

At early stage: someone who can write production code and lead hiring. At growth stage: someone who can architect for scale and translate to the board. They are different profiles.