What a Vendor Contract Needs to Say (That a Vendor Contract Never Says)

We signed a software vendor agreement without reading it carefully. The software was a tool we used to manage client work. The contract was long and written in standard vendor terms. We had used the software for two years before we tried to export our data.

The contract contained a clause that gave the vendor a license to our data for the purpose of improving their product. The clause also specified that data exports were available only in their proprietary format. Migrating our client history to a different tool required building a conversion script, which took a week. The contract had defined the relationship clearly and entirely in the vendor's favor. We had not noticed.

Who the standard contract protects

A vendor-drafted contract is written to protect the vendor. This is not cynical. It is rational. The vendor's attorneys drafted the agreement to minimize the vendor's exposure and maximize the vendor's rights. Every provision that is vague or silent on a point that matters to you defaults to the vendor's interest.

The IP clause in a typical software agreement grants the vendor broad rights to your data and your usage patterns. The limitation of liability clause caps the vendor's exposure for failures at a multiple of what you paid them, which for a $50 per month tool is a trivially small number. The termination clause gives the vendor the right to terminate with 30 days notice for any reason while requiring you to continue paying through the end of your contract term. The governing law clause puts disputes in the vendor's home jurisdiction.

In aggregate, it means you have paid for a service while the vendor has retained most of the rights and most of the power in the relationship.

What to look for before you sign

Data portability is the provision that matters most for software vendors. What format is your data exportable in? Is it a standard format that other tools can read, or is it proprietary? What happens to your data after the contract ends? The contract should specify that you can export your data in a usable format at any time and that the vendor will destroy or return your data within a defined period after termination. If it does not, negotiate it or treat the absence as a factor in your vendor selection.

Termination rights matter particularly for services vendors. A contract that locks you in for a year with no termination for convenience creates exposure if the service declines. A 30-day termination right, even at a modest penalty, is worth more than a lower rate on a twelve-month commitment you cannot exit.

Limitation of liability is worth reading carefully for any vendor whose failure could cause significant damage to your business. If a payroll vendor errors on your payroll, the cost of fixing it, including penalties you incur with tax authorities, may far exceed what you paid the vendor for the service. A cap on liability at one month's fees is not meaningful protection. Most vendors will not remove the liability cap, but some will increase it.

The provisions that are worth negotiating

Net 30 payment terms are the vendor default. For a business with multiple vendors, net 30 on all of them creates a cash flow obligation that does not match your revenue timing. If a vendor offers net 30 but your revenue arrives on net 45 or net 60, you are financing the vendor's cash flow. Asking for net 45 or net 60 costs nothing to ask and is sometimes available without pushback.

Price change terms matter on long-term contracts. A contract that allows the vendor to increase prices annually by any amount they choose is not a fixed-price contract. A cap on annual price increases, tied to CPI or a fixed percentage, gives you predictable cost planning.

Automatic renewal clauses are standard and dangerous for busy operators. A contract that renews automatically for another year unless cancelled 60 days before the renewal date will renew, because the cancellation window is easy to miss. Add the renewal date and the cancellation deadline to your calendar when you sign, or negotiate a shorter renewal window.

For professional services specifically

A professional services agreement, whether for a marketing agency, a development shop, or a consulting engagement, should address three things that generic agreements often leave ambiguous: who owns the work product, what constitutes completion of each deliverable, and what happens if you are dissatisfied.

IP ownership in a professional services context defaults, in many jurisdictions, to the creator unless the agreement specifies otherwise. A website built by a contractor may be the contractor's intellectual property unless the agreement contains a work-for-hire provision or an IP assignment. This is not a detail. It is who owns the thing you paid to have built.

Read the agreement. If it is long, read the IP, termination, limitation of liability, and governing law sections. Those are the provisions that determine what your options are when something goes wrong.