NET(net), Inc.


Salesforce.com calls for End of Maintenance by jigordon
April 29, 2009, 9:32 am
Filed under: contract management, current events, license grant, maintenance, pricing, SaaS

Below is the contents of an internal salesforce.com memo CEO Marc Benioff shared with Vinnie Mirchandani (and posted on his blog: deal architect).  I’m pasting it here for simplicity’s sake and because of the power of the message itself.

“For ten years, we’ve been driven by a simple vision: The End of Software.  Now it’s time to take on a new challenge: The End of Maintenance.

Let me tell you about a customer that I met on our Cloudforce tour. This customer currently uses Siebel software to run her call center.  She pays more than $15 million a year for the privilege of having to implement the updates that Siebel sends her.  That does not include backup. Or disaster recovery. And of course, it does not guarantee that she will be using the latest technology.  The maintenance agreement only assures her that her outdated software will continue to work.  She is paying tolls on a road to nowhere.

We can help her, and many other customers, and deliver much more for a fraction of what they currently pay in maintenance. It’s time to open up a new front in “The End of Software”– one that is long overdue.

It’s time for The End of Maintenance.

Every year, companies spend billions on maintenance fees and get relatively little in return. Maintenance fees cover updates that are mostly  patches and fixes, but they stop far short of the kind of innovation every that enterprise needs to survive.  Companies pay to keep the past working and they end up doubling down on technology that can never keep up with their needs.  The fees that companies pay have actually been rising, from something like 17% a few years ago to numbers more like 22% today. Every four or five years, companies are paying for their software all over again.

It’s time to set these businesses free and make them successful in the Sales Cloud,  Service Cloud and on our Force.com platform.

Our new mission begins at a critical time in the economy, when companies are questioning conventional wisdom as they never have before.  That, of course, extends to their IT budgets as well. The CIO is in a tough spot right now.  Corporate budgets are tightening.  And our rivals in the legacy client-server world are using this opportunities to extract more money from their customers by raising maintenance fees.  I call this phenomenon “the compression of IT” and it resonates with just about every CIO I speak with these days.

We have a better vision. We sell our customers a service and every customer is able to use the latest. Innovations are included. Upgrades are automatic and invisible. Customers’ intellectual property of customizations and extensions is rigorously preserved, and carried forward without disruption.

The service gets better, not just less buggy. That’s not what people are getting for all those fees that supposedly buy them “maintenance.”

It’s time to set these business people free: to give them the experience of being wildly successful in the Sales Cloud, the Service Cloud, and in their own unique applications that they can build on our Force.com platform. This is the time to do it, because this is when people need it: their IT budgets are tight, their business situations are critical, and their old-world software vendors are taking care of themselves instead of meeting the needs of their customers.

We’ve raised people’s expectations for better alignment of business value with IT cost. We’ve earned our leadership position in enterprise cloud computing. It’s time for us to set people free from paying more and more to get less and less. It’s time for The End of Maintenance.

Aloha,

Marc”



More interesting copyright issues by jigordon
April 28, 2009, 9:32 am
Filed under: copyright, current events

According to this article from Wired, Apple is involved in some very interesting copyright violation cases related to their fairplay copy protection scheme and DMCA takedown notices they provided to folks discussing how to circumvent Apple technologies.

I would pay attention to what the US Copyright Office decides based on their review – and on the results of the lawsuit itself.  While I still strongly believe that US intellectual property right laws are able to handle new technologies… I’ve become a little concerned about how the courts have been reacting to various claims (as well as legislative moves like the DMCA).



Oracle’s Compliance Scheme: Proactively Manage your Licenses by rlachs

It appears Oracle has increased its due diligence in the area of auditing customers.  On the one hand, this exercise may be helpful (as Oracle will profess) in enabling customers to better understand holistically precisely what their entitlements are and to what degree those entitlements are being leveraged.  This is useful information that many customers often struggle to reconcile on their own, and could shed some light on where opportunities for downsizing of entitlements might occur.

On the other hand, customers should be cautious.  In a down economy, where the volume of deals and overall license spending is lower than desired, auditing is a means by which Oracle may be hoping to find opportunities for incremental licensing events.  Especially for customers who either may not have been positioned to actively keep track of utilization trends over time, or who may not be familiar with original agreements and the parameters of utilization in these agreements,  Oracle will be seeking to capitalize whereever possible to bring your license entitlements and utilization back into compliance. 

Resolving compliance issues is likely to be done through a new licensing event.  Unlike a situation where a customer may be giving Oracle an opportunity to earn additional licensing business via a purchase that is not the result of an existing contractual obligation to Oracle, it is more challenging to negotiate a favorable license arrangement to adress compliance matters.  In fact, with certain product families, it is likely that the costs associated with the need to add incremental licenses has already been identified.  With other product families, Oracle is likely to use its standard list pricing as a starting point, and given that the absence of the licenses constitutes a breach of contract in a compliance situation, they are not under as much pressure to discount.  This puts the customer at a disadvantage, not only as it relates to the new license cost, but the associated maintenance costs related with those new licenses too – as the maintenance and support services costs are generally based on the net license value.

Customers would be well advised to invest time in assessing their license entitlements and utilization, and truly ensuring the parameters of their licenses are well accounted for, in advance of Oracle aggressively pursing completion of an audit.  If misalignment is identified, and you find that you will require additional licenses to ensure your utilization needs are met into the foreseeble future, it is better to address that with Oracle proactively with bringing a new license opportunity to them.  Given the possible stakes, this may be an area where enlisting professional help may be a worthwhile investment to either a) ensure you have no exposure; or b) help you address any potential exposure in a way that is most optimal for your organization.



Guth Studying for the Bar by jigordon
April 24, 2009, 9:32 pm
Filed under: fun

Our good friend Stephen Guth of The Vendor Management Office has been on hiatus recently, studying to take (and probably ace) yet another bar exam.  For those of you who have never tried one, I don’t recommend it.  Usually 2+ days long, 6-8 hours per day.  One half is typically a 200+ multiple-choice question exam called the Multi-State Bar Exam.  The other half is typically essays, based on the substantive state laws of whatever state bar you’re trying to pass.  Recently graduated law students typically spend about a month in bar-prep courses prior to the exam – trying desperately to learn the substantive law of their chosen state (you don’t have to go to school where you want to pass the exam – so most schools don’t “teach to the test”).

It’s grueling work – and if you’re like Stephen – having already passed in one venue and then doing it all over again in another many years after law school, it’s even more difficult – you simply have forgotten much of what you learned that’s outside your practice area.  So Stephen’s disappearance is highly warranted – between work, studying and his personal life, I’m surprised he’s still breathing… or sane.  Which might account for this random post that just appeared on his site.

Stephen:  if you’re out there and listening – hang in there buddy!  You’re gonna’ nail that exam.



Friday Fun by jigordon
April 24, 2009, 9:32 am
Filed under: fun, negotiation, Uncategorized

I found an interesting site that covers the trial and tribulations of customer service representatives – stories from the frontlines.  A few even relate to negotiation (and one on contracts), so I thought I would share:

The Lesser of Two Evils

Reorientation Disorientation

They Start So Young

Why Our Contracts Are a Gazillion Pages Long

Have a great weekend!



How to… redline by jigordon
April 21, 2009, 9:32 am
Filed under: contract management, process, risk matrix

When you’re about to enter a contract negotiation, and assuming you’ve not been successful in using your templates, the first step is to review and redline the agreement.  This How-To is intended to teach you the obvious (and not-so-obvious) skills of redlining.

  1. Ordinarily, I suggest a quick once-over.  This is a perusal designed to see if the major sections of the contract are present.  Using a checklist like the Software License Risk Matrix will help you verify that all of the headlines are covered.  Not all contracts will contain the same sections, of course, and just because a contract has a stated Header doesn’t mean that the language in that section actually matches the Header’s description.
  2. For any “missing” sections of the agreement that you would like to insert, create new sections in an appropriate place (as you read an agreement, you typically have a feel for where certain sections will need to go.  You’ll also have to make adjustments based on numbering schemes or sub-numbering schemes to match the original – so watch the blind copy-pasting.
  3. Now, hopefully you’ve got the contract in Microsoft Word (or other word processing format) to facilitate an easy redline.  Enable Word’s “Track Changes” feature via the Tools menu.  Advanced users will also note that you can quickly turn Track Changes on and off via the green-light at the bottom of that document’s window next to the “TRK”.  If the other side has sent you a document via PDF and refuses or is otherwise unable to send you a Word version, use the free service at www.pdftoword.com run by the great folks at NitroPDF.  This service will convert your PDF almost flawlessly and e-mail you a converted Word file.
  4. Read each section carefully.  Start with the definitions and make sure that all defined terms have a definition (many times this isn’t the case).  Now march your way through the agreement.
  5. Where you do not like particular language, the Track Changes feature allows you to “delete” the language – but instead of actually removing the offending words, it changes the color and puts a strike-out line through the deleted language.
  6. On the flip-side, when you insert language, Track Changes will insert your new words in the same color as the deleted text, only this time is underlined.
  7. Where possible, suggest new language that you’d prefer to be in the agreement rather than just strike-out the language you find troublesome.  This will provide a great basis for a negotiation.  If you simply delete language, I would assume that you simply want the language removed and nothing else added.  When this is the case, I will sometimes make a note to tell the other negotiator why I made a particular change:  “[JeffNote:  I don’t believe I should have to indemnify you for this.]”  This call-out makes it easier on the other reader to accept or reject your change, as your explanation might be all that’s needed for them to accept your modification.
  8. Then, when you’re the recipient of a redlined document, your first task is to review the changes to see if any of them are acceptable without discussion.  If so, simply right-click on the change and select “Accept Deletion” or “Accept Insertion” from the pop-up menu.  HOWEVER, DO NOT SIMPLY REJECT CHANGES!  This would create a presumption on your part that you shouldn’t make without talking to the other side first.  Rather, leave unacceptable changes in redline format as open for discussion.
  9. As the second reviewer (and the presumptive owner of the original), you might feel some initial pain at making any changes at all to your template.  Remember, however, that you’d do the same thing to someone else’s template.  Additionally, while I’m sure you wrote your template with every conceivable situation in mind, there might be a situation you didn’t conceive.  In other words, give the redline a chance.  Read it with the intent to accept as many changes as you possibly can.  This is a negotiation, afterall.
  10. If you need to suggest language back to the first reviewer, Track Changes anticipates this and will (unless you make changes to the Preferences settings) automatically assign each individual reviewer a different color.  If you place your pointer over a particular change, Word will tell you the name (as set in Word’s preferences) of the editor for that change and the date/time of the change.  If your name doesn’t appear on changes, make sure that you’ve entered your name in the preferences settings and you’ve also unchecked the box that has Word remove the name of the reviewer as part of its security process.
  11. So now you have a document that should have fewer redlines than when the first person was done, might have some additional redlines from the document’s original author and the document is now ready for negotiation.
  12. Set aside plenty of time for negotiation – rushing is to neither party’s benefit.  You do not have to make it through the entire contract in a single session.
  13. Once pleasantries are out of the way, discuss who will be the document owner (I typically volunteer… it keeps me alert and I feel much better about how the changes are completed).
  14. During the negotiation, systematically review the agreement from the top on down.  Continue to make any new additions or deletions in redline.  But accept/reject prior changes as agreed during the negotiation.  Thus, when done, you’ve got a document that ONLY has points of contention or new language changes still in redline.  In rare cases, in a trusting relationship, you might agree to make “blackline” changes.  If so, never breach that trust.
  15. OK, so after a few back and forth discussions, you should have resolved all open issues.  Take one more quick review to look for any open issues.  Use Track Changes to see if there are any unseen remaining edits (use the “Next Change” button to see if there are any you missed).
  16. What you’re left with is a blackline document – everything’s in black and white.  GREAT JOB!
  17. If you’ve got to do a redline by hand, here are a few additional suggestions:  a) Don’t.  Seriously.  Scan and use PDFtoWord.  b) But if you have to, learn to write very small in the margins with tiny arrows indicating where new language would go.  c) Actually strike through (with a single line) each word you don’t like.  d) Don’t waste time handwriting in entire new sections.  Just note what new ones are necessary – add new language electronically later.  e) If you must, create a separate document and create an amendment document where you describe each deletion and/or insertion.  Again, this method is HIGHLY outdated, but some organizations just can’t seem to get away from it.

Once you’re done, I sometimes also recommend using a tool called DeltaView (or even Word’s own Document Compare feature) to compare the original against the finished product.  This helps you check all of the redlines that were actually agreed upon and gives you a level of comfort that neither party tried to sneak in a change the other party didn’t accept.  However, unless I have reason to believe that the other party isn’t trustworthy, I typically have been diligent enough through each turn of the document to not require this final step.

All that’s left now is execution and managing post-contract obligations.  But that’s another day.



“Microsoft’s free XP, Office 2003 support ends April 14” by scottbraden
April 17, 2009, 12:46 pm
Filed under: Microsoft, Risk Mitigation | Tags: , , ,

Clarification:

Users will still be able to get free “Product-specific information that is available by using the online Microsoft Knowledge Base” and “Product-specific information that is available by using the Support site at Microsoft Help and Support to find answers to technical questions”

Details here:
http://support.microsoft.com/gp/lifepolicy