The number is agreed before the work starts.
You do not buy a bag of hours. Builds start at €3,500 and ongoing care at €95 a month, though neither figure means much until the audit works out what the system actually needs. What the audit produces is a scope with one fixed price against it, agreed in writing before anything begins. I take one business per niche per market, so a competitor cannot buy the same system.
The figure this usually gets compared to.
The comparison people reach for first is a hire. A senior engineer in Europe on a €90,000 salary costs €110,000 to €115,000 fully loaded, roughly €9,200 to €9,600 a month once employer contributions, tooling and management are counted, and senior technical recruitment averages 5.4 months. The exact figure moves with the market you hire in. What does not move is that it buys one person in one discipline. The comparison that tells you more is the one against your current setup, which the cost calculator totals, including the parts that never reach an invoice.
Every engagement starts with a short conversation.
The fee is fixed and agreed before any work starts, and a free twenty-five minute conversation comes first, which works out whether there is a problem here worth looking at. The audit itself runs across the servers, the site, the data and the automations between them, and ends in a written assessment you own. The contact page covers what is in it.
If a build or a retainer follows, I credit the €450 in full against it.
Book a 25-minute diagnosticBuild engagements.
One-time builds, scoped after the audit and delivered against milestones.
Not everything needs operating.
A site with a contact form on it and a platform with moving parts do not need the same attention, and they are not charged as though they do. This is the light option, for a system built here that needs keeping safe rather than watching over. It does not take one of the three engagement slots.
Or €950 paid annually. Only on a system built or rebuilt here.
Book a 25-minute diagnosticOngoing care, matched to the system.
Four levels, matched to how much operational surface the system actually has. Partner is the level I recommend by default. It is the first one where engineering is part of the month rather than changes as they come up, and what a business gets from keeping one engineer is mostly what that engineer builds next. The three levels above Upkeep are a cap on the monthly bill, not a quantity of hours. Retainers bill monthly in advance. Upkeep does not use one of the three engagements I run at a time, because it is built to need almost none of the attention that cap exists to protect.
Starting points across all four disciplines.
Every service can be built here, or taken on and operated afterwards. Optimising happens inside an engagement rather than as something you buy on its own.
Servers, DNS, security, pipelines. I keep them up.
Your site stops describing the business you were two years ago.
Your CRM, your content and your reporting, connected, so you can see what is happening.
The copying between tools that somebody on your team is still doing by hand.
Questions this usually comes down to
The price starts with the problem.
Every number on this page is a starting point until the audit produces a scope, and the twenty-five minutes is where you find out whether the audit is worth doing at all.
Twenty-five minutes on Google Meet, and a straight answer either way.
- 01
You describe what you are running, in whatever words you use for it internally.
- 02
You get a straight answer on whether the audit is worth doing at all, including when it is not.