Engagements
Mandates come in three sizes, set by scope and duration rather than by package. The hours below are indicative, and the final scope is agreed in writing before work starts.
How every engagement runs
Interviews
With the people closest to the question: management, operations, finance, IT and, when useful, your vendors.
Working sessions
To test findings with your team and make decisions as we go, not at a final presentation.
Written deliverables
Your team keeps them and can use them without us.
Focused diagnostic
4-6 weeks
Who it fits. A company with one clear question: framing a system decision, finding a starting point for AI or taking stock of a project that's slipping.
What is delivered
- A current-state assessment focused on that question
- Findings and prioritized recommendations
- A list of quick wins to start right away
How it runs. A kickoff, a round of targeted interviews, then working sessions to test the findings and settle the recommendations.
How to start. A 30-minute call, then a written scope proposal.
Diagnostic and roadmap
8-12 weeks
Who it fits. A company that wants a full view of its technology and a plan it can act on.
What is delivered
- A digital-maturity diagnostic across the company
- Priorities ranked by impact, feasibility and expected return
- A roadmap sequenced around quick wins, with owners and decision points
- An explicit "not now" list
How it runs. Interviews across the relevant functions, a synthesis, then working sessions with management to settle priorities and confirm the roadmap.
How to start. A 30-minute call, then a written scope proposal.
Extended program
3-6 months
Who it fits. A company ready to move from plan to execution: an end-to-end system selection, AI preparation and delivery or a roadmap followed by the start of implementation.
What is delivered
- The diagnostic and roadmap deliverables, as needed
- The selection, delivery or implementation support set out in the scope
- A steering committee and go/no-go checkpoints at major stages
- A documented handover to your team
How it runs. Tight scoping up front, then a steady rhythm of working sessions and steering meetings with your team and vendors.
How to start. A 30-minute call, then a written scope proposal, which can be split into phases.
Fractional CIO
An ongoing role rather than a fixed-length mandate: a set number of days per month and a meeting rhythm agreed together, adjusted as your needs change.
What it isn't. Not a helpdesk or managed IT service. We direct your IT staff or service provider; we don't replace them.
Typical rhythms. Range from a monthly management meeting with advice in between, to a set day or two every week for companies in the middle of a major project. The rhythm is agreed in writing and adjusted as your needs change.
How it runs. It starts with an onboarding period: a review of current projects, contracts and technology spend, and a short list of decisions to make now. It then settles into an agreed rhythm with management, run remotely by default, with access between meetings and on-site presence planned for key moments. What the fractional CIO decides, and what stays with management, is agreed in writing at the start. The arrangement is reviewed every quarter.
How to start. A 30-minute call to see whether the model fits your company.
Let's talk about your situation
In 30 minutes, we'll work out which engagement size fits.