We’re big believers in clear agreements. That’s why we like to define the framework for post-launch collaboration before a website goes live.
At its core, our maintenance agreement covers:
- Core maintenance: The services we proactively take care of.
- Extended support: Processes and retainers for additional support.
- Follow-up projects: How we handle larger changes.
We can also define service levels together – that is, the metrics that determine what “successful” maintenance looks like. The setup can e.g. include sentries and automated tests (to ensure uptime and functionality) or standardized tests for page speed.
Core maintenance
The absolute essentials: this includes setting up a Git repository with an integrated ticketing system, configuring the various hosting environments, and carrying out regular CMS and security updates.
For these services, we typically charge a modest annual flat fee.
Extended support
This covers all ongoing day-to-day maintenance work, including frontend and backend bug fixes, integration maintenance, and larger CMS updates (such as major version releases). It also includes smaller design adjustments, as well as consulting and concept development for new website features.
We’re also available to support editorial teams when questions arise or workflows need clarification. And when necessary, we can step in as a technical advisor when coordinating with other service providers, such as hosting companies.
For extended support, we usually agree on an annual spending cap (a retainer). Requests up to a predefined effort threshold – for example, half a day of work – can then be handled on demand, whether via a ticket or through a dedicated support email address.
At the end of the agreed period, we provide a record of all work completed and bill accordingly.
Follow-up projects
Larger updates or structural changes to a website are quoted separately. In many cases, it also makes sense to bundle smaller requests from the backlog into a single package to implement them more efficiently.
On request, we also offer refresher training for CMS usage and content management – for example, when new team members join – or workshops on the editorial requirements of accessible websites.
Project-based work is scoped and estimated in advance, then implemented once approved.
Questions? Get in touch: info@diebrueder.com