Separate three kinds of work
Technical maintenance covers security updates, dependencies, monitoring, backups and compatibility. Editorial administration means publishing content within the existing structure. Development changes behaviour, components, integrations or the data model. Combining all three in one subscription makes costs difficult to understand and expectations impossible to manage.
What the team should be able to do
- Edit copy and SEO metadata in approved fields.
- Publish services, projects, articles or team members.
- Replace images while following defined formats.
- Reorder elements where order has editorial meaning.
- Preview, schedule or withdraw content without touching code.
Not every website needs all these capabilities. A rarely updated page may be more efficient without a CMS. The right decision starts with the actual volume of changes, not the assumption that a complex editor is mandatory.
What maintenance pays for
A useful maintenance service has measurable scope: what is monitored, how often updates happen, who responds to incidents, which backups exist and what response time is promised. Reporting should show work completed and risks identified, not merely that the website stayed online.
Build a predictable model
A combination works for many organisations: autonomy for frequent content, recurring technical maintenance and separate budgets for improvements. Small requests can be grouped into a monthly window, while major changes are estimated as projects. Development is not treated as free, and editorial activity does not become a permanent toll.
Questions for the contract
- What counts as maintenance and what is new development?
- What can the client update without extra cost?
- Who owns access and data?
- What happens in an urgent incident?
- How are extra hours approved and reported?
- How can the engagement end and the system be transferred?
Good maintenance buys continuity and lower risk, not permission to use your own website.