← All articlesInfra and cloud

What a fractional CTO actually does

Less code than you would expect, more decisions, and a higher hourly cost than a salary. Price is not the right test.

Julien Mauclair · ~7 min · intermediate
StackCTOStartupTechnical leadership

A fractional CTO is a technical leader who works for you part of the week: they make architecture decisions, set the technical roadmap, guide the team and help hire, as madewithlove describes the role. It mostly pays off when a team already ships and nobody is settling the decisions.

The usual volume is around 15 hours a week, barely two days. So they replace neither a full-time developer nor a manager who is there every day.

01Where the hours go

Most pages on this topic list duties and never mention time. Yet that is the whole question: on two days a week, every item comes at the expense of another.

RaftLabs, a vendor selling this service, gives an indicative split: 30% technical strategy, 25% team, 25% hands-on architecture, 20% communication. Applied to the 15 hours in the Go Fractional benchmark, that gives the weekly budget below. Treat it as an order of magnitude for scoping an engagement, not a measurement.

Technical strategy: tool choices, architecture, roadmap4 h 30
Team: hiring, one-on-ones, ways of working3 h 45
Hands-on: specs, proofs of concept, reviews of risky code3 h 45
Communication: founders, product, investors3 h

Look at the third line: under four hours a week near the code. The same point comes up in this Reddit account from a former CTO of two young startups, who was full-time at that: code took less than half of the day, and the rest went to translating between founders and engineers, to operations and to people. They also describe resenting that part for a long time, as if it were a demotion, when it was the job. It is only one story, but it corrects a common expectation: if what you mainly want is someone to write code, this is the wrong role.

02What they take on, and what they don't

Part-time work imposes a simple rule: they take what can wait a day or two, and nothing that blocks the team when they are away. RaftLabs says so too: no feature development, no mandatory review on every change, no critical sprint path in their hands. Here is the line to put in writing from the start.

Takes onArchitecture and vendor choices, technical debt trade-offs
Takes onTechnical hiring: job descriptions, interviews, final opinion
Takes onReview of sensitive changes: security, data, deployment
Takes onTechnical preparation for a funding round or investor due diligence
Leaves outThis week's features: someone absent three days out of five becomes a bottleneck
Leaves outApproving every code change
Leaves outBeing on call alone: monitoring and backups must work without them
Leaves outDay-to-day management of a growing team

Interim work is the exception. madewithlove separates the two clearly on its French page: an interim CTO leads full-time through a period of change, often for 3 to 6 months, whereas fractional is a part-time rhythm that tends to last longer. If your CTO just left and the team has no direction, you need an interim.

03The cost, recalculated

The US market has a public benchmark. Go Fractional, a marketplace in this field, shows in November 2026 an average of $203 an hour and $12,100 a month for 15 hours a week, against $250,000 a year for a comparable full-time role, loaded. Its $145,200 annual figure assumes 12 months of 4 weeks, so 48 weeks. Over 52 weeks, using its own 780 annual hours, you get $158,340, which is 63% of full-time rather than 58%.

The most useful calculation is the hourly one. The Go Fractional figure of $250,000 over 2,080 hours comes to about $120 an hour, so fractional costs roughly 1.7 times more per hour. At that rate it overtakes a full-time cost from 1,231 hours a year, about 24 hours a week. This marker is approximate: the benchmark rests on few job posts and many profiles, and its full-time reference covers all IT managers, without equity or recruiting fees.

In France, the closest benchmark is the interim CTO rate: €800 to €1,200 a day according to Régie Portage, and up to €2,000 in critical contexts. Assuming 44 working weeks a year, an assumption of this calculation, one day a week is 44 days, or €35,200 to €52,800 a year. Two days a week is 88 days, or €70,400 to €105,600. Three days a week is 132 days, or €105,600 to €158,400.

Compare that with the €85,000 gross a year that Licorne Society reports as the average pay of a startup CTO in France, plus employer contributions and often 1 to 2% of equity. Without those contributions, the gross figure is reached between 1.6 and 2.4 days a week depending on the rate (85,000 divided by the rate, then by 44). With them the threshold rises, but the conclusion holds: at two days a week, the price gap is far less dramatic than advertised. What you are buying is a senior profile with no long commitment and no equity. These sources sell payroll and recruiting services, so read them as ranges, not studies.

04At what stage it helps

Ask these questions in order and stop at the first answer that fits.

·Nobody codes day to day? You first need someone who builds. Licorne Society says the same for early stage: a tech lead or technical founder who can code themselves. Two days a week of leadership do not write a product.
·You have one decision to make, or a doubt to clear before investing? A short, bounded engagement is enough: an audit, an architecture review, a second opinion on a cloud bill.
·Your CTO just left, or delivery has stalled? Take a full-time interim, then hire.
·A team ships, but technical choices drag or contradict each other, and you cannot settle them yourself? That is the typical fractional case.
·You are preparing a round and investors will look at the tech? Fractional fits too, provided it starts early enough to fix what it finds.
·The team needs daily management, or technology is your competitive edge? Hire full-time. A fractional CTO can prepare that hire and hand over.
Careful

Code generated quickly with AI and reviewed by nobody does not change the order of these questions: it only makes the second one more urgent. Start with the common mistakes with Claude Code and the basic security holes in Next.js.

05Three clauses to avoid dependency

The risk of fractional work is not the price, it is depending on one person who knows everything and is only there two days a week. Three commitments to ask for before starting:

·Written decisions: every important choice is recorded with its reason, somewhere the team owns.
·Access in your name: repositories, cloud account and secrets stay with the company, never on a personal account.
·A planned exit: who takes over what, and when. madewithlove quotes 3 to 18 months for an engagement, and RaftLabs 6 to 18 months before moving to light advisory. An engagement with no review date tends to go on out of habit.

The good sign at three months: the team makes more and more decisions without them.

06FAQ

What is the difference between a fractional CTO and a consultant?

A consultant gives an opinion and leaves. A fractional CTO owns the decisions over time: they join team rituals, talk to engineers, hire and answer for the technical outcome to the founders. If nobody can say who settled an architecture choice, the role is not really being filled.

How many hours a week should I plan for?

The Go Fractional benchmark gives about 15 hours a week on average, or 1.9 days. Start there and adjust after the first month. If the need regularly goes past 3 days a week, the calculation above points toward hiring.

Can a fractional CTO work for several companies?

Yes, that is the principle, and it is what makes the model possible. Just ask which companies are involved, rule out direct competitors and agree on a response time for incidents.

Should I give them equity?

Nothing requires it. At a market price, the engagement is paid in fees. The 1 to 2% cited by Licorne Society concerns an employed CTO, committed full-time and for the long term.

In short

A fractional CTO helps when a team already ships but nobody settles the technical decisions. Before that, you need someone who builds. After that, you need someone who is there every day.

Talk about your project ↗
Julien MauclairJulien Mauclair is the co-founder and CTO of Klickbee, where he builds the agency’s websites, tracking and AI automations, and develops Klickbee Tracking. He also runs Stralya, which designs and runs AWS infrastructure for scale-ups. Before that, he built the entire AWS infrastructure of an e-commerce business, since sold.

Read next