How to write a proposal for a retainer (ongoing hours per month)

Retainer jobs look simple on the surface. A client wants someone available every month. You quote hours. Everyone stays happy.

In practice, retainers fail when the proposal is vague about what “available” means. Clients imagine unlimited small tasks. Freelancers imagine a calm buffer of predictable income. Neither side wrote down the rules, so both feel cheated by month two.

A strong retainer proposal does not need to sound corporate. It needs to answer what the client will get each month, what happens when work spikes, and how either side can exit without drama.

What clients are really buying on a retainer

Most retainer posts are not buying “ten hours.” They are buying reduced friction:

• Someone who already knows the product, brand, or stack
• Faster turnaround on small requests
• A single point of contact instead of re-hiring for every task
• Predictable monthly spend instead of surprise invoices

Your proposal should mirror that outcome in the first lines, then translate it into hours, channels, and deliverables.

If the post only says “ongoing support” with no detail, treat it like a vague brief. Use the same discipline as short job post proposals: mirror the outcome, name assumptions, ask two or three sharp questions.

The retainer proposal structure that works

Use this order:

1. Restate the ongoing outcome (not your biography).
2. Define the monthly bucket (hours, tasks, or both).
3. List what is in scope vs what needs a separate quote.
4. Set response time and communication channel.
5. Explain rollover, overages, and how you report usage.
6. Offer a sane start (pilot month or first-week checkpoint).

That is enough for most marketplace posts and email replies.

Opening that sounds like a partner, not a vendor

Hi [Name],

You need steady [role] support each month without re-explaining the project every time. I work on retainer with a few clients in [niche], and the setup that works best is a fixed monthly block of hours with clear priorities and a simple usage report.

For your post, I would start with [X hours] per month focused on [core tasks]. Anything outside that list (for example [example out-of-scope item]) would be quoted separately or scheduled into the next month if capacity allows.

That opening answers “do you understand my situation” before you talk about yourself.

How to package hours without inviting scope creep

Pick one primary model and say it plainly.

Hours-only retainer: Best when tasks vary (dev fixes, ops, admin). State monthly hours, minimum billable increment (15 or 30 minutes is common), and that unused hours do or do not roll over.

Deliverable retainer: Best when output is predictable (four blog posts, eight social posts, weekly reporting). Tie the fee to deliverables, then mention approximate hours only as context.

Hybrid: A monthly deliverable cap plus a small buffer of ad-hoc hours. Useful for marketing and design retainers. Define which lane a request uses.

Avoid “unlimited small requests.” Clients hear unlimited. You hear bankruptcy.

Example: developer retainer (20 hours/month)

Hi [Name],

I can take on ongoing development support for [product] on a monthly retainer. Based on your note about [bugs, small features, monitoring], I would reserve 20 hours per month for:

• Bug fixes and regressions in the existing codebase
• Small UI or API adjustments that fit in under half a day each
• Dependency and security patch reviews
• A short monthly check-in call (30 minutes, counted in the block)

Work that needs a full feature build, new third-party integrations, or net-new pages would be scoped separately with a fixed milestone, similar to how I handle one-off projects in fixed-price proposals.

Hours: 20 per month, billed at [rate]. Rollover: up to 5 unused hours roll to the next month; the rest do not. Response: business-day replies within [X hours] for normal items; urgent production issues flagged in the subject get same-day triage. Reporting: a short end-of-month note with hours used and what shipped.

Start: I suggest a one-month pilot with a capped backlog list so we can calibrate volume before committing long term.

This example works because it names categories, escape hatches, and a pilot.

Example: marketing retainer (deliverable-led)

Hi [Name],

For ongoing marketing support, I use a deliverable-led retainer so you always know what ships each month. For your channels ([list from post]), month one would include:

• 4 short-form posts per week on [platform]
• 1 email draft per week (you approve before send)
• A one-page metrics snapshot on the first Monday of the month

Ad-hoc requests (landing pages, campaign strategy, influencer outreach) sit outside this retainer unless we swap them in and adjust the fee.

Revisions: one consolidated round per deliverable type per week. Approvals: content goes live after your written OK in [tool]. Meetings: one 45-minute planning call per month included.

If you need a higher volume in launch months, we can add a one-off sprint rather than pretending the same retainer covers a product launch.

Deliverable retainers reduce the “that only took ten minutes” argument because the unit of value is output, not time.

Pricing and presenting the monthly fee

Clients compare retainers to hiring part-time staff, agencies, and doing nothing. Help them compare fairly.

• Anchor to outcomes: “monthly product stability” beats “20 hours.”
• Show what happens when hours run out mid-month (pause, overage rate, or top-up pack).
• If the post lists a budget, respond to it directly. See hourly rate when the post says make an offer for language that does not sound evasive.

A clean fee line:

The retainer is [fee]/month for [hours or deliverables], invoiced on the first business day, due within [terms]. Overage work is billed at [rate] with your approval before I start.

Do not hide overage pricing. Surprise bills kill retainers faster than slightly high base fees.

Rollover, pauses, and exit (write these or regret them)

Rollover: If you allow rollover, cap it. “Up to 5 hours roll once” is clearer than “unused hours accumulate.”

Pauses: Clients travel, fundraise, or freeze spend. Offer one planned pause per quarter with one week notice, or freeze at half fee to hold the slot.

Exit: Month-to-month with 14 days notice is enough for most freelancers. Longer notice is fine if the client wants priority scheduling.

Priority: If you have multiple retainers, say how you triage when two clients need the same day. Honest capacity beats fake immediacy.

Questions worth asking before you lock a retainer

Pick three to five that change price or shape:

• What does a typical week of requests look like? Examples help more than adjectives.
• Who approves work, and how fast do they usually respond?
• Are there seasonal spikes (launches, holidays, reporting cycles)?
• What tools and access do I need on day one?
• Is there existing documentation, or am I rebuilding context from tickets?
• Do you want proactive suggestions, or only work when you assign tasks?

Do not ask fifteen questions in the first message. Ask the ones that separate a 10-hour retainer from a 30-hour retainer.

Mistakes that kill retainer deals

Selling availability without boundaries. “I am always here for you” becomes midnight Slack messages.

No definition of urgent. Define urgent (production down, revenue blocked) vs normal (cosmetic tweak next week).

Skipping the pilot month. A pilot is not weakness. It is how you learn whether their “small tasks” are actually small.

Underpricing to win, then resenting the client. Retainers should include administrative overhead: coordination, context switching, reporting.

Sounding like a template. Quote one detail from their post: stack, industry, tool, or pain point. If you reuse a skeleton, change at least two sentences every time. Reuse proposals across similar jobs without copy-paste tells.

When to decline or redirect to milestones

Not every ongoing post should be a retainer.

Redirect to milestones or fixed phases when:

• The work is a one-time build with vague “maybe maintenance later”
• They want senior strategy but only budget junior hours
• They refuse any reporting or approval process
• The backlog is clearly a disguised full project (new app, rebrand, migration)

You can still reply: propose a bounded discovery or build phase, then offer a retainer after launch.

Checklist before you send

• First paragraph mirrors their ongoing outcome.
• Monthly scope is hours, deliverables, or hybrid (named clearly).
• Out-of-scope examples are specific.
• Rollover, overages, and response times are stated.
• Pilot month or first checkpoint is offered.
• At least two sentences could not go to another client unchanged.
• No em dashes; plain punctuation only.

Run the final pass against the proposal checklist. Retainers reward clarity more than charm: the client should know what month two feels like before they hire you for month one.