Zombie Contracts (or "Contracts That Just Won't Die")

A few years back, I hit on a concept that I've been a firm proponent of ever since: the perpetual contract.  One reason I like perpetual contracts is because I never have to worry about renewing them because they never expire.  In fact, I try to put a perpetual contract in place with every one of my vendors.

Even if you're new to purchasing, you're probably right now thinking to yourself:
  • Things change--it doesn't make sense to have a perpetual contract.
  • What if we only plan on using the vendor once?
  • If you enter into a perpetual agreement with a vendor, you're going to lose a ton of leverage.
  • I can see a perpetual license for software or some other IP, but a perpetual contract doesn't really apply to anything else.
Let me alleviate your concerns...  First, though, I want to emphasize (again) how important it is to be operating off of your own contract templates--what I'm about to describe only works if you're operating off of your own paper.  OK, on to the rational and mechanics of a perpetual contract...

Beyond my not wanting to have to worry about renewing expiring contracts, my real reason for wanting a perpetual contract is that I never again want to re-negotiate the original terms and conditions with a vendor.  That assumes that the vendor either executed my contract template as-is or negotiated changes such that the contract is still favorable or equitable for me.  Once I have that contract signed and sealed, I want to protect those terms and conditions in perpetuity, and I don't want to risk them being re-negotiated unless they absolutely need to be.

The other reason is efficiency.  With my contract templates, what I do is separate the "legal" terms from the "business" terms.  The "Master" contains the legal terms and what I call the "Exhibit A" contains the business terms.  If the vendor is awarded future business, it's just a matter of negotiating another "Exhibit A."  Here are some examples of the structure by commodity:
  • Master Professional Services Agreement - Exhibit A (Statement of Work)
  • Master Software License Agreement - Exhibit A (Product Description)
  • Master Purchasing Agreement - Exhibit A (Purchase Order)
  • Master Hotel Services Agreement - Exhibit A (Booking Sheet)
Mechanically, here's how the Master / Exhibit structure works.  In the Master (I'm using a professional services agreement as an example for the following provisions), there's a provision immediately following the recitals that describes the Master / Exhibit structure:

1.    Vendor Services.  Vendor agrees to provide, in accordance with the terms of this Agreement, the services as set forth on an Exhibit A (sequentially numbered) in the form of the Exhibit A attached hereto or in other statements of work containing substantially similar information and identified as an Exhibit A (the "Services").  Vendor shall control the manner in which the Services are provided, giving due consideration to the requests of Customer.

Once I execute the Master, I then execute an Exhibit A for each statement of work.  Using professional services as an example, the first statement of work would be called Exhibit A-1, the next statement of work would be called Exhibit A-2, and so on.  The start of an Exhibit A form for professional services is as follows:

Exhibit A-___

Vendor’s Statement of Work

This Exhibit A - Vendor’s Statement of Work shall be incorporated in and governed by the terms of that certain Master Professional Services Agreement by and between CUSTOMER (“Customer”) and VENDOR (“Vendor”) dated ______________________, as amended (the “Agreement”). Unless expressly provided for in this Exhibit A, in the event of a conflict between the provisions contained in the Agreement and those contained in this Exhibit A, the provisions contained in the Agreement shall prevail.

Some of you may still be wondering about flexibility--how can the Master be flexible enough to handle the variability of future purchases?  Here's an example taken from a professional services agreement that demonstrates the flexibility of the Master:

7.    Acceptance Period.  Unless otherwise specified in the applicable Exhibit A, for all Services provided under this
Agreement, Vendor grants to Customer a thirty (30) day acceptance period ("Acceptance Period") commencing on the date completed Services are delivered to Customer. <snip>

The key clause that provides the flexibility is "Unless otherwise specified in the applicable Exhibit A..."  Since, as indicated in the Exhibit A-___ incorporation clause excerpted a couple of paragraphs above, the Exhibit A "rules" the master.  So, my Exhibit A also serves as an amendment vehicle to the Master without having to formally / permanently amend the Master using a separate amendment.  Here's another example of the key "unless otherwise" clause in action:

6.3.    Billing Procedures.  Unless otherwise provided for under an Exhibit A, Supplier shall bill to Customer the sums due pursuant to an applicable Exhibit A by Supplier’s invoice, on a monthly basis in arrears, which shall contain: <snip>

What the above provision allows is for a customer to specify a milestone-based invoice structure in an Exhibit A (if needed), but if no payment structure is specified in an Exhibit A, that Exhibit A defaults to a monthly invoice structure.

Some of you may wonder about what happens once an Exhibit A has been performed (and therefore terminated).  Well, whether you think it at the time or not, once you've done business with a vendor, you'll likely do business with that vendor again (unless the vendor didn't perform as expected).  However, even if you don't do business with a vendor again, the Master is basically dead because there's no active Exhibit A.  Once an Exhibit A has been performed, the Master lies in wait--just waiting and hoping for another Exhibit A to come along.  Sure, the parties still have certain obligations under the Master, like confidentiality, but those types of obligations I'm OK living with.  If I haven't executed another Exhibit A with a vendor after a couple of years, I'll go back and formally terminate the Master.

Once you get used to the structure, you won't believe how much efficiency and flexibility you gain.


Played: 98 | Download | Duration: 00:04:04

 del.icio.us  Stumbleupon  Technorati  Digg 

 

What did you think of this article?




Trackbacks
  • No trackbacks exist for this entry.
Comments

  • 2/8/2008 11:46 AM charlie wrote:
    Steve, nice write up. I am curious when you have a master for a professional services agreement and then also have a need for purchase of product involved that includes both hardware product, services and training . Does your or would a separate parent agreement cover all the T'cs of the Professional services again and supercede the original professional services agreement?
    So When I view a agreement thats starts off as a services agreement I may miss my other items.. What preference do you follow? It's more a question of which agreement is the right agreement to startoff with? Or Is it more that the or agreement is referenced as amendment of the Professional services agreement or vice a versa?
    Reply to this
    1. 2/8/2008 4:30 PM Stephen Guth wrote:
      Charlie,

      Excellent question!  As painful as it sounds, I execute different agreements.  An example is a software package that my customer needs to have customized and needs to be trained on.  In that case, I'm executing two agreements: Software License Agreement (for the software license) and the Master Professional Services Agreement (for the customization work and the training).  The license agreement will have an Exhibit A-1 to cover the software license, maintenance, and training, and the professional services agreement will have an Exhibit A-1 for the customization work.  In fact, here's a provision directly from my software license agreement contract template:

      5.             Training and Professional Services.  Vendor shall make training available to Customer to train Customer’s personnel in the use of the Product, as further described in an Exhibit A to this Agreement or, if applicable, to a training services addendum to such Exhibit A.  In addition, Vendor shall make professional services available to Customer on matters pertaining to the installation, use, operation, and modification of the Product at Customer's request, as more specifically described in a separate professional services agreement.


      Again, it's short-term pain for long-term gain.  I know darn well, despite what my customer says, that we'll have more customization and more training--we may even buy more / different software from the vendor.  If I can paper it all now in the modular fashion that I'm putting it in, the future deals are going to be nearly pain-free from a contracting perspective.  In some cases, even if there's no current customization work or consulting--but I think there will be--I have the vendor sign both a purchase / license agreement and a professional services agreement.  The professional services agreement may never be used, but it's there if I need it, and it's only activated when there's an Exhibit A (statement of work).

      I try to avoid including any language referencing other agreements in the Master--I do that in the Exhibits.  Using the example above, the professional services agreement has no reference to the software license agreement.  But the professional services agreement Exhibit A-1 (customization statement of work) definitely refers to the software license agreement Exhibit A-1 (product description).

      Cheers!
      Stephen

      Reply to this
Leave a comment

 Enter the above security code (required)

 Name

 Email (will not be published)

 Website

Your comment is 0 characters limited to 3000 characters.