[consulting] Structuring Security and Module Update Services

[Susan Stewart]

We offer clients the opportunity to sign up for a hosting, maintenance,
and support plan that includes a few minutes of support per month, plus
application of all security updates within 48 hours of release and a run
of non-security updates weekly.  (The price varies depending on the
complexity of the site and the resource usage allowed.)

Clients who don't host with me can get updates and support on an hourly
basis.

The difference here is that on our system, we have automation tools to
speed the administration of updates, and we never have to deal with
client's forgetting to tell us passwords have changed, or changing
anything between updates that we don't know about.

-- Susan

Sam Cohen wrote:
> Hi all,
> 
> I am now going to be offering all my clients security and module updates
> as an ongoing service -- I know.  I should have done it all along. 
> 
> I'm curious how others structure this service.  Do most of you do it at
> a regular interval (to cover modules) or just every time there's a new
> release.  
> 
> My thought is to offer an option where every time there is a Drupal
> release I will install it and at that time I will check for any module
> updates and install those as well.  But pricing wise, it's tricky,
> because what if you run into trouble due to a module upgrade that leads
> to a conflict.  Not to mention, the time you should take for testing ? 
> 
> It seems like the safest way to offer this service is to just say you
> will bill hourly for whatever time it takes every time there is a
> release.  Is that how others do it?  If not, how much time to you
> typically charge/take for this. 
> 
> Thanks,
> Sam
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting