The contract between a developer (whether they be a software developer, app developer or web developer) and their customer is a very important document – it governs each party’s obligations and, if both parties act properly, can avoid disagreements at a later date. Get it wrong and both parties could end up walking away from the project without getting what they wanted!
Below are a few tips to help you get it right…
DON’T attach the developer’s proposal. This is a sales document and is unlikely to be drafted in a way that is suitable for a contract.
but…
DO include a “Specification” detailing (at the very least) the key features of the end product or “Deliverables”. This should be as specific as possible.
DON’T expect the requirements to stay the same throughout the development project. It is almost inevitable that one or other party will identify improvements prior to the final version.
so…
DO include a “Change Control Procedure”. A defined process helps the parties to agree changes in an efficient manner.
DON’T assume that the customer will own any IPR just by virtue of having paid the developer to create it. In the absence of any written agreement to the contrary the developer will own everything they create.
DO be clear about the customer’s rights to use the developer’s existing products (if any). If the developer will be providing an existing product or standard code under licence, the contract must be clear about the permitted use and any restrictions.
DO ensure that you include any requirements for customer input e.g. providing content, ensuring the availability of staff for decision making and acceptance testing and/or providing hardware.
DON’T give (or accept) fixed price quotes without being very clear about the scope of work (see point 1 above!)
DO ensure that charges and payment terms are clearly spelled out so that there can be no confusion.
DON’T forget to make provision, if applicable, for some services (e.g. support) and licences to continue after the term of the development project has ended.
DO consider the circumstances under which each party should have the right to terminate.
DON’T assume that they are all standard! The “legal” bits tucked away at the end of the contract can make a huge difference to your risk. They are often the most hotly negotiated terms.
DO contact Waterfront! Whether you are a developer or a customer, we can ensure that your contracts are watertight, keeping your risk to a minimum.
Although most users of your website will not read your terms, this is an important part of your business. Having to argue in court is expensive, so a little investment to avert the risk is a pragmatic approach. This article highlights some of the most common points which your terms should cover so that the risks explained below do not crystallise.
If your business involves sending personal data outside the UK and EEA, you may be aware of the need for a transfer risk assessment (TRA) to demonstrate that you have properly considered and mitigated any associated risks.
When it comes to commercial negotiations, they often don’t turn out the way you had hoped and then there is no going back. Instead of struggling on your own, losing a lot of management time and still not being sure you have got the best deal, let us negotiate for you.
Get it in writing – Commercial Contracts