How many days a month does a fractional CTO work?

Usually 2 to 8 days a month, depending on whether a build is running. What matters is not the day count but which decisions they own.

Do they write code themselves?

Sometimes, but that is not the core of the role. If all their time goes into code, you are paying for an expensive developer rather than a CTO.

Do non-technology businesses need one?

That is exactly where the role pays off. F&B, laundry, and multi-outlet businesses have complex operations but rarely have someone who can translate operations into systems.

How long is a typical engagement?

Three to six months for the first cycle, then extended monthly. Anything shorter usually ends before results are visible.

What is a fractional CTO?

Last updated 6 September 2026 · Published 1 September 2026

Short answer

A fractional CTO is a part-time CTO who owns the technology, systems, vendor, and technical hiring decisions in your business. They work a few days a month on a retainer instead of a salary. It fits businesses that need good technical decisions but cannot yet carry a full-time CTO.

What a fractional CTO owns, and what they do not

What a fractional CTO owns, and what they do not
In scope	Out of scope
Setting systems direction and build order	Being the only developer writing daily code
Choosing and supervising vendors or developers	Acting as the day-to-day IT helpdesk
Writing process and SOPs before software is built	Selling tools or software licences
Turning operational data into decisions	Running marketing and content

What the work actually looks like

Deciding which systems are worth building and which ones only add friction. Choosing and supervising vendors or developers. Writing the process and SOPs so the system actually gets used. Reading operational data and turning it back into decisions.

The part most people miss: a good fractional CTO will refuse to build software while the process is still a mess. Process first, technology after.

How this differs from an agency or a freelancer

Agencies and freelancers wait for your spec and then build to it. A fractional CTO helps decide what the spec should be, and answers to the operational result rather than the number of shipped features.

How I work

I run 8 laundry outlets and I built the SaaS POS those outlets run on. So when I step in as a fractional CTO, my reference point is daily operations, not theory.

When this is the wrong fit

If your business is still validating an idea with no revenue running, you do not need a fractional CTO yet. What you need is execution hands, not someone to own systems decisions.

Questions that come up most

How many days a month does a fractional CTO work?: Usually 2 to 8 days a month, depending on whether a build is running. What matters is not the day count but which decisions they own.
Do they write code themselves?: Sometimes, but that is not the core of the role. If all their time goes into code, you are paying for an expensive developer rather than a CTO.
Do non-technology businesses need one?: That is exactly where the role pays off. F&B, laundry, and multi-outlet businesses have complex operations but rarely have someone who can translate operations into systems.
How long is a typical engagement?: Three to six months for the first cycle, then extended monthly. Anything shorter usually ends before results are visible.

Sources and further reading