Fractional CTO vs technical co-founder.

A non-technical founder choosing between hiring a fractional CTO and finding a technical co-founder is choosing between cash and equity, between bounded engagement and lifetime commitment, and between two different shapes that are not substitutes for each other. The decision sequence matters more than the comparison.

Non-technical founders ask me this question often enough that the comparison is worth writing down. The market sells fractional CTO retainers as "CTO without the equity," which sounds like the better deal until you realise the missing equity is also missing the commitment, the alignment, and the founder-level willingness to wade into the parts of the work that nobody is paying for.

Here is the honest version.

The thing that actually decides it.

Are you pre-product, or post-product? That is not a casual question. It is structurally the deal-decider, because the work that needs doing in each state is different.

Pre-product, the technical work IS the product. Building it correctly the first time, choosing the architecture that will not need to be torn out at Series A, taking on the long-term maintenance burden of every shortcut, and being the person on the other side of every difficult engineering tradeoff for the first eighteen months. Nobody does that work for a monthly fee. The structural problem is that the person with the most context, the most ownership, and the most painful nights when something breaks at 3am is the one who needs to be making those calls. That role is a co-founder. Hiring a fractional CTO into it is asking the wrong shape to do the work; the engagement falls apart when the first hard tradeoff arrives and the operator's incentive (preserve the retainer) does not match the founder's incentive (preserve the company).

Post-product, the founding-engineering work is done. Someone built the system. Real users are using it. The founder is no longer the only person making technical calls. What you need now is senior judgment on the architecture decisions that compound, on the senior hires you are about to make for the first time, and on the technical narrative for the Series-A pitch. That is precisely what a fractional CTO is good at. The hourly investment is small; the leverage is high. The retainer earns its keep on those specific decisions, not on building the product.

If you are pre-product, find a co-founder. If you are post-product and need senior judgment in the room every week, fractional fits. The middle case (post-product but no specific senior-judgment work to do) usually wants a paid hourly advisor, not either of these.

The cap-table question is the second filter.

If you have decided pre-product = co-founder, the next question is one most non-technical founders avoid: what equity are you willing to give up?

A technical co-founder at the founding stage typically takes 20% to 40% equity with a four-year vest and one-year cliff. The range moves higher (often 30-50%) if the non-technical founder is pre-traction or has not raised. That is the price of full-time, founder-level commitment from someone who could otherwise have been a senior engineer at a funded startup making €120K-€180K. They are absorbing 18-24 months of foregone senior-engineer wages in exchange for that equity stake.

Founders who are not willing to give up 20-40% equity usually are not willing to find a co-founder. Then the conversation gets honest: either you find someone you can convince to take 10-15% (rare, and usually it is rare for a reason), or you accept that you will be building this product without a technical co-founder, which means you are either learning to build it yourself or commissioning the build under a fractional or contracting arrangement.

This is where fractional CTO conversations often surface, and where they often go wrong. The fractional CTO at €8K-€12K per month is offered as a substitute for the missing technical co-founder. Same role, different price tag. It is not the same role.

What a fractional CTO will not do (that a co-founder will).

Three things that come up in every engagement I have ever turned down at the wrong stage.

A fractional CTO will not write the founding code. They will review yours, advise on architecture, point out where it is going to bite at scale. They will not be in the codebase at 2am when the deploy breaks; that has to be the founder or the founder's contracted dev shop. A co-founder writes the code, owns it, and absorbs the maintenance burden as their own.

A fractional CTO will not pitch alongside you to the early customers. The credibility of having a named technical lead is something they can lend on a slide deck or in a board prep, not something they bring to early customer conversations. A co-founder is in the room for the first ten enterprise customer calls, named in the pitch, attached to the company narrative.

A fractional CTO will not take the long-term maintenance burden of decisions. Every architectural decision they advise on becomes someone else's problem to maintain. That someone is you or the engineer you hire. A co-founder is the someone, and that changes how the decisions are made.

None of that is a reason to skip the fractional CTO at the right stage. It is a reason not to hire one at the wrong stage and ask them to do co-founder work.

When a fractional CTO is actually the right hire.

You shipped the first version. You are post-product. You have at least one engineer besides yourself, or a contracting team that is shipping. Architectural decisions are starting to matter more than they did at week six. You are three to nine months from a Series-A pitch and the technical narrative needs to be in shape. You have not made a senior engineering hire before and the next one is on your desk.

That is the shape where a fractional CTO at €8K-€12K per month earns its keep. The work is on architecture review, senior screen design, board-prep on the technical narrative, and the calls outside the sprint board. Not on building the product. The product is built; what you are buying is judgment on what to do next with it.

The decision sequence.

Three steps, in order.

First, are you pre-product or post-product? If pre-product, skip to step two. If post-product, skip to step three.

Second (pre-product): are you willing to give up 20-40% equity to a technical co-founder, fully accepting the dilution? If yes, find a co-founder. If no, you have a tighter problem than this essay can solve. Either learn to build the product yourself, or commission the build at full agency rates (which is meaningfully more expensive than a fractional CTO retainer because you are buying both leadership AND production code authorship), or rethink whether the venture as currently scoped is the right one.

Third (post-product): the call comes down to decision volume. If only one or two senior-judgment decisions hit your desk per week, an hourly advisor at €300-€500 per hour is more honest than a retainer. If the volume is higher and reasonably steady, a fractional CTO retainer at €8K per month is the shape that fits. If your team is larger and the role has tipped into needing line-management presence, you are past fractional territory and into a full-time CTO conversation. The 6-question fit check walks through the math.

The mistake non-technical founders make most often is treating the fractional CTO as the answer to a question the role does not answer. If you walk into that engagement asking it to be a co-founder substitute, you will be back here in five months looking for what you actually needed.