How to Write a Support Contract

I hope the start of your work week is going well.

If you’re having a case of the Mondays, take a look at the giant smile I accidentally included in this past weekend’s email.

We’re getting pretty close to wrapping up this series on support contracts. So far we’ve covered:

Recall that you want to eliminate gaps in your revenue. What you’d rather see from this point forward is

  1. Never hitting a week of zero revenue again, AND
  2. Having as many backup sources for revenue as you can manage.

As a bonus benefit you’ll see your overall revenue numbers go up. Why?

For the first time in your freelance career your revenue will not be tied to your time.

Need to go on vacation? That support contract check is still going to come in while you’re away.

Check out what reader Brandon Savage was able to do when he put in this principle into practice:

I signed a $42,000 support contract based on your suggestions last week. I knew I needed to do it, and we closed before I left on a week-long trip.

Support Contracts generate you recurring revenue just like the seven other recipes in my book, the 7 Recurring Revenue Recipes for Freelancers. Like the recipe for your favorite meal, they will give you step by step instructions to give it a try.

Let’s get started with learning how to write a support contract.

How to Write a Support Contract

Writing a support contract is no different than writing a proposal. It needs to cover the work you will be doing plus the constraints involved in the project.

In every one of my support contracts I have a section entitled “The Things We Will Do for You”. It covers in specific detail the kind of support that will be offered.

A good example is the email and phone support I provide to some clients:

Any IT related questions pertaining to the Application will be answered by Retainer. A total of eighty (80) hours of Retainer time for the duration of this contract is given to the Client for this purpose. Retainer time includes:

  • Phone or email-based user-level support.
  • Time spent by Retainer to resolve the issue, except in the case of defect.

It should be emphasized that an annual service contract is not designed to replace an on-site system administrator, but rather to provide a secondary support role in cases when the local system administrator is unable to perform certain tasks.

You’ll notice how specific the language is. It covers the support being provided and the limit of the support (80 hours).

In some cases you have to protect yourself by also specifying things not included in the service.

For the previously mentioned contract I also had a section that covered things excluded by the contract:

It may seem like overkill to define everything but doing so allows you to remain on the same page as your client.

It leaves little room for assumption. And it’s perfectly ok to provide support outside the realm of this agreement.

Other Important Things to Include

Finally you need to have all this looked over by your lawyer. They’ll make sure you do not state anything too ambiguous that will come back to bit you later on.

Do you have support contracts of your own? Was there anything I missed? If so, send a comment below.