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

13 April 2026

What does a fractional CTO do is the question that follows naturally from hiring one. The job description is clear in theory: own the technology layer of the business. What that means in a specific week, for a specific SME, is less obvious.

A fractional CTO means a senior technology leader working across two or three clients on a fractional basis instead of full-time. At twohundred.ai, a typical week looks like this.

Monday: architecture decisions

Monday starts with the client Telegram channels. Any urgent technology decisions that came up over the weekend get addressed first. These are usually vendor questions or production issues that need a fast call.

For a Manchester SaaS client in week three, Monday morning means reviewing the pull requests from the previous week. The developer built a feature. The fractional CTO checks whether the architecture is correct, whether the database schema will cause problems at 10x current data volume, and whether integration decisions are baked into the code that should have been made explicitly. This review catches the decisions that create six months of debt in a single sprint.

Tuesday: system build

One day per week is reserved for active system building. For a Dubai hospitality client on the Growth tier, Tuesday in week four means finishing the WhatsApp qualifier integration. The fractional CTO writes this code. Not a junior developer. Not an offshore team. First system live in 14 to 21 days from kickoff is only achievable when the most senior person in the room is doing the build.

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 technology roadmap for the quarter: what shipped last month and did it move the number, what ships next month and why, and what technology decisions are coming up before they default to the wrong answer.

Wednesday also means vendor calls. A SaaS provider pitches a new data integration tool. The fractional CTO takes the call, evaluates fit against the existing stack, and sends the founder a one-paragraph recommendation. The founder does not sit in that call.

Thursday: AI system work and data infrastructure

Thursday typically involves the AI system layer. For a London services firm on the Growth tier, Thursday means testing the Gmail-side AI responder that went live Tuesday. The system reads incoming inquiries, drafts a reply in the client voice, and queues it for human approval before sending. Average draft time: under 60 seconds per email.

AI-referred customers convert at 14.2 percent versus Google 2.8 percent. That is a 5x improvement in conversion rate on the same traffic, which is why these systems get priority in every engagement.

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 systems shipped in the week get a short handover note documenting how they work and what the team should do if something breaks.

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 is the developer and product owner job.

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

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 the prioritised build list for the quarter. First working system typically ships in week three of the engagement.

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 is 15 to 20 hours per month. Dominance is continuous, effectively replacing a full-time CTO for the relevant scope.

What is the first system a fractional CTO ships?

The first system is always the one with the highest ratio of revenue impact to build time. For most SMEs this is either a lead qualification workflow (WhatsApp or email based) or a SaaS rationalisation that frees up £1,000 to £3,000 per month within the first 30 days.

Want this built for your business? Book a call.