Software development agreements in Kenya define the legal relationship between a technology business and the developers, agencies, or contractors it engages to build its products. Whether you are a startup commissioning a custom platform, a corporate commissioning internal systems, or a software house contracting with enterprise clients, a comprehensive software development agreement protects intellectual property, allocates risk, sets expectations around deliverables and timelines, and determines what happens when things go wrong. The absence of a well-drafted agreement is among the most common causes of technology disputes in Kenya.

Why Software Development Agreements Matter in Kenya

Software development engagements in Kenya frequently go undocumented or are covered only by a brief scope-of-work email or informal purchase order. This creates significant legal risk on both sides. The client risks paying for software it cannot legally own or use, receiving deliverables that do not meet its requirements, or being locked out of critical source code if the relationship breaks down. The developer risks not being paid, being held liable for delays caused by the client’s failures, or losing ownership of reusable code components to a client with an overly broad IP assignment clause.

Intellectual Property Ownership: The Critical Provision

The most commercially significant provision in any software development agreement is the allocation of intellectual property rights in the work product, and this is also where the most common misunderstanding arises. Under the Copyright Act, 2001, section 31(1), where a work is created by an employee in the course of employment, copyright vests in the employer. Separately, where a work is commissioned by a person who is not the author’s employer under a contract of service, which describes most independent contractor and agency engagements, the copyright is deemed to be transferred to the person who commissioned the work, unless the parties have agreed otherwise. The default position therefore already favours the paying client, not the developer, contrary to the common assumption that a client only owns commissioned software if the contract expressly says so.

This default only applies to a genuine commissioning relationship and can be excluded or limited by agreement, so relying on it without checking the contract carries real risk. The position is less clear where the relationship does not sit neatly within a commission, for example a developer who contributes code before any formal engagement is signed, a hybrid employee-contractor arrangement, or a foreign developer whose work may be governed by a different country’s law. Moral rights, including the right to be identified as author and to object to derogatory treatment of the work under section 32 of the Act, are also not transferred even where economic copyright is. For these reasons a well-drafted agreement should still include an explicit written assignment or licence clause confirming ownership, addressing moral rights, and covering any pre-existing or background code the developer brings to the project, rather than relying on the statutory default and hoping a dispute never tests where the line between commissioned and non-commissioned work falls.

Background IP versus Foreground IP

A balanced software development agreement in Kenya distinguishes between background IP, pre-existing technology, frameworks, libraries, and tools that the developer brings to the engagement, and foreground IP, the new code, designs, and documentation created specifically for the client’s project. Background IP typically remains with the developer, who grants the client a licence to use it as embedded in the deliverables. Foreground IP is assigned to the client, consistent with the statutory default discussed above, though the agreement should still say so expressly rather than relying on the default alone. The agreement should precisely define each category, since a dispute over whether a given component is background or foreground code is far more expensive to resolve after the relationship has broken down than to define clearly at the outset.

Scope of Work, Deliverables, and Acceptance Testing

A software development agreement must contain a clear specification of the deliverables, the features, functionality, performance requirements, and technical specifications of the software to be built. Vague scope is the primary driver of cost overruns and disputes in technology projects.

The agreement should include a formal acceptance testing process: the client reviews the deliverables against agreed acceptance criteria, raises defects within a defined period, and the developer corrects them within a defined remediation period. Acceptance marks the point at which the deliverable is deemed complete, payment milestones are triggered, and risk of the deliverable passes to the client.

Payment Structure and Milestones

Software development projects in Kenya are typically priced on a fixed-fee basis (for well-defined projects with a clear specification), a time-and-materials basis (for agile projects where requirements evolve), or a hybrid approach with a fixed retainer plus variable charges for out-of-scope work. The payment structure should be tied to milestone deliverables, partial payment on signing, payment on delivery of agreed milestones, and final payment on acceptance, rather than paying the full fee upfront.

Warranties, Liability, and Indemnities

The developer should warrant that the software will materially conform to the specification for a defined warranty period, that the software does not infringe third-party intellectual property rights, and that the developer has the right to assign the IP as agreed. The client should warrant that any materials it provides, including data, content, third-party licences, do not infringe third-party rights.

Both parties should agree on liability caps, typically the total fees paid under the agreement, and exclusions of consequential loss, loss of profits, and loss of data. Without a liability cap, a developer could face unlimited claims for consequential business losses caused by a software defect.

Data Protection Compliance

Where the software processes personal data, the agreement must include data processing provisions compliant with the Data Protection Act 2019. If the developer processes personal data on behalf of the client, the developer acts as a data processor and must be bound by data processing terms covering the security measures to be applied, restrictions on the use and disclosure of the data, sub-processing arrangements, data breach notification obligations, and the return or deletion of data on termination.

For a fuller treatment of these obligations, see our guide to data protection compliance for technology companies in Kenya.

Confidentiality, Source Code Access, and the Computer Misuse and Cybercrimes Act

Developers frequently require privileged access to a client’s servers, databases, and production systems during a build. The agreement should require developers to use that access only for the purposes of the engagement, since accessing or interfering with a computer system without authorisation, or exceeding authorised access, can trigger criminal liability under the Computer Misuse and Cybercrimes Act, 2018, regardless of whether the developer’s civil contract with the client is otherwise in good standing. A confidentiality clause covering the client’s trade secrets and business information, addressed in more detail in our guide to trade secrets in Kenya, should sit alongside, not instead of, clear rules on system access and credential handling once the engagement ends.

Copyright registration and licensing guidance for software and digital works is available from the Kenya Copyright Board.

For comprehensive legal drafting and advisory on software development agreements in Kenya, including IP assignment, scope management, liability structuring, and data protection compliance, consult our technology and startups legal services team. We also advise on IP protection through our intellectual property law practice from our offices at Nextgen Mall, Nairobi.