Comments on: Tips for SaaS Contract Negotiations, and Knowledge Transfer http://leapcomp.com/2009/02/tips-for-saas-solution-negotiations-and-knowledge-transfer.html Mon, 21 May 2012 16:37:49 +0000 http://wordpress.org/?v=2.6 By: Jon http://leapcomp.com/2009/02/tips-for-saas-solution-negotiations-and-knowledge-transfer.html#comment-57606 Jon Wed, 08 Sep 2010 18:45:20 +0000 http://leapcomp.com/?p=813#comment-57606 I think your article's subject is one thing (negotiating a SAAS Contract), but then talks about something else (knowledge xfer)... i.e. 'take it with you'? Are you kidding? So tell me, if I customize (rather, configure) my salesforce.com account, if I leave SFDC, how do you propose I 'take it with me?' Sure...documenting customizations and configuration for future reference is fine, but how is that related to negotiating SaaS contracts? your colorful brain picture is very pretty, but 'tip 1' is a whole other area of project mgmt and nothing to do with tips 2-5. I think your article’s subject is one thing (negotiating a SAAS Contract), but then talks about something else (knowledge xfer)…

i.e. ‘take it with you’? Are you kidding? So tell me, if I customize (rather, configure) my salesforce.com account, if I leave SFDC, how do you propose I ‘take it with me?’

Sure…documenting customizations and configuration for future reference is fine, but how is that related to negotiating SaaS contracts?

your colorful brain picture is very pretty, but ‘tip 1′ is a whole other area of project mgmt and nothing to do with tips 2-5.

]]> By: Elliot Ross http://leapcomp.com/2009/02/tips-for-saas-solution-negotiations-and-knowledge-transfer.html#comment-4252 Elliot Ross Wed, 11 Feb 2009 16:35:46 +0000 http://leapcomp.com/?p=813#comment-4252 Julien, How true, and I could not agree more. Even with 'in house' software - organizations tend to neglect documenting their cusomizations. No matter how minor they appear they should be documented. Because at some time in the future someone will be wondering why that change was made. Julien, How true, and I could not agree more.

Even with ‘in house’ software - organizations tend to neglect documenting their cusomizations.

No matter how minor they appear they should be documented.

Because at some time in the future someone will be wondering why that change was made.

]]>