Understand the website before defining support
Support requirements depend on the platform, functionality and current condition of the site. A straightforward company website and a store with several integrations may need different arrangements.
We discuss your setup and existing responsibilities before defining the work. This helps establish what is covered and where another supplier is involved.
Agree what maintenance includes
A useful support agreement makes the responsibilities clear. The discussion should address:
- Routine maintenance requirements.
- Website performance and security priorities.
- How requests and issues are reported.
- Which changes fall within the support scope.
- How larger development work is handled.
Specific activities, coverage and response expectations need to be agreed for your website.
Keep maintenance and development distinct
Maintenance helps care for the website you have. A new feature, substantial redesign or major integration is a different type of project.
Clear boundaries help your team understand how a request will be assessed and whether it needs separate planning. That is more useful than an open-ended promise that every possible change is included.
Give your team a practical support process
Your staff need to know where to report an issue and what information to provide. The website address, affected journey and a clear description help establish what needs attention.
We also discuss who approves changes and who maintains access to the relevant systems. Support works better when the responsibilities are understood before an issue occurs.