Operate
Handing over is easy. Operating is the work.
Most projects end at launch. After that begins the part nobody sells: updates, outages, security gaps and the small changes that suddenly nobody can make any more. We stay.
We do not hand over and disappear. What we have built, we keep running — if something fails at night, that is our problem and not yours.
Why operation instead of handover
Why operation instead of handover
Whoever built it knows the places
An outside maintainer reads unfamiliar code at every fault. We read our own — which is why the answer to “can that be done quickly?” is usually yes here.
A system ages even when nobody touches it
Dependencies get security gaps, certificates expire, browsers change their rules. None of it announces itself, and none of it waits for the next project budget.
The outage does not come during office hours
It comes at night, at the weekend, on holiday. The question is not whether somebody notices it, but who notices first: the monitoring or your customer.
What turns out to be wrong in operation gets changed
No build survives its first real month unchanged. In a project with a sign-off date something like that gets documented and left standing. In operation it gets changed.
What is included
What is included
Hosting
Servers, domains and certificates — set up, paid for and in our hands.
Monitoring
The site reports when it is unreachable. Not your customer.
Updates
Dependencies and system versions stay current — before a gap becomes an incident.
Security
Access, permissions, headers and transport encryption at the level set when it was built.
Backups
Backed up and restorable. A backup that has never been restored is not one.
Support
One contact who built the system himself. A call back the next working day.
Further development
Whatever turns out to be wrong in operation gets changed — not documented and left standing. Within the monthly changes; anything newly added is a project of its own.
No availability in per cent, no response time in hours, no “24/7”. What is promised is what is written here — and we keep it on holiday too.
Dependency
Operation does not mean dependency.
The system and all the data in it belong to you from day one. Support can be cancelled monthly, with no minimum term. Afterwards everything stays with you — code, content, access and domain. What ends is the support, not your access.
Ongoing support
Operation instead of handover.
After launch the site stays in operation — and we stay reachable. Not a package that administers something, but the person who built it.
Included
- Hosting and security updates
- Up to 2 content changes per month
- Keeping the Google Business Profile current
- An accessibility pass on every change, once a year by hand
- A call back the next working day
Not included
- New pages, new features, a new design — that is a project with its own scope and its own fixed price
- More than two content changes per month (not accumulated, not transferable)
- Writing copy, taking photographs, sourcing content
- Looking after systems that are not ours
- On-call duty, weekend service, a response time promised in hours
Ongoing operation is for systems we built — otherwise we would be answering for code we do not know. If your site already exists and is staying: we will look at it and tell you whether we can take it on. That is a separate question, not a refusal.
Next step
A fixed price for your scope — after twenty minutes.
What is above is the entry point. What your business needs, we look at before anyone names a figure — free and without obligation.