12 Tips to Writing a Website Development Agreement

Many web developers prefer to create their own Website Development Agreements for clients. Do you know if your agreement template addresses all of the key issues it should? This article provides a checklist of the provisions that you should be including in your standard form agreement. At the very least, you need to include clauses covering:

• who owns the website and content after completion,
• protection of intellectual property rights for any software or resources used in building the site,
• the development phases (what constitutes completion of a phase),
• functionality testing,
• resolution of problems that arise during the process,
• covenants, warranties and undertakings given by each party,
• confidentiality and non-disclosure provisions to protect the parties, and
• what level of ongoing support will be provided.

1. Clearly outline the project specifications and development phases.

• Provide detailed specifications for the design of the website, which will then serve as criteria for final testing of the website to determine if the specifications have been met and if acceptance of the website is warranted. The specifications must be approved or modified by the client before work commences on the development of the site.

• Clearly define the developer's performance obligations to avoid any ambiguity between the parties. Clarify how extra work will be approved and billed.

• If the project warrants it, the Agreement should contemplate appointing a project manager to oversee and coordinate the development and to be the point of contact with the client.

• Set out a timetable for development / performance milestones and for progress meetings at key points in the timetable, and include the payment schedule attached to those milestones and key points.

• List all deliverables and resources required from the client and the times at which these are required. Include provisions which cover the implications if the client is late in delivering these items, i.e. how it will affect the timetable and completion date. Clarify what happens if a milestone is not met or the completion date is missed through no fault of the client.

• Ensure that the Agreement allows you to subcontract any part of the development services if necessary.

• The developer's performance obligations should include providing documentation and source code for all software used during the process.

• The Agreement must be flexible enough to allow for changes to the site specifications, and must also clarify how those changes will affect the timetable and development costs.

2. Make sure all parties agree on what is included in the contract price and how payments are to be made.

• Include everything that is included in the price, such as software licensing fees and applicable taxes.

• Payment should be tied to performance milestones. At least 1/3 of payment should be held back until the website has been thoroughly developed, delivered, tested and accepted by the client, and the website is ready to go live.

• There should also be a further holdback (10%-15%) for a reasonable period following acceptance to ensure that all defects have been detected and fixed.

3. Specify who owns the website and the elements.

• Unless otherwise agreed to with the client, the Agreement should expressly provide that the work done under the Agreement is a work-made-for-hire, and that all content, graphics, domain names, files and the look-and-feel of the site (together with all underlying code, software, digital programming) are the sole property of the client. A copyright notice should be displayed on the website.

• For greater certainty, the developer should sign over all proprietary rights in the work to the client under an assignment provision. Unless the developer is an employee of the client, the developer must convey copyright ownership to the client in writing in order for the client to acquire all rights reserved to the author under the copyright laws.

• Clarify whether the developer retains any rights to use any materials or software created during the development.

4. Hardware and software considerations.

• If the developer is providing any of the hardware, are any manufacturer's warranties being provided?

• If the developer is using any proprietary software in the development of the website, include provisions for the client to be able to license the software and access the source code in the event that the relationship between the parties is terminated or the developer goes out of business or becomes otherwise unavailable. The license granted to the client should be perpetual, royalty-free, irrevocable and worldwide, and should be transferable.

• Is any third party software or material (such as graphics) being used in the development? Have the required licenses / consents been obtained? Who is responsible for, and who pays the costs for, obtaining them? And who is liable for the performance of that software?

5. Clarify how third party infringement claims will be dealt with.

• Each of the parties should provide warranties that none of the material they provided infringes any intellectual property rights or other proprietary rights of any third party.

• There should also be mutual indemnification by each party of the other party.

• The developer should carry adequate liability insurance coverage to protect against third party claims.

6. Confidentiality and non-solicitation provisions.

• The Agreement should contain confidentiality clauses to protect each party's confidential information and proprietary data.

• The Agreement should also contain a non-solicitation provision barring either party from soliciting the other's employees during and for a reasonable period of time following completion of the project.

• If either party wishes to refer to the relationship in its marketing materials (including putting the developer's name and/or link on the website), this should be agreed to in the contract.

7. Compliance with laws and regulations.

• If the website collects any personal information from site visitors, all applicable local and international privacy and data security laws must be complied with.

• If the website is an e-commerce site which will be processing payment transactions, PCI compliance must be included in the scope of services.

• The website must contain all the required notices and disclosures for users (privacy, use of personal information, cookies, copyright, etc.)

8. Liability provisions.

• Each party should indemnify the other for any loss or damages arising as a result of such party's breach of its obligations. The liability should be limited to the total of the fees paid by the client under the Agreement.

• Each party should indemnify the other against third party infringement claims with respect to content, material or resources supplied by that party.

9. Functionality testing.

• The Development Agreement should clearly specify the anticipated functionality of the website, including page load times, connection speed, mobile friendliness, download speed, number of simultaneous connections and response times for user requests, compatibility with all Internet browsers, security protocols, checkout and payment systems.

• The functionality provisions should also cover integration of the site with the client's existing data server structure.

• The client must be able to make changes to the website without interfering with the site's operation or functionality.

• Website functionality should also include the procedure for accessing, recording and compiling user data and analytics.

10. Provisions governing installation and acceptance testing.

• The developer is responsible for transferring and installing the site and all associated software and files on the client's web server.

• The Agreement must address the following questions:

• Who will take responsibility for acceptance testing?

• Who will determine whether the testing has been successful?

• Will acceptance testing occur in stages?

• The client should have the right to reject the site if the site fails to meet designated specifications and does not pass the acceptance tests.

11. Warranties of the parties.

• In addition to the developer's warranty that there are no infringing materials, the developer should also warrant that the website will be delivered free from all known viruses and material defects, and will conform to the specifications. There should be a reasonable period of time allotted to resolve any defects or shortcomings.

• The client should provide a warranty that it has complied with all legal, financial and data protection matters.

• Determine how long the developer's warranty should be in effect, and set out the start date and end date.

12. Specify the types of ongoing support that will be provided.

• Determine whether the client will require training (e.g. html, CMS functionality, etc.) and if so, whether and for how long the developer will provide that training, and at what cost.

• Will the developer be providing support and maintenance after completion? Is this tied to a warranty period? If not, then consider signing a separate support and maintenance agreement.

• Determine the service level requirements, the costs to be billed to the customer, and billing and payment schedules.