Fractional CTO vs Dev Agency vs First Engineering Hire

You have money in the bank, a product to build, and nobody owning the technology. Three doors: a dev agency, a first engineering hire, a fractional CTO. Behind each one, a salesperson insisting theirs is the obvious choice.

I've sat on every side of this table — four years running Toptal's developer vertical, watching hundreds of companies buy external engineering; VP of Engineering at a venture studio, buying agencies and contractors myself; fractional CTO today. Discount accordingly.

What you're actually buying

Not "development." Three things, in different ratios:

• Decisions — what to build, buy, or skip, in what order.
• Execution — the code itself.
• Context — understanding of your business that makes every next decision cheaper.

Agency = execution. First hire = execution plus slowly compounding context. Fractional CTO = decisions and context, execution where it counts.

Don't know which one is your constraint? Answer that first. Buying execution when your problem is decisions gets you the wrong product, beautifully built, on schedule.

The four questions that matter

What does it really cost? Agency: €60–150/hour, and the €50k MVP has a habit of becoming €120k. First hire: €150k+ real first-year cost once you count employer costs, equity, recruiting, and ramp time. Fractional: a capped monthly retainer, a fraction of the executive salary it substitutes. But sticker price is the least interesting number — the dominant cost in early-stage tech is wrong decisions, and one bad architecture call outprices all three options combined.

Who wins when you spend more? An agency's revenue is your burn rate — your scope creep is their business growth. Not malice; structure. A first hire with no senior counterweight trends toward resume-driven development: the novel stack you'll pay for over years. A fractional CTO on a capped retainer is the only one whose economics reward deleting work — buy over build, kill the feature, prioritize ruthlessly, keep it boring.

Who owns the outcome? The agency owns delivery of a spec; when the spec turns out wrong, that's a change request. A hire owns their code, not strategy they've never done before. A real fractional CTO owns the technical outcome, week to week. If you're getting slide decks and nodding, you bought advisory theatre.

What's left when they leave? Agency: a codebase and a dependency — you can't cheaply let go of the only people who understand the system. Hire: context that walks out with the average 2–3 year tenure. Fractional done right: documented architecture, decision records, a hiring bar, and eventually the team that replaces them. If the plan doesn't make them progressively less necessary, that's a permanent line item, not leadership.

The decision in one table

	Dev agency	First hire	Fractional CTO
Cost	Hourly; meter runs	€150k+ real year one	Fixed, capped retainer
Best at	Bounded, specified execution	Continuous product work	Decisions, direction, hiring
Incentives	More scope = more revenue	Job security, CV	Rewarded for deleting work
Owns	The spec	Their code	The outcome
Leaves behind	Codebase + dependency	Context, if they stay	Docs, hiring bar, a team
Unwinding	Hard — they hold the context	Painful	Easy — that's the design

When each is right

• Agency — bounded, well-specified work under existing technical leadership. Agencies under a CTO: great tool. Agencies as the CTO: how budgets die.
• First hire — continuous product work past validation, with someone senior to define the role and hold the bar. I was that early hire at Farmeron; it worked because there was direction above me while I grew.
• Fractional — revenue, small team, irreversible decisions piling up. Or an agency nobody technical is supervising — that alone usually pays the retainer.

One more for the "hire fractional CTO Europe" searchers: US rates run $10–20k+/month. Senior CEE talent delivers the same tier of scar tissue at materially lower rates, on EU timezones and EU contracts. I've shipped for US companies from Zagreb for fifteen years — the only remote thing about the work was the invoice address.

The honest close

Sometimes the right answer is the agency or the hire — and a good fractional CTO will tell you so, because they're the only one at the table whose incentives allow it. If you're weighing this now, here are the four ways I work with companies. The first conversation occasionally ends with "you don't need me yet." That's the product.