CTO · VP Engineering · Head of Engineering
New CTO: Your First 90 Days in an Inherited Org
Ninety days is what you get. Not because a book says so, but because that's roughly when a CEO stops hearing still mapping the org as diligence and starts hearing it as drift. An inherited org makes it harder: the person who knew where everything was buried has left, and the place kept running on habits nobody chose.
The failure mode here isn't moving too slowly. It's spending all ninety days learning and arriving at day 91 with an excellent map and no decisions.

What ninety days really buys you
Thirty intro 1:1s feels like diligence and mostly isn't. After the first eight you're hearing variations, and each further conversation costs a day you don't have. Meanwhile two of your directors are interviewing elsewhere, and neither of them is waiting for you to finish onboarding.
So we run the intake as an investigation with a deadline instead of a listening tour. Stakeholder map, delivery diagnosis, retention risk ranked by who you'd genuinely struggle to replace, and a tech-debt score that puts a cost against the top three items rather than a feeling. Three weeks is usually enough for that, provided you give up on being exhaustive.
Then you commit to two initiatives. Two, because a new CTO who commits to five has told the org that nothing is really the priority. I coach you through defending those two to your CEO, including the part where you name what you're explicitly not doing this quarter, which is the sentence that makes everything else credible.
Day 90: two initiatives with owners, dates and metrics. Retention risks named and, where it was still possible, handled. And nobody on the exec team asking what it is you own on the platform.
Working it 1:1

Weekly through the first ninety days, then bi-weekly once the fires have names. I have sat in the seat: built Mews into a $2bn+ unicorn from 8 to 80 teams, led engineering at Manta before IBM acquired it, and spent 4+ years in the Bay Area as Principal Software Architect at Databricks. The pattern data comes from 3,400+ unique sessions with engineering leaders in 17+ countries. Rated 9.17/10 on average across 300+ reviews.
Pricing is public: 430 EUR per session, 361 EUR per session for ELC members, or 2,580 EUR per quarter (6 sessions over 3 months). The quarter drops to 2,166 EUR if you build the inquiry with my AI the inquiry: under 16 minutes, €361 a session on every package. You only pay for a session you rate 7 out of 10 or higher. Full pricing.
Related reads
The other situations CTOs bring
- The board wants a delivery number →
- Technical due diligence before a raise →
- AI adoption pressure from the board →
- Every decision routes through you →
- A sounding board without politics →
All six, plus the questions CTOs ask most: CTO coaching & mentoring