To describe the problem, briefly: context switching is what happens when multiple projects and responsibilities get handed to one individual. If you work in the nonprofit sector, you're thinking "Multiple projects and responsibilities being handed to one individual? Never!" ...because if you're been there, you know you're so overworked that it's now beyond a sad joke.

Over the past ten years, I've seen the nonprofit tech sector grow by leaps and bounds. We attend conferences, increasingly savvy clients come in already asking for Drupal or CiviCRM, and nonprofit-focused consulting is proving a viable business model for a rapidly growing number of organizations (including ours!). The technology, too, has evolved tremendously; the Drupal-based sites we consider "standard" today would have been impossibly expensive even three years ago.

Web design and development professionals will usually be asked to host a client's website or database at some point in their careers. I've been asked to host client sites since I started building websites ten years ago, and most of my colleagues have had similar requests. It's not surprising; it's hard to find a reliable hosting company, and a top-notch hosting company with 24/7/365 professional support suitable for a non-techie nonprofit is usually out of that nonprofit's price range.