What Does a Fractional CTO Actually Do? (A Week in the Life)

Most articles about fractional CTOs tell you what the model is. Day rates, retainer versus project, the cost comparison against a full-time hire. Useful if you're costing it up. Useless if what you actually want to know is: what will this person do on a Tuesday?

I've been providing fractional and interim technology leadership to startups in the UK for a while now. The question I get most, from CEOs and from the recruiters sourcing these roles, isn't: “What's a fractional CTO?” It’s: “Can someone really understand our business in one or two days a week?”

Fair question. So instead of defining the role again, let me walk you through a week.

This is a composite of a typical week across a few scale-up clients. The details are changed, the work is real.

Monday: The Board Conversation

The first thing a fractional CTO does is not technical. It's translation.

The CEO has a board meeting on Thursday. One of the investors keeps asking, “What's our AI plan?" and the honest answer so far has been a shrug. We spend ninety minutes turning the team's actual work into three things the board will understand: what we're building, why, and what we've decided not to build.

That last one matters most. Boards don't lose confidence because a team is doing too little. They lose it because nobody can explain the trade-offs.

By the end of the call the CEO has a one-page story they can defend. No deck theatre, just a clear line from business goal to what gets built.

Tuesday: The Roadmap, and the word "No"

Tuesday is roadmap day. The team has a backlog of forty-odd things. Everyone's busy, but nothing’s shipping that actually moves the numbers.

This is the most common pattern I spot in startups, and it's rarely a developer problem. The engineers are good; they're just being asked to build everything, which means they're prioritising nothing.

So we cut. Out loud, on a call, I say "Stop building that" about three features that have been in progress for weeks. One of them was a personal favourite of a senior stakeholder. That's the bit a full-time hire often can't do in month one, and an outside agency never does: say no, and make it stick, because I'm not playing the internal politics.

A fractional leader who only ever validates the team isn't worth the day rate. The value is honest challenge.

Wednesday: Alignment & Review

People assume fractional means hovering at the strategy layer and parachuting out. The opposite is true, or it should be.

Wednesday I'm in the weeds. A code review conversation about why a particular integration keeps breaking. A one-to-one with a senior engineer who's quietly being set up to be the first full-time CTO, helping him think like a leader rather than the best individual contributor. A look at the deployment process, which is held together with hope and a few manual steps.

I'm not writing the code. I'm the person making sure the people writing it are building the right thing, in a way that won't collapse at the next stage of growth. Different skill, complementary to the engineers, not a replacement for them.

Thursday: Structure & Recruitment

The board meeting happens (it goes fine; the one-pager does its job). Then the real Thursday work: team structure.

This company has developers but no one owning product direction. So we map what the next twelve months actually need. Do they hire a full-time CTO now, or a Head of Product first? My honest answer here was "CPO before CTO" - they don't have a technology problem, they have a "what should we build and for whom" problem. We draft the role, agree the shape, and I commit to helping them hire and onboard the person. Part of doing this job well is making yourself replaceable.

Friday: The Unglamorous Governance

Friday is the work nobody puts on LinkedIn. A simple decision log so the team stops re-litigating settled questions. A lightweight guardrail for how staff use AI tools, because half of them are already pasting customer data into chatbots and nobody had written down whether that's allowed. (It wasn't. Now there's a rule, and a sanctioned alternative.)

This is the part that outlasts the engagement. Strategy decks evaporate. Process and governance stay.

So, what does a fractional CTO actually do?

Across the week: translate technology into board language, force strict prioritisation, get into the details with the team, fix team structure and hiring, and leave behind processes that survive without me. One to two focused days doing that is worth more than five days of someone stretched across everything.

It is not writing your production code. It is not a slide deck and a handshake. And it is not permanent – done properly, the job includes working out when you no longer need me, and helping you hire the person who replaces me.

If you've got developers but no one owning the direction, or your CTO has left and you need senior cover while you recruit, that's exactly the gap this fills. Happy to talk it through - no pitch, no pressure.

Book a call with me directly.