Free Web Design Contract Template
A web design contract covers WordPress build deliverables, payment terms, change requests, ownership, portfolio use, responsibility limits, and how either side can end the project.
Share template
A site goes live, then a WordPress update lands or a form stops sending, and the buyer is stuck wondering who fixes what and what access to hand over. This web design contract gives both sides a written line between build work, handover, and post-launch responsibility, so the project doesn’t turn into “we thought you meant…” after launch.
The contract starts with what gets delivered for the WordPress build, including the custom theme, core setup, the plugin and licenses list, content migration, a redirect map, and a handover pack, then it pins down how staged payments work and when work pauses for late invoices. The wording also spells out how revision rounds run, how out-of-scope changes get priced and approved, and what the client owns after final payment, leaving third-party items like plugins and fonts with their makers. Raleway headings over Inter body text sit on enamel blue with honey-amber accents, so the structure reads clearly while the key actions still stand out.
- What you get Names the WordPress deliverables, plus what launch checks cover and what the handover includes.
- Payment Locks the project to fixed pricing in SGD and explains staged invoicing, due dates, and what happens when payment is late.
- Changes Defines a revision round and says how extra rounds or new page types get priced and approved before work continues.
- Who owns what Says what transfers on full payment, what stays with third-party vendors, and what the developer keeps as reusable components.
- Ending the project Explains written notice, what gets paid if the client ends early, what gets handed over if the developer ends it, and includes the signature block.
What changes once the contract is in your workspace is the details: names, dates, and any terms that need to match how you run frontend development work. You send it, the client signs online, and the signed copy becomes the version both sides can refer back to when something breaks, changes, or ends early.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What this contract contains
| Part | What it covers |
|---|---|
It is meant to match how | Sets the expectation of clear deliverables and access, and ties acceptance of the proposal to agreeing to the terms. |
What you get | Spells out the WordPress build scope, including the theme, plugin and licenses list, content migration, redirects, and the handover pack. |
Payment | Explains fixed project pricing in SGD, staged invoicing, late-payment pauses, and how approved third-party costs get handled. |
Changes | Defines how revision rounds work and how out-of-scope requests get priced and approved in writing before continuing. |
Who owns what | Says what the client owns after paying in full, what the developer keeps, and what stays owned by third-party makers. |
Showing the work | Covers portfolio use after launch, what never gets shared, and how to request confidentiality before launch. |
What I am responsible for | Defines what bugs get fixed, what sits outside scope, and how post-launch issues get diagnosed and routed. |
Ending the project | Covers written notice, early-end payments and handover, returning or deleting access, and carries the signature section. |
Who it is for
Web designers and developers delivering WordPress builds, plus teams handling CMS & WordPress work that needs a clear handover and post-launch responsibility line.
Questions about this contract template
What should a web design contract include for a WordPress build?
A web design contract usually covers deliverables, payment terms, how changes get approved, ownership after final payment, and who fixes what after launch. This one also addresses plugins and licenses, content migration, redirects, a handover pack, portfolio use, and how either side can end the project.
How do you handle plugin costs and licenses in a WordPress project?
Plugin and license responsibilities need to be named so nobody assumes the wrong thing at launch. This contract lists a plugin stack and licenses as part of the deliverables, and it also states that third-party items stay owned by their makers.
Can a contract cover content migration and keeping old URLs?
A contract can name content migration as a deliverable and define what “agreed pages” means for scope. This one also includes a URL redirect map and basic launch checks, including redirects from old URLs to new ones.
What counts as a revision round in web design and development?
A revision round can mean one consolidated set of notes after a review point like a staging link or a template preview. This contract defines that process and says extra rounds or plan changes get priced and approved in writing before work continues.
Who owns the website code after the final payment?
Ownership terms usually transfer the finished project deliverables to the client once payment is complete. This contract says the client owns the finished site deliverables and custom theme code after paying in full, while the developer keeps reusable libraries and third-party tools stay with their makers.
What happens if something breaks after a site launch?
A contract can separate build bugs from issues outside the developer’s control, like hosting outages, email server delivery problems, or third-party plugin updates. This one says the developer will help diagnose the problem and clarify what they can fix versus what needs a host or vendor, with claims limited to the fees paid for the project.
Start free today
Your entire business, one login away
No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.
No credit card required
