What does ongoing website maintenance cost?

A website or online shop is not finished at launch: the CMS, shop system and extensions receive continuous updates, security vulnerabilities are patched, and browsers and devices keep evolving. Maintenance and care are therefore not an optional extra but the protection of your investment. How high the running costs are depends on the system and the desired scope of services – there is no one-size-fits-all answer, but there are clear cost factors.

What maintenance and care typically include

• Core and plugin updates: Regular updates of the CMS or shop system and all extensions – tested in a staging environment first for critical systems.
• Security patches: Prompt installation of security-relevant fixes before known vulnerabilities can be exploited.
• Backups: Regular data backups, including the ability to restore a working state in an emergency.
• Monitoring: Monitoring of availability and errors so that issues are noticed before customers report them.
• Performance checks: Keeping an eye on loading times and metrics, since updates and growing content can affect speed.
• Bug fixing and support: A dedicated contact for incidents, questions and minor adjustments.
• Content maintenance (optional): Updating copy, images, products or job listings – depending on the agreement.

Four factors above all determine the level of running costs: the system in use – a shop system with payment and ERP connections requires more maintenance than a compact CMS website –, the number of plugins and integrations, the share of custom code that has to be checked for compatibility with every update, and the agreed response times. For the most common systems we offer specialised packages, such as WordPress maintenance and Shopware maintenance.

Maintenance and hosting are often mentioned in the same breath, but they are different services: hosting provides servers, storage and availability, while maintenance keeps the software running on top of it up to date and secure. If you buy the two separately, responsibilities should be clearly defined – otherwise it remains unclear in the event of an incident who is responsible for cause and remedy. If both services come from a single source, these interfaces disappear.

Billing models for ongoing support

Three models are common: a monthly maintenance plan covers defined services such as updates, backups and monitoring in a predictable way. Hour quotas combine the basic coverage with a fixed time budget for adjustments and content maintenance. Pure time and materials billing, finally, suits websites with very low maintenance needs – but carries the risk that updates are postponed for cost reasons. Maintenance is often combined with hosting so that infrastructure and support come from a single source and no questions of responsibility arise in the event of an incident.

In our experience, saving on maintenance means saving in the wrong place: outdated systems are a common entry point for attacks, and an update backlog accumulated over months makes the eventual upgrade considerably more laborious than regular small updates would have been. In the worst case, downtime, data loss or a necessary complete overhaul are added on top – costs that a well-kept maintenance routine generally avoids.

The maintenance budget is also money well spent because it creates the basis for further development: a system that is kept up to date can be extended with new features, content or optimisations at any time. In practice, an hour quota is therefore often used not only for updates but also for continuous improvements to loading times, search engine visibility and conversion – small, regular steps instead of rare large-scale projects.