The timing

When to hire a fractional CIO

Almost nobody arrives at this on a plan. It is triggered, and the trigger usually has a date on it that somebody else set.

The wrong question

It is not a question about size

The question companies ask is whether they are big enough yet. It is the wrong axis. Size correlates loosely with needing technology leadership and predicts almost nothing about when, because the thing that creates the need is not headcount. It is a decision arriving that the current arrangement cannot make well.

A sixty-person company midway through an acquisition needs this more than a comfortable three-hundred-person one that is not deciding anything. The first has four directories, two contract sets and a date; the second has a working estate and a quiet year. Headcount says the opposite in both cases.

The more useful test has two parts. Is there a decision coming whose consequences outlast the people making it, and is there somebody accountable for getting it right whose job is not something else. Where the answer is yes and no, in that order, the timing is now, whatever the headcount says.

This is also why it is almost never planned. Nobody budgets for technology leadership in the abstract. They ring somebody in the week after the incident, the resignation or the diligence request, which is later than ideal and still the right call.

The fork

Two ways this usually goes

What usually happens

Wait until it is undeniable

The signals accumulate quietly and none of them is individually urgent, so the decision waits for something loud. By the time it arrives, the deadline belongs to somebody else and the available answers have narrowed to one.

What changes the outcome

Act on the signal, not the crisis

The signals below are all observable and all checkable this week. Acting while there are still several answers available is the whole of the difference, and it costs less than acting when there is one.

The signals

Four places the pressure shows up first

Observable things rather than feelings. Every one of these is checkable in an afternoon, which is the point: a signal you cannot verify is an anxiety.

At board level

The questions arrive before the capability to answer them does.

  • Somebody has asked what technology costs and against what return, and the answer took weeks
  • A board paper on technology risk was requested and nobody was the obvious author
  • An investor, insurer or acquirer has started asking for evidence rather than assurances
  • The technology section of the plan is a list of systems rather than a set of decisions

In the commercials

Money is moving on decisions nobody owns.

  • Renewals arrive and get signed because the alternative is disruption
  • Spend is rising faster than headcount and nobody can explain the gap
  • Licences are bought per team, and nobody holds the total
  • A major contract is up and there is no plan for it beyond renewing

In the risk picture

The exposures are known to somebody and written nowhere.

  • There is no risk register, or there is one and nothing on it has a date
  • An incident happened and the follow-up actions are still open
  • A cyber insurance application asked questions you could not evidence
  • Backups are reported as working and have not been restored from in living memory

In the people

The knowledge is in a person rather than in the company.

  • One person is the only one who knows how something critical works
  • The IT lead has resigned, or you suspect they are about to
  • A capable operator has been given a strategy title and no mandate
  • Decisions wait for a person who is already fully committed to delivery
The cost of waiting

What deferring actually buys you

Consequences rather than percentages. Every one of these is something a reader can check against their own last two years.

The decision gets made anyway

This is the part people miss. Waiting does not defer the decision, it delegates it, usually to whoever raised the topic or whoever is selling something. A default is still a choice, it is just one nobody reviewed.

Options close in a fixed order

Early in a renewal cycle you can negotiate, run a selection or walk. Six weeks out you can renew. The set of available answers shrinks on a schedule that has nothing to do with when you get round to it.

The cost stops being visible

Unused licences, overlapping tools and an overrunning project do not appear as a line item called waste. They appear as a slightly higher number every year, which is exactly the shape that never triggers a review.

The evidence gets harder to assemble

Every month of undocumented change makes the eventual audit, diligence or insurance application longer and more expensive, and those deadlines are set by other people.

Both answers

Now, and not yet

It is time when

  • A decision is coming that is bigger than any the current setup has made
  • Somebody at board level has started asking questions nobody can answer
  • The IT lead is leaving, or has already left
  • An acquisition, an audit, a renewal or an insurance application has a date on it
  • You are being asked to sign something you cannot evaluate
  • An incident has happened and you do not want the next one to look the same

It is not yet when

  • Nothing is deciding: no renewal, no incident, no plan that technology has to serve
  • There is no internal owner at all, so advice would have nobody to land with. Fix execution first
  • You need hands rather than direction. Engineers or a managed service is the honest answer
  • A capable technology executive is already in the seat and performing
  • The company is small enough that the estate is the strategy, and you are the one running it
Your case

If one of these is what is happening

Each of these has its own page: what is actually going on underneath it, what to do in what order, and what you should end up holding.

Questions

What people ask about timing

How big do we need to be?

Size is the weakest predictor of the four. The band where this usually fits is roughly 50 to 500 people, or $10m to $250m in revenue, but the useful question is not headcount. It is whether a decision is coming that the current arrangement cannot make well. A 60-person company midway through an acquisition needs this more than a comfortable 300-person one does.

Is it too late if the thing has already happened?

No, and this is the most common way these engagements start. Almost nobody hires ahead of the trigger; they hire in the week after the incident, the resignation or the diligence request. Later is more expensive because options have closed, but the work is the same work and the first ninety days do not change.

Should we wait until after the current project finishes?

Usually the opposite. An in-flight project is one of the clearer cases for bringing somebody in, because a project that is drifting rarely corrects itself and the cost of that drift is being paid weekly. Waiting until it finishes means paying the full price of whatever went wrong and then reviewing it.

What if we are not sure it is the right time?

Then it is worth a conversation rather than a proposal. Whether the timing is right is exactly the sort of thing an intro call settles quickly, and a firm that cannot tell you honestly that it is too early is telling you something about how they sell.

Not sure whether it is time?

That is a thirty-minute conversation rather than a proposal. If the answer is not yet, we will say so.