Contract & Proposal Writer
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/contract-and-proposal-writer, including the files SKILL.md points to. - Describe your job in plain words. Claude Code follows the skill from there.
npx degit alirezarezvani/claude-skills/business-growth/skills/contract-and-proposal-writer#main ~/.claude/skills/contract-and-proposal-writerFor one project only, change the path to .claude/skills/contract-and-proposal-writer. This skill also uses contract.md — copying SKILL.md alone won't be enough. See the folder on GitHub.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of Contract & Proposal Writer
Show the full text424 lines
| name | description |
|---|---|
| contract-and-proposal-writer | Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting points. Use when drafting a freelance contract, preparing a client proposal, writing an SOW for a new engagement, or producing an NDA before sharing sensitive material. |
Contract & Proposal Writer
Tier: POWERFUL
Category: Business Growth
Domain: Legal Documents, Business Development, Client Relations
Overview
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Outputs structured Markdown with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions.
Not a substitute for legal counsel. Use these templates as strong starting points; review with an attorney for high-value or complex engagements.
Core Capabilities
- Freelance development contracts (fixed-price & hourly)
- Project proposals with timeline/budget breakdown
- Statements of Work (SOW) with deliverables matrix
- NDAs (mutual & one-way)
- Master Service Agreements (MSA)
- Jurisdiction-specific clauses (US/EU/UK/DACH)
- GDPR Data Processing Addenda (EU/DACH)
Key Clauses Reference
| Clause | Options |
|---|---|
| Payment terms | Net-30, milestone-based, monthly retainer |
| IP ownership | Work-for-hire (US), assignment (EU/UK), license-back |
| Liability cap | 1x contract value (standard), 3x (high-risk) |
| Termination | For cause (14-day cure), convenience (30/60/90-day notice) |
| Confidentiality | 2-5 year term, perpetual for trade secrets |
| Warranty | "As-is" disclaimer, limited 30/90-day fix warranty |
| Dispute resolution | Arbitration (AAA/ICC), courts (jurisdiction-specific) |
When to Use
- Starting a new client engagement and need a contract fast
- Client asks for a proposal with pricing and timeline
- Partnership or vendor relationship requiring an MSA
- Protecting IP or confidential information with an NDA
- EU/DACH project requiring GDPR-compliant data clauses
Workflow
1. Gather Requirements
Ask the user:
1. Document type? (contract / proposal / SOW / NDA / MSA)
2. Jurisdiction? (US-Delaware / EU / UK / DACH)
3. Engagement type? (fixed-price / hourly / retainer)
4. Parties? (names, roles, business addresses)
5. Scope summary? (1-3 sentences)
6. Total value or hourly rate?
7. Start date / end date or duration?
8. Special requirements? (IP assignment, white-label, subcontractors)
2. Select Template
| Type | Jurisdiction | Template |
|---|---|---|
| Dev contract fixed | Any | Template A |
| Consulting retainer | Any | Template B |
| SaaS partnership | Any | Template C |
| NDA mutual | US/EU/UK/DACH | NDA-M |
| NDA one-way | US/EU/UK/DACH | NDA-OW |
| SOW | Any | SOW base |
3. Generate & Fill
Fill all [BRACKETED] placeholders. Flag missing data as "REQUIRED".
4. Convert to DOCX
# Install pandoc
brew install pandoc # macOS
apt install pandoc # Ubuntu
# Basic conversion
pandoc contract.md -o contract.docx \
--reference-doc=reference.docx \
-V geometry:margin=1in
# With numbered sections (legal style)
pandoc contract.md -o contract.docx \
--number-sections \
-V documentclass=article \
-V fontsize=11pt
# With custom company template
pandoc contract.md -o contract.docx \
--reference-doc=company-template.docx
Jurisdiction Notes
US (Delaware)
- Governing law: State of Delaware
- Work-for-hire doctrine applies (Copyright Act 101)
- Arbitration: AAA Commercial Rules
- Non-compete: enforceable with reasonable scope/time
EU (GDPR)
- Must include Data Processing Addendum if handling personal data
- IP assignment requires separate written deed in some member states
- Arbitration: ICC or local chamber
UK (post-Brexit)
- Governed by English law
- IP: Patents Act 1977 / CDPA 1988
- Arbitration: LCIA Rules
- Data: UK GDPR (post-Brexit equivalent)
DACH (Germany / Austria / Switzerland)
- BGB (Buergerliches Gesetzbuch) governs contracts
- Written form requirement for certain clauses (para 126 BGB)
- IP: Author always retains moral rights; must explicitly transfer Nutzungsrechte
- Non-competes: max 2 years, compensation required (para 74 HGB)
- Jurisdiction: German courts (Landgericht) or DIS arbitration
- DSGVO (GDPR implementation) mandatory for personal data processing
- Kuendigungsfristen: statutory notice periods apply
Template A: Web Dev Fixed-Price Contract
# SOFTWARE DEVELOPMENT AGREEMENT
**Effective Date:** [DATE]
**Client:** [CLIENT LEGAL NAME], [ADDRESS] ("Client")
**Developer:** [YOUR LEGAL NAME / COMPANY], [ADDRESS] ("Developer")
---
## 1. SERVICES
Developer agrees to design, develop, and deliver:
**Project:** [PROJECT NAME]
**Description:** [1-3 sentence scope]
**Deliverables:**
- [Deliverable 1] due [DATE]
- [Deliverable 2] due [DATE]
- [Deliverable 3] due [DATE]
## 2. PAYMENT
**Total Fee:** [CURRENCY] [AMOUNT]
| Milestone | Amount | Due |
|-----------|--------|-----|
| Contract signing | 50% | Upon execution |
| Beta delivery | 25% | [DATE] |
| Final acceptance | 25% | Within 5 days of acceptance |
Late payments accrue interest at 1.5% per month.
Client has [10] business days to accept or reject deliverables in writing.
## 3. INTELLECTUAL PROPERTY
Upon receipt of full payment, Developer assigns all right, title, and interest in the
Work Product to Client as a work made for hire (US) / by assignment of future copyright (EU/UK).
Developer retains the right to display Work Product in portfolio unless Client
requests confidentiality in writing within [30] days of delivery.
Pre-existing IP (tools, libraries, frameworks) remains Developer's property.
Developer grants Client a perpetual, royalty-free license to use pre-existing IP
as embedded in the Work Product.
## 4. CONFIDENTIALITY
Each party keeps confidential all non-public information received from the other.
This obligation survives termination for [3] years.
## 5. WARRANTIES
Developer warrants Work Product will substantially conform to specifications for
[90] days post-delivery. Developer will fix material defects at no charge during
this period. EXCEPT AS STATED, WORK PRODUCT IS PROVIDED "AS IS."
## 6. LIABILITY
Developer's total liability shall not exceed total fees paid under this Agreement.
Neither party liable for indirect, incidental, or consequential damages.
## 7. TERMINATION
For Cause: Either party may terminate if the other materially breaches and fails
to cure within [14] days of written notice.
For Convenience: Client may terminate with [30] days written notice and pay for
all work completed plus [10%] of remaining contract value.
## 8. DISPUTE RESOLUTION
US: Binding arbitration under AAA Commercial Rules, [CITY], Delaware law.
EU/DACH: ICC / DIS arbitration, [CITY]. German / English law.
UK: LCIA Rules, London. English law.
## 9. GENERAL
- Entire Agreement: Supersedes all prior discussions.
- Amendments: Must be in writing, signed by both parties.
- Independent Contractor: Developer is not an employee of Client.
---
CLIENT: _________________________ Date: _________
[CLIENT NAME], [TITLE]
DEVELOPER: _________________________ Date: _________
[YOUR NAME], [TITLE]
Template B: Monthly Consulting Retainer
# CONSULTING RETAINER AGREEMENT
**Effective Date:** [DATE]
**Client:** [CLIENT LEGAL NAME] ("Client")
**Consultant:** [YOUR NAME / COMPANY] ("Consultant")
---
## 1. SERVICES
Consultant provides [DOMAIN, e.g., "CTO advisory and technical architecture"] services.
**Monthly Hours:** Up to [X] hours/month
**Rollover:** Unused hours [do / do not] roll over (max [X] hours banked)
**Overflow Rate:** [CURRENCY] [RATE]/hr for hours exceeding retainer
## 2. FEES
**Monthly Retainer:** [CURRENCY] [AMOUNT], due on the 1st of each month.
**Payment Method:** Bank transfer / Stripe / SEPA direct debit
**Late Payment:** 2% monthly interest after [10]-day grace period.
## 3. TERM AND TERMINATION
**Initial Term:** [3] months starting [DATE]
**Renewal:** Auto-renews monthly unless either party gives [30] days written notice.
**Immediate termination:** For material breach uncured after [7] days notice.
On termination, Consultant delivers all work in progress within [5] business days.
## 4. INTELLECTUAL PROPERTY
Work product created under this Agreement belongs to [Client / Consultant / jointly].
Advisory output (recommendations, analyses) are Client property upon full payment.
## 5. EXCLUSIVITY
[OPTION A - Non-exclusive:]
This Agreement is non-exclusive. Consultant may work with other clients.
[OPTION B - Partial exclusivity:]
Consultant will not work with direct competitors of Client during the term
and [90] days thereafter.
## 6. CONFIDENTIALITY AND DATA PROTECTION
EU/DACH: If Consultant processes personal data on behalf of Client, the parties
shall execute a Data Processing Agreement (DPA) per Art. 28 GDPR.
## 7. LIABILITY
Consultant's aggregate liability is capped at [3x] the fees paid in the [3] months
preceding the claim.
---
Signatures as above.
Template C: SaaS Partnership Agreement
# SAAS PARTNERSHIP AGREEMENT
**Effective Date:** [DATE]
**Provider:** [NAME], [ADDRESS]
**Partner:** [NAME], [ADDRESS]
---
## 1. PURPOSE
Provider grants Partner [reseller / referral / white-label / integration] rights to
Provider's [PRODUCT NAME] ("Software") subject to this Agreement.
## 2. PARTNERSHIP TYPE
[ ] Referral: Partner refers customers; earns [X%] of first-year ARR per referral.
[ ] Reseller: Partner resells licenses; earns [X%] discount off list price.
[ ] White-label: Partner rebrands Software; pays [AMOUNT]/month platform fee.
[ ] Integration: Partner integrates Software via API; terms in Exhibit A.
## 3. REVENUE SHARE
| Tier | Monthly ARR Referred | Commission |
|------|---------------------|------------|
| Bronze | < $10,000 | [X]% |
| Silver | $10,000-$50,000 | [X]% |
| Gold | > $50,000 | [X]% |
Payout: Net-30 after month close, minimum $[500] threshold.
## 4. INTELLECTUAL PROPERTY
Each party retains all IP in its own products. No implied licenses.
Partner may use Provider's marks per Provider's Brand Guidelines (Exhibit B).
## 5. DATA AND PRIVACY
Each party is an independent data controller for its own customers.
Joint processing requires a separate DPA (Exhibit C - EU/DACH projects).
## 6. TERM
Initial: [12] months. Renews annually unless [90]-day written notice given.
Termination for Cause: [30]-day cure period for material breach.
## 7. LIMITATION OF LIABILITY
Each party's liability capped at [1x] fees paid/received in prior [12] months.
Mutual indemnification for IP infringement claims from own products.
---
Signatures, exhibits, and governing law per applicable jurisdiction.
GDPR Data Processing Addendum (EU/DACH Clause Block)
## DATA PROCESSING ADDENDUM (Art. 28 GDPR)
Controller: [CLIENT NAME]
Processor: [CONTRACTOR NAME]
### Subject Matter
Processor processes personal data on behalf of Controller solely to perform services
under the main Agreement.
### Categories of Data Subjects
[e.g., end users, employees, customers]
### Categories of Personal Data
[e.g., names, email addresses, usage data]
### Processing Duration
For the term of the main Agreement; deletion within [30] days of termination.
### Processor Obligations
- Process data only on Controller's documented instructions
- Ensure persons authorized to process have committed to confidentiality
- Implement technical and organizational measures per Art. 32 GDPR
- Assist Controller with data subject rights requests
- Not engage sub-processors without prior written consent
- Delete or return all personal data upon termination
### Sub-processors (current as of Effective Date)
| Sub-processor | Location | Purpose |
|--------------|----------|---------|
| [AWS / GCP / Azure] | [Region] | Cloud hosting |
| [Other] | [Location] | [Purpose] |
### Cross-border Transfers
Data transfers outside EEA covered by: [ ] SCCs [ ] Adequacy Decision [ ] BCRs
Common Pitfalls
- Missing IP assignment language - "work for hire" alone is insufficient in EU; need explicit assignment of Nutzungsrechte in DACH
- Vague acceptance criteria - Always define what "accepted" means (written sign-off, X days to reject)
- No change order process - Scope creep kills fixed-price projects; add a clause for out-of-scope work
- Jurisdiction mismatch - Choosing Delaware law for a German-only project creates enforcement problems
- Missing limitation of liability - Without a cap, one bug could mean unlimited damages
- Oral amendments - Contracts modified verbally are hard to enforce; always require written amendments
Best Practices
- Use milestone payments over net-30 for projects >$10K - reduces cash flow risk
- For EU/DACH: always check if a DPA is needed (any personal data = yes)
- For DACH: include a Schriftformklausel (written form clause) explicitly
- Add a force majeure clause for anything over 3 months
- For retainers: define response time SLAs (e.g., 4h urgent / 24h normal)
- Keep templates in version control; track changes with
git diff - Review annually - laws change, especially GDPR enforcement interpretations
- For NDAs: always specify the return/destruction of confidential materials on termination
| 1 | |
| 2 | name "contract-and-proposal-writer" |
| 3 | description "Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting points. Use when drafting a freelance contract, preparing a client proposal, writing an SOW for a new engagement, or producing an NDA before sharing sensitive material." |
| 4 | |
| 5 | |
| 6 | # Contract & Proposal Writer |
| 7 | |
| 8 | **Tier:** POWERFUL |
| 9 | **Category:** Business Growth |
| 10 | **Domain:** Legal Documents, Business Development, Client Relations |
| 11 | |
| 12 | |
| 13 | |
| 14 | ## Overview |
| 15 | |
| 16 | Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Outputs structured Markdown with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. |
| 17 | |
| 18 | **Not a substitute for legal counsel.** Use these templates as strong starting points; review with an attorney for high-value or complex engagements. |
| 19 | |
| 20 | |
| 21 | |
| 22 | ## Core Capabilities |
| 23 | |
| 24 | Freelance development contracts (fixed-price & hourly) |
| 25 | Project proposals with timeline/budget breakdown |
| 26 | Statements of Work (SOW) with deliverables matrix |
| 27 | NDAs (mutual & one-way) |
| 28 | Master Service Agreements (MSA) |
| 29 | Jurisdiction-specific clauses (US/EU/UK/DACH) |
| 30 | GDPR Data Processing Addenda (EU/DACH) |
| 31 | |
| 32 | |
| 33 | |
| 34 | ## Key Clauses Reference |
| 35 | |
| 36 | | Clause | Options | |
| 37 | |--------|---------| |
| 38 | | Payment terms | Net-30, milestone-based, monthly retainer | |
| 39 | | IP ownership | Work-for-hire (US), assignment (EU/UK), license-back | |
| 40 | | Liability cap | 1x contract value (standard), 3x (high-risk) | |
| 41 | | Termination | For cause (14-day cure), convenience (30/60/90-day notice) | |
| 42 | | Confidentiality | 2-5 year term, perpetual for trade secrets | |
| 43 | | Warranty | "As-is" disclaimer, limited 30/90-day fix warranty | |
| 44 | | Dispute resolution | Arbitration (AAA/ICC), courts (jurisdiction-specific) | |
| 45 | |
| 46 | |
| 47 | |
| 48 | ## When to Use |
| 49 | |
| 50 | Starting a new client engagement and need a contract fast |
| 51 | Client asks for a proposal with pricing and timeline |
| 52 | Partnership or vendor relationship requiring an MSA |
| 53 | Protecting IP or confidential information with an NDA |
| 54 | EU/DACH project requiring GDPR-compliant data clauses |
| 55 | |
| 56 | |
| 57 | |
| 58 | ## Workflow |
| 59 | |
| 60 | ### 1. Gather Requirements |
| 61 | |
| 62 | Ask the user: |
| 63 | |
| 64 | Document type? (contract / proposal / SOW / NDA / MSA) |
| 65 | Jurisdiction? (US-Delaware / EU / UK / DACH) |
| 66 | Engagement type? (fixed-price / hourly / retainer) |
| 67 | Parties? (names, roles, business addresses) |
| 68 | Scope summary? (1-3 sentences) |
| 69 | Total value or hourly rate? |
| 70 | Start date / end date or duration? |
| 71 | Special requirements? (IP assignment, white-label, subcontractors) |
| 72 | |
| 73 | ### 2. Select Template |
| 74 | |
| 75 | | Type | Jurisdiction | Template | |
| 76 | |------|-------------|----------| |
| 77 | | Dev contract fixed | Any | Template A | |
| 78 | | Consulting retainer | Any | Template B | |
| 79 | | SaaS partnership | Any | Template C | |
| 80 | | NDA mutual | US/EU/UK/DACH | NDA-M | |
| 81 | | NDA one-way | US/EU/UK/DACH | NDA-OW | |
| 82 | | SOW | Any | SOW base | |
| 83 | |
| 84 | ### 3. Generate & Fill |
| 85 | |
| 86 | Fill all [BRACKETED] placeholders. Flag missing data as "REQUIRED". |
| 87 | |
| 88 | ### 4. Convert to DOCX |
| 89 | |
| 90 | |
| 91 | # Install pandoc |
| 92 | brew install pandoc # macOS |
| 93 | apt install pandoc # Ubuntu |
| 94 | |
| 95 | # Basic conversion |
| 96 | pandoc contract.md -o contract.docx \ |
| 97 | --reference-doc=reference.docx \ |
| 98 | -V geometry:margin=1in |
| 99 | |
| 100 | # With numbered sections (legal style) |
| 101 | pandoc contract.md -o contract.docx \ |
| 102 | --number-sections \ |
| 103 | -V documentclass=article \ |
| 104 | -V fontsize=11pt |
| 105 | |
| 106 | # With custom company template |
| 107 | pandoc contract.md -o contract.docx \ |
| 108 | --reference-doc=company-template.docx |
| 109 | |
| 110 | |
| 111 | |
| 112 | |
| 113 | ## Jurisdiction Notes |
| 114 | |
| 115 | ### US (Delaware) |
| 116 | Governing law: State of Delaware |
| 117 | Work-for-hire doctrine applies (Copyright Act 101) |
| 118 | Arbitration: AAA Commercial Rules |
| 119 | Non-compete: enforceable with reasonable scope/time |
| 120 | |
| 121 | ### EU (GDPR) |
| 122 | Must include Data Processing Addendum if handling personal data |
| 123 | IP assignment requires separate written deed in some member states |
| 124 | Arbitration: ICC or local chamber |
| 125 | |
| 126 | ### UK (post-Brexit) |
| 127 | Governed by English law |
| 128 | IP: Patents Act 1977 / CDPA 1988 |
| 129 | Arbitration: LCIA Rules |
| 130 | Data: UK GDPR (post-Brexit equivalent) |
| 131 | |
| 132 | ### DACH (Germany / Austria / Switzerland) |
| 133 | BGB (Buergerliches Gesetzbuch) governs contracts |
| 134 | Written form requirement for certain clauses (para 126 BGB) |
| 135 | IP: Author always retains moral rights; must explicitly transfer Nutzungsrechte |
| 136 | Non-competes: max 2 years, compensation required (para 74 HGB) |
| 137 | Jurisdiction: German courts (Landgericht) or DIS arbitration |
| 138 | DSGVO (GDPR implementation) mandatory for personal data processing |
| 139 | Kuendigungsfristen: statutory notice periods apply |
| 140 | |
| 141 | |
| 142 | |
| 143 | ## Template A: Web Dev Fixed-Price Contract |
| 144 | |
| 145 | |
| 146 | # SOFTWARE DEVELOPMENT AGREEMENT |
| 147 | |
| 148 | **Effective Date:** [DATE] |
| 149 | **Client:** [CLIENT LEGAL NAME], [ADDRESS] ("Client") |
| 150 | **Developer:** [YOUR LEGAL NAME / COMPANY], [ADDRESS] ("Developer") |
| 151 | |
| 152 | |
| 153 | |
| 154 | ## 1. SERVICES |
| 155 | |
| 156 | Developer agrees to design, develop, and deliver: |
| 157 | |
| 158 | **Project:** [PROJECT NAME] |
| 159 | **Description:** [1-3 sentence scope] |
| 160 | |
| 161 | **Deliverables:** |
| 162 | - [Deliverable 1] due [DATE] |
| 163 | - [Deliverable 2] due [DATE] |
| 164 | - [Deliverable 3] due [DATE] |
| 165 | |
| 166 | ## 2. PAYMENT |
| 167 | |
| 168 | **Total Fee:** [CURRENCY] [AMOUNT] |
| 169 | |
| 170 | | Milestone | Amount | Due | |
| 171 | |-----------|--------|-----| |
| 172 | | Contract signing | 50% | Upon execution | |
| 173 | | Beta delivery | 25% | [DATE] | |
| 174 | | Final acceptance | 25% | Within 5 days of acceptance | |
| 175 | |
| 176 | Late payments accrue interest at 1.5% per month. |
| 177 | Client has [10] business days to accept or reject deliverables in writing. |
| 178 | |
| 179 | ## 3. INTELLECTUAL PROPERTY |
| 180 | |
| 181 | Upon receipt of full payment, Developer assigns all right, title, and interest in the |
| 182 | Work Product to Client as a work made for hire (US) / by assignment of future copyright (EU/UK). |
| 183 | |
| 184 | Developer retains the right to display Work Product in portfolio unless Client |
| 185 | requests confidentiality in writing within [30] days of delivery. |
| 186 | |
| 187 | Pre-existing IP (tools, libraries, frameworks) remains Developer's property. |
| 188 | Developer grants Client a perpetual, royalty-free license to use pre-existing IP |
| 189 | as embedded in the Work Product. |
| 190 | |
| 191 | ## 4. CONFIDENTIALITY |
| 192 | |
| 193 | Each party keeps confidential all non-public information received from the other. |
| 194 | This obligation survives termination for [3] years. |
| 195 | |
| 196 | ## 5. WARRANTIES |
| 197 | |
| 198 | Developer warrants Work Product will substantially conform to specifications for |
| 199 | [90] days post-delivery. Developer will fix material defects at no charge during |
| 200 | this period. EXCEPT AS STATED, WORK PRODUCT IS PROVIDED "AS IS." |
| 201 | |
| 202 | ## 6. LIABILITY |
| 203 | |
| 204 | Developer's total liability shall not exceed total fees paid under this Agreement. |
| 205 | Neither party liable for indirect, incidental, or consequential damages. |
| 206 | |
| 207 | ## 7. TERMINATION |
| 208 | |
| 209 | For Cause: Either party may terminate if the other materially breaches and fails |
| 210 | to cure within [14] days of written notice. |
| 211 | |
| 212 | For Convenience: Client may terminate with [30] days written notice and pay for |
| 213 | all work completed plus [10%] of remaining contract value. |
| 214 | |
| 215 | ## 8. DISPUTE RESOLUTION |
| 216 | |
| 217 | US: Binding arbitration under AAA Commercial Rules, [CITY], Delaware law. |
| 218 | EU/DACH: ICC / DIS arbitration, [CITY]. German / English law. |
| 219 | UK: LCIA Rules, London. English law. |
| 220 | |
| 221 | ## 9. GENERAL |
| 222 | |
| 223 | - Entire Agreement: Supersedes all prior discussions. |
| 224 | - Amendments: Must be in writing, signed by both parties. |
| 225 | - Independent Contractor: Developer is not an employee of Client. |
| 226 | |
| 227 | |
| 228 | |
| 229 | CLIENT: _________________________ Date: _________ |
| 230 | [CLIENT NAME], [TITLE] |
| 231 | |
| 232 | DEVELOPER: _________________________ Date: _________ |
| 233 | [YOUR NAME], [TITLE] |
| 234 | |
| 235 | |
| 236 | |
| 237 | |
| 238 | ## Template B: Monthly Consulting Retainer |
| 239 | |
| 240 | |
| 241 | # CONSULTING RETAINER AGREEMENT |
| 242 | |
| 243 | **Effective Date:** [DATE] |
| 244 | **Client:** [CLIENT LEGAL NAME] ("Client") |
| 245 | **Consultant:** [YOUR NAME / COMPANY] ("Consultant") |
| 246 | |
| 247 | |
| 248 | |
| 249 | ## 1. SERVICES |
| 250 | |
| 251 | Consultant provides [DOMAIN, e.g., "CTO advisory and technical architecture"] services. |
| 252 | |
| 253 | **Monthly Hours:** Up to [X] hours/month |
| 254 | **Rollover:** Unused hours [do / do not] roll over (max [X] hours banked) |
| 255 | **Overflow Rate:** [CURRENCY] [RATE]/hr for hours exceeding retainer |
| 256 | |
| 257 | ## 2. FEES |
| 258 | |
| 259 | **Monthly Retainer:** [CURRENCY] [AMOUNT], due on the 1st of each month. |
| 260 | **Payment Method:** Bank transfer / Stripe / SEPA direct debit |
| 261 | **Late Payment:** 2% monthly interest after [10]-day grace period. |
| 262 | |
| 263 | ## 3. TERM AND TERMINATION |
| 264 | |
| 265 | **Initial Term:** [3] months starting [DATE] |
| 266 | **Renewal:** Auto-renews monthly unless either party gives [30] days written notice. |
| 267 | **Immediate termination:** For material breach uncured after [7] days notice. |
| 268 | |
| 269 | On termination, Consultant delivers all work in progress within [5] business days. |
| 270 | |
| 271 | ## 4. INTELLECTUAL PROPERTY |
| 272 | |
| 273 | Work product created under this Agreement belongs to [Client / Consultant / jointly]. |
| 274 | Advisory output (recommendations, analyses) are Client property upon full payment. |
| 275 | |
| 276 | ## 5. EXCLUSIVITY |
| 277 | |
| 278 | [OPTION A - Non-exclusive:] |
| 279 | This Agreement is non-exclusive. Consultant may work with other clients. |
| 280 | |
| 281 | [OPTION B - Partial exclusivity:] |
| 282 | Consultant will not work with direct competitors of Client during the term |
| 283 | and [90] days thereafter. |
| 284 | |
| 285 | ## 6. CONFIDENTIALITY AND DATA PROTECTION |
| 286 | |
| 287 | EU/DACH: If Consultant processes personal data on behalf of Client, the parties |
| 288 | shall execute a Data Processing Agreement (DPA) per Art. 28 GDPR. |
| 289 | |
| 290 | ## 7. LIABILITY |
| 291 | |
| 292 | Consultant's aggregate liability is capped at [3x] the fees paid in the [3] months |
| 293 | preceding the claim. |
| 294 | |
| 295 | |
| 296 | |
| 297 | Signatures as above. |
| 298 | |
| 299 | |
| 300 | |
| 301 | |
| 302 | ## Template C: SaaS Partnership Agreement |
| 303 | |
| 304 | |
| 305 | # SAAS PARTNERSHIP AGREEMENT |
| 306 | |
| 307 | **Effective Date:** [DATE] |
| 308 | **Provider:** [NAME], [ADDRESS] |
| 309 | **Partner:** [NAME], [ADDRESS] |
| 310 | |
| 311 | |
| 312 | |
| 313 | ## 1. PURPOSE |
| 314 | |
| 315 | Provider grants Partner [reseller / referral / white-label / integration] rights to |
| 316 | Provider's [PRODUCT NAME] ("Software") subject to this Agreement. |
| 317 | |
| 318 | ## 2. PARTNERSHIP TYPE |
| 319 | |
| 320 | [ ] Referral: Partner refers customers; earns [X%] of first-year ARR per referral. |
| 321 | [ ] Reseller: Partner resells licenses; earns [X%] discount off list price. |
| 322 | [ ] White-label: Partner rebrands Software; pays [AMOUNT]/month platform fee. |
| 323 | [ ] Integration: Partner integrates Software via API; terms in Exhibit A. |
| 324 | |
| 325 | ## 3. REVENUE SHARE |
| 326 | |
| 327 | | Tier | Monthly ARR Referred | Commission | |
| 328 | |------|---------------------|------------| |
| 329 | | Bronze | < $10,000 | [X]% | |
| 330 | | Silver | $10,000-$50,000 | [X]% | |
| 331 | | Gold | > $50,000 | [X]% | |
| 332 | |
| 333 | Payout: Net-30 after month close, minimum $[500] threshold. |
| 334 | |
| 335 | ## 4. INTELLECTUAL PROPERTY |
| 336 | |
| 337 | Each party retains all IP in its own products. No implied licenses. |
| 338 | Partner may use Provider's marks per Provider's Brand Guidelines (Exhibit B). |
| 339 | |
| 340 | ## 5. DATA AND PRIVACY |
| 341 | |
| 342 | Each party is an independent data controller for its own customers. |
| 343 | Joint processing requires a separate DPA (Exhibit C - EU/DACH projects). |
| 344 | |
| 345 | ## 6. TERM |
| 346 | |
| 347 | Initial: [12] months. Renews annually unless [90]-day written notice given. |
| 348 | Termination for Cause: [30]-day cure period for material breach. |
| 349 | |
| 350 | ## 7. LIMITATION OF LIABILITY |
| 351 | |
| 352 | Each party's liability capped at [1x] fees paid/received in prior [12] months. |
| 353 | Mutual indemnification for IP infringement claims from own products. |
| 354 | |
| 355 | |
| 356 | |
| 357 | Signatures, exhibits, and governing law per applicable jurisdiction. |
| 358 | |
| 359 | |
| 360 | |
| 361 | |
| 362 | ## GDPR Data Processing Addendum (EU/DACH Clause Block) |
| 363 | |
| 364 | |
| 365 | ## DATA PROCESSING ADDENDUM (Art. 28 GDPR) |
| 366 | |
| 367 | Controller: [CLIENT NAME] |
| 368 | Processor: [CONTRACTOR NAME] |
| 369 | |
| 370 | ### Subject Matter |
| 371 | Processor processes personal data on behalf of Controller solely to perform services |
| 372 | under the main Agreement. |
| 373 | |
| 374 | ### Categories of Data Subjects |
| 375 | [e.g., end users, employees, customers] |
| 376 | |
| 377 | ### Categories of Personal Data |
| 378 | [e.g., names, email addresses, usage data] |
| 379 | |
| 380 | ### Processing Duration |
| 381 | For the term of the main Agreement; deletion within [30] days of termination. |
| 382 | |
| 383 | ### Processor Obligations |
| 384 | - Process data only on Controller's documented instructions |
| 385 | - Ensure persons authorized to process have committed to confidentiality |
| 386 | - Implement technical and organizational measures per Art. 32 GDPR |
| 387 | - Assist Controller with data subject rights requests |
| 388 | - Not engage sub-processors without prior written consent |
| 389 | - Delete or return all personal data upon termination |
| 390 | |
| 391 | ### Sub-processors (current as of Effective Date) |
| 392 | | Sub-processor | Location | Purpose | |
| 393 | |--------------|----------|---------| |
| 394 | | [AWS / GCP / Azure] | [Region] | Cloud hosting | |
| 395 | | [Other] | [Location] | [Purpose] | |
| 396 | |
| 397 | ### Cross-border Transfers |
| 398 | Data transfers outside EEA covered by: [ ] SCCs [ ] Adequacy Decision [ ] BCRs |
| 399 | |
| 400 | |
| 401 | |
| 402 | |
| 403 | ## Common Pitfalls |
| 404 | |
| 405 | **Missing IP assignment language** - "work for hire" alone is insufficient in EU; need explicit assignment of Nutzungsrechte in DACH |
| 406 | **Vague acceptance criteria** - Always define what "accepted" means (written sign-off, X days to reject) |
| 407 | **No change order process** - Scope creep kills fixed-price projects; add a clause for out-of-scope work |
| 408 | **Jurisdiction mismatch** - Choosing Delaware law for a German-only project creates enforcement problems |
| 409 | **Missing limitation of liability** - Without a cap, one bug could mean unlimited damages |
| 410 | **Oral amendments** - Contracts modified verbally are hard to enforce; always require written amendments |
| 411 | |
| 412 | |
| 413 | |
| 414 | ## Best Practices |
| 415 | |
| 416 | Use **milestone payments** over net-30 for projects >$10K - reduces cash flow risk |
| 417 | For EU/DACH: always check if a DPA is needed (any personal data = yes) |
| 418 | For DACH: include a **Schriftformklausel** (written form clause) explicitly |
| 419 | Add a **force majeure** clause for anything over 3 months |
| 420 | For retainers: define response time SLAs (e.g., 4h urgent / 24h normal) |
| 421 | Keep templates in version control; track changes with `git diff` |
| 422 | Review annually - laws change, especially GDPR enforcement interpretations |
| 423 | For NDAs: always specify the return/destruction of confidential materials on termination |
| 424 |
Discussion
Browse more free Claude skills or everything in Legal & compliance.