Write a Retainer Scope Both Sides Can Live With

Added 2026-11-05

Most retainer disputes hide outside the "what is included" list.

I am offering a monthly retainer service: [service, client type, fee]. Make the scope explicit: 1) list the fixed deliverables, on-demand items, and exclusions, each with one acceptance line; 2) flag the small-looking requests that eat margin — rush jobs, endless revisions, doing work the client should own; 3) give the out-of-scope rule: how it is quoted, who approves, when it takes effect; 4) set a capacity cap — rounds of revision, meetings per month — and what happens at the cap; 5) write the client-facing version, explaining the rules rather than defending against them; 6) if the client pushes back, give the order in which to concede.

Site original

Chinese original

Open in ChatGPT

Replace these placeholders 1

Swap the bracketed parts for your own details before sending.

[service, client type, fee]

How to use

A retainer sells predictable output and response, not hours.

Try tweaking it

Have it state how the hypothesis could be falsified before discussing execution.
Split the plan into a one-week testable experiment.

What you should get

A small testable experiment with a failure threshold
Costs, risks, and what needs outside confirmation

Common mistakes

Asking for a "full business plan" and getting unverifiable optimistic assumptions.
No failure threshold, so you never know whether to continue.

How to check the output

There is a clear failure threshold, testable within a week.
Costs, assumptions and risks are listed separately.

Where it works

Good for: turning business assumptions into a small testable experiment with a failure threshold first.
Watch out: for pricing, contracts and legal points, treat output as a draft needing professional review.