Answers

What is a fractional CTO, and does a small business need one?

A fractional CTO is an experienced technology leader who works for a business part time instead of as a full-time hire. The role is to make technology choices, review quotes and plans, and oversee the people who build, not to build everything personally. A small business may find one useful for a first build, a project going wrong or a choice between vendors, and often needs less for simple tools. Titles vary, so ask what is included.

The role

CTO stands for chief technology officer, the person responsible for a company's technology choices. Fractional means part of the time: often a few hours a week or month, for as long as the need lasts. In a small business the job is usually to decide what to build and in what order, read proposals and say what is missing, check the work at each stage and explain the trade-offs in plain words.

It is not the same as the developer. A fractional CTO may write some code, but the job is mainly judgment and oversight. Titles are used loosely, so ask what the person has led before and what they would do in the first month.

When it can earn its place

  • Before a first build: help with the brief, comparing quotes and choosing a developer.
  • A project going wrong: a second opinion on what exists, what to keep and what to do next.
  • A choice between vendors, or between buying and building.
  • Software you rely on every day that nobody on your team understands.
  • A developer leaving, when someone must read the work and decide what happens next.

When it probably does not

For a website, or a bought tool you set up yourself, a fractional CTO is often more than the job needs; the related answer on whether you need an IT person covers accounts, updates and backups. For a small, clear job with a developer you trust, a short written brief and staged checks may be enough; the related answer on checking a developer's work describes the staged checks. Either way, it only helps if someone has time to act on the advice.

What it should hand over

  • Decisions in writing, each with its reason, so the next person can see why.
  • The brief and plan, in words another developer could use.
  • Every account the system uses in the business's name, with you as an owner or administrator and the adviser added as a user, not the other way around.
  • Notes on where the data lives and who can read it.
  • A ranked list of what to do next, including what to leave alone.

Alternatives, and a disclosure

Ascent Vision gives technical advice and also builds software, so read this with that in mind. If one firm does both, the related answer on an AI consultant or an AI builder draws the same line for AI work and lists the questions to ask it. The related answer on comparing quotes from software developers is a useful companion at the first decision.

OptionOften fitsWatch for
A trusted peer or advisorA quick opinion on one quoteLimited time or technical depth
A one-off review of a planA single decisionIt ends once the decision is made
A builder that also advisesSmall jobs and one-stop projectsAdvice and sales coming from the same place
An IT providerAccounts, devices and backupsOften not a software-design role
A staff hireDaily technology workHard to justify for occasional decisions

Related answers

Custom software and apps

Off-the-shelf tools get you most of the way. When the last stretch is where the time goes, we build the part that fits: the dashboard, the portal, the internal tool or the app.