Monthly hours are easy to compare, but they do not describe the whole support relationship. A useful agreement explains what happens when a site has an urgent problem, how planned work is approved, and who owns decisions about the website.
Describe the work you expect
Make a short list of recurring needs: dependency updates, incident investigation, editorial assistance, small enhancements, and hosting coordination. Ask which activities are included and which need a separate estimate. This avoids treating every request as if it has the same urgency or complexity.
Drupal distinguishes routine updates from major upgrades in its update documentation. A support conversation should make a similar distinction when discussing the effort and testing required.
Define priorities with examples
We recommend agreeing on examples of urgent and routine work. A failed inquiry form and a request to change button wording should enter different conversations. State the coverage hours, escalation path, and expected response process in the agreement rather than relying on an ambiguous promise.
Response time is also different from resolution time. Investigation may uncover a third-party outage or a dependency that requires another team’s action. Ask how progress and next steps will be communicated in those situations.
Check ownership and evidence
- Who controls the repository, hosting account, and domain?
- Who can authorize a production deployment?
- What testing accompanies an update?
- Where are change notes and recovery instructions stored?
- How is unused or additional time handled?
Review the arrangement regularly
A small brochure site can develop into a platform with more integrations and editorial activity. Revisit the support scope when the website’s role changes. Use a short monthly review to identify recurring problems and decide which deserve a lasting fix.
The aim is a predictable working relationship with clear decisions and useful records. Compare the Druproid support plans as a starting point, then confirm scope, coverage, and response terms for your own website.