A Web Developer usually reaches for a Retainer Agreement when for continuing work billed on a repeating monthly cycle. This free template does one job well: it sets recurring fees, an agreed scope and notice terms for ongoing monthly work. 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 Retainer Agreement rather than something looser, because for a single fixed-scope project — use a service agreement 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.
RETAINER AGREEMENT — WEB DEVELOPER
1. PARTIES
This Retainer Agreement ("Agreement") is made on ____________ between ____________ ("Client") and ____________ (the "Provider"), a Web Developer. Together they are the "Parties".
2. MONTHLY SCOPE
Each month the Provider will deliver the following for the Web Developer engagement: ____________. Work beyond this monthly scope is agreed in writing and billed separately.
3. FEES & BILLING CYCLE
The monthly fee is $____________, billed on the ____________ of each month. Standard terms for a Web Developer are staged payments tied to milestones, often 30% up front and the rest on acceptance.
4. HOURS / DELIVERABLES
The retainer covers ____________ hours or the deliverables listed above each month. Typical support for a Web Developer includes working, deployed source code and a live site.
5. ROLLOVER & OVERAGE
Unused hours do not roll over unless agreed in writing. Work beyond the monthly block — for example new pages, integrations or design changes added after the spec is signed off — is billed at $____________ per hour with prior approval.
6. TERM & NOTICE
This retainer runs month to month and renews automatically. Either Party may cancel with ____________ days' notice; the client pays for all milestones completed to date on termination.
7. IP & CONFIDENTIALITY
The Client owns the deliverables produced under this retainer once paid. Both Parties keep each other's information confidential, which for a Web Developer especially covers source-code ownership transferring only on final payment, plus third-party and open-source licences.
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 Retainer Agreement ("Agreement") is made on ____________ between ____________ ("Client") and ____________ (the "Provider"), a Web Developer. Together they are the "Parties".
Each month the Provider will deliver the following for the Web Developer engagement: ____________. Work beyond this monthly scope is agreed in writing and billed separately.
The monthly fee is $____________, billed on the ____________ of each month. Standard terms for a Web Developer are staged payments tied to milestones, often 30% up front and the rest on acceptance.
The retainer covers ____________ hours or the deliverables listed above each month. Typical support for a Web Developer includes working, deployed source code and a live site.
Unused hours do not roll over unless agreed in writing. Work beyond the monthly block — for example new pages, integrations or design changes added after the spec is signed off — is billed at $____________ per hour with prior approval.
This retainer runs month to month and renews automatically. Either Party may cancel with ____________ days' notice; the client pays for all milestones completed to date on termination.
The Client owns the deliverables produced under this retainer once paid. Both Parties keep each other's information confidential, which for a Web Developer especially covers source-code ownership transferring only on final payment, plus third-party and open-source licences.
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.
Without one, new pages, integrations or design changes added after the spec is signed off eats the month for free. Price any work beyond the agreed block.
Decide up front whether unused hours carry over — silence is where arguments start for web developers.
Set the notice to cancel so a client cannot drop a Web Developer mid-month, and confirm the client pays for all milestones completed to date on termination.
When the work repeats every month rather than being a marketing site or web-app build with defined milestones with a clear finish line.
On a monthly cycle, commonly staged payments tied to milestones, often 30% up front and the rest on acceptance. The template bills in advance so you are never working unpaid.
Yes. Once you and your client sign it — including with an electronic signature — this Retainer 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 →