When considering adopting a support and maintenance plan for your Drupal website, one of the most typical concerns is choosing the correct amount of monthly hours for the agreement.

Through years of experience, our team has identified the following general recommended hours:
5 to 10 monthly hours for small websites with low risk and low complexity
15 to 30 monthly hours for medium websites with medium risk and medium complexity
50+ monthly hours for large websites with high risk and high complexity

Use Case Scenario: Small Drupal Website

Having provided support and maintenance for over a hundred Drupal websites, our team has determined that even a small organization with access to a dedicated technical webmaster requires at least 4 monthly hours of outside support consulting. In cases when the organization does not have access to a dedicated technical webmaster, the minimum recommendation is 8 monthly hours.

The following table illustrates a typical usage case of support and maintenance hours for a small Drupal website, such as a business information portal or a company brochure site. This scenario assumes that the Drupal website is fully functional and free of major concerns.

 

Monthly Services
Month 1
Month 2
Month 3
Avg Monthly
Periodic backups
included
included
included
 
Support portal + issue tracking
included
included
included
 
Monthly report and billing
included
included
included
 
Website monitoring
included
included
included
 
   Maintenance-related arising issues
 
2
 
0.7
   Report on arising issues
 
1
 
0.3
CMS support
1
   
0.3
CMS training
 
1
 
0.3
Technical questions
1
   
0.3
Drupal strategic consulting
   
1
0.3
Minor bug fixes
1
 
3
1.3
Basic Support Total
3
4
4
3.7
         
Module and security updates
   
3
1.0
Minor feature enhancements
2
3
1
2.0
Updates + Minor Features Total
2
3
4
3

 

This chart shows that for the support and maintenance of a small Drupal website, over a period of 3 months, there is a typical usage of 4 monthly hours of basic support, and an additional 3 hours to include ongoing security updates and minor feature enhancements if the organization does not have access to a technical webmaster.