What does a fractional CTO actually do week to week?
You are considering a fractional CTO but every description of the role is abstract, so it is impossible to tell what you would actually be buying or how to judge it.
A working fractional CTO engagement is roughly one to three days a week split across four things: decision support at the moments decisions land, technical review of what the team is shipping, vendor and agency accountability, and hiring — writing specs, screening candidates technically, and sitting in interviews. What it is not is a monthly strategy call. If the arrangement produces advice but no artefacts, you have bought an advisor rather than technical leadership.
The artefacts are how you tell the difference, and they are worth naming in the contract: an architecture decision record for choices that are expensive to reverse, a written hiring bar and scorecard, a risk register that gets updated, and review notes on what shipped. Ask a prospective fractional CTO what they will leave behind that outlasts the engagement. A good answer is specific and short. A vague one predicts a relationship that feels productive in the meeting and changes nothing between them.
Why the role is so often misunderstood
- The category is mostly sold abstractly. 'Strategic technical leadership' describes an outcome, not a week, so buyers cannot compare offers.
- Advisory and operating models are conflated. Advice-only and hands-on are different products at similar prices, and the difference only becomes obvious in month three.
- Availability matters more than hours. A fractional CTO unreachable when a decision lands is not providing the service, whatever the day count says.
What to expect in the first ninety days
-
01
Ask any candidate to describe last week on an existing engagement, concretely. Vagueness here is diagnostic.
-
02
Establish whether they will read code. If they will not, you are buying advice — legitimate, but price and expect it accordingly.
-
03
Agree the artefacts up front: documented architecture decisions, a technical roadmap, a hiring spec. Artefacts are what survive the engagement.
-
04
Define availability, not just days. 'Reachable within four hours on weekdays' is a more useful commitment than 'two days a week'.
-
05
Write the exit condition at the start — the point at which you outgrow the arrangement.
The handover, and almost nobody plans for it. A fractional CTO who has not documented architecture decisions and their rationale leaves you re-learning your own system at exactly the moment you are onboarding an expensive full-time hire — who then re-litigates settled questions while everyone waits. We treat the documented technical estate as a deliverable rather than a by-product, specifically because the engagement is designed to end.
More on the fractional CTO role
Typically one to three days depending on tier. Availability at decision points matters more than the total: a fractional CTO who cannot be reached when a decision lands is not providing the service.
Usually they work with the team rather than above it, unless you specifically want line management. Introducing the role as oversight rather than support is the most common way these engagements start badly.
A documented technical estate, architecture decisions with their rationale written down, a roadmap tied to business milestones, and either a hiring spec or a vendor being held to account. If none of those exist, the engagement is not working.
More on Fractional CTO Services
Still not sure this is your problem?
A 20-minute fit check. We will tell you if it is something you can fix without us — that happens often enough that we lead with it.
Book a Strategy Session →Browse every answer.
The full Solution Desk — specific questions, straight answers, no gate.
Open the Solution Desk →