Some organisations have capable technical people and responsive suppliers, but nobody senior is responsible for the decisions between them. Priorities compete. Costs accumulate. Projects move without settling ownership of the systems and risks they create.
I provide fractional or virtual CIO and CTO services to organisations that need executive technology direction, but not necessarily a permanent full-time technology executive. The role can be ongoing and part-time, or defined for a transition. What matters is that the mandate specifies what I lead, who decides, how we work and what success will look like.
This is client-side leadership, working with the organisation's own people and with the specialists who deliver.
Strategy, budgets, suppliers, operational resilience, information governance, security risk, technology people and board reporting. The CIO question is whether technology supports the organisation's actual responsibilities and can be run, changed and recovered with confidence.
Architecture, platform choices, engineering priorities, technical debt, data and AI, build-versus-buy, technical team and delivery oversight. The CTO question is whether what is being built can perform, evolve and justify its cost.
Some assignments need both perspectives. The first conversation establishes which decisions actually need ownership rather than handing the client two job titles.
Understand systems, contracts, costs, people, information flows, operational dependencies and the decisions already in motion.
Agree a manageable technology agenda, with the few choices that matter, their consequences and owners.
Take part in defined leadership meetings, challenge decisions, maintain the record of risks and decisions, and report clearly to the responsible principal, board or executive.
Set expectations, evaluate proposals, monitor what matters, address dependencies and escalate when work is not producing the expected result.
Protect access to records, documentation, knowledge, recovery and the ability to change providers or leadership without starting over.
Before accepting a continuing role, we agree what sits inside it: CIO or CTO scope, reporting line, decision and approval authority, time allocation, remote and on-site expectations, access to systems and people, named delivery owners, confidentiality arrangements, exclusions, review points and handover. Where legal, regulatory or professional approvals belong elsewhere, they stay there.
The practical output may include a technology roadmap, budget and supplier decisions, an executive risk view, an architecture direction, a programme recovery plan or a regular board briefing. It is not a stack of reports for their own sake; those are the tools of sustained leadership.
| Arrangement | Typically means | A good question to ask |
|---|---|---|
| Fractional | Ongoing, part-time executive responsibility | Which decisions will you own, and how often will we work together? |
| Virtual | Technology leadership delivered substantially remotely | What leadership scope and actual availability sit behind the word? |
| Interim | Time-bounded executive responsibility during a gap or change | What must be stable or handed over at the end? |
| Permanent executive | Full-time leadership inside the organisation | Is the workload and continuity need sufficient to justify a permanent appointment? |
I am not a managed IT provider, a general-purpose software development agency or a standing full-time IT department. A fractional executive works with those providers, including a client's existing people and vendors, without duplicating their jobs. Where the work genuinely needs full-time attention, I will say so.
I have held formal CIO responsibility and earlier led information security and IT risk, DevOps, data and technology operations. My experience also includes product and platform direction. That range matters when the organisation's real problem spans several functions and no single supplier sees all of it.
Often the words overlap. “Virtual” describes where much of the work is done; “fractional” is more useful for describing continuing part-time executive responsibility. The mandate needs to spell out actual access, cadence, authority and accountability either way.
Yes. The purpose is to provide client-side direction, evaluate trade-offs and give the people delivering technology clearer priorities. It is not to displace a useful operational team.
A time-bounded leadership appointment may be possible where the role, required capacity, decision rights and handover are clearly defined. This is assessed individually; availability is not promised on the website.
I can direct technology and product priorities, set technical expectations, oversee delivery and work alongside specialist implementers. Building an application, providing managed operations or supplying developers would require a separate, appropriate delivery arrangement.
Start with the business situation, not a system inventory. The initial discussion determines whether the need is a bounded review, ongoing executive leadership, an interim appointment or something that should remain with the existing team. Sensitive documents should only be shared after a suitable scope and information channel have been agreed.
When judgement needs to become direction.
Describe the type of organisation, the leadership gap and approximate timing. Do not send client or family records in the initial message.