In this guide 6 sections
A fractional CTO gives a business a few days a month of senior technology leadership: reviewing vendor work, approving architecture choices, sitting in negotiations and keeping the roadmap current. No coding. No helpdesk. No substitute for a full-time team once the workload outgrows the arrangement.
A few days a month, aimed at decisions
Owners who face technology choices with nobody senior to decide them hire this role for one or two days a month, plus a phone line for urgent questions. Days go to decisions, never to code.
Think of the person as the reader of contracts your developer skips, the one who asks why a quote carries forty hours for a login screen. They spot hosting with no backup.
Hours are fixed in advance, so cost stays predictable. That is the real difference from a consultant who appears only after the invoicing module has failed in front of customers.
Reviewing what your vendor builds
Agencies get judged on the demo. A fractional CTO judges the work by the repository, the staging server, the deployment script and the backup job underneath, which is where hidden cost sits.
The review is short. It repeats every month. Problems found in month two cost far less than problems found at handover, when the agency has moved on to another client.
The vendor mentions a schema migration. The owner hears noise. The CTO restates it as a date, a risk and one question you can answer before your next customer call, so the decision rests on facts.
- Pull requests and commit history, to see who is doing the work
- Staging and production environments, and how code moves between them
- Backup schedule and a restore test, not just a promise
- Packages with expired licences or no maintainer
- Estimates compared against the scope document line by line
Approving architecture and joining negotiations
Some choices are costly to reverse, such as the database engine, the hosting region, buying or building a booking engine, and how the mobile app reaches the back office. The CTO signs off in writing.
The reasons go on record. Staff change. The same person sits in vendor negotiations, where licences come with seat counts, API call limits, exit clauses and data export terms.
One missed clause traps you for three years. Their notes become a one-page decision record, so a newcomer can read why the team chose Postgres over a spreadsheet when the original staff have long since left.
Keeping the roadmap honest
A roadmap rots in a quarter without an owner. So the CTO keeps a rolling list of what to build, buy, retire or leave alone, each with a reason, a rough size and a dependency.
They also say no. A request from sales for a customer portal gets weighed against the unfinished stock-sync fix, and a refusal with a reason beats a long wish list.
Each quarter they walk the list with you, drop what no longer matters, move dates and hand the vendor a plan it can actually price, not a slide deck.
What the role does not cover
This person is not your developer or sysadmin. A dead printer or a locked account is somebody else’s job, and paying senior rates to fix either wastes the days you bought. Hands-on delivery belongs with a developer billed at a developer’s rate, under the CTO’s review.
The arrangement has a ceiling. Once you run several products, a team of six or more, or regulated customer data, a full-time hire makes sense, and a good fractional CTO will say when.
Before signing, list the three decisions you most need help with this year, and ask each candidate how they would handle them. Pick the one who answers with questions first.
- Writing production code as the main task
- Device repair and password resets
- Managing a full-time team of more than a handful
- Legal advice on contracts or data law
Fractional CTO scope sheet
A single sheet in four blocks. The first fixes the monthly days and the urgent-call response time, and the second tabulates recurring duties: vendor code review, architecture sign-off, contract review and the quarterly roadmap session. The third lists three decisions you need help with this year, each with an owner, a date and the evidence the CTO should read first. The fourth lists exclusions.
Open a blank worksheet to printQuestions owners ask
How many days a month does a fractional CTO work?
Most arrangements run one to four days a month, depending on how much vendor work is live and how many decisions are waiting. Start with two. Adjust after a quarter.
Is a fractional CTO the same as an IT consultant?
No. A consultant usually answers a single question and leaves. The fractional hire stays on a retainer, knows your systems, follows every vendor, attends sprint reviews and keeps one roadmap alive across many months.
When should we hire a full-time CTO instead?
When the technology workload fills most of a week, several teams depend on you, or you handle data that needs constant oversight. Until then, fixed days cost less.
Can a fractional CTO manage my current developer?
They can review the developer’s work, set coding standards and sit in planning calls, but daily task management stays with whoever runs the project. Their role is direction and quality.