What Does a Fractional CTO Do? A Week-by-Week Look
November 20, 20266 min read
Here is what a fractional CTO does: they own a company's technology decisions part time, usually one to two days a week. That covers architecture, the engineering roadmap, hiring and coaching engineers, vendor and build-versus-buy choices, security basics, and explaining all of it to the CEO and board. They direct the team's work and rarely write the code themselves.
A chief technology officer is accountable for whether the company's technology supports the business: whether the product ships, stays up, is safe enough, and costs a sensible amount to run. A fractional CTO carries the same accountability on a part-time contract, typically for a company with a small engineering team (or an outside development agency) and no senior technical leader. The deeper overview is in the fractional CTO guide. This article is about how the time gets spent.
A typical week
Assume a two-day engagement with a team of six engineers and one product manager. The days vary, but the week tends to contain the same blocks.
| Block | Time | What happens |
|---|---|---|
| CEO sync | 45 minutes | Priorities, risks, anything the business is about to promise a customer that engineering has not seen |
| Engineering leads one-on-ones | 30 minutes each | Blockers, people issues, coaching on decisions the lead made that week |
| Product and roadmap review | 60 minutes | With the product manager: what ships next, what got cut, estimates challenged, scope trimmed |
| Architecture review | 60 minutes | One or two design proposals from engineers, reviewed before the code is written |
| Incident and quality review | 30 minutes | Outages, near misses, error trends, what gets fixed so it does not repeat |
| Hiring | 1 to 3 hours when roles are open | Final-round interviews, scorecard calibration, closing candidates |
| Deep work | 3 to 4 hours | Writing: a decision record, a vendor comparison, the security plan, a board update |
| Async on off days | A few short check-ins | Unblocking decisions in chat, reviewing a design document, approving a spend request |
Notice what is missing: daily standups, ticket grooming, and long stretches of coding. Those stay with the team. A fractional CTO who fills the two days with hands-on programming is working as an expensive contractor, and the leadership gap is still there.
A typical month
Some responsibilities run on a monthly or quarterly clock.
- Week one: numbers. Review the cloud bill line by line against the prior month. Check delivery measures such as how often the team deploys, how long changes take to reach production, and how many releases caused an incident. Update the technology section of the board or investor report.
- Week two: roadmap. Reconcile the engineering plan with sales commitments and the product roadmap. Flag anything that will slip while there is still time to act.
- Week three: risk. Walk the security and reliability checklist: access reviews, backup restore test, dependency updates, open findings from any customer security questionnaire or audit.
- Week four: people. Review each engineer's growth and workload with the leads. Adjust the hiring plan. Deal with performance concerns before they become resignations.
Quarterly, add a planning session with the CEO and product leader, a review of technical debt (what to pay down and what to keep living with), and a look at major vendor contracts coming up for renewal.
The decisions and artifacts a fractional CTO owns
You can judge the work by what exists on paper after three months. Expect most of these:
- Architecture overview. A current diagram of systems, data stores and integrations that a new engineer can understand in an hour.
- Decision records. Short write-ups of each significant technical choice (the options, the choice, the reasoning) so decisions are not relitigated every quarter.
- Technology roadmap. The engineering work behind the product roadmap, including platform and debt items, by quarter.
- Build-versus-buy calls. For example, whether to write an in-house billing system or adopt a vendor, with cost and switching risk laid out.
- Hiring loop. Role definitions, interview stages, a practical exercise, and scorecards so the team hires consistently.
- On-call and incident process. Who gets paged, how incidents are declared, and a template for the review afterward.
- Security baseline. Single sign-on, access by role, secrets handling, backups, and a plan toward whatever certification customers are asking for.
- Vendor and agency oversight. If an outside firm builds the product, the CTO reviews their work, their estimates and their invoices on the company's behalf.
- Board-ready summary. One page a non-technical director can read: what shipped, what is at risk, what it costs.
What a fractional CTO does not do
- Carry the pager as primary on-call. They design the rotation and join major incidents, but someone who works two days a week cannot be first responder.
- Write most of the code. A prototype or a tricky review, yes. Feature delivery belongs to the engineers.
- Manage every engineer day to day. They manage through one or two leads. If there is no lead, creating one is an early task.
- Act as project manager. Tracking tickets and chasing status is a different role.
- Replace product management. They partner with whoever decides what to build, and they push back on scope. Deciding what customers need is not theirs alone.
- Stay forever by default. A good one tells you when the company has grown into needing a full-time technology leader and helps hire that person.
How the first month differs from the steady state
The rhythm above takes a few weeks to reach. The first month is heavier on discovery: reading the codebase and infrastructure, sitting in on existing meetings, interviewing each engineer, checking who holds admin access to critical accounts, and reviewing the last several incidents. The output is a short assessment with the top risks and a 90-day plan.
Companies can speed this up by preparing access and documents before day one. The checklist in how to onboard a fractional executive covers what to have ready.
How to tell whether it is working
If you are the company, look for three things by the end of the first quarter. Estimates and delivery dates have become more reliable. The CEO gets fewer technical surprises, because risks arrive early and in plain language. Engineers say decisions are clearer and they are waiting less. If none of those has moved, raise it directly. For help choosing the right person in the first place, see how to hire a fractional executive.
If you are the executive, protect the shape of the week. The pull toward becoming a senior engineer on call is strong, especially in a small team that is behind. Keep the standing meetings, keep writing decisions down, and keep a visible list of what you are choosing not to do. Many fractional CTOs hold two or three engagements at once, and that only works when each client knows which days are theirs and how to reach you between them. A published profile with bookable time, such as one on the ExecRoster roster, makes that first conversation easier to start.
One practical test applies to both sides. Ask what would happen if the fractional CTO disappeared for three weeks. If the team would keep shipping because the roadmap, the decision records and the on-call process are all written down and owned, the role is being done properly.
For experienced executives
Get found and hired for fractional work.
- A profile companies can find
- A calendar they can book
- Paid to your bank, you keep 90%
Frequently asked questions
What does a fractional CTO do on a weekly basis?+
In a typical two-day week they hold a sync with the CEO, one-on-ones with engineering leads, a product and roadmap review, an architecture review, and an incident review. They also interview candidates when roles are open and spend a few hours writing decision records, vendor comparisons or board updates.
Does a fractional CTO write code for the company?+
Rarely. They might build a quick prototype or review a difficult change, but feature delivery stays with the engineers. A fractional CTO who spends the contracted days programming is acting as a contractor, and the company still lacks someone owning architecture, hiring, roadmap and risk.
How many hours a week does a fractional CTO typically work?+
Most engagements run one to two days a week, with short asynchronous check-ins on other days to unblock decisions. The first month is usually heavier because of discovery work: reading the codebase and infrastructure, interviewing engineers, checking admin access, and reviewing recent incidents before writing a 90-day plan.
What is a fractional CTO not responsible for?+
They are not the primary on-call engineer, the day-to-day manager of every developer, the project manager tracking tickets, or the product manager deciding what customers need. They design the on-call rotation, manage through leads, challenge scope, and join major incidents, but those daily roles belong to the team.