Friday, December 19, 2014
Follow Us On Twitter

5 hours ago
RT @PEPEBOOBISON: It's official: Celtics ship Rondo to Mavericks: The Boston Celtics have traded Rajon Rondo to the Dallas Maver... http://


5 hours ago
RT @MapleLeafs: The #Leafs come up short and have their win streak snapped at six in Carolina. #TMLtalk http://t.co/axo53aYc3i


5 hours ago
RT @TorontoStar: Many potential organ donors not identified, report findshttp://t.co/TJXvYdZwQH http://t.co/XD8p0i9yvO


6 hours ago
RT @SoftballOz: Softball WA Flames have unveiled their team for a title crack at the Australian Women's Softball Championships in... http:/


6 hours ago
RT @KellyNg: Boston CIO & Philadelphia Chief Data Officer reveal the secret to their successful #opendata projects #Egov @SAP http://t.co/o





Contact Us

Don't Be a Software Vendor Victim, You Have Choices

Friday, August 7, 2009
Don't Be a Software Vendor Victim, You Have Choices
I was on a call with a client today who is renegotiating a contract with a vendor.  I am not going to name names because it does not make any difference.  It made me angry because the client was acting like a victim.  "What if the vendor comes to audit our software usage and finds we are out compliance.  It might cost us a lot of money".  The client was bending over backwards to try to make sure that they were in compliance.  There is nothing wrong with that.  Most customers do make their best effort to be compliant.  The challenge is that this particular vendor has so much ambiguity in the language of their contracts and policies that the client cannot really tell if they are in compliance.
Here are two examples of ambiguity:
  • The vendor offers a limited use and a full use version of a product.  There is no clear criteria about the limits of use for the limited use version.  Complicating matters, the customer purchased the product before the vendor started to delineate between a limited use and full use version.  So, they also might have used it in ways that go beyond the limited use prior to their being a full use solution.  They are not sure.  I was not sure in some cases. 
At a minimum, when vendors introduce these distinctions, anyone who had bought the product prior to the policy or offering change should be grandfathered.  Period.  Trying to convince the customer that they should pay additionally to get the full use version is just plain wrong (unless they intend to use it going forward in ways that would require the full use version). 


FULL ARTICLE
Copyright © 2002-2014 Phenix Management International
For more information please read our Privacy Policy and our Terms of Use
Designed and Hosted by Net Reliant
Powered by Reliant CMS