CLSkills
Legal

How to Use Claude for Writing Terms of Service

The exact prompt, setup, and codes to get great results.

The Problem

Every SaaS needs ToS but hiring a lawyer to draft them costs $2,000-5,000. Most founders either copy someone else's (risky) or skip them entirely (riskier).

The Prompt (Copy & Paste)

Draft Terms of Service for [PRODUCT/SERVICE].

Product type: [SAAS / MARKETPLACE / APP / API]
Business model: [SUBSCRIPTION / ONE-TIME / FREEMIUM]
User base: [B2B / B2C / BOTH]
User-generated content: [YES / NO]
Data collected: [LIST KEY DATA TYPES]
Payment processor: [STRIPE / PAYPAL / etc.]
Jurisdiction: [STATE/COUNTRY]

Include sections:
1. Acceptance of terms
2. Description of service
3. User accounts and responsibilities
4. Acceptable use policy
5. Intellectual property (your IP + user content)
6. Payment terms and refund policy
7. Limitation of liability
8. Disclaimer of warranties
9. Termination
10. Dispute resolution (arbitration vs. litigation)
11. Modifications to terms
12. Contact information

Make it readable by normal humans β€” not wall-of-text legalese.

NOTE: This is a starting draft. It must be reviewed by a qualified attorney before use.

Replace the [BRACKETED] placeholders with your specific details.

What You Get

A comprehensive, human-readable Terms of Service draft that covers all essential sections. Ready for lawyer review β€” not ready for production without one.

Prompt Codes That Help

Add these prefix codes to the start of your prompt for even better results:

Click any code to see its before/after examples and learn how it works.

Want all 120+ prompt codes?

The Claude Prompt Cheat Sheet has every tested code with before/after examples, combo stacks, and 10 workflow playbooks for different roles.

More Legal Tasks

πŸ“¬

Get new prompts + workflows weekly

Join developers and professionals getting tested Claude prompt codes, workflows, and real-world techniques. One email when there’s something worth sharing.