What a Fractional CTO Costs in Spain in 2026 (and What the Price Is Actually Buying)

Ask five vendors what a fractional CTO costs and you will get five numbers that cannot all be describing the same service. US-market listicles quote anywhere from five to twenty-five thousand dollars a month. Spanish guides land in the two-to-six-thousand-euro range. And I sell the seat from a few hundred euros a month. The spread is not dishonesty; it is that «fractional CTO» names a role, not a quantity, and nobody is telling you the quantity.

I have been a CTO for a long time, and I have been the fractional one for founders who could not yet justify the full-time one. So let me do what the listicles do not: give you the hourly rate behind each price, the formats the rate turns into, and the honest answer to what each format can and cannot do.

The price is a rate times a fraction, so start with the rate

Every fractional CTO price decomposes into two numbers: an hourly rate for a senior technical lead and the fraction of a month you are buying. Vendors hide the decomposition because a monthly figure sounds like a product. Ours, in the open: a senior lead bills at €22–28 an hour, on a monthly invoice, with 30-day notice. That rate is the same one an embedded senior engineer bills at on our bench; the CTO seat is not a premium tier, it is a different use of the same seniority.

From there the formats are arithmetic:

• Advisory — two days a month (about 16 hours). Architecture reviews, hiring interviews, board and investor preparation, a second opinion on every irreversible decision. From roughly €350 a month.
• Fractional — one day a week (about 32 hours a month). Owns the technical roadmap, runs the engineering rituals, reviews the pull requests that matter, sits in your planning. From roughly €700 a month.
• Embedded — half-time (about 80 hours a month). Acts as your CTO to the team, the vendors and the investors, and keeps code in the loop. From roughly €1,760 a month.

Compare that with the Spanish guides that put a fractional CTO at €2,000–6,000 a month and the US pages that start at $5,000. Those figures are not wrong for what they describe — they usually bundle a fixed retainer, a minimum term and a single individual's personal brand. The difference in our number is structural: the rate is published, the fraction is yours to set, and the seat is backed by a bench, so the person does not disappear on holiday.

What you are buying is a decision set, not a calendar slot

I made this argument at length in what CTO-as-a-service actually is, so I will compress it. The value of a CTO is concentrated in a small number of decisions that are expensive to reverse: the data model, the deployment and hosting strategy, the first three engineering hires, the answer to «should this be an LLM feature or a rule», the technical narrative you give an investor. A full-time CTO makes those decisions and then spends the rest of the month on everything else — which is fine when there is an «everything else» worth a full salary.

At two to fifteen people, there usually is not. The decision set fits in two days a month; the calendar does not need to be filled to make the decisions good. That is why the advisory format is not a lesser product. It is the product, with the idle time removed.

Where the cheap format stops working, and you should pay for more

I will concede the objection before you raise it: two days a month is not enough for every company, and a vendor who pretends otherwise is selling you a number. The advisory format stops working at three identifiable points:

1. When the team crosses five engineers. Below that, the founder can still run the day-to-day and the CTO reviews. Above it, somebody has to run the rituals, unblock the mid-level engineers and hold the quality bar every week, not every fortnight. That is the one-day-a-week format.
2. When you are shipping AI into a product with real users. An LLM feature that is a demo costs nothing to get wrong. One that is billing tokens on production traffic needs evals, cost limits and observability designed by someone who has done it — and reviewed weekly, because the model behind it will change under you.
3. When the investors are doing technical due diligence. For a funding round, the CTO seat needs to be in the room for the six weeks it takes, and the person needs to have written the architecture they are defending. That is a half-time month, sometimes two.

The right reading of the price list is not «cheapest format wins». It is buy the smallest fraction that covers the decisions in front of you this quarter, and move up when the decisions do. Because the fraction is monthly and the notice is 30 days, moving up and back down costs nothing but the conversation.

What the price does not include, in every format

Three things are not in any fractional CTO's fee, ours included, and founders regularly assume they are:

• The hands. A CTO decides; engineers build. If the roadmap needs building, that is a separate line — an embedded engineer, a squad, or your own hires. A fractional CTO who also writes most of the code is either overpriced as a CTO or underpriced as an engineer.
• Availability at every hour. The seat is fractional. Incidents outside the agreed days go to whoever is on call, which should be someone with root access who is not your part-time CTO.
• Equity-aligned incentives. A fractional CTO is paid in cash and leaves cleanly. That is a feature for the founder who wants to hire a full-time one later without a cap-table problem, and a limitation for the founder who wants a co-founder. Know which one you want before you shop.

Five moments when paying beats not paying

The cost question is only half the decision; the other half is whether the seat is needed at all. In my experience the five moments are these, and each one has a price of not having the seat:

1. Your roadmap is decided by whoever argues loudest. The cost is a rewrite at month nine.
2. You are about to hire your first engineers and nobody can interview them. The cost is a mis-hire, which in Spain, with severance, is the most expensive mistake on this list.
3. Investors ask technical questions you answer with adjectives. The cost is a valuation haircut you never see itemised.
4. An agency built the product and now nobody owns it. The cost is a second build.
5. You need AI in the product and cannot tell a demo from a system. The cost is a feature that impresses in the pitch and bills you in production.

If none of the five applies, keep your money. If two do, the advisory format pays for itself the first time it prevents one of the outcomes above — and at a few hundred euros a month, it does not need to prevent much.

The honest summary

A fractional CTO in Spain in 2026 costs whatever the vendor's hourly rate is, times the fraction of a month you buy. Ask for both numbers. If a vendor will only give you the monthly figure, you are being sold a retainer, not a seat. Ours are €22–28 an hour and a fraction you choose — the three formats are on the service page, and the first conversation, where we tell you whether you need the seat at all, costs nothing.