A fractional CTO is a senior technology executive who leads a company’s technology part-time, usually on a monthly retainer, instead of as a full-time employee. They own the roadmap, the stack and vendor decisions, security, and the oversight of the developers and vendors the company already uses.

The role fits when a company needs someone senior making technology decisions on a steady basis, but not enough of them to fill a full week. This article covers what the role is, what the person actually does, how it differs from the other people you might hire, and the signs that you do or do not need one.

What a fractional CTO is

A chief technology officer is, in the usual definition, the executive responsible for an organization’s strategic use of technology. What that covers varies with the company. In some it faces outward, toward the product and the customer. In others it faces inward, toward infrastructure, vendors, and internal systems. In a small company one person often holds all of it.

“Fractional” means the company buys a fraction of that person’s time. You will also see “part-time CTO” and “virtual CTO” used for the same arrangement. The title is not what matters. What matters is whether one senior person is accountable for the technology decisions over time, rather than delivering a document and leaving.

What a fractional CTO does

The work is mostly decisions, and keeping them consistent from one month to the next. In practice it comes down to a handful of standing responsibilities:

  • A technology roadmap tied to what the business is trying to do, so engineering and vendor spend follow the plan instead of the last request.
  • Architecture and stack decisions, with the reasons written down so the next developer does not reopen them.
  • Vendor and software evaluation: what to buy, what to consolidate, what to cancel, and what the contract commits you to.
  • Security as a standing item in the plan, not a project that starts after an incident.
  • Oversight of in-house developers, agencies, and IT providers: setting expectations, reviewing the work, and being the person who can tell whether it is good.
  • Hiring plans, and the interviews when it is time to build a full-time team.
  • The technical voice in conversations with investors, partners, and customers.

What the role is usually not: a full-time pair of hands. A fractional CTO directs the building more than they do all of it, and they are not the help desk. If the need is forty hours a week of hands-on engineering, that is a hire or an agency, not a retainer.

Fractional CTO vs CTO vs consultant vs agency

Who owns the technology decisions, and for how long
Owns decisions over timeTypical outputBest fit
Full-time CTOYes, as an employeeStrategy, team, delivery, daily leadershipA company where technology leadership is a full-time job
Fractional CTOYes, part-timeRoadmap, decisions, vendor and developer oversightA company that needs senior judgment on a steady basis, not a full week of it
Technology consultantNo, advice at a point in timeAn assessment or a recommendationA defined question with a start and an end
Development agencyNo, executes a defined buildWorking software to a specificationA build that someone already decided should be built
IT provider (MSP)No, runs day-to-day ITSupport, devices, accounts, uptimeKeeping the current environment running

The common failure is expecting one of the bottom three to do the job of the top two. An agency will build what it is told to build, and an IT provider will keep the environment running. Neither is accountable for whether the company is building the right thing, or for what it will cost to maintain in two years. That gap is what the fractional role fills.

When you need a fractional CTO

The signs are usually visible before anyone names them:

  • You have developers or an agency, and nobody senior to direct them or judge their work.
  • The stack was chosen by the first contractor and nobody has reviewed the choice since.
  • Vendors and tools get added one at a time, and nobody can say what the company pays for or why.
  • Investors, partners, or larger customers are starting to ask technical questions, and the honest answer is “I would have to check.”
  • Security is assumed rather than checked.
  • A first engineering hire is coming, and nobody on the team can write the job or run the interview.
  • Technology spend keeps growing and the owner cannot tell whether it is working.

The pattern across all of these is the same. Decisions are being made, by default, by whoever happens to be closest to the problem. A fractional CTO replaces that with a person who is responsible for them.

When you probably do not

  • You have a technical founder who is making these calls well and has time to make them.
  • Your need is a defined project: a migration, an audit, a build. A consultant or an agency fits that better, and the project ends.
  • Your company is large enough that technology leadership is a daily job. At that point the fraction becomes a full week and the role should be a hire.
  • You want someone to be on call and available at all hours. That is an operations arrangement, and it is priced and staffed differently.

How to check before you hire anyone

Three questions show whether you have a leadership gap or just a staffing one. Write the answers down.

  1. Who decides? For the last three technology decisions the company made, name the person who made each and say whether they were qualified to.
  2. What do we own? List the systems, vendors, and accounts the company depends on, and who holds the access to each.
  3. What would break first? Pick the one system whose failure would stop revenue, and say who would know about it and how fast.

If the answers are vague, the company has a leadership gap, and the first step is to find out where it stands before deciding what to hire. A written assessment of the current state is a straightforward way to do that, and it gives any engagement a starting point.

Frequently asked questions

What is a fractional CTO?
A fractional CTO is a senior technology leader engaged part-time, usually on a monthly retainer. They own the technology roadmap, stack and vendor decisions, security, and oversight of developers and vendors, without being a full-time employee.
What does a fractional CTO do day to day?
Mostly decisions and reviews: setting the roadmap, choosing and documenting architecture, evaluating vendors and contracts, reviewing developers’ and agencies’ work, planning hires, and acting as the technical voice with investors and partners. They direct the building more than they do all of it.
Is a fractional CTO the same as a virtual CTO?
In practice, yes. Fractional, part-time, and virtual CTO describe the same arrangement: a senior technology leader who works for the company part-time. The useful question is whether one person is accountable for the decisions over time.
Does a company with no developers need a fractional CTO?
Often it does. A service business that runs on vendor software still makes technology decisions every month about tools, vendors, data, and security. The role shifts from directing developers to directing vendors and IT providers.
How is a fractional CTO different from a consultant or an agency?
A consultant delivers advice at a point in time and an agency builds what it is told to build. A fractional CTO stays accountable for the decisions over time and directs the consultants, agencies, and developers the company uses.

Sources