TL;DR
On this page
ChatGPT will draft a freelance retainer agreement from a single prompt, and the structure it returns is fine. The problem is the four clauses it leaves generic, because those four are exactly the ones a retainer dispute turns on: the scope cap, the unused-hours rollover policy, the termination notice period, and the rate-review trigger. Use the prompt below to generate the skeleton, then tighten those four before you send it.
This walkthrough is part of the complete guide to freelancing in the AI era, and a sibling of the project-contract AI prompt.
Getting it right is worth the few minutes, because the retainer is now the default way ongoing work gets billed. In SparkToro's 2026 agency survey, Paddy Moogan found the model has only gained ground:
Our survey confirmed what many of us would guess instinctively, 85% of agencies prefer to work with clients on a retainer basis.
Source: Paddy Moogan, SparkToro (January 2026)
That is up from 81% the year before. The same logic pulls solo freelancers toward retainers for their steady clients: predictable income on your side, guaranteed access on theirs. The agreement is what makes the arrangement safe.
The prompt
Paste this into ChatGPT, Claude, or Gemini. Replace the bracketed placeholders with your details, and keep real client names out of it until the draft is done (more on that below).
You are drafting a freelance retainer agreement. Write a clear, plain-English
monthly retainer agreement between [YOUR BUSINESS NAME] (the Provider) and
[CLIENT PLACEHOLDER] (the Client) for ongoing [YOUR SERVICE, e.g. SEO,
design, bookkeeping] work.
Include and clearly label these sections:
1. Parties and term (month-to-month, auto-renewing)
2. Monthly fee of [AMOUNT] and payment terms (due date, late fee, method)
3. Scope: a cap of [N HOURS or N DELIVERABLES] per month, with a clear
line stating that work beyond the cap is billed separately at [RATE]
4. Unused hours: state explicitly whether unused hours expire at the end of
each billing cycle or roll over, and if they roll over, the cap and limit
5. Termination: [14 or 30] days written notice by either party, and what
happens to in-progress work and the final invoice
6. Rate review: the monthly fee may be reviewed every [12 months]
7. Confidentiality and IP ownership transferring to the Client on payment
8. Governing law: [YOUR STATE OR COUNTRY]
Use short sentences. Do not invent legal citations. Flag any section where
you need more detail from me.
That prompt already forces the model to address the four weak clauses by name. Even so, read what it returns closely, because AI tends to soften exactly these points back into vagueness.
The four clauses AI leaves generic
Scope cap and out-of-scope boundary. This is the one that quietly sinks retainers. A model asked for a "monthly retainer" will happily write a fee and a friendly description of the work and never pin down a limit. A practitioner writing as ACE on dev.to names the failure mode directly:
The most common failure mode is the "monthly fee for ongoing services" template, a contract that specifies the monthly fee but doesn't specify either an hour budget or a scope boundary.
Source: ACE (@acehq), dev.to
The fix is two sentences: a cap ("up to 20 hours per month") and an out-of-scope line ("work beyond 20 hours is billed at $X/hour with prior written approval"). That single addition turns "while you're at it" requests from free work into a billing decision. The deeper playbook for this is in how to handle scope creep.
Unused-hours rollover policy. AI almost never addresses what happens to hours the client did not use, and silence here is the single most common retainer argument: the client assumes the hours banked, you assumed they expired. There is no default rule, so state one. Either "unused hours do not roll over and expire at the end of each billing cycle," or "up to 50% of unused hours roll over for one billing cycle, then expire." Pick the one that matches your capacity and write it in plain words.
Termination notice period. A model will often write "either party may terminate this agreement" with no notice window, which leaves you exposed to a client who cancels the day before a month starts after you have blocked the time. Specify the notice: 14 or 30 days written notice by either side, plus a line on how in-progress work and the final invoice are handled.
Rate-review trigger. This is the invisible one. AI-drafted retainers lock you at your launch rate with no mechanism to revisit it, so a client you signed at an introductory price stays there for years. Add a single line giving the fee a review point, for example "the monthly fee may be reviewed every 12 months." It does not force an increase; it just keeps the door open so a long retainer does not become an underpaid one.
pro tip
The scope clause is the highest-leverage of the four. If you only tighten one, tighten that. The full anatomy of a defensible retainer, including pricing and the pitch to move a client onto one, is in the freelance retainer agreement guide.
Keep client data out of the draft
One safety note that applies to every AI-drafting workflow. Until the agreement is finished, use placeholders like [CLIENT PLACEHOLDER] rather than pasting your client's real name, rates, or project details into a consumer AI tool, because on most personal plans those inputs can be used for training. Draft with placeholders, then fill in the real details in your own document afterward. The full reasoning is in is it safe to paste client info into ChatGPT.
Draft fast, tighten the four, send
The AI handles the 80% that is boilerplate, and in a 2025 Useme report, 48% of freelancers said AI helps them deliver work more efficiently. You handle the 20% that protects you. That split is the whole reason to use a prompt: it removes the blank-page work without removing your judgment on the clauses that matter.
Before you send the retainer
If you would rather skip the prompt-and-tighten loop entirely, FreelanceDesk builds contracts with the scope, payment, and transfer-on-payment terms already structured, so a retainer starts from a sound base instead of a generic draft. It is free, and the document never leaves your browser. For the model-by-model version of the same workflow, the project-contract AI prompt covers one-off engagements, and the broader AI document guide maps every document type to its best prompt.