What CFOs Need to Know Before Signing and/or Negotiating a Cloud Computing Agreement
Book Details
Author(s)Mike Meikle
ISBN / ASINB00IRL1MS8
ISBN-13978B00IRL1MS9
MarketplaceUnited Kingdom 🇬🇧
Description
This webinar is a time-efficient way to get the most up-to-date information on the key terms to make sure are included (or not included) in your cloud computing agreement, negotiation strategies to use with prospective vendors, and understand how other CFOs are getting the best terms as well as protecting their company from a legal standpoint from the potential pitfalls of cloud computing. Take the 60 minutes to view this webinar (on your computer, mobile phone, iPod, iPad, Kindle or printed out) to make sure that you are aware of how to best negotiate the terms and legal issues associated with cloud computing and are prepared with the best tips and techniques from other CFOs and cloud computing lawyers before negotiating and signing an agreement on behalf of your company.
The webinar is led by an expert on advising CFOs on cloud computing agreements, Mike Meikle (CEO - The Hawkthorne Group), and focuses on:
• Everything you need to know in 60 minutes before signing or negotiating a cloud computing agreement on behalf of your company
• A line-by-line look at an updated cloud computing agreement, highlighting terms that are most negotiable right now, and specific wording examples of provisions that you want to ask for (warranties, caps on fee increases, litigation cooperation clauses, continued access to your company's data even in the event of a dispute with the vendor, etc.) and avoid (disclaimers of liability for data loss, etc.)
• Specific negotiating strategies for getting better terms from vendors in the current economy
• The 10 questions most asked by CFOs with respect to cloud computing and how to help their company avoid any legal pitfalls with respect to using cloud computing
• Case studies of other CFOs that have had success negotiating cloud computing agreements that are financially advantageous to their company, what worked best for them, and important lessons learned

