Payment protectionDetails
- Revisions within the package are free.
- If you do not respond within 3 days of delivery, the work is accepted automatically.
The money is reserved when you pay and released only once you accept the work.
Example result
Contract template: web design services agreement
Website Design Services Agreement
This Agreement is made on [DATE] between:
- Designer: Lena Park, trading as Park Studio Design, [BUSINESS ADDRESS], [EMAIL]; and
- Client: [CLIENT NAME / COMPANY], [ADDRESS], [EMAIL].
1. Services
1.1 The Designer will design and build a website of up to [NUMBER] pages as described in the Project Brief in Appendix A. 1.2 Work not listed in Appendix A, such as copywriting, photography or ongoing maintenance, is outside this Agreement and will be quoted separately.
2. Timeline
2.1 The project starts once the deposit and all content listed in Appendix A are received. 2.2 Estimated delivery: [NUMBER] weeks from the start date. Delays in Client feedback or content extend the timeline by the same period.
3. Fees and payment
3.1 Total fee: [AMOUNT AND CURRENCY]. 3.2 Payment schedule: 50% deposit on signing, 50% before the website goes live. 3.3 Invoices are due within [14] days. Late payments may pause work until settled.
4. Revisions
4.1 The fee includes two rounds of revisions at the design stage and one round after development. 4.2 Further revisions are charged at [HOURLY RATE] per hour.
5. Ownership
5.1 After full payment, the Client owns the final website design and content created for it. 5.2 The Designer may show the finished website in a portfolio unless the Client objects in writing. 5.3 Third-party fonts, plugins and stock images remain subject to their own licences.
6. Termination
6.1 Either party may end this Agreement with [7] days' written notice. 6.2 The Client pays for work completed up to the termination date; the deposit is non-refundable once design work has begun.
7. Liability
The Designer's total liability under this Agreement is limited to the fees paid by the Client.
Signatures: Designer ________ Date ______ / Client ________ Date ______
Review checklist before signing
- Appendix A lists every page and feature you agreed on by email.
- The deposit percentage and late-payment terms match how you actually work.
- The liability cap and termination terms are acceptable under the law of [COUNTRY/STATE]; a local lawyer can confirm this.
- Hosting and domain: decide who pays and add a clause if you manage them.
- Both parties' legal names are written exactly as registered.
This is a template to adapt to your business, not legal advice.
Client: Lena Park, a freelance web designer trading as Park Studio Design. Template for one-off website projects. Fields in [BRACKETS] are filled in for each new client.
The client and all details are made up.
About this service
Choosing between MIT, Apache 2.0, GPL or a source-available licence decides what others may do with your code, and every library you ship carries its own licence with notice duties. Tell us how you want your project used and paste or attach your dependency list with their licences, and we explain the options for your own code in plain words and build a third-party notices file in the format most licences ask for. We also flag dependency licences that may clash with how you distribute, such as copyleft code inside a closed app.
What is included
- What you getA licence guide for your project, a third-party notices file with each component, its version, licence and copyright line, and a list of possible conflicts, as text and a Word (.docx) file. It is information, not legal advice: have a lawyer check licensing decisions that matter for your business.
- Licence optionsPermissive, copyleft and others compared
- Recommendation logicWhich fits the use you describe
- Notices fileComponent, version, licence, copyright
- Conflict flagsLicences that clash with your distribution
- README wordingA short licence section to paste
How it works
- 1BriefYou describe the project and dependencies
- 2ReviewWe compare licences and check the list
- 3DeliveryYou get the guide and notices file
What we need from you
What the software is and how you distribute it (open repo, app store, SaaS, embedded device), what you want others to be allowed to do, and the dependency list with names, versions and licences, for example a licence report from your package manager pasted as text or attached as Word, Excel or PDF.
We will ask you:
- How do you distribute the software?
- What should others be allowed to do with your code?
- Do you have a dependency list with licences?
- Do you plan to accept outside contributions?
Compare packages
| Packages | BasicNotices file$15 | StandardGuide and notices$35 | PremiumFull licensing pack$69 |
|---|---|---|---|
| Deadline | 1 day | 2 days | 3 days |
| Revisions | 1 | 2 | 3 |
| Dependencies in notices file | up to 30 | up to 100 | up to 250 |
| Licence options compared | 3 options | up to 5 options | up to 5 options |
| Contributor terms | No | No | Yes |
| Order Basic | Order Standard | Order Premium |
Payment protection
You pay when you order, but the money is released only for accepted work.
- Fixed priceThe package price does not change after you pay.
- The money is reservedWhen you pay, the amount is only reserved. It is released to the service once you accept the work.
- Checked before deliveryEvery result goes through a quality check before it reaches you, and you see it on the order page before accepting it.
- Free revisionsAsk for changes within your brief as many times as the package allows.
- Acceptance after 3 daysIf within 3 days of delivery you neither accept the work nor ask for changes, it is accepted automatically. If you write in the order chat after delivery, the order waits; once we answer, we may start the 3 days again and will say so in the chat.
- Redo or a full refundIf the result does not match your brief and the revisions did not fix it, or the work takes more than twice its deadline, write in the order chat: we will redo the work or refund the payment in full.
Questions and answers
Is this legal advice?
No. It explains common licences and how they usually work. Licensing can affect your business and investors, so have a lawyer confirm important choices.
Will you scan my code for licences?
No, we do not access your repository. We work from the dependency list you send; your package manager or a licence tool can produce one.
What if a licence in my list is missing or unclear?
We list it separately with what to check, such as the project's own licence file, instead of guessing.