Fractional CTO, advisor or full-time CTO?

These options are often presented as three prices for the same service. They are not. Someone who reviews a decision, someone who helps own the decisions over time and someone who leads a technology organisation every day have different jobs. Choosing on day rate alone misses the more important distinction.

An advisor helps you examine a question

Advice fits a bounded need: reviewing a system, assessing a supplier proposal or deciding whether an idea needs custom software. You bring the context, the advisor investigates and explains the options, and your organisation owns what happens next. That can be exactly enough.

The boundary should be visible. A good audit does not quietly become a promise to manage implementation forever. If the recommendations are clear and your team can act on them, you may not need an ongoing leadership arrangement.

A fractional CTO stays with an agreed responsibility

This fits when important technical decisions recur and the company needs continuity, but not a full-time leadership position. The involvement can connect management, developers and suppliers, keep the technical roadmap coherent and follow the choices through to delivery.

Part-time only works when the agreement is realistic. Define availability, the decisions the person can make and the work that remains with your team. There must be a way to handle urgent issues between the agreed working periods. A small allocation cannot provide continuous presence by implication.

A full-time CTO carries a different organisational load

When daily leadership, recruitment, multiple teams, budget responsibility and organisational change need sustained attention, a full-time role may be the right answer. This is not a failure of the fractional model. It means the work has grown into a different job.

An external technical leader can help you define that position and prepare a handover. The organisation should own its decisions, documentation and relationships. Transition becomes harder if those have accumulated in a consultant's private inbox.

Ask these questions before choosing

• Is the need one decision, a recurring set of decisions or a daily leadership function?
• Who will implement and support what is decided?
• How much continuity and availability does the team actually need?
• Which responsibilities must stay inside the company?
• When will we review whether the arrangement still fits?

You may need development capacity instead

If the direction is clear and the real problem is a lack of people to implement it, another leadership layer may slow things down. Scope the implementation work rather than buying a title to solve a capacity gap. The useful arrangement is the one that addresses the missing responsibility, not the most impressive label.

Our advisory service and fractional CTO support describe those different starting points. Levi's professional profile sets out the experience behind the work.