Retainer vs Project: How Fractional CTOs Actually Work With Scale-Ups

What a Retainer with a Fractional CTO Buys You

A retainer is structured continuity, which means you pay for someone to own a set of strategic and operational outcomes across weeks and months.

In my fractional engagements, a typical retainer covers three things. First, strategic direction and decision-making. I’ll own the product roadmap, technology choices, build vs buy vs partner decisions, and go-to-market sequencing. I make the calls and stand behind them when the board or investors ask questions.

Second, team structure and hiring. Most scale-ups have developers but no clarity on who should lead what. A fractional CTO restructures the team, defines roles properly, and either hires the right permanent leaders or sets up the organisation so you can hire them later without undoing everything.

Third, operational rhythm and governance. This is the least visible but often the most valuable part. Setting up decision frameworks, sprint structure, reporting cadence, and the rituals everyone aligned without endless meetings. This is the stuff that only works if someone is there every week to course correct when it drifts.

A one-off project can't do these things. They require iteration and correction, where you see if a week two decision pays off in week eight. That's why retainers exist.

When Project Work Makes More Sense

Not every engagement needs a retainer. Some problems have a clear start and end point. The scope is bounded and the output is a discrete artefact or decision.

Technology strategy sprints are a common example: a four-week engagement to assess your current platform, map dependencies, and produce a roadmap with clear build/buy/partner recommendations. You get a strategy document, a costed plan, and a handover session. Then you execute it with your own team or bring someone in to oversee delivery.

Due diligence or acquisition support also works well as project work. Any sort time-boxed, high-stakes evaluations that don't need ongoing presence once the report is delivered. The same applies to hiring and team design. Once they're in place, my job is done.

The pattern here is that the deliverable is a plan, a decision, or a structure (not ongoing execution or accountability). If you need someone to stick around and make sure it works, that's a retainer.

How Retainers Are Structured

Most fractional retainers I see in the UK market sit between one and two days per week for about six months. That usually translates to £750–£1,500 per day, depending on the complexity and seniority required. There’s usually an option to extend an engagement or transition to advisory once a permanent hire is in place.

What a day of retained work looks like varies by need, but a common rhythm includes:

• One day on-site or fully embedded with the team
• One half-day for board or investor reporting, strategy work, and planning
• Asynchronous availability throughout the week for urgent decisions, hiring discussions, or stakeholder alignment

The key difference between this and project work is that the retainer isn't tied to producing a specific thing by a deadline. It’s about making the right things happen consistently, week after week, until the organisation no longer needs external leadership in that area.

The Conversation You Should Have Before Signing Anything

The worst retainer engagements I've seen started without a clear conversation about what success looks like. The CEO assumed they were buying strategic advice. The fractional leader assumed they were restructuring the team and roadmap. Three months later, both sides were frustrated.

Before you agree to a retainer structure, get specific on what decisions are you delegating. A retainer only works if the fractional leader has authority. If every product or technology decision still needs CEO sign-off, it’s just expensive advice.

Next, define what 'done' looks like. Even ongoing engagements need exit criteria. In most of my retainers, 'done' means one of three things: we've hired a permanent CTO or CPO and transitioned them in, we've built enough structure and process that the existing team can run without external leadership, or we've reached a natural pivot point where the business needs a different kind of support.

Finally, establish how you'll know if it's working. Retainers can drift into performative presence if there's no feedback loop. Agree upfront on how you'll evaluate progress. If you can't measure whether the engagement is working, it probably isn't.

When to Choose a Retainer Over Project Work

Choose a retainer if the problem is ongoing accountability. If you need someone to own things, make calls that compound over months, and embed structure that survives after they leave, that's a retainer.

Choose project work if the problem is discrete, one-off, scoped and time-boxed.

Most scale-ups I work with start with a project (usually a strategy sprint or discovery phase) and then move into a retainer once the scope and trust are established. That's often the right sequence. You get clarity on what needs fixing, then you bring someone in to fix it and make sure it sticks.