The latest in AI, every dayAI News

Business · July 18, 2026

Turn a project's scope into a freelance contract

From your project's scope, build a simple freelance contract in plain language with deliverables, payments and deadlines, ready to send.

This prompt turns a project's scope you already agreed with a client into a simple, plain-language freelance contract, with deliverables, payments, deadlines and the basic protections so you don't work for free or go unpaid.

For: ChatGPTClaude
Full prompt
Act as a business consultant (NOT a lawyer) who helps freelancers protect themselves with
simple, plain-language contracts, no unnecessary legal jargon. I'm going to give you a
project's scope. Your job is to turn it into a simple freelance contract, ready to copy and
send to my client.

Project scope:
[PASTE HERE: what you'll do, for whom, what you'll deliver, how much you'll charge, in how
much time]

Agreement details:
- My name or business: [YOUR NAME OR BUSINESS]
- Client name: [CLIENT NAME]
- Currency: [CURRENCY, e.g. USD]
- Country or state the agreement applies to: [COUNTRY OR STATE]

Structure the contract like this:
1. **Header**: both parties' names, date of the agreement.
2. **Purpose of the contract**: 2-3 lines on what will be done and why.
3. **Deliverables**: a specific, measurable list (never vague: not "logo design" but "1 final
   logo in PNG, SVG and PDF, with 2 rounds of revisions included").
4. **What's NOT included** (to avoid unpaid extra work).
5. **Price and payment terms**: total amount, breakdown if applicable, and when each part is
   paid (use [PAYMENT TERMS] if I didn't give you details).
6. **Timeline**: start date, delivery date, and what happens if the client delays providing
   information or approvals.
7. **Revisions**: how many rounds of changes are included and what an extra round costs.
8. **Cancellation**: what happens if either party cancels midway (use [CANCELLATION TERMS] if
   I didn't give you details).
9. **Ownership and confidentiality**: when ownership of the work transfers to the client
   (usually on final payment) and a simple confidentiality clause.
10. **Signatures**: space for name, date and signature from both parties.

Rules:
- Clear, direct language, no unnecessary legal jargon, but with the essential protections for
  the freelancer.
- If an important detail is missing (price, timeline, scope), do NOT invent it: write
  [detail to verify] instead and tell me at the end what information is missing.
- At the end, add a short note: "This is a reference template, not legal advice; have a lawyer
  review it if the project is large or the client requests changes."
- Deliver the result ready to copy into a document or email.
Short link: wandabuilds.ai/p/2CHi

Come back tomorrow for another, or see all prompts.