What a fractional CTO actually does in the first 90 days

Before anything else, listening

The first thing that happens, before any decisions get made or any changes suggested, is a lot of listening. That means conversations with you, obviously, but also with whoever’s currently doing the technical work, whoever’s closest to customers, and often whoever’s been quietly frustrated about something for months without a clear way to raise it. Most businesses already know, roughly, where their problems are. The first job is finding that out honestly, rather than arriving with a fixed plan and trying to make the business fit it.

Alongside the conversations, there’s usually a proper look at the actual technology: the codebase, the infrastructure, how deployments happen, what documentation exists (and what clearly doesn’t), and how decisions have historically got made. This part is unglamorous but essential. You can’t fix what you haven’t actually looked at.

The first few weeks: an honest picture, not a strategy deck

By roughly the two to three week mark, the aim is to have a genuinely honest picture of where things stand: what’s working better than the business gives itself credit for, what’s genuinely fragile, and where the real risk sits. This gets shared plainly, in terms that make sense to you, not buried in technical language or padded out into an eighty-slide deck nobody will read past page four. If something’s broken, that gets said clearly. If something’s actually fine and doesn’t need touching yet, that gets said too, because part of the job is protecting the team’s time from unnecessary change as much as it is driving change that matters.

This is also usually when the first small, visible improvements start happening. Not because rushing is the goal, but because a team that’s been struggling quietly benefits from seeing that something has actually shifted, rather than waiting three months for a grand unveiling.

The middle stretch: building trust with the team

A fractional CTO who only talks to the business owner and never properly engages with the engineering team isn’t doing the job. Through the middle of the first ninety days, a lot of the real work happens in the day-to-day: sitting in on planning, reviewing how work gets prioritised, coaching more junior developers, and generally becoming a working part of how the team operates rather than an outside observer checking in occasionally. Trust with the existing team matters as much as trust with the business owner, arguably more, because the team is who has to keep building after the engagement settles into its normal rhythm.

This is often where the more structural problems get tackled: the single point of failure who holds too much undocumented knowledge, the process that relies entirely on informal chat, the parts of the system everyone’s quietly been avoiding.

By day ninety: a working rhythm, not a finished job

Ninety days isn’t long enough to fix everything, and it was never meant to be. What should exist by that point is a working rhythm: clear priorities, a team that knows who to go to and trusts that person, a business owner who has a genuinely accurate picture of technical risk instead of a vague unease about it, and a visible reduction in whatever specific problem prompted the engagement in the first place.

What it shouldn’t look like is a large binder of recommendations nobody has time to implement. The value of doing this on a fractional, embedded basis rather than as a one-off consulting project is that the person making the recommendations is also the person accountable for acting on them, alongside the team, week after week.

By this point, most businesses have a fairly clear sense of whether the arrangement is working, not from a report, but from how different the day-to-day already feels compared to ninety days earlier.

What changes after day ninety

The engagement doesn’t end there, it settles. The intensity of the first three months, all that listening, assessing, and untangling, gives way to something steadier: regular time on the calendar, ongoing input on decisions as they come up, and a working relationship where the business owner isn’t relying on guesswork anymore. Some businesses scale the arrangement down once the initial work is done and only the odd big decision needs senior input. Others find there’s enough ongoing work, new hires to guide, a bigger platform change to plan, that the arrangement continues much as it started. Either is a reasonable outcome. What matters is that by day ninety, that decision is being made from a position of clarity rather than crisis.