The champagne has been poured and everyone's thrilled with your awesome project. You've made it through the crazy project changes, the scope creep, the signoff that wasn't sign-off but you didn't know it, and the main stakeholders changing halfway through. The launch was flawless, twitter lit up with how awesome this new site is, and the happy dances have commenced.

You, as the developers, now need to switch gears, because you have other wonderful projects to go play on. However, your clients (who you trained on the new system) aren't self-sufficient with their new site. They just aren't, for a number of different good reasons. They still need support, but no conversation was had about what happens after the initial site build. This is a very sticky place to be, because no side is really prepared for what happens after active development.

However, all is not lost. There are ways to be able to manage this. Transitioning into support does not have to taste like the morning after too much champagne! We'll go over:

• the project lifecycle
• how support ties into this cycle, (how it's been missing and what the impacts have been)
• a short conversation about code rot and why it's important to guard against it
• how a project manager can deal with this
• setting up your business to be able to recognize this
• the care and feeding of support staff
• what resources are available in the Drupal community to make the afterparty not the end of your rope