A CIO seat at the table. For the months you actually need one.

Some companies need a CIO every Tuesday. Others need one for nine months while they integrate an acquisition, hire a permanent successor, or steer through a crisis. We're built for the second case.

Three patterns. If yours doesn't fit, the intake is free.

Pattern 01

The successor gap

Your CIO has left, retired, or moved on. Recruiting the replacement well takes 4 to 9 months. The business can't wait that long for IT to make decisions.

Pattern 02

The integration mandate

An acquisition, carve-out, or joint venture is mid-flight. The receiving IT organisation needs senior weight to absorb it without disrupting run-the-business work.

Pattern 03

The reset

IT has lost executive credibility. Costs are unclear, projects slipping, audit findings open. Someone needs to come in, say what's going on, and lay out a 90-day plan.

A working CIO. In the org chart. Operating from week one.

Three things it isn't: a project manager, an architect, or a senior advisor on retainer. What it is: accountable to the CEO and board, with full authority to make calls within agreed thresholds.

From a recent executive reference

"Builds stable teams and leadership structures that scale beyond interim mandates."

Day-rate engagement. Fixed minimum runway. Defined exit gate. No 30-day "discovery" before the work starts. Discovery happens while we're already running the function.

Four phases. Six to twelve months.

Phase 01 · Days 1–14

Stabilise and read the room

Take the seat. Meet the team, executive peers, top-three vendors, open audit findings. Decide what's on fire and what's just smoking.

Phase 02 · Days 15–45

The 90-day plan

One document the CEO and board can approve. Three to five priorities, budget transparency, and the org changes needed to hit them.

Phase 03 · Days 46–end

Run, deliver, leave a stronger team

Operate the function. Deliver priorities. Reorganise where needed. Develop succession candidates internally. Hire the permanent CIO if asked.

Phase 04 · Last 30 days

Handover

To the permanent successor, internal or external. Documented operating model, vendor contracts, open risks, and a frank conversation about what they're walking into.

Six artefacts a typical mandate leaves behind.

The 90-day plan

Board-approved, budgeted, with named owners.

Cost transparency pack

IT OPEX/CAPEX, vendor consolidation opportunities, contract calendar.

Risk and security position

Open findings, remediation plan, security maturity uplift.

Operating model

Org structure, RACI, escalation paths, ITSM/ITOM discipline.

Talent and succession map

Who's ready, who needs development, who needs replacing.

Handover pack

For your permanent CIO. A working binder, not a deck.

Five things buyers ask before the call.

What's the typical mandate length?

Six to twelve months. Anything shorter risks turning into "advisory" without operational accountability. Anything longer, and you should be hiring the permanent CIO, not extending us.

How many days per week?

Three to five, depending on the situation and the size of the IT function. Crisis or integration mandates start at five and taper. Successor-gap mandates often run at four. The team has to know we're there.

Will you compete to become the permanent CIO?

No. We don't take permanent roles with clients. It biases the work. The agreement is for an interim mandate with a clean exit.

What about confidentiality during M&A or carve-outs?

Standard NDA, plus the operating discipline of a CIO who's done IT due diligence on multiple acquisitions. We're used to working in shareholder-driven and PE-style governance models where information control is a real constraint.

What does it cost?

Day rate, fixed for the duration. We share it after the intake. The day rate is irrelevant if the mandate isn't right for us. That's the conversation we want to have first.

Where to from here

30 minutes to test fit. Bring the situation.

Leave knowing whether an interim CIO is the right answer, or whether something cheaper is.