Blog
What a Fractional CTO Actually Does in 10 Hours a Week
Founders sign a retainer for “10 hours a week of CTO time” and then, a few weeks in, ask some version of the same question: what am I actually paying for?
It’s a fair question. Ten hours a week isn’t enough to write meaningful code, sit in every standup, or be the person your engineers Slack when something breaks at 4pm. So if a fractional CTO isn’t doing any of that, what’s left?
The honest answer: the highest-leverage 10 hours of technical decision-making your company will make that week. Concentrated into the calls that are expensive to get wrong and hard to un-make later. This post breaks down where those hours actually go, using a real week as the example.
The short answer
A fractional CTO spends their hours on judgment, not execution: architecture and vendor decisions, hiring and interviewing, 1:1 coaching for technical leads, and translating engineering risk for founders, investors, or the board. They’re not writing your product’s code or managing daily sprint execution. They’re making the decisions that everyone else’s daily work depends on, so the wrong call doesn’t quietly compound for six months before anyone notices.
A sample week, hour by hour
Every engagement is scoped differently, but here’s a realistic breakdown for a 10-hour-a-week retainer with an early-stage startup. The kind of split I’d actually run.
| Hours | Activity | What it looks like |
|---|---|---|
| 2 hrs | Architecture & technology decisions | Reviewing a proposed data model, deciding whether to build a feature in-house or buy it, sanity-checking a scaling plan before it’s locked in. |
| 2 hrs | Hiring & interviewing | Writing or refining a job spec, running a technical interview, reviewing a coding assessment, advising the founder on an offer. |
| 2 hrs | 1:1s with technical leads or senior engineers | Weekly or biweekly check-ins to surface blockers, calibrate technical direction, and coach engineers who are ready for more ownership. |
| 1.5 hrs | Codebase or team health spot-check | A focused look at a specific risk area. Not a full audit every week, but a rotating check on the parts of the system or team most likely to cause problems. |
| 1.5 hrs | Founder/investor-facing translation | Prepping the technical section of a board deck, explaining a delay in terms of cost and risk, answering a due-diligence question in plain language. |
| 1 hr | Async availability & follow-ups | Responding to a flagged Slack thread, reviewing a pull request that a lead wants a second opinion on, unblocking a decision that can’t wait for the next scheduled block. |
That’s 10 hours of work that touches architecture, hiring, people, and the board. Because those are exactly the areas where a wrong call is expensive and slow to reverse. Everything else is intentionally left to the team.
What’s deliberately not in those 10 hours
This is the part that surprises founders coming from a full-time-CTO mental model:
- No daily standups. If technical decisions need a person in the room every day, that’s a full-time-CTO problem, not a fractional one.
- No day-to-day sprint management. That’s a lead or EM’s job, and a fractional CTO who tries to own it is either underpricing the engagement or overstepping the team.
- Minimal hands-on coding. Occasionally a targeted spike or proof-of-concept, but writing production code isn’t where 10 hours of senior judgment is best spent.
- No always-on Slack availability. Async check-ins happen, but “reachable within the hour” is a full-time expectation priced into full-time comp.
None of this is a lesser version of a full-time CTO doing less of everything. It’s a different, narrower scope built around the decisions that actually need senior judgment versus the ones that need a person physically present.
Why fewer hours can mean better decisions
This sounds counterintuitive, but it plays out consistently: a fractional CTO who’s only in the room for the decisions that matter tends to make sharper calls than a full-time hire drowning in the day-to-day. Ten focused hours, scoped around architecture, hiring, and risk, forces a level of prioritization that a 40-hour week doesn’t. Nothing gets a decision by default just because there’s time to fill. Every hour has to earn its place.
The tradeoff is availability, not quality. You’re not getting a worse decision-maker for fewer hours. You’re getting the same judgment, applied only to what genuinely needs it.
When 10 hours stops being enough
Ten hours a week works until technical decisions start happening daily instead of weekly, or until the team is big enough that people-management alone would fill the retainer. At that point the honest move is scaling the hours up, or having the conversation about whether the company has outgrown fractional entirely. (I wrote about exactly where that line tends to fall in Do You Need a Fractional CTO or a Full-Time One? A Founder’s Checklist.)
FAQ
How many hours a week does a fractional CTO typically work? Most engagements run 10–20 hours a week, though it depends on scope. A defined project like an architecture audit might be a short, fixed-hour engagement, while ongoing hiring and technical leadership support usually runs as a standing weekly retainer.
Does a fractional CTO write code? Occasionally, for a targeted spike or proof-of-concept, but writing production code generally isn’t the best use of a fractional CTO’s limited hours. The value is in decisions that affect the whole team or codebase, not in individual features.
Will a fractional CTO manage my engineers day to day? No. Day-to-day management usually stays with a team lead or engineering manager. A fractional CTO typically works one level up: coaching the leads themselves, setting technical direction, and stepping in on decisions those leads shouldn’t have to make alone.
Can a fractional CTO attend board meetings? Yes, this is one of the higher-leverage uses of the hours. Translating technical risk and roadmap tradeoffs for a board or investor audience is exactly the kind of work that justifies senior judgment over raw hours.
Wondering if 10 hours a week is even the right number for where you are? Book a call and we’ll figure out the actual scope — hiring, architecture, board prep, or all three — before we talk about hours.
