Use ChatGPT to Write a UX Designer Contract (Research IP, Source Files & Revision Caps)

A finished UX project often ends with one request: hand over every Figma file, the research recordings, and the wireframes. By default those files are yours, but most AI-drafted contracts have already signed them away, because the model assigns "all work product" to the client in a single sweep. The fix is to make ChatGPT name the three UX-specific clauses as it drafts: who owns the research artifacts, whether the source files transfer, and how many revision rounds you owe before the next one is billable. Use the prompt below to generate the contract, then harden those three before you send it.

This walkthrough is part of the complete guide to freelancing in the AI era, and a profession-specific version of the general contract prompt.

The stakes are not small. Freelance UX work runs from $25 to $70 an hour at junior level up to $100 to $250 for expert consultants (Twine), so a single research-and-prototype engagement is often a four-figure project. The asset a client most wants after that project ends is your editable source file, and that is exactly the asset you keep by default. As California attorney Jonathan Tobin puts it, writing for AIGA Los Angeles:

As the creator of the source files, you are the owner of those files. Aside from some exceptions, you are not required to part with them.

Source: Jonathan Tobin, California attorney, AIGA Los Angeles

That default only holds if your contract does not quietly sign it away. A generic AI draft will often assign "all work product" to the client in one clause, handing over the source files and the research data for free. The fix is to name the three clauses explicitly when you generate the draft.

The prompt

Paste this into ChatGPT, Claude, or Gemini. Fill in the brackets, and keep the client's real name and project details out until the draft is done.

You are drafting a freelance UX designer contract between [YOUR BUSINESS
NAME] (the Designer) and [CLIENT PLACEHOLDER] (the Client) for a UX design
project.

Include and clearly label:
1. Scope of services: list exactly what is included (e.g. user research,
   [N] user-testing sessions, wireframes, [N] prototype screens, design-
   system components), and a line stating anything not listed is out of
   scope and billed separately
2. Revisions: [N] rounds of revisions per phase are included; additional
   rounds are billed at [RATE]; define what counts as a revision versus a
   new scope item
3. Deliverable ownership: final UI deliverables transfer to the Client on
   cleared final payment; state separately whether editable source files
   (Figma/Sketch) and user-research artifacts (recordings, transcripts,
   personas) transfer, and on what terms
4. Source-file handoff: state whether editable working files are delivered
   at all, and that no files are released until full and final payment
   has cleared
5. Background IP: the Designer retains ownership of reusable, pre-existing
   components and design-system assets; the Client receives a license to
   use them within the delivered product
6. Fees, payment schedule, late fee, and a kill fee if the project is
   cancelled mid-way
7. Confidentiality and governing law: [YOUR STATE OR COUNTRY]

Plain English, under two pages where possible. Do not invent legal
citations.

Ask for a generic "UX design contract" without naming those three clauses and the model hands you a clean-looking document that quietly assigns everything to the client and caps nothing.

The three clauses AI gets wrong

Research IP and deliverable ownership. A UX engagement is not one deliverable; it is several, and they do not all carry the same default. Per Perkins Thompson, the protected deliverables include "research reports, descriptions of personas, sitemaps, user journeys and flows," and "copyright remains with the person or company that created the deliverables until there is a written agreement that assigns (transfers) the copyright." Name the research artifacts as a distinct class and decide which of them transfer. Raw interview recordings of identifiable participants also carry data-protection rights, so a folder of recordings is not yours to hand over casually even if you wanted to.

Source-file handoff. The flattened deliverable and the editable Figma file are two different assets, and the second is the valuable one. State whether the working file transfers at all, and tie any handoff to cleared final payment. Matt Olpinski puts the practitioner version of Tobin's legal point bluntly:

If you're providing digital files to a client, make sure you don't deliver the final files until AFTER they pay your final invoice.

Source: Matt Olpinski, UI + UX Designer

Revision caps. An unbounded revision clause is how a fixed-fee project turns into unpaid work. Most professional agencies include 2 to 3 revisions per design phase, with additional rounds billed as extra cost (Alfyi). The number is the easy part; the boundary is the clause that actually protects you. Define a revision as a refinement within the agreed direction, and a new screen, new flow, or new research question as a billable scope change. Without that line, "can we just try one more version" lands as a free round every time.

Keep client data out of the draft

Use a placeholder instead of the client's real name, product, and research findings until the contract is finished, because consumer AI plans can use your inputs for training by default. Draft with placeholders, then fill in the real details in your own copy. If the client has asked how you use AI on the project itself, that belongs in its own clause, covered in AI clauses in freelance contracts.

Generate it, then harden the three clauses

The model drafts; you decide. A practical split is the 10-80-10 rule: you handle the first 10% of strategy, hand 80% of the drafting to AI, then own the final 10% of quality control, which for a UX contract is precisely these three clauses. That last 10% is where the value sits. AI-skilled freelancers earn 44% more per hour than peers who do not use it (Upwork data via Winvesta), and 48% of freelancers say AI helps them work more efficiently (Useme), but the premium goes to those who use that speed to do better work, not cheaper work.

FreelanceDesk builds contracts with the scope, payment, and transfer-on-payment terms already structured, so a UX agreement starts from a sound base, and it is free. You add the research-IP, source-file, and revision clauses on top, and the document never leaves your browser. For the rates side of the engagement, see the UX salary versus freelance rate report. For the full AI-document workflow, the AI document guide maps every document type to its prompt.

References

• Does a Designer Have to Turn Over Source Files When a Client Asks for Them? : AIGA Los Angeles
• User Experience (UX) Design Agreements: 4 Essential Clauses : Perkins Thompson
• What to Do If Your Freelance Client Refuses to Pay : Matt Olpinski
• UI/UX Design Agency Contract Essentials : Alfyi
• UX Designer Hourly Rate : Twine
• Freelancing with AI in 2026 : Useme
• AI Cut Freelance Rates 30%: How Top Earners Fight Back : Winvesta