Fractional means you buy senior technology leadership by the day, not by the salary. You get a CTO or CIO for one or two days a week, on a rolling retainer, with the seniority of someone who has done the job rather than only advised on it. What follows is how the engagement actually runs week to week, what it costs against a full-time hire, how the delivery side is handled, and where it is the wrong answer.
The three ways it usually runs
Retained days. The most common model. One or two days a week on a monthly retainer, holding the technology seat, setting direction, leading the team and reporting to the board. Predictable cost, steady presence. This is the model for a business that needs a technology leader in the room regularly but not daily.
Project-based. A fixed piece of work with a clear outcome, a technology review, a re-platform plan, due diligence support for a raise. Scoped, priced and time-boxed. This suits a business with a specific question to answer or a specific thing to get done, rather than an ongoing need.
Light advisory. A few hours a month for a founder or team who mostly need a sounding board and the occasional hard call. Cheapest, and the right fit when the business is steady and the technology is not the problem.
Most engagements start in one of these and move between them as the need changes. A review turns into retained days. Retained days step up around a raise and step down afterwards. That flexibility is the point, and it is the main thing a full-time hire cannot offer.
What a retained week actually looks like
Take a one-day-a-week arrangement. The day is usually fixed, say Tuesday, so the team knows when to bring decisions. It starts with a short check-in with the founder, what has changed, what needs a call. Then time with the team, reviewing progress, unblocking, making the technical decisions that have been waiting. Then supplier or customer conversations as needed. It ends with a written note, a few lines on what was decided and what is next, so there is a record and the founder is never guessing.
Between days, there is a standing rule. Urgent things get a call. Everything else waits for Tuesday. That discipline is what makes one day a week work. Without it, a fractional CTO becomes an always-on contractor at a part-time rate, which serves nobody.
Two days a week follows the same shape with more room for hands-on work, hiring, and the longer conversations that strategy needs.
What it costs, honestly
A full-time CTO is expensive once you count everything. Base pay in the UK commonly runs £120,000 to £170,000, and the real cost lands nearer £200,000 to £350,000 a year after employer National Insurance, pension, benefits and equity. Add recruitment fees, which are often 20% of salary, and the months the seat sits empty while you search.
Fractional is priced by the day. Typical UK day rates run around £1,000 to £1,600, so one day a week sits roughly at £4,500 to £6,000 a month, two days around double. You pay for the seniority you use, which is why providers often describe fractional as 40 to 50% of the cost of a full-time hire. Treat that as a guide rather than a guarantee, because the honest comparison depends on how many days you actually need. A business that needs four days a week should hire.
The backdrop helps explain the shift. UK vacancies fell to 712,000 in the three months to June 2026, and businesses are reaching for senior help without committing to a permanent salary. Fractional has moved from a workaround to a normal way of buying leadership.
When we lead delivery, and when we bring in a partner
Leadership is one thing, building is another. A fractional CTO sets direction and standards. Somebody still has to write the software. We work two ways, and we are open about which applies.
Sometimes ScaleAround leads the delivery end to end, under one relationship. The fractional CTO holds the seat and our delivery capability does the build, with one point of accountability. Our forward deployed engineering work covers this when the plan calls for real delivery rather than advice alone.
Other times the sensible move is to advise, stay in as the senior lead with the governance, and bring in a trusted engineering partner to do the build. The fractional CTO specifies the work, selects the partner, reviews the quality and holds them to the outcome. Where a referral like that applies, we tell you. You should always know who is doing the work, why, and whether any arrangement sits behind the introduction.
Both models work. The choice depends on the size of the build, the skills needed, and what the business already has. What does not work is a fractional CTO who quietly steers delivery to a partner without saying so.
Where fractional is the wrong answer
It is not a fit for everything, and a straight answer saves everyone time.
If you genuinely need someone in the building five days a week, hire full-time. A product business with 30 engineers and a daily stream of decisions needs a CTO who is there daily.
If you are in a live crisis that needs hands on keyboards around the clock, fractional leadership alone will not cover it, though it can set up and direct the team that does. A platform outage, a breach, a failed migration, these need intensity before they need strategy.
If the scope is vague, fractional struggles, because the model works on clear priorities and accountable outcomes, not open-ended availability. ‘Help with technology’ is not a brief. ‘Own the roadmap, fix delivery and get us through the raise’ is.
And if the founder is not willing to give a couple of hours a week to decisions and context, it fails, because the plan ends up with no owner inside the business.
The common mistakes
Buying too few days for the real need and then being disappointed. Size the days to the problem, review at three months, and adjust.
Treating the fractional CTO as a contractor rather than a leader. Keep them out of leadership conversations and you get a technician.
Not agreeing the delivery model up front. Decide early whether the fractional CTO will lead the build, bring in a partner, or direct your existing team, and write it down. Our piece on what to expect in a fractional CTO contract covers what that agreement should say.
How to size it
Start small. A technology review or a month of retained days tells you how big the need really is before you commit to more. From there the right number of days is easy to judge, and easy to change. The fractional CTO cost page sets out the ranges in more detail.
Frequently asked questions
How many days a week is a fractional CTO?
Usually one or two, on a monthly retainer. Some engagements are lighter, a few hours a month, and some step up temporarily around a raise or a big delivery.
How does fractional compare with a full-time salary?
A full-time CTO costs roughly £200,000 to £350,000 a year all in. Fractional is paid by the day, so a one-day-a-week retainer is a fraction of that. You pay for the time you use.
What happens between the retained days?
Urgent matters get a call. Everything else waits for the next scheduled day. That discipline is what keeps a part-time arrangement working for both sides.
Can a fractional CTO also build the thing?
Leadership and delivery are separate. We either lead delivery ourselves or bring in a trusted engineering partner, and we always tell you which, so you know who is doing the work.
Is fractional right for a business in crisis?
Usually not on its own. A crisis needs intensity. A fractional CTO can direct the response and set up the team, but the hands-on work needs more than a day or two a week until it is stable.
How do we get started?
A short review or a month of retained days, so you see the value before committing further. Start the conversation on our contact page.