Somewhere between “my nephew builds websites” and “we hired a CTO” sits a gap that most established businesses fall into. Your site, your servers, your data, and the automations that hold your week together all matter commercially. But they do not add up to a job you can hire for, and the people you have tried so far, an agency here, a freelancer there, never quite stuck around. Fractional engineering is the name for the model that closes that gap, and after twelve years of doing this work I think it is the most honest way to buy engineering at this size of business.

The short definition

Fractional engineering is senior engineering capability shared across a small number of businesses instead of employed by one. You get the same engineer on a monthly retainer, accountable for building and running your systems, at a fraction of what that person would cost on payroll. The “fractional” refers to the cost and the allocation, not the seniority and not the accountability.

Where the model comes from

You have probably met the pattern already in other departments. A fractional CFO gives a company real financial leadership for two days a month. A fractional CMO brings senior marketing judgement without a director’s salary. The logic is identical here: most established businesses need senior engineering judgement and hands regularly, but not forty hours of them every week. Hiring full-time means paying for the idle hours. Not hiring means nobody owns the systems. Fractional is the third option.

What a fractional engineer actually does

In my practice, a retainer month looks unglamorous from the outside, and that is rather the point. It typically covers:

  • Monitoring and incident response, so problems are found before your customers find them
  • Security updates and dependency maintenance across the site and the servers under it
  • The improvements queue: performance work, new automations, small builds, content architecture
  • A monthly report in plain language, so you always know what you have and what state it is in
  • Being the person who answers when something breaks, including when it breaks at a bad hour

The difference from a support contract is ownership. A support desk resolves tickets against a system nobody there has met. A fractional engineer runs a system they built or audited themselves, which changes both the speed and the quality of every decision.

Fractional engineering is not a fractional CTO

The terms get blurred, so it is worth separating them. A fractional CTO is an advisory role: strategy, hiring plans, architecture reviews, board slides. Valuable, but nobody patches a server. Fractional engineering is the delivery layer: the systems themselves, built, maintained, and improved. For most established businesses under, say, fifty people, the honest need is the second one. Strategy questions do come up, and a good fractional engineer answers them, but the reason you sleep better is that someone competent is actually holding the systems.

What it costs, honestly

A single senior engineer in Europe typically costs somewhere in the region of €6,000 to €9,000 a month once you count salary, employer taxes, tools, and management. That buys one person, in one discipline. My Operate retainers run from €1,200 a month for monitoring and maintenance to €5,000 a month for a fully embedded partnership, covering infrastructure, web, data, and automation together. The full breakdown is on the pricing page, fixed and public, because a model built on trust should not hide its numbers.

The catch to watch for

Fractional has a failure mode, and you should screen for it: over-subscription. An engineer serving fifteen clients is not fractional, they are diluted, and you will feel it the first time two clients have a bad day at once. Ask any fractional provider how many clients they take. I cap mine at three, which is the number at which every system still fits in one head. Whatever the number, it should exist, it should be stated, and it should be small.

Is it right for your business?

The model fits if most of these are true: your revenue depends on your site and systems working; things have broken before and nobody could say whose job it was; you are past the cheapest-option stage but nowhere near justifying a €70,000+ engineering salary; and you want one accountable person rather than a rotation of strangers. It does not fit if you need a large product team shipping daily, or if your systems genuinely do not matter to revenue yet.

If the description sounds like your business, the longer explanation of how I run the model lives on the fractional engineering page, and the way to test the fit is a free 45-minute diagnostic call. No pitch. You describe what is going wrong, and you leave knowing what is actually causing it, whether or not we go further.