Fractional CTO vs full-time CTO vs agency: which fits?

Full-time CTO if tech is the product and you can fund it for years. Fractional CTO for senior decisions part-time. Agency for a fixed, written scope.

· Comparison · · 8 min read

Hire a full-time CTO when technology is the product, the team needs a leader in the room every day, and you can fund a senior salary for years. Take a fractional CTO when you need senior technical decisions and a delivery rhythm now, without 40 hours a week of them. Use an agency when the scope is written down and someone on your side can judge the result. Most early-stage and scaling companies need the fractional option first.

I have sat in all three seats: CTO at Onport through its acquisitions by Farfetch and Vinted, a decade running a technical consultancy that delivered agency-style projects, and now fractional CTO alongside running LeaderNova. What follows is how I would choose if I were the founder.

How do the three options compare?

Fractional CTO Full-time CTO Agency
Cost model Monthly retainer for a block of hours. Salary plus employer contributions, severance accrual (TFR in Italy) and usually equity Fixed price per project, or time and materials at a day rate per role
Time to start Weeks Months: search, interviews, then the candidate's notice period Weeks, after scoping and contract
Commitment Monthly, ends with notice Permanent contract, equity vesting One project or statement of work at a time
What you own at the end Written decisions (roadmap, architecture notes, risk register), a team that stays yours, code and accounts in your name Whatever the CTO built and wrote down; what stayed in their head leaves with them The delivered code, if the contract assigns the IP; check who holds the cloud and tool accounts
Who is accountable A named person for technical direction and delivery cadence; you keep the business priorities The CTO, fully The agency, for the contracted scope until acceptance or the warranty ends
Best fit Seed to growth stage, SMBs with developers but no tech leader, an AI-built MVP heading to production, due diligence coming up Technology is the core asset; a large team needs daily leadership A defined build, with technical judgement already in-house
Poor fit You need someone present five days a week managing a big team You can't yet describe the job, or the budget only lasts a year The scope keeps moving and nobody on your side can review the work

When is a full-time CTO the right call?

A full-time CTO makes sense when the technology is what investors are buying, when the team is big enough that people management, hiring and architecture fill a week, and when the company can carry the cost long enough for the hire to pay off.

The cost is real. The Hays Salary Guide 2025 puts the average gross annual salary for a CIO or CTO in Italy with more than ten years' experience at €95,000 to €100,000, highest in Milan (Money.it, 30 October 2025). Payscale's Italian data, updated 29 December 2025 and based on only 21 profiles, shows a lower average base salary of about €76,000 (Payscale). Either way, the cost to the company is higher once employer contributions and TFR are added, and startups usually add equity on top.

The bigger risk is hiring too early. If you can't yet say what the CTO will decide in their first 90 days, you are paying a full salary for someone to discover the job. A wrong senior hire costs the months of searching, the months it takes to see it isn't working, and the decisions made in between.

When is a fractional CTO the right call?

A fractional CTO fits when the problems are leadership problems: priorities change every week, nothing finishes, releases scare people, the founder is the bottleneck on every technical decision. Adding engineers to that makes it worse. What helps is someone who sets the architecture direction, slices the backlog so work closes within a sprint, and gives every decision a named owner.

At LeaderNova this is the fractional CTO engagement we call Leadership as a Service. It runs on a weekly cadence inside your team's own tools: leadership blocks, backlog review, sprint planning, and progress reported in numbers the board can read. Cost depends on how many hours a week the role needs, whether it includes hiring or technical due diligence, and whether it comes with delivery capacity from our product team.

Investors sometimes ask whether outsourced tech leadership is a red flag. In my experience the question behind it is "who answers for the technology?" A fractional CTO who presents the roadmap, the security posture and the delivery metrics to the board answers it. A vacant seat doesn't.

When our fractional CTO is the wrong choice

  • You need daily presence. If the team is large enough that someone has to run one-to-ones, unblock people every morning and sit in every planning session, a part-time role will always be behind. Hire full-time.
  • You need a co-founder. If the company's story depends on a technical co-founder with significant equity, a fractional engagement is a bridge at best. We can help you hire that person; we can't be them.
  • You need hands, and you have judgement. If a senior engineer on your side already makes good technical decisions and you only need more capacity, an agency or a dedicated product team is the better use of the budget.

When a client is ready for a full-time CTO, our job changes: we define the profile, assess candidates technically, and run a 60-day handover of the risk register, decisions and procedures. After that we either stay on with fewer hours to support the new CTO, or step away with normal notice.

When is an agency the right call?

An agency is the efficient choice for a well-defined build: a marketing site, an integration with a documented API, a mobile app whose screens and flows are already designed. You pay for the scope, the agency manages its own people, and you get a finished deliverable.

It works when two conditions hold. The scope is stable enough to write down, so change requests don't eat the budget. And someone on your side can review what comes back: the architecture, the security, whether the next team can maintain the code. Without that person, you are accepting a delivery you can't judge.

Agencies are built to finish projects. Product decisions, trade-offs between features and the roadmap after launch usually sit outside the contract. That is a fair business model, as long as you know who owns those decisions on your side.

What changes six months after launch?

The three options look most different six months after go-live, and that is where most of the cost hides.

Ownership of code and accounts. Check whose name is on the repository, the cloud account, the domain, the app store listing and the third-party API keys. With a full-time CTO they are yours by default. With an agency it depends on the contract, and "we'll transfer it at the end" is a common source of friction. In every LeaderNova engagement the client owns the code and the accounts from day one.

Someone who answers for it. Software keeps needing decisions after it ships: a dependency with a vulnerability, a spike on the cloud bill, a regulator's question about where the data lives. A full-time CTO answers by definition. A fractional CTO answers within the agreed hours, as a named person. An agency answers if you bought a maintenance contract, for what that contract covers.

AI-written code. Every option now ships code written with Claude Code, Cursor or Copilot. That is fine, as long as someone reviews it, gates it with tests and security scans, and decides what the tools are allowed to touch. Ask any candidate, fractional or full-time, and any agency, how they review AI-written changes before they reach production. A vague answer tells you how the codebase will look in a year.

How to decide: five questions

  1. Can you describe what the technology leader will decide in the next 90 days? No → start fractional and let the job take shape.
  2. Is technology the core asset investors are buying, with a team that needs daily leadership? Yes, and you can fund it for several years → hire full-time.
  3. Is the scope written down and stable, with a technical reviewer on your side? Yes → an agency is efficient.
  4. Who will answer for the system after launch, by name? If the honest answer is "nobody", fix that before choosing anyone to build.
  5. Will the code, accounts and documentation be in your name at the end? Get it in writing, whatever you pick.

If you are still unsure whether you need a CTO at all, this longer piece on when fractional leadership fits covers what a fractional CTO should own in the first 90 days.


If you are weighing these options right now, book a 30-minute strategy call. We'll look at your stage, your team and what's blocking delivery, and tell you plainly which of the three fits, including when it isn't us. Book a strategy call

Tell us what you're building.

Book a strategy call. We'll tell you where we can help, and say so quickly if we can't.

Let's talk