The fractional CTO playbook
What a good fractional CTO actually does in their first 30 days — and three anti-patterns to avoid when hiring one.
Most fractional CTO engagements underwhelm for the same reason: both sides are unclear on what the job is. Here's what it actually should look like in the first thirty days.
Days 1–10: listen
Read the code. Read the runbooks (if any). Talk to every engineer 1:1. Map the product architecture on a whiteboard. Sit in on a sprint planning. Do not change anything yet — you haven't earned the right and you don't have the context.
At day 10, deliver a plain-English written diagnosis to the CEO: what's working, what's not, and what's on fire. No jargon. This document is your contract for the next 20 days.
Days 11–20: fix the one thing on fire
There's always one thing. Prod is going down. The lead engineer is leaving. The AWS bill has doubled. The CEO can't get a straight answer on when something ships. Pick the one that's the biggest risk to the business and go fix it.
Resist the urge to fix everything. A fractional CTO who ships one visible win in the first month is trusted for the next year. One who writes a 40-page strategy doc is fired by month three.
Days 21–30: put the system in place
Now you install the things that'll make the engineering org boring in the best way:
- A weekly written status email from engineering to the exec team.
- A documented on-call rotation and incident response process.
- A simple hiring pipeline with a calibrated interview loop.
- Quarterly planning that ends in commits, not slides.
Three anti-patterns
1. The advisor who doesn't code
If your fractional CTO hasn't opened the repo by day 14, fire them. You're paying for engineering leadership, not a management consultant with a hoodie.
2. The 40-hour-a-month strategist
Fractional CTO is not “one call a week and some Slack.” It's 1–2 days a week of real work, in the codebase and with the team. Price it accordingly.
3. The rebuild artist
“The whole thing needs to be rewritten in Rust” is almost always wrong. Your product is working. Do not let the new hire burn six months rewriting the machine that's currently printing money.
When not to hire one
If you have fewer than three engineers, you don't need a fractional CTO — you need a senior engineer who pairs with you. If you have more than fifteen, you need a full-time CTO. The fractional sweet spot is 4–12 engineers, where engineering is big enough to need structure but small enough that a part-time leader is still plausible.
Got a project like this?
Tell us in one paragraph. A real engineer replies within a day.
Keep reading
What we actually mean by “vibe coding”
It's not vibes instead of rigor. It's vibes plus AI plus senior taste, so the boring 80% of work gets compressed into a morning.
How we ship an MVP in three weeks (and why you should)
A play-by-play of our 21-day MVP process: what we cut, what we keep, and how we keep quality from collapsing.