What a fractional CTO does in the first 90 days

Hiring senior technology leadership part-time is a sound idea that is easy to execute badly. The failure mode is diffusion rather than incompetence. A capable person arrives, is interested in everything, produces a thoughtful strategy document, and leaves behind no change in how decisions get made.

A good first 90 days is narrower and considerably more boring than that.

Days 1–14: find out what is actually true

Not what the org chart says, or what the last consultant reported. The specific artefacts worth having before offering a single opinion:

• A systems inventory. Every application and service in use, who owns it, what data it holds, and what it costs monthly. This list is almost always longer than the leadership team expects.
• An access map. Who (including suppliers, contractors and former staff) can reach what. The gap between the intended answer and the real one is usually the most urgent finding of the whole engagement.
• The spend register. Total software and services cost, with renewal dates and notice periods. Frequently the first item that pays for the engagement outright.
• The dependency list. Which single points of failure are systems, and which are people. The second category is the one nobody has written down.

Alongside this, talk to the people doing the work rather than only their managers. Ask what breaks weekly, what they work around, and what they have stopped raising because nothing happened last time. That last question is the most informative one available.

Days 15–30: fix the embarrassing things immediately

Every estate has three or four items that are indefensible once written down: an admin account belonging to someone who left, backups never test-restored, a production database reachable from the open internet, MFA applied to email but not to the finance system.

These get fixed now, not sequenced into a roadmap. Two reasons. They are genuine risk, carried for no benefit. And a fractional leader who delivers visible improvement in month one earns the standing to make harder arguments in month three. Credibility is a resource and this is how you acquire it.

Days 30–60: make the trade-offs explicit

Now the strategy work becomes possible, because it can be grounded in the inventory rather than in ambition. The output should be uncomfortable to read, a plan that offends nobody has not made any choices.

• What gets built, bought, replaced or retired, in what order, at what cost.
• Which technical debt is being paid down and which is being carried deliberately, with the reason recorded.
• Which risks are accepted, by name, at what level of the business.
• What the business will not do this year, and what that buys.

That last item is the one clients remember. Most technology roadmaps fail because they are additive: everything is a priority and nothing is sequenced. A useful plan names what is being given up.

Days 60–90: change how decisions happen

The deliverable of a fractional engagement is not a document. It is a functioning decision process that survives the adviser being away for a fortnight. In practice:

1. A monthly technology review with a fixed agenda: progress, spend, risks, and the two or three decisions actually needed this month.
2. A live risk register with named owners and dates, reviewed rather than filed.
3. A supplier gate, no new software or contract signed without a technical review of terms, exit rights and data portability.
4. Board reporting in language a non-technical director can challenge, so technology stops being a line item taken on trust.

What success looks like at day 90

You can answer, without asking anyone: what we run, what it costs, who can reach it, what our biggest technology risk is, and what we are doing about it this quarter. Those five answers are the whole point.

And how to tell it is going wrong

• Month two and there is still no systems or spend inventory.
• Every recommendation is a purchase.
• The engagement produces documents but no decisions.
• Your team has not changed how they work, only who they copy in.
• The adviser has become a single point of failure, which is precisely the problem you hired them to remove.

A fractional engagement should be structured so that outgrowing it is the expected ending. When the role justifies a permanent hire, the right adviser writes the specification, helps you interview, and hands over a documented estate rather than a set of relationships held in their own head.