What does a fractional CTO do? A week in their calendar
Direct answer
What a fractional CTO actually does day to day, from technology audits to built systems. A real look at the work, not the job description.
- What a fractional CTO actually does day to day, from technology audits to built systems. A real look at the work, not the job description.
- The strongest AI work starts with one operational bottleneck, one owner, and one result the team can inspect.
- Use the article as the diagnosis layer, then move into a scoped build, proof path, or commercial workflow page.
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 regional 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 the first few weeks 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 built last month and did it move the number, what builds 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 built 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 delivered 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 builds 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 builds?
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.
See also: what is a fractional CTO, fractional CTO services, fractional CTO overview, AI strategy consultant
How does a fractional CTO compare to hiring 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, managing a team of engineers full time, and representing technology in the senior leadership group. A fractional CTO earning £2,000 to £5,000 a month makes sense for the majority of SMEs in the £1m to £10m revenue range: they need senior technology judgement on two to three days a month, not twenty. The fractional model also gives a business the ability to change direction without an expensive hire-and-fire cycle if the technology strategy needs to pivot.
What does the first month of a fractional CTO engagement look like?
The first week is usually a technology audit: the stack, the deployed systems, the vendors, the data pipelines, the backlog, the team skills, and the commercial scorecard. The second week is decisions: what to stop, what to build, what to keep, what to kill. The third week is the first live deliverable, usually a small and measurable system that addresses a real revenue or cost lever. The fourth week is the review and the shape of the next 90 days. Any engagement that cannot produce a live system inside the first month is almost certainly in the wrong shape.
How do you know the fractional CTO engagement is working?
Three measurements give an honest view. The first is whether built systems are live and the commercial metric they target is moving. The second is whether the team around the CTO is making better technology decisions without waiting for input. The third is whether the CTO is being used more as a decision-maker and less as an executor as the engagement progresses. If the executor share is rising rather than falling, the engagement has drifted into the job of a senior contractor and the business is paying the wrong role for the work.
What should the handover look like when the engagement ends?
A clean handover has four parts. A documented architecture showing exactly what runs where, maintained by a named internal owner. A list of active vendors with contract terms, renewal dates, and the escalation contacts on each side. A short roadmap covering the next two quarters of technology work with explicit commercial targets. A standing monthly or quarterly check-in scheduled with the outgoing fractional CTO so the handover is reviewable, not one-shot. Engagements that finish without these four usually bounce back with the same business pain inside six months.
How should the team around a fractional CTO be structured?
The common shape is a single internal owner on the technology side, usually a senior engineer or an operations lead with technical instincts, plus whichever external specialists the current work needs (a dev shop, a freelance data engineer, a vendor implementation team). The fractional CTO runs the structure. The internal owner is the one who accumulates institutional knowledge and keeps systems healthy between the CTO's visits. Without that named internal owner, every engagement risks becoming a series of disconnected projects.
Related reading across this cluster
For the full service framing, read our fractional CTO pillar. If you want the operator-level breakdowns, What is a fractional CTO? and What does a fractional CTO do? are the usual starting points, and the pillar again (fractional CTO) links out to the rest of the cluster.
Related implementation paths
AI implementation services
Turn the article into a scoped first system with clear ownership, data, and measurement.
AI workflow automation
Automate one operational workflow inside the tools the team already uses.
AI agent development company
Design agents around jobs, tools, approval points, and measurable business outcomes.
Questions this article answers
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 builds 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 builds?
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. See also: what is a fractional CTO, fractional CTO services, fractional CTO overview, AI strategy consultant
How does a fractional CTO compare to hiring 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, managing a team of engineers full time, and representing technology in the senior leadership group. A fractional CTO earning £2,000 to £5,000 a month makes sense for the majority of SMEs in the £1m to £10m revenue range: they need senior technology judgement on two to three days a month, not twenty. The fractional model also gives a business the ability to change direction without an expensive hire and fire cycle if the technology strategy needs to pivot.
What does the first month of a fractional CTO engagement look like?
The first week is usually a technology audit: the stack, the deployed systems, the vendors, the data pipelines, the backlog, the team skills, and the commercial scorecard. The second week is decisions: what to stop, what to build, what to keep, what to kill. The third week is the first live deliverable, usually a small and measurable system that addresses a real revenue or cost lever. The fourth week is the review and the shape of the next 90 days. Any engagement that cannot produce a live system inside the first month is almost certainly in the wrong shape.
How do you know the fractional CTO engagement is working?
Three measurements give an honest view. The first is whether built systems are live and the commercial metric they target is moving. The second is whether the team around the CTO is making better technology decisions without waiting for input. The third is whether the CTO is being used more as a decision maker and less as an executor as the engagement progresses. If the executor share is rising rather than falling, the engagement has drifted into the job of a senior contractor and the business is paying the wrong role for the work.
What should the handover look like when the engagement ends?
A clean handover has four parts. A documented architecture showing exactly what runs where, maintained by a named internal owner. A list of active vendors with contract terms, renewal dates, and the escalation contacts on each side. A short roadmap covering the next two quarters of technology work with explicit commercial targets. A standing monthly or quarterly check in scheduled with the outgoing fractional CTO so the handover is reviewable, not one shot. Engagements that finish without these four usually bounce back with the same business pain inside six months.
How should the team around a fractional CTO be structured?
The common shape is a single internal owner on the technology side, usually a senior engineer or an operations lead with technical instincts, plus whichever external specialists the current work needs (a dev shop, a freelance data engineer, a vendor implementation team). The fractional CTO runs the structure. The internal owner is the one who accumulates institutional knowledge and keeps systems healthy between the CTO's visits. Without that named internal owner, every engagement risks becoming a series of disconnected projects.