Admittedly, I take on some large issues in this column. But this is neither a treatise on contract law, nor the forum to attempt one. I am simply attempting to give some pointers for negotiating commercial contracts. I do very much appreciate the emails that I receive that suggest where I missed some salient information, or that offer critiques to some of my strategies. I’ve even used some of them and credited the authors, to the extent they’d allow. Funny thing about this site, most people don’t want to be identified. It’s almost end of year, so here goes:
Let’s say you’re in the heat of a commercial lease negotiation and the customer says to you: “What are these payments in the event of default? Why should I be penalized if your product doesn’t work as it should? Are you telling me that I have no remedies? Don’t you stand behind your products?”
I wrote about these contractual issues the week before Thanksgiving. I received so many emails that I thought it best to flesh these topics out a bit more. Also, some of these headings are from the anonymous “comments” section on this site, so I can’t attribute them (and I’ve also edited them for language).
1) “Real life example: Company A hired to refurbish shipping vessel owned by Company B. Contract obligated Company B to indemnify Company A fully, worded broadly enough and specifically enough to require indemnification for Company A’s own fault. Company A sets the boat on fire through clearly negligent actions and then tries to put it out with a garden hose. Fifth Circuit Court of Appeals tells Company B that yes, Company A was at fault; yes, you are out quite a bit for the value of the boat and the lost income, but you must eat it as you have to indemnify Company A for your own claim.”
Why on Earth someone would agree to indemnify a Customer for their own negligence is beyond me. I have been through this scenario many times, and I always inquire as to how I am expected to indemnify my Customer for its own negligence. In the B2B arena, indemnity should be limited (if possible) to third party claims against the potential indemnitee, at which point the indemnitor would take on the payment.
This raises another point: even if I indemnify you, who is going to defend you?
Caveat: I did not write the following dialogue. It is from the “comments” section of one of my columns where I mentioned I’d be writing about HIPAA and GLBA. Unfortunately, I cannot attribute the comments to the persons who wrote them, as they are anonymous; however they are quite apropos of today’s subject:
1) “I wish vendors would get it into their heads that indemnity for being sued on a confidentiality basis doesn’t cut it for financial institutions and other customers/clients that have affirmative obligations without being sued in the event of a breach of confidentiality.”
2) “I wish financial institution customers would get it into their heads that the ‘customer information’ they’re obligated to protect is not the sort of thing they would ever disclose to the vast majority of their vendors, and stop using their ‘affirmative obligations’ as a tool to cram unnecessarily restrictive confidentiality terms down the throats of vendors.”
Perfect. Those two comments capture the schism between vendors and customers when dealing with private financial or personal confidential information….
So, the Customer wants you to take on unlimited liability for breach of confidentiality, indemnify (and hold harmless) for any and all bad acts of your employees, and to carry a multi-million dollar insurance policy. What do you do?
First, begin by triaging these from simplest to more complicated. During a negotiation it can be helpful to appear to “give” as much as possible up front when you’re down to a few points. This way, when the final hot button items arise, you appear reasonable.
Insurance requirements are usually no-brainers, and as long as the amounts demanded are not grotesquely high, your Risk folks will approve the proposed language with very light editing, if any. Today, it is also not unusual for the Customer to demand to be named as a payee in the event of a loss; this is often fine, and usually not an issue. More practice pointers, after the jump….
The legal industry is being disrupted at every level by technological advances. While legal tech entrepreneurs and innovators are racing to create a more efficient and productive future, there is widespread indifference on the part of attorneys toward these emerging technologies.
Ed. note: The Asia Chronicles column is authored by Kinney Recruiting. Kinney has made more placements of U.S. associates, counsels and partners in Asia than any other recruiting firm in each of the past seven years. You can reach them by email: firstname.lastname@example.org.
We at Kinney Asia have made a number of FCPA / White Collar US associate placements in Hong Kong / China thus far in 2014. Most of such placements have been commercial litigation associates from major US markets, fluent in Mandarin, switching to FCPA / White Collar litigation. Some have already had FCPA experience, but those are difficult candidates for firms to find (this will change in coming years as US firms are now promoting FCPA / White Collar to their 2L summers who are fluent in Mandarin and have an interest in transferring to China at some point).
Legal Week quoted Kinney’s Head of Asia, Evan Jowers, extensively in the following relevant article here.
There is a new trend in the market, though, where mid-level transactional US associates, fluent in spoken Mandarin and written Chinese, are interviewing for and in some cases landing junior FCPA / White Collar spots in Hong Kong / China at very top tier US firms.
When the LexisNexis Cloud Technology Survey results were reported earlier this year, it showed that attorneys were starting to peer less skeptically into the future, and slowly but surely leaning more toward all the benefits the law cloud has to offer.
Because let’s face it, plenty of attorneys are perhaps a bit too comfortable with their “system” of practice management, which may or may not include neon highlighters, sticky notes, dog-eared file folders, and a word processing program that was last updated when the term “raise the roof” was still de rigueur.