What fractional actually means

A fractional CTO is a senior technology leader engaged part-time, usually for a fixed number of hours per month or a defined retainer scope, rather than as a full-time executive. They are not a contractor building features. They are not a consultant writing a strategy document. They are the technical decision-maker for a business that is not yet at the stage where a full-time CTO makes financial sense.

The distinction matters because both "fractional CTO" and "tech consultant" get used to describe very different things. A tech consultant analyses and recommends. A fractional CTO decides, directs, and is accountable for outcomes. If the person you are engaging will not own the consequences of their recommendations, you have a consultant, not a fractional CTO. Both can be useful. They are not the same thing.

The clearest signals you need one

You are a non-technical founder making technical hiring decisions with no way to evaluate the candidates. Every technical hire you make is essentially a bet based on incomplete information. A fractional CTO evaluates candidates, defines the technical role properly, and can tell the difference between a strong CV and a strong engineer.

Your development team is producing but you do not know if what they are building is right. Code is being delivered. Features are being shipped. But you have no visibility into whether the architecture will hold at scale, whether the security posture is adequate, or whether technical debt is accumulating faster than it is being paid down. You need someone senior enough to give you an honest answer to those questions.

You are approaching a fundraise or a major enterprise sale and technical due diligence is coming. A technical due diligence from a serious investor or a large client will find things your internal team missed. Having a fractional CTO who has been embedded for three to six months means the hard questions have already been asked internally, the gaps have been addressed, and someone credible can represent the technical side of the business.

You need to make a significant technology decision and the stakes are too high to get wrong. Build or buy? Which cloud provider? Rebuild the core product or extend it? These decisions have long tails. A wrong call here costs a year and a significant budget. Paying a senior technologist to own the decision is cheaper than owning the consequences of a bad one.

What a fractional CTO does not do

They do not write code. If you need someone building features, you need a developer. The confusion is common and expensive: hiring a fractional CTO when you need a senior developer means paying executive rates for the wrong work, and the work still does not get done.

They are not a substitute for a technical co-founder. A technical co-founder is equity, commitment, and full presence. A fractional CTO is a hired engagement with a defined scope. Both are valid. They are not interchangeable, and the businesses that have confused them have usually done so at significant cost.

They do not make the business decisions. Technology strategy is always in service of business strategy. A fractional CTO who is making product and business decisions without the domain expertise to make them well is overstepping. The relationship works when there is clear separation: the founder owns the business direction, the fractional CTO owns the technical execution of it.

What it costs in South Africa

Fractional CTO engagements in South Africa typically run on a monthly retainer, with scope defined by hours or by outcomes. The market range for a genuinely senior engagement, someone with real production experience and the commercial literacy to translate between technology and business, is R15,000 to R45,000 per month depending on time commitment and seniority.

Engagements below that range tend to reflect either junior execution dressed up as strategic leadership, or a very limited scope (one meeting per week, minimal availability). Both can be appropriate depending on what you actually need. The number to check against is whether the cost is less than the cost of one bad technical decision at your current stage. For most businesses where this is a live question, it is.

How to evaluate one

Ask them to describe a technical decision they made that turned out to be wrong. How did they find out? How did they address it? What would they do differently? This is not a trap question. Every senior technologist has made expensive mistakes. What you are evaluating is their relationship to being wrong, which predicts how they will operate in your business when things are uncertain.

Ask them what they will not do. A fractional CTO who will take on any scope has no specialisation. You want someone who has a clear view of where they are exceptional and where they would recommend someone else. The ones who claim to cover everything usually cover nothing particularly well.

And ask them how they measure success at the end of an engagement. If the answer is only about deliverables, they are operating as a consultant. If it is about the capability left behind in the business, about what the team can do that they could not do before, you are talking to someone who has thought about what the role is actually for.