Before you search: do you lack judgment or hands?
Almost every conversation we have about fractional CTO work starts the same way. Someone tells us their tech project is slow, that they are not sure their vendor is charging fairly, or that they have a big decision to make and nobody to ask.
The first question to ask yourself is simple. If you know exactly what you want to build and lack people to build it, you do not need a fractional CTO: you need developers or an agency. If what you lack is someone to decide what to build, in what order and with whom, then you do. We explain it in more depth in fractional CTO or development agency, and the concept itself in what a fractional CTO is.
The questions worth asking in the first meeting
You do not spot a good fractional CTO by their list of technologies. You spot them by how they think when you put a problem in front of them. These questions help:
- Which technical decision did you have to undo later? Anyone who has been deciding for years has one. If the answer is that they have never been wrong, be wary.
- Tell me about a project where your recommendation was not to build. A CTO who only knows how to add development will cost you a lot.
- How many companies do you work with at once, and how many hours will I really get? The commitment has to be in writing, not in a promise.
- Who carries out what you decide? If they also sell development, they should say so clearly and explain how they avoid recommending what suits their billing.
- What do you deliver in the first month? A reasonable answer is a written diagnosis with prioritized risks and a plan for the quarter.
- How will we know this is working? They should talk about business milestones and concrete technical indicators, such as deployment frequency or how long it takes to recover from a failure.
- What does the exit look like? Documentation, access, passwords and knowledge must stay with the company on the day the relationship ends.
- Have you worked with personal data? If your product handles customer or patient data, the GDPR is part of the architecture from day one.
Red flags
We have seen enough fractional CTO relationships, ours and other people's, to have this list fairly clear:
- They propose a development team before understanding your problem.
- They ask a lot about technology and little about the business, the customers or the numbers.
- They have a favorite stack and recommend it in every case.
- They will not start with something bounded, such as a two or three week audit.
- They give timelines and budgets without a diagnosis.
- They put nothing in writing: no decisions, no reasons, no discarded alternatives.
- They want the domains, cloud accounts or repository in their name.
- They cannot tell you when you would stop needing them.
Contract models
In Spain there are four common formats. Choosing the right format matters as much as choosing the person:
- Strategic, 5 to 10 hours a week. Direction and judgment with no operational involvement. It fits when there is a team and nobody to decide.
- Operational, 20 to 40 hours a week. They join the team, manage vendors and own the roadmap.
- Full-time interim. They take the CTO seat for a specific phase: a migration, a funding round or the departure of whoever ran technology.
- Fixed-scope project. A goal with a start and an end, such as a technical audit, due diligence or an architecture design.
What the contract should say
We are not lawyers, and an adviser should review yours. But there are things that, from the technical side, we often miss when we are called in to fix a relationship that did not work:
The minimum commitment in hours or days and how it is counted. The deliverables for each period. That the code, domains and cloud accounts belong to the company and are in its name. Confidentiality. Notice to terminate, for both sides. And a quarterly review where you decide to continue, adjust the commitment or stop.
One more detail. The technical quality you ask for at the start shapes what changes will cost later. Martin Fowler explains it very well when he discusses why high quality software ends up cheaper, and it is a good standard to ask your CTO to defend.
What a fractional CTO costs in Spain
These are the ranges we use as a reference for the Spanish market in 2026:
- Fractional: 2,000 to 5,000 euros a month, with two or three days a week.
- Interim: 8,000 to 12,000 euros a month, full-time for a specific phase.
- Fixed-scope project: 4,000 to 15,000 euros, depending on the scope of the audit, due diligence or design.
How to read those prices
The usual comparison is with an in-house CTO's salary, which in Spain ranges from 80,000 to 140,000 euros gross a year plus hiring costs. But almost nobody looking for a fractional CTO was about to hire an in-house one. The real comparison is with carrying on without technical judgment. The full breakdown is in what a fractional CTO costs in Spain, and the rest of our prices are on our pricing page.
When you should not hire a fractional CTO
We say it even if it costs us clients, because a badly framed relationship ends badly for both sides.
If what you need is someone to write code, look for a developer or an agency. If you are fewer than three people and still working out what to sell, technical decisions are cheap to change and the money is better spent talking to customers. If you already have an in-house CTO who works, at most you need a one-off audit or a second opinion. And if nobody in management will have one hour a week to sit with the CTO, do not do it either: without that hour, their decisions go nowhere.
If you want to talk it through
At Elevatec Techlearn, an artificial intelligence agency and fractional CTO based in Madrid, we work as a fractional CTO for startups and SMEs, with the technical side led by Carlos Dodero, lecturer in Artificial Intelligence at Universidad Alfonso X el Sabio.
Book a thirty minute call. Tell us which decision is on the table and we will tell you frankly whether you need a fractional CTO, a one-off audit or simply a good development team.
Sources
External references cited or useful for this article, consulted on November 3, 2026:
Frequently asked questions
Which technical decision they had to undo and what they learned, which project they advised not to build, how many hours you will really get, who carries out their decisions, what they deliver in the first month, how you will measure whether it works and what the exit looks like: documentation, access and knowledge must stay with the company.
As a 2026 market reference, 2,000 to 5,000 euros a month on a fractional basis, 8,000 to 12,000 euros a month as a full-time interim, and 4,000 to 15,000 euros for a fixed-scope project such as a technical audit or due diligence.
Proposing a development team before understanding the problem, asking little about the business, always recommending the same stack, refusing to start with something bounded, giving timelines without a diagnosis, putting nothing in writing or wanting domains and accounts in their own name.
Four common ones: strategic, 5 to 10 hours a week; operational, 20 to 40 hours a week; full-time interim for a specific phase; and a fixed-scope project with a start and end, such as an audit or due diligence.
The minimum commitment, deliverables for each period, that the code, domains and cloud accounts belong to the company, confidentiality, notice to terminate for both sides and a quarterly review. A legal adviser should review it.
When what you need is coding, when the company has fewer than three people and is still working out what to sell, when there is already an in-house CTO who works, or when nobody in management can give it one hour a week.
It depends on what you need next. A freelancer can be a good option if you already have people to execute. A company with a team behind it gives you continuity if the person is unavailable and capacity to carry out decisions, as long as it is clear you are not obliged to hire it for development.