You build a retainer offer without inviting scope creep by defining exactly what the monthly fee covers, setting limits in hours or deliverables, stating how requests are made and how fast you respond, and deciding in advance what happens when the client asks for more. A retainer is a defined bundle of capacity, not an open-ended promise to be available.
Below is a step-by-step build: choose the model, define inclusions and exclusions, set a request process, handle overage, price it, write the terms, and review it regularly. Dollar and hour figures are illustrative placeholders.
Why retainers invite scope creep
A retainer feels simple to clients: pay a monthly fee and get help. That simplicity is also the risk. If the offer says “ongoing support” or “as needed,” the client can reasonably assume that anything related falls inside it. Requests arrive daily, sizes vary, and by month end you have done far more than you priced.
Three features make creep worse in retainers than in projects:
- No natural end. A project finishes. A retainer renews, so unclear terms repeat every month.
- Small requests accumulate. Each seems minor, so you say yes without noticing the total.
- Familiarity. As the relationship grows comfortable, boundaries soften.
The fix is a structure that makes usage visible and gives both sides a simple way to adjust. If you are still deciding whether a retainer is the right format, see when to use retainer vs project pricing.
Step 1: Choose how the retainer is measured
| Model | How it works | Scope-creep risk | Best for |
|---|---|---|---|
| Hours bank | A set number of hours a month | Lower, since hours are visible | Mixed or unpredictable tasks |
| Defined deliverables | A fixed list, such as 4 articles or 2 design updates | Medium, if “update” is vague | Repeatable output |
| Availability or access | Priority response and a call each month | Higher, unless limits are stated | Advisory or consulting work |
Hours banks are the easiest to control because you can show usage. Deliverable-based retainers feel better to clients because they get a tangible output, but each deliverable must be defined. Availability retainers need extra limits on response windows and meeting time. A combined version often works: a fixed number of deliverables plus a small bucket of hours for small requests.
Step 2: Define what is included and excluded
Write the included services in concrete terms.
Weak: “Ongoing website support.”
Better: “Up to 8 hours per month of website support: text and image updates on existing pages, minor layout adjustments, and a monthly check that forms and links work.”
Then list exclusions in plain language:
- New page builds or new features (quoted as separate projects)
- Redesigns or rebranding
- Work on third-party tools or integrations
- Emergency work outside business hours, unless a rush rate applies
- Strategy workshops or training sessions
Think about what the client is most likely to ask for that is not included, and put those items on the list. The initial project usually shows which ones. The article on setting a project scope that does not drift immediately and the project scope checklist help with this step.
Step 3: Create a clear request process
Creep often comes from informal requests: a text, a passing comment on a call, an email buried in a thread. A simple process fixes this.
- One channel. Requests go to a shared inbox, a form, or a project board.
- A short template. A description, a deadline, and any files or links.
- Confirmation. You reply within a stated time with an estimate of hours or confirmation that it fits.
- A running tally. Share usage live in a shared sheet or in a short end-of-month note.
Sample wording: “Requests are submitted via [channel]. I will confirm receipt within one business day and give an estimated time. Standard turnaround is three business days after confirmation.”
A visible tally changes behavior. When a client can see that most of the hours are gone mid-month, they tend to prioritize, which is what you want.
Step 4: Decide what happens when limits are reached
This is the most important rule in the offer, and the one most often skipped. Decide before the first month what you will do when the client uses all the hours or asks for something outside the scope.
- Pause until next month. Requests wait for the next cycle.
- Overage at an hourly rate. Additional hours billed at your standard rate or a premium.
- Upgrade the plan. Offer the next tier for the rest of the month or going forward.
- Quote separately. Larger work becomes its own project.
Sample wording: “If the monthly hours are used, additional requests will be billed at $X per hour with the client’s approval, or scheduled for the next month. Work that requires more than [N] hours will be quoted as a separate project.”
Choose a rollover rule too, and state it. Some freelancers let unused hours expire because they reserved capacity regardless of use; others allow limited rollover. Either can be fair if it is written down.
Step 5: Price the retainer
Start from your floor rate and the capacity you will reserve. For example, if your floor is $80 an hour and you reserve 12 hours a month, the floor price is $960. Then consider:
- Admin time. Retainers can cut selling time but add reporting and coordination.
- Priority access. If you promise fast turnaround, consider a premium.
- Commitment discount. Some freelancers offer a modest discount for a minimum term. Only do it if the numbers still work.
- Risk. A client with a history of heavy requests may need a higher price or a smaller scope.
Do not set a retainer below your floor to win commitment. Pricing freelance work without undercharging shows how to build the floor, and the pricing worksheet can help. Compare your estimate with a few months of real usage and adjust at review. Many freelancers bill at the start of the month to reduce payment risk; make sure your terms match your contract.
Step 6: Write the terms
Put the key terms in a short agreement or a clear section of your proposal:
- Term and renewal. For example, a minimum term, then month-to-month
- Fee and billing date
- Included work and exclusions
- Hours or deliverables per month
- Request process and turnaround
- Overage handling and rollover rule
- Notice period to end or change the plan
- Review schedule
Contract rules and what is enforceable vary by state and country. Some places, including New York State and a few cities, have laws on written agreements and payment timing for freelancers above certain amounts, so check what applies to you. A qualified professional, such as an attorney, can review your retainer agreement, especially terms on termination, ownership, and liability.
Step 7: Review and adjust
A retainer is not set and forget. Schedule a short review after the first month and then every quarter. Ask:
- Did the client use the full amount? Is it too much or too little?
- Which requests were most common? Should they become a defined deliverable?
- How many requests fell outside the scope, and how were they handled?
- Was the turnaround realistic?
- Is the price still right for the work?
If a client regularly exceeds the plan, propose the next tier. If they use far less, check whether the retainer still gives them value; a client who feels they overpay may cancel, and early honesty can save the relationship.
Sample retainer summary
“Monthly Support Plan. Includes up to [N] hours of [service] per month, covering [list]. Requests are submitted via [channel] and acknowledged within one business day. Standard turnaround is three business days. Unused hours expire at the end of the month. Additional hours are available at $X per hour with approval. Work outside the scope, such as [examples], is quoted separately. Fee: $Y per month, billed on the 1st. Minimum term: [length], then [notice period]. Review: quarterly.”
If clients push past these terms anyway, setting better freelance boundaries with clients has scripts.
Where this comes from
This article is based on common freelance and consulting practice for structuring recurring work, plus published summaries of New York State’s Freelance Isn’t Free Act and similar local freelancer-payment laws. It is not based on first-hand testing and contains no income claims; all figures are illustrative. It is general information, not legal advice, so have a qualified professional review any agreement. Prices, rates, and rules change and should be checked at the source.