Fractional Is Not Interim | What A Fractional CTO Actually Is, And When You Want The Other One

There are two different things a mid-market company buys when it does not have a chief technology officer, and in conversation they get the same name. That causes real damage at contract time. An interim CTO fills a seat that has become empty. A fractional CTO occupies a seat you were never going to fill. Those are different purchases. Different durations, different deliverables, and a completely different answer to the question of what happens at the end. Buy one thinking it is the other and you will be disappointed on schedule, at around month four. One disclosure before I go further. We sell fractional services. So take the framing for what it is worth, and test it against your own situation rather than mine. Start with what each one is actually for. An interim CTO is a response to a gap. Somebody left, or is about to, and the roadmap cannot stop while you run a search. The engagement is full-time or close to it, it is measured in months, and its success condition is a handover. A good interim CTO makes themselves unnecessary, and then goes. A fractional CTO is a response to a shape. The company needs senior technology judgment, architecture, sequencing, vendor decisions, hiring calls, but it needs perhaps a day a week of it, and it will still need a day a week of it in two years. There is nothing to hand over to, because the alternative was never a full-time hire. The alternative was nobody. Same skills. Different problem entirely. So the word doing the work here is not part-time. It is standing. A fractional arrangement is a continuing relationship with a decision-maker who already knows your estate. That last part is the entire value, and it is the part you cannot buy in hours. The reason a fractional CTO is useful in month eighteen is that they were there in month two, when the integration was designed, and they remember why it was designed that way. Which also says what a fractional arrangement is not. It is not staff augmentation, because you are not buying capacity. It is not advisory, because advice does not carry accountability. And it is not just cheaper seniority, although it usually is cheaper. The price is a consequence of the shape rather than the reason for it. Three questions will tell you which one you are shopping for. One. Is there a seat that is currently empty, and do you intend to fill it? If yes to both, you want interim, and you want the handover written into the engagement on day one rather than negotiated at the end of it. Two. In two years, will you need this judgment less than you need it today? If the honest answer is no, a temporary arrangement will get renewed until it becomes permanent by accident. That is the worst version of both options. You pay interim rates for a fractional need, and you never get the continuity you were paying for. Three. Who is accountable if a decision turns out to be wrong? Not who advised. Who is accountable. If the arrangement has no answer to that, you bought hours, whatever the invoice calls it. Here is what buying the wrong one looks like, and the reason it is worth describing is that it does not look like a failure at first. You bring in someone excellent, on an interim basis, to steady a stack nobody owns. They do it. They write the plan, they make the calls, they get the stalled integration project moving again. Then the engagement ends, because interim engagements are supposed to end. And the plan they wrote stays on the shared drive. Eight months later the same class of decision comes back, because decisions in a business systems estate are not one-time events. They recur every time something is added, replaced or connected. And now there is nobody with the context to make them. So they get made by whoever is nearest, which is usually the person who owns the tool rather than the person who owns the outcome. One last thing, because this is where the distinction stops being semantic. A fractional arrangement is not a substitute for implementation, integration or managed operations. It is what makes those three coherent. Somebody has to decide the sequence, hold the architecture, and say no to the request that will cost more later than it saves now. That is a different job from doing the work, and it does not disappear when the work is outsourced well. If you have three vendors and nobody deciding between them, you do not have a technology problem. You have a missing role. And it is not a full-time one. So, plainly. Interim fills a seat. Fractional occupies one you were not going to fill. Ask whether the need shrinks in two years, and ask who is accountable when a call goes wrong. We are CodeStringers. Fractional technology leadership is one of our four service lines, alongside implementation, integration and managed technical operations, and it exists to hold the other three together rather than to stand in for a hire you have not made. If you are about to write a job description you privately doubt you need, that is the moment this distinction is worth twenty minutes of your time.