Hosting, updates, backups, security and further development with one party, with the arrangements on paper. You should not need to know who your hosting provider is to be able to assume it is taken care of.
We also take over sites we did not build ourselves.
Almost never a deliberate choice. It is something that grew slowly because the builder left or the contract was never updated.
The hosting is with one party, the domain with another, and the site was built by a third who is no longer around. When something breaks, the search begins.
Because nobody dares to do them or because nobody feels responsible for them. Every month that passes makes updating harder and riskier.
A backup you have never restored is an assumption. You only find out whether it works at the moment you need it most.
No monitoring, so you hear it from a customer. No arrangements, so you do not know when someone will look at it.
Not every company needs an SLA. But it does help to know what you actually have right now.
| Managed by us | Arranged piecemeal | |
|---|---|---|
| Point of contact | One party for everything | Hosting, domain and builder all separate |
| Updates | A fixed routine, tested | When someone remembers |
| Backups | Automatic and restore-tested | Usually present, rarely tested |
| Outage | Monitoring spots it first | You hear it from a customer |
| Response time | Set out in the agreement | Depends on who is available |
| Further development | A fixed allowance per period | A separate quote for every wish |
The dull work you only notice once it stops happening.
Hosting and monitoring
Hosting on infrastructure that matches your visitor numbers, with monitoring on availability, speed and errors.
Updates and backups
Updates to the CMS, framework and dependencies at a fixed rhythm, with backups we periodically restore for real.
Further development
A fixed allowance per period for improvements instead of a quote for every wish. Small steps, based on what users actually do.
Even when we did not build the site and the previous party is not cooperating.
Where everything sits: hosting, domain, DNS, certificates, licences and access. Surprisingly often the moment it turns out a domain is on someone's private account.
Overdue updates, vulnerabilities, speed and error messages. You get to hear what is there, even when that is uncomfortable.
Migration to our environment with as little downtime as possible, clearing the backlog and switching monitoring on.
What we do, how quickly we respond and what counts as further development. On paper, so it does not depend on individuals.
Management with an SLA, security requirements and several suppliers side by side. The route for organisations with an IT department.
What we build, we also manage. That way the knowledge about your system stays in one place.
Sometimes deferred maintenance can no longer be caught up and replacing is cheaper than repairing.
Management is also part of the monthly packages, together with findability and advertising. A fixed amount per month.
Yes, we do that regularly. We start with a baseline: what state is the technology in and which backlog has to go first. After that we both know what we are getting into.
Annoying, but rarely a blocker. With access to the domain and hosting we usually get there. Make sure the domain is in your own organisation's name, that is the one point where things can genuinely get stuck.
We arrange it, unless you have your own infrastructure or requirements that dictate otherwise. Then we work in your environment. Either is fine.
Improvements to what is already there: an extra page, a change to a form, a revised block. A new module or an integration is a project and we budget for it separately, so the fixed allowance does not quietly disappear into a single wish.
To a notice period, not to us. Your code, content and access are yours and come with you if you leave.
If not, that is the answer to the question of whether management is taken care of. In a conversation we map out what is there now.