What is a fractional CTO?

What a fractional CTO owns: which decisions, on what cadence, and how the handoff works when part-time leadership is enough.

Talk through your CTO need

By Keith Rull ·

A fractional CTO is a part-time technology executive who owns a written set of decisions, on a cadence you agree up front, and hands that work back when the company no longer needs the cover. When those decisions need someone every day, look at interim or full-time leadership instead.

The offer itself, including the signs it fits and what you should leave with, is on the fractional CTO page. This article is how to scope the role so the list is real: who decides, how often, and what ends it.

What decisions does the role own?

Before you agree an engagement, list the decisions that actually come up and when they come up. For a small company those often include a hiring plan, a platform investment, a vendor choice, and how reliability risk is explained to the rest of leadership. A title without that list is a standing meeting.

Split the list three ways. Some decisions the fractional CTO makes, some stay with the founder (especially spend and customer promises), and some stay with the engineering lead, especially the release in front of them and the incident on a Tuesday night. Write the urgent path for a day the fractional CTO is not there. If that path is “wait,” the company needs a different shape of leadership.

This split is a pattern to fill in, not a client record.

Decision Fractional CTO Founder Engineering lead
Architecture direction for the next two quarters Recommends, and decides when the scope says so Approves spend and customer impact Owns the implementation plan
Who to hire next Sets the bar and runs the loop Makes the offer Interviews for the craft
Whether to pause a release Advises, unless the scope includes the call Accountable for the business outcome Carries out the pause
An incident on a night the fractional CTO is off Named in the escalation path, not assumed on call Knows who is on call Runs the incident, unless the scope says otherwise

Read the last row with care. Part-time leadership does not include unspoken night-time ownership. If you need that, say so and staff it, or hire interim or full-time cover. Fractional or interim CTO: which one fits? is the comparison when the seat itself might be empty.

What cadence matches those decisions?

Set the cadence from the decisions, not from a pile of unused hours. A recurring architecture review helps when the hard choices cluster around releases. A time-boxed weekly session helps while the company is choosing a hiring plan or a migration path. A monthly slide, with no decision on it, is not a cadence. It is a status habit.

Here is an illustrative division, not a past engagement. A team is considering a database migration. The fractional CTO guides the evaluation and writes the decision: options, the rollback limits, and the review date. The engineering lead keeps release control and incident ownership. The founder approves the spend. That split is enough while the choice is still open. It stops being enough if the migration needs a person in the design reviews every day. At that point the work is an embedded effort or a fuller leadership seat, and the fractional scope should say so.

I have run an independent fractional CTO practice since 2007. The engagements that stay healthy are the ones where the decision list is short enough to rehearse, and the cadence matches how often those decisions actually appear. A long list on a thin calendar is how expectations drift.

When is a different shape the better fit?

Part-time cover is the wrong tool in a few ordinary situations, and naming them early is a scope correction rather than a failure of the idea.

The engineering lead already owns the decisions, and they get made. You may want a single second opinion, which is CTO consulting on one question, and then a stop. You do not need a standing CTO to confirm a choice the team is already making.

The CTO seat is empty. Releases, incidents, and hiring need authority this week. That is interim CTO cover, with a handoff to the permanent hire. A fractional scope will feel helpful and still leave the seat empty on the day you need it.

Technology decisions are continuous, the team needs daily leadership, or the role is now central to fundraising and strategy. Hire a full-time CTO. A fractional engagement can write the role, run the technical loop, and overlap with the new hire. It should not stand in for the seat once the calendar is full.

Leadership wants someone inside a single stuck transformation until a team can run it. That is embedded work, and it has a different exit. Do not stretch a fractional cadence across a delivery floor and call it the same role. What a Forward Deployed CTO does is that shape: inside the delivery reviews until one workflow ships. If the gap is builders rather than a decision owner, staff augmentation or a dedicated team is the closer fit. The practice behind these engagements is Keith Rull.

How does the handoff work?

Write the handoff when you write the scope. A fractional engagement should leave a decision log with owners, assumptions, and review dates. It should leave a hiring plan when hiring was in scope, and a short account of technology risks for the leadership team. It should name the trigger that changes the arrangement: daily presence, a larger team, or a full-time search.

The handoff lists open risks in the same ink as the finished work. “Complete” with a hidden incident path is not a handoff. The engineering lead, or the full-time CTO, should be able to run the next release from the log without a meeting to recover the context.

Review the trigger on the cadence you already have. If it has tripped, change the shape. Extending a part-time scope because the relationship is comfortable is how a clear role turns into an unclear one.

A founder can draft this list without help when the decisions are few and the engineering lead is already strong. Use a conversation when the same decision keeps returning, the founders are answering investor questions they do not yet trust, or nobody can say who pauses a release.

FAQ

What does a fractional CTO do in a normal month?

They work the decision list on the agreed cadence. That might be an architecture call before a release, a hiring loop, a vendor recommendation, and a short risk note for leadership. They do not silently absorb incident command, people management for the whole team, or every technical question in the company chat. If the month is full of those, the scope is wrong and should be rewritten.

How are decision rights split with the founder?

The founder keeps spend, customer commitments, and the call on whether to hire a full-time CTO. The fractional CTO owns, or recommends, the technology choices in the written list. Put the line in the scope, including what happens when the fractional CTO is unavailable. A split that lives only in conversation will be relitigated on the worst day.

When should we hire a full-time CTO instead?

When decisions are needed continuously, the engineering team needs daily leadership, or technology leadership has become central to fundraising and strategy. You can use a fractional engagement to define that job and to run the technical interviews. You should not use it as a long substitute once those conditions are already true.

What should we bring to a first conversation?

The decisions that are stuck, how often they come up, and who handles a release or an incident today. Company stage and a deadline help. Leave confidential documents and customer data out of the first note. The fractional CTO page lists the questions worth settling before any scope is signed.

If you’re deciding whether part-time CTO cover fits, talk to us.

Senior technology leadership, without the full-time hire

Talk through your CTO need