What a fractional CTO actually does in the first ninety days
· 6 min read · Dhiraj Chatpar
The job is rarely writing code. It is finding the one decision that unlocks the next twelve months.
A fractional CTO engagement usually begins with a company that has already shipped something and has begun to slow down. The product works. Growth is respectable. But every new feature takes longer than the last, and nobody can say precisely why.
The first weeks are diagnostic. Read the architecture, read the deployment history, watch how a change travels from idea to production, and ask the people involved why they route around the process in the places they do. The workarounds identify the real constraints faster than any diagram.
Invariably there is one decision that has gone unmade. A data model that should have split. A service that should own state it currently borrows. A deployment that should stop being manual. The reason it went unmade is almost never technical ignorance and almost always that nobody owned it, because everyone could see that addressing it meant pausing visible delivery.
The fractional role is often useful precisely because it sits outside the reporting line. A full-time leader defers that decision for political reasons that are perfectly rational. Someone with a defined engagement and no stake in next quarter can name the cost out loud and get agreement to pay it.
By ninety days the useful outcome is not a rewrite. It is a clear technical position, one architectural decision reversed, a delivery path that no longer depends on a single person, and a written explanation that survives after the engagement ends.