Do you actually need a fractional CTO at seed stage?

Most seed-stage founders do not. The conversation gets sold to founders who would be better served by a paid advisor on a few hours a month, or by hiring their second engineer earlier. Here is how to tell if you are the exception, and what to spend the same money on if you are not.

I get this question often enough from seed-stage founders that I think the honest version of it is worth writing down. The fractional CTO market wants every seed founder to think they need one. The seed founder's actual interests usually point the other way.

Here is how I think about it when someone asks.

The two questions that decide it

The first one is uncomfortable: do you have a working product with paying users, or are you still pre-product? If you are pre-product, hiring a fractional CTO at €8K per month is a very expensive substitute for either a technical co-founder or for finishing the build yourself. There is no architecture review to do because there is no architecture. There are no engineers to manage because there are no engineers. The work a fractional CTO is good at simply does not exist yet. You will end up paying for senior conversation, which is real but is not what you needed.

The second one: have you, in the last sixty days, made the same kind of architectural decision badly twice, and can you name the cost in engineer-weeks? The pattern looks like picking a queueing system, hating it, switching to a different one, hitting the same problem, and now staring at a third option without knowing what you missed. Or onboarding a new engineer twice into completely different codebases because you re-platformed without writing down why. If that pattern is recognisable AND you can name the engineer-week cost it has already imposed, a senior reviewer on those decisions has real leverage. The €8K is buying you out of repeating that specific cost. If you cannot name the cost, the €8K is a status purchase.

If both answers are yes, you are probably the exception. Read on. If either is no, the rest of this essay is about how to spend the same money better.

The cheaper alternative when the answer is no

The most underrated move at seed stage is hiring a paid technical advisor on a 4-to-6 hour per month engagement at €300 to €500 per hour. That is €1,500 to €3,000 per month for the same access to senior judgment, without the operational shape of a retainer. You get the conversations you actually need (architectural sanity check, hiring panel for a senior role, vendor audit) and you skip the parts of fractional CTO work that do not apply to you yet (weekly cadence, monthly written reviews, hiring pipeline support for roles you are not hiring).

I tell founders to try this for three months before they consider a retainer. Track the questions you actually bring to the advisor. If at the end of three months you find you have wanted them in the room more than they were available, the retainer is the right next step. If you have wanted them less, you saved €15K to €25K and learned what you needed.

The other underrated move is hiring your second engineer six weeks earlier than you planned. If the architectural mistakes are happening because the founder is the only senior person making decisions, the right fix is rarely a part-time external brain. It is full-time internal capacity at the next experience tier. €8K per month buys roughly half of a strong mid-level engineer's monthly compensation in most EU markets. Spend it there if your bottleneck is execution, not judgment.

The seed-stage founder who actually fits

The trait that does the most filtering is the third one below. The first two describe almost every seed founder; the third filters most of them out.

One, the founder is technical but stretched. They wrote the original product. They still ship code. Their judgment is good, but the volume of decisions has outgrown the time they have to make them carefully, and they are starting to make architecture decisions in twenty minutes that should take an afternoon. Almost every seed founder fits this; do not over-weight it.

Two, they have a Series-A target window three to six months out. Same caveat: a lot of seed-stage founders fit this band. Useful as a calendar marker, not as a filter.

Three, and this is the one with teeth: they have a specific named decision the retainer is solving for, and they can describe it in one sentence on the discovery call. A senior hire they have not made before, and they need to ship the JD next week. A platform decision (multi-tenancy, event-streaming, managed-service-versus-self-host) where the wrong call costs eighteen months. A regulator question that just landed on them. The retainer earns its keep on that specific call; the rest of the rhythm is supporting work.

If you can name the third trait in one sentence, the conversation is worth having. If you cannot, the paid-advisor route is probably the right fit. If you have to invent a problem to fit the retainer, do not buy.

What pre-Series-A founders actually need that is not a fractional CTO

Three things, in order of how often they get neglected.

First, the boring one: writing decisions down. The thing that actually limits a small team is not lack of senior judgment, it is loss of context as the team grows. Every architectural decision should land in a one-page document with the date, the problem, the options considered, and the choice with reasoning. Most teams do this for the first six weeks and then stop. The team that keeps doing it past month nine is the team whose third engineer onboards in a week instead of a month. This is a habit, not a hire.

Second, a senior reviewer for the technical narrative before the Series-A pitch. Two or three sessions, paid by the hour, with someone who has read enough Series-A decks that they can tell you which slide is going to get you cut on the technical question. This is the highest-leverage technical work most seed-stage founders never buy and badly need. It is not a fractional CTO engagement; it is project work, billable as one or two days of senior advisory.

Third, hiring help on the first senior engineer. The first senior engineer is the highest-stakes hire a seed-stage founder will make for the next twelve months. A wrong hire eats six months of momentum. A right hire compounds for years. Buy help on the JD, the screen, and the panel for that one hire. Pay by the role, not by the month.

If you decide the answer is yes, anyway

If you have read this far and you still think you fit the exception case, two things to do before signing a retainer.

One, take the four-week pilot rather than committing to a six-month minimum from day one. Most senior fractional CTOs will offer one. Use the pilot to verify that the operator actually moves the needle on the specific decisions you brought into the engagement. If after four weeks you cannot point to two decisions where their input changed the outcome, do not extend.

Two, write down before the pilot starts what you expect the engagement to solve. The single most common failure mode of seed-stage retainers is that the founder hires senior judgment and then never brings the questions to the call. Decide in advance what the three or four hard decisions of the next quarter are going to be, and run those through the operator first. If the operator moves the needle on those, the rest of the rhythm follows naturally.