What does a fractional CTO do? A week in their calendar

What does a fractional CTO do in a normal week?

What does a fractional CTO do once the contract is signed and the job description stops being useful? They own the technology layer of a business while splitting their time across two or three clients instead of going full-time at one. The work is senior, hands-on, and measured against commercial outcomes, not headcount or hours logged.

The clearest way to answer the question is to walk through an actual week rather than restate the role. A fractional CTO at twohundred.ai runs a repeating five-day rhythm: architecture decisions, system building, technology direction, AI system work, and audit output. Each day has a different shape because each client sits at a different stage. One is in week three of an audit, another is mid-build, a third is on a monthly review cadence. The pattern below is what that looks like in practice.

Monday: architecture decisions

Monday starts in the client Telegram channels. Any urgent technology decisions that surfaced over the weekend get handled first, usually vendor questions or production issues that need a fast, senior call rather than a meeting.

For a Manchester SaaS client in week three, Monday morning means reviewing the previous week's pull requests. The developer built a feature. The fractional CTO checks whether the architecture is correct, whether the database schema will hold at 10x current data volume, and whether integration decisions got baked into the code that should have been made explicitly first. This is where six months of technical debt gets caught inside a single sprint, before it compounds. A good review on a Monday is worth more than a roadmap deck, because it changes the code that ships that week.

Tuesday: system build

One day a week is reserved for active building. For a regional hospitality client on the Growth tier, Tuesday in week four means finishing the WhatsApp qualifier integration. The fractional CTO writes this code personally. Not a junior developer. Not an offshore team. The first live system inside the first few weeks of an engagement is only achievable when the most senior person in the room is doing the build, because they make the architecture call and implement it in the same sitting.

Wednesday: technology direction and vendor calls

Wednesday is the working session for at least one client. For a Singapore logistics SME on the Foundation tier, the monthly session reviews the quarter's technology roadmap: what got built last month and whether it moved the number, what gets built next month and why, and which technology decisions are coming up before the team defaults to the wrong answer by accident.

Wednesday also means vendor calls. A SaaS provider pitches a new data integration tool. The fractional CTO takes the call, tests fit against the existing stack, and sends the founder a one-paragraph recommendation. The founder does not sit in that call. Protecting the founder's time from vendor pitches is part of the job, not a side effect of it.

Thursday: AI system work and data infrastructure

Thursday is the AI system layer. For a London services firm on the Growth tier, Thursday means testing the Gmail-side AI responder that went live on Tuesday. The system reads incoming inquiries, drafts a reply in the client's voice, and queues it for human approval before anything sends. Average draft time runs under 60 seconds per email, which is the difference between a lead that gets a same-hour reply and one that goes cold in an inbox.

The reason this work gets priority is the conversion gap. AI-referred customers convert at 14.2 percent versus 2.8 percent for Google traffic. That is a 5x improvement in conversion rate on the same volume of inbound interest, so the systems that capture and route AI-referred demand sit at the front of nearly every build queue.

Friday: audit output and pipeline review

Friday is documentation and pipeline work. Any audit findings get written up for the founder to share with their accountant, developer, or investor. Any system built during the week gets a short handover note covering how it works and what the team should do if it breaks. The aim is that nothing important lives only in the fractional CTO's head, which is what keeps the engagement from turning into a dependency.

What a fractional CTO does not do

A fractional CTO does not manage your developer day to day. They set the architecture, review the output, and make the technical calls. Daily sprint management belongs to the developer and the product owner, and a fractional CTO who slides into that seat is being paid a senior rate to do a coordinator's job.

A fractional CTO also does not hand over a 60-page strategy document and call it a quarter of work. Every engagement at twohundred.ai delivers working code inside the tools the client already uses. The fractional CTO red flags guide covers how to spot one who pitches their own product instead of solving your problem.

How the work compares to a full-time CTO

The question that matters is not seniority, it is operating context. A full-time CTO earning £150,000 to £220,000 a year makes sense when the business has enough technical surface area to need someone making architecture decisions every day, running a full engineering team, and representing technology in the senior leadership group. A fractional CTO earning £2,000 to £5,000 a month makes sense for most SMEs in the £1m to £10m revenue range, because they need senior technology judgement two or three days a month, not twenty. The fractional model also lets a business change direction without an expensive hire-and-fire cycle if the strategy needs to pivot. For the full picture of the role and where it fits, the what is a fractional CTO guide sets out the definition and the cases where the model works.

How twohundred runs this in practice

In practice, the trap that sinks most fractional engagements is the slow drift from decision-maker to executor. The early weeks are heavy on building because there is a backlog of obvious wins. If the executor share keeps rising after that, the business is paying a CTO rate for contractor work and the engagement has lost its point. The way twohundred keeps the ratio honest is a single named internal owner on the client side who accumulates the institutional knowledge between visits, plus a monthly review that measures whether built systems are live and moving their target metric. If you want the role scoped against your stack and revenue levers before committing, the fractional CTO services page lays out how the tiers map to hours and deliverables.

Frequently asked questions

What does a fractional CTO do in the first month?

The first month is the technology audit. The fractional CTO maps the full stack, identifies the highest-impact systems to build or fix, and produces a prioritized build list for the quarter. The first working system typically goes live in week three of the engagement, not at the end of a long discovery phase.

How many hours per month does a fractional CTO work?

At twohundred.ai the Foundation tier runs roughly 8 to 10 hours per month across working sessions, build time, and async decision support. Growth runs 15 to 20 hours per month. Dominance is continuous, effectively replacing a full-time CTO for the relevant scope of work.

What is the first system a fractional CTO builds?

The first system is always the one with the highest ratio of revenue impact to build time. For most SMEs that is either a lead qualification workflow, built on WhatsApp or email, or a SaaS rationalisation that frees up £1,000 to £3,000 per month within the first 30 days. The point is a measurable result early, not a grand platform.

How do you know a fractional CTO engagement is working?

Three signals give an honest read. Built systems are live and the commercial metric they target is moving. The team around the CTO is making better technology decisions without waiting for input. And the CTO is being used more as a decision-maker and less as an executor as the months pass. If the executor share is climbing instead of falling, the engagement has drifted into senior-contractor work.

---

Related Services

For businesses working through an AI strategy before committing to a build, AI consulting services covers the advisory and planning layer. When ready to move from strategy to deployment, AI implementation services covers the full rollout.