Software Developer Agreement
Software Developer Agreement for Technology Businesses
Why do you need a Software Developer Agreement?
When a company engages a Software developer to create something unique and bespoke, it gives rise to many questions about ownership, maintenance, and acceptance. This requires a carefully thought out agreement that agrees various terms and avoids future disputes over ownership.
What is a Software Developer Agreement?
A Software Development Agreement must catch all provisions and scenarios that can arise in a developer/customer relationship in order to avoid any uncertainty.
It is important to clearly state what the developer is creating, and their responsibilities for modification, training and implementation, as well as customer obligations for payment and assistance. It should also hash out the licensing and ownership of intellectual property. These are all elements that Law 365 will help to resolve with our bespoke Software Developer Agreements.
Software Developer Agreement
Table of contents
View the contents of a Software Developer Agreement
Software Developer Agreement contents
1. Interpretation
2. Scope
3. Software and Documentation
4. Services
5. Pre-installation Testing
6. Software Delivery, Installation and Delays
7. Acceptance Tests
8. Acceptance
9. Implementation Plan and Extension of Time
10. Payment
11. Change Control and Technology Substitution
12. Ownership
13. Software Licence and Documentation
14. Transfer or Reproduction of Licensed Software
15. Use and Adaptation of Licensed Software
16. Support Services
17. Training
18. Supplier Personnel: Supplier Software and Support Services
19. Supplier Software: Project Management
20. Support Services: Customer's Obligations
21. Confidentiality and Publicity
22. Data Protection
23. Export and Compliance with Policies
24. Warranties
25. Intellectual Property Rights Indemnity
26. Limitation of Liability
27. Assignment and Subcontracting
28. Duration
29. Termination
30. Waiver
31. Rights and Remedies
32. Entire Agreement
33. Variation
34. Severance
35. Counterparts
36. Third-Party Rights
37. No Partnership or Agency
38. Force Majeure
39. Notices
40. Dispute Resolution
41. Governing Law
42. Jurisdiction
Key facts
Contact us for further information
This has got to be Intellectual Property. The Software Developer will create for their client a product that may become an integral part the client’s company, perhaps even their biggest asset. It is important to set out that all proprietary rights in bespoke software will vest automatically with the client. This avoids any confusion (or arguments) further down the line.
Delays are usually the most common issue we see in a software developer/customer relationship. Delays may arise from either party, because of a party’s acts or omissions, changes in requirement. It is important to carefully draft the agreement with considerations toward the implementation and timeframe of the project, considering what circumstances might allow for any extension.
Speak to an expert
Used by
- Managed Services Providers
- ISV, Software, Apps and IP
- System Integrators Professional Services Consultancy Partners
- Hosting Partners
- Licensing Partners
Other documents we can help you with...
Get in touch with Law 365
Whether you have a question or are looking for legal help for your business we are here to help - our mission is to support your businesses growth with less risk.
Book a free, no obligation call with our team.
Speak to an expert