← Back to blog
Technology Leadership15 May 20267 min read

What Does a Fractional CTO Actually Do?

The title sounds impressive. But what does a fractional CTO actually do all day? Here is a practical look at the role — no corporate jargon, just the work.

You have heard the pitch: “Get a CTO without the full-time salary.” But what does that actually mean in practice? What happens on the days your fractional CTO is working? And what happens on the days they are not?

I have been working as a fractional CTO for multiple SMEs simultaneously, and the role looks different from what most business owners expect. It is not about writing code all day (although I do that too). It is about making the technology decisions that save — or cost — your business tens of thousands of pounds.

The four pillars of the role

Every fractional CTO engagement is different, but the work clusters around four areas: strategy, architecture, people, and vendors. The balance shifts depending on your business stage, but all four matter.

1. Technology strategy: deciding what to build and what to buy

The most expensive technology mistakes are not bugs. They are building the wrong thing, or buying a £40,000 system when a £4,000 tool does the job. A fractional CTO evaluates your business goals and maps them to technology decisions.

This means reviewing your current stack, identifying gaps, and creating a roadmap that aligns technology spending with business priorities. Not a 50-slide PowerPoint — a living document that your team actually uses.

2. Architecture and code: the technical backbone

When your developers propose a new feature or system, someone needs to evaluate whether the architecture will scale, whether the technology choices are sound, and whether the implementation is production-ready. That is the fractional CTO.

At SelectWise, this is hands-on. I review pull requests, design system architectures, and write production code. If your team built a prototype with AI tools like Cursor or Bolt, I assess whether it is ready for production or needs hardening. Not every fractional CTO codes — but the ones who do bring a different level of credibility with development teams.

3. People: hiring, mentoring, and managing developers

Most SME founders are not qualified to interview developers. They cannot tell a strong engineer from someone who interviews well but ships poorly. A fractional CTO writes job specs, conducts technical interviews, and helps you avoid the £30,000 bad-hire mistake.

Once the team is in place, ongoing mentoring keeps them growing. Code reviews, architecture discussions, and regular one-to-ones turn junior developers into senior contributors — without you hiring a team lead.

4. Vendor management: stopping overspend

SaaS subscriptions, IT support contracts, cloud hosting bills — these accumulate quietly. I have yet to walk into an SME and not find at least £10,000 per year in unnecessary spending. Duplicate tools, oversized licenses, contracts that auto-renewed at inflated rates.

Vendors behave differently when a CTO is in the room. I review contracts, benchmark costs, and negotiate on your behalf. The savings from the first vendor audit often pay for the entire engagement. A technology health check is the fastest way to surface these hidden costs.

What a typical week looks like

On a 4-day-per-month engagement (the most common), a typical month might look like:

Day 1:Leadership meeting, review last sprint’s output, update the technology roadmap, handle any urgent decisions that queued up during the week.

Day 2:Deep technical work — architecture review for a new feature, code reviews, security audit of a proposed integration.

Day 3: Vendor evaluation or contract negotiation. Interview a developer candidate. Review the automation pipeline we are building.

Day 4: Team mentoring session, document key decisions, prepare the board update on technology progress.

Between those days, I am available on Slack for quick decisions. Most questions take 5 minutes to answer but would cost your team 5 days of going down the wrong path.

What a fractional CTO does NOT do

A fractional CTO is not your IT support helpdesk. They do not reset passwords, fix printers, or troubleshoot Wi-Fi. They do not project-manage your development sprints day-to-day (that is a delivery manager or scrum master). And they do not replace your development team — they make your existing team significantly more effective.

Is it right for your business?

If you are spending more than £50,000 per year on technology, have developers (in-house or outsourced) without senior oversight, or are making technology decisions that feel like guesses — a fractional CTO will almost certainly save you more than they cost. Read about the 5 signs your SME needs a fractional CTO or check what it costs in the UK.

Frequently asked questions

What does a fractional CTO do day-to-day?

A fractional CTO typically spends their time on technology strategy, architecture reviews, vendor negotiations, security oversight, team mentoring, and key hiring decisions — usually 2 to 8 days per month.

How is a fractional CTO different from a consultant?

A consultant delivers a report and leaves. A fractional CTO is embedded in your business — they attend leadership meetings, make ongoing decisions, and are accountable for outcomes over months or years.

Does a fractional CTO write code?

Some do, some do not. At SelectWise, the fractional CTO both architects systems and writes production code alongside your team — not just strategy documents.

See if a fractional CTO fits your business

Free 15-minute call. No pitch, no obligation — just honest advice on whether you need one.

Book a free consultationTake the AI Readiness Quiz
JS
Jan Sevcik
Technology Advisor at SelectWise. 22 years in enterprise technology, now helping SMEs make better technology decisions.