A Web Developer usually reaches for a Service Agreement when for a defined project with a clear start, deliverables and end. This free template does one job well: it defines the scope, timeline, payment and ownership for a one-off project. It is written for how web developers actually work — around a marketing site or web-app build with defined milestones, the familiar headache of endless post-launch bug reports being treated as free work, and getting paid on staged payments tied to milestones, often 30% up front and the rest on acceptance. Use a Service Agreement rather than something looser, because for open-ended ongoing work — use a retainer instead. Edit any line to fit your rates and terms, then send it for e-signature in a couple of minutes — no account for your client, and it is legally binding under the ESIGN Act and eIDAS.
SERVICE AGREEMENT — WEB DEVELOPER
1. PARTIES
This Service Agreement ("Agreement") is made on ____________ between ____________ ("Client") and ____________ (the "Provider"), a Web Developer. Together they are the "Parties".
2. SCOPE OF WORK
The Provider will deliver working, deployed source code and a live site for a marketing site or web-app build with defined milestones. The agreed scope is: ____________. Anything not listed here is out of scope and is quoted separately before work begins.
3. TIMELINE
The Provider will start on ____________ and aim to deliver by ____________. Timelines assume the Client supplies everything needed on time; Client delays move the delivery date by the same amount.
4. FEES & PAYMENT
The fee is $____________. Payment terms: staged payments tied to milestones, often 30% up front and the rest on acceptance. Invoices are due within ____________ days. Late payments may pause work and accrue interest at ____________% per month.
5. REVISIONS
The fee includes ____________ rounds of revisions. Additional rounds, or changes such as new pages, integrations or design changes added after the spec is signed off, are billed separately.
6. OWNERSHIP & IP
On full payment, the Client owns the final delivered working, deployed source code and a live site. The Provider keeps ownership of tools, templates and any source-code ownership transferring only on final payment, plus third-party and open-source licences until paid, and may show the work in a portfolio unless agreed otherwise.
7. TERMINATION
Either Party may end this Agreement with ____________ days' written notice. On termination, the client pays for all milestones completed to date on termination, and the Client pays for all work completed to that point.
8. GOVERNING LAW
This Agreement is governed by the laws of ____________, and any dispute will be handled in the courts of ____________.
9. SOURCE-CODE OWNERSHIP
The Client owns the custom source code on full payment. Pre-existing libraries and the Provider's reusable components remain the Provider's, licensed to the Client for this project.
10. ACCEPTANCE
The Client has ____________ days to review the delivered working, deployed source code and a live site and report issues. If no issues are raised, the work is deemed accepted.
11. WARRANTY & FIXES
The Provider will fix genuine defects reported within ____________ days of delivery at no charge. Beyond that window, or for new pages, integrations or design changes added after the spec is signed off, work is billed as new.
12. THIRD-PARTY & OPEN SOURCE
The build may use third-party or open-source components under their own licences. The Client is responsible for any paid third-party services after handover.
SIGNATURES
Signed by the Parties on the date first written above. Both Parties keep a copy. An electronic signature is legally binding under the ESIGN Act and eIDAS.
Client: ______________________ Date: __________
Provider: ____________________ Date: __________This Service Agreement ("Agreement") is made on ____________ between ____________ ("Client") and ____________ (the "Provider"), a Web Developer. Together they are the "Parties".
The Provider will deliver working, deployed source code and a live site for a marketing site or web-app build with defined milestones. The agreed scope is: ____________. Anything not listed here is out of scope and is quoted separately before work begins.
The Provider will start on ____________ and aim to deliver by ____________. Timelines assume the Client supplies everything needed on time; Client delays move the delivery date by the same amount.
The fee is $____________. Payment terms: staged payments tied to milestones, often 30% up front and the rest on acceptance. Invoices are due within ____________ days. Late payments may pause work and accrue interest at ____________% per month.
The fee includes ____________ rounds of revisions. Additional rounds, or changes such as new pages, integrations or design changes added after the spec is signed off, are billed separately.
On full payment, the Client owns the final delivered working, deployed source code and a live site. The Provider keeps ownership of tools, templates and any source-code ownership transferring only on final payment, plus third-party and open-source licences until paid, and may show the work in a portfolio unless agreed otherwise.
Either Party may end this Agreement with ____________ days' written notice. On termination, the client pays for all milestones completed to date on termination, and the Client pays for all work completed to that point.
This Agreement is governed by the laws of ____________, and any dispute will be handled in the courts of ____________.
The Client owns the custom source code on full payment. Pre-existing libraries and the Provider's reusable components remain the Provider's, licensed to the Client for this project.
The Client has ____________ days to review the delivered working, deployed source code and a live site and report issues. If no issues are raised, the work is deemed accepted.
The Provider will fix genuine defects reported within ____________ days of delivery at no charge. Beyond that window, or for new pages, integrations or design changes added after the spec is signed off, work is billed as new.
The build may use third-party or open-source components under their own licences. The Client is responsible for any paid third-party services after handover.
Signed by the Parties on the date first written above. Both Parties keep a copy. An electronic signature is legally binding under the ESIGN Act and eIDAS.
If the agreement does not name exactly what working, deployed source code and a live site is included, endless post-launch bug reports being treated as free work follows. List the deliverables line by line.
Without a revision limit, new pages, integrations or design changes added after the spec is signed off quietly becomes unpaid work. Fix the number of rounds in writing.
Say that source-code ownership transferring only on final payment, plus third-party and open-source licences only pass on full payment, or a Web Developer loses all leverage once the files are out.
Use it for a marketing site or web-app build with defined milestones — a defined job with a clear end. For continuing month-to-month work, a retainer fits better.
Yes. It fixes your fee and terms, which for web developers is usually staged payments tied to milestones, often 30% up front and the rest on acceptance.
Yes. Once you and your client sign it — including with an electronic signature — this Service Agreement is a binding contract under the ESIGN Act, eIDAS and similar laws in most countries.
Point them back to the scope. Extra work such as new pages, integrations or design changes added after the spec is signed off is quoted separately — that is exactly what the written terms are for.
Yes. Paste it into Signr, drop the signature fields on, and send a link. Your client signs from any device with no account, and you both get a sealed, court-ready copy.
Paste the template into Signr, drop signature fields on, and send. Your client signs from any device, no account needed, and you both get a sealed, court-ready copy.
Create your free agreement →