For developers

Contracts for developers

Developers often take on builds where scope, ownership of code and ongoing support need to be clear. Contracts.io drafts those terms with Lex and gets them signed from one link.

Draft this with Lex

Free for the other side

Lex drafts it in Plain English beside the legal wording. Share one link; both sides agree and sign.

Templates developers use most

Client workWebsite build agreementA website build agreement covers designing, building and launching a site: pages, CMS, rounds of changes, hosting handover and ownership.Read →Client workStatement of workA statement of work sets the scope, deliverables, milestones and fees for one project under a wider services agreement.Read →HiringIndependent contractor agreementAn independent contractor agreement hires someone to do work as a business of their own, setting the work, pay, ownership and how the arrangement ends.Read →NDAs & IPMutual NDAA mutual NDA lets two businesses share confidential information both ways before a deal, and says what each side can do with it.Read →Client workRetainer agreementA retainer agreement sets a monthly fee for a set amount of your time or availability, and what happens to unused hours.Read →Client workConsulting agreementA consulting agreement sets out advice and expertise you provide to a client, billed by the day, the month or the project.Read →

How do I stop scope creep on a build?

Most build contracts describe the scope in a statement of work, with features, milestones and acceptance steps written out. Anything outside it is commonly handled as a change request with its own fee and timeline. Many contracts also limit how many rounds of revisions are included. Lex can turn a feature list into an SOW, so both sides know what is in and what is not.

Who owns the code I write?

It depends on the contract. Clients often expect to own the code written for them once it is paid for. Developers commonly keep their own libraries, frameworks and reusable components, and grant the client a licence to use them. Open-source components usually stay under their own licences. Writing these points into the IP clause avoids confusion when the client moves to another developer.

How do I charge for support after launch?

Many developers offer a monthly retainer after launch, covering a set number of hours for fixes, updates and small changes. The retainer usually says what response times apply, whether unused hours roll over, and how extra work is billed. Others bill support by the hour. Either way, a short written agreement makes it clear what the client is paying for each month.

Frequently asked questions

What contract do I need to build a website for a client?

Many developers use a website build agreement, or a services agreement with a statement of work, covering scope, milestones, fees, ownership of the code and support after launch.

Do developers usually limit their liability?

Many development contracts include a liability cap, often linked to the fees. In England and Wales, the Unfair Contract Terms Act 1977 says liability for death or personal injury caused by negligence cannot be excluded.

Can clients sign without creating an account?

Yes. You share one link, the client reads the agreement in Plain English, agrees and signs. It is free for the other side.

Related