What you are paying for each month, in plain terms, including the parts you never see.
The most common question about a retainer is also the most reasonable one: what am I actually paying for each month? Retainers have a reputation problem, earned by every agency that ever invoiced monthly for work nobody could point to. So here is an ordinary month in this practice, in the order it happens. Nothing glamorous appears below, which is rather the point.
The invisible layer: monitoring that never stops
Underneath everything, monitoring runs continuously: uptime checks, performance baselines, security signals, backup verification. Most months this layer produces nothing but quiet confirmation. In the month it produces an alert instead, you hear about the problem from me, with a diagnosis attached, rather than from a customer or a blank screen. This is the part of the retainer you cannot see and would miss most.
The maintenance rhythm
Every month carries a maintenance pass. Security updates go on, dependencies come current, backups get restored somewhere safe to prove they still work, and the small degradations that accumulate in any live system get caught early. A database that has grown sluggish. A plugin update that needs reviewing before it can be trusted. A disk creeping towards full. Individually trivial, and collectively the difference between a system that lasts and one that quietly rots.
The visible layer: the improvements queue
On Partner and Embedded, development work is part of the month. You keep a running queue and it gets worked in priority order: a new automation, a landing page, a performance push, a data report the business suddenly needs. None of it is sold to you as a quantity of hours, because a quantity of hours is a thing you can lose at the end of the month. The fee is a cap on the bill instead. Anything genuinely outside the tier gets quoted before it happens, rather than absorbed quietly and resented later.
Because the same engineer runs the whole system, none of that work carries an onboarding tax. The person building your new automation already knows why your server is configured the way it is.
What you actually receive
Every month closes with a note in plain language: what was monitored and what it showed, what was updated, what was built, what I recommend next, and anything that needs a decision from you. If the month was quiet, the note says it was quiet and why that is good news. You should never have to wonder what a retainer did for you. The answer should arrive in writing.
When something breaks anyway
Systems fail. What the retainer decides is what failure costs you. Incident response sits inside every tier above the routine plan: the monitoring gets there first, usually before you do, and the person who answers is the person who built the thing, which shortens every diagnosis. I answer a message sent through the site the same working day, including the ones I turn down. When two things go wrong at once, Partner and Embedded come first, which a cap of three engagements keeps rare.
The terms, plainly
There are four levels of ongoing care, and only three of them are retainers. Upkeep, at €95 a month or €950 for the year, is a subscription to the routine on a system built or rebuilt here. That means updates with a render check afterwards, security monitoring, backups with a tested restore, certificate and domain expiry watch, and a short monthly note. It excludes server and hosting management, content changes, new pages and features, performance and SEO work, and same-day incident response. It also sits outside the cap of three engagements, because it is built to need almost none of the attention that cap exists to protect.
Above it, Maintain is €1,200 a month for the monitoring-and-maintenance layer, Partner is €2,500 with development work, and Embedded is €5,000. Three months to reach steady state, then rolling monthly with thirty days notice. No annual lock-in, because the only honest reason to keep paying is that leaving somebody who already understands your systems does not make sense. The full breakdown is on the pricing page.
If your current provider invoices monthly and you could not describe what last month contained, that gap is worth examining. Examining it properly is what the audit does: €450, fixed before it starts and credited in full against a build or a retainer if one follows. The document is yours whether anything follows or not. It opens with a free conversation of about twenty-five minutes, which works out whether this is a problem worth looking at and which route you are on. That conversation will not tell you what is wrong with your systems. The audit will, in writing, and the contact page sets out what it covers.