The First 90 Days With a Fractional CTO or CIO

A fractional CTO or CIO engagement doesn't start with a strategy document. It starts with finding out what's actually true: what's being spent, what's at risk, and what's been quietly assumed for years without anyone checking. The first 90 days follow a fairly predictable shape, and knowing that shape in advance stops organisations from judging the engagement by the wrong milestone.

Most of the anxiety around a new engagement comes from not knowing what "normal" looks like. Here is what actually happens, roughly in order.

Weeks one to three: getting visibility

The first stretch is discovery, and it's less exciting than it sounds. It means sitting down with every vendor contract, every licence, every system that touches money or risk, and building an honest picture of what's actually in place, not what the org chart or the last handover document says. Most organisations are surprised by how much of this picture didn't exist anywhere in one place before. A Technology Executive Diagnostic is often the formal version of exactly this step, run before a longer engagement even begins.

This phase produces no visible wins yet, and that's normal. It's the foundation everything else in the 90 days sits on.

Weeks three to six: the first real decisions

Once the picture is clear, the first concrete moves happen: a contract renewal gets paused rather than auto-renewed, a glaring security gap gets flagged and closed, a vendor relationship gets challenged for the first time in years. These aren't dramatic transformations. They're the obvious things that nobody had the seniority, time or mandate to act on before.

The first wins are rarely new ideas. They're old problems finally getting someone's attention.

Weeks six to ten: the roadmap takes shape

With the picture clear and the obvious fires addressed, the engagement shifts to sequencing: what should actually happen over the next twelve to eighteen months, and in what order. This is where a Technology Strategy & Transformation engagement earns its keep, turning a list of problems into a roadmap the leadership team can actually follow and the board can actually see.

This is also usually the first point where the organisation starts to feel the difference between having a technology function and having technology leadership.

Weeks ten to thirteen: settling into rhythm

By the end of the first quarter, the engagement should have found its ongoing shape: a regular cadence of check-ins, clear reporting lines, and a working relationship where the fractional executive is trusted to make calls rather than constantly re-explaining first principles. If that rhythm hasn't formed by around 90 days, it's worth a direct conversation about why, rather than assuming it will resolve on its own.

What good looks like at the 90-day mark

Three things, realistically: a genuinely accurate picture of the technology estate that didn't exist before, at least one or two concrete decisions already acted on, and a roadmap the leadership team has seen and agreed to. Anything beyond that in the first quarter is a bonus, not the baseline to expect.

The mistake to avoid

The most common misstep is judging the engagement on activity in week two rather than outcomes at week thirteen. A Fractional Technology Executive engagement that looks quiet in the first month is usually doing exactly what it should: getting the picture right before making changes that are hard to reverse. Organisations that push for visible wins before the discovery work is done tend to end up reacting to symptoms instead of fixing the actual problem.

The bottom line

Ninety days isn't long enough to transform a technology function, and it isn't meant to be. It's long enough to know exactly what's really going on, fix the obvious things, and have a roadmap everyone actually agrees with. Everything after that builds on what those first thirteen weeks got right.

Frequently asked questions