How to Price an Agency Retainer When Client Work Varies Month to Month

Pricing an agency retainer is difficult when the work changes from month to month. One month may bring a launch, a rush of revisions, or a reporting cycle; the next may be quieter. If you charge only for the hours used, revenue becomes unpredictable. If you charge a flat fee without defining what it covers, the team can end up delivering far more than the client is paying for.

The answer is not to make every month look identical. It is to price a clear commitment: a defined level of access, capacity, or recurring work, with rules for handling peaks and quieter periods. This guide explains how to build that price, set boundaries, and check whether the arrangement remains sustainable.

Start by deciding what the retainer buys

A retainer is a recurring commercial agreement, but that alone does not define the service. Before calculating a fee, decide what the client is buying. Common models include:

  • Reserved capacity: The agency holds a stated amount of team availability each month, which the client can direct within agreed limits.
  • Recurring deliverables: The fee covers a defined set of outputs, such as campaign management, a reporting package, or a set number of content pieces.
  • Ongoing access and advice: The client pays for regular strategic input and a specified response or meeting cadence, rather than a fixed production volume.

These models can be combined, but the agreement should make the main commitment easy to understand. “Marketing support as needed” is difficult to price and harder to manage. “Up to 30 hours of agreed work per month, with a weekly planning call and a two-business-day response target” gives both sides something concrete to discuss.

If the work is actually a series of separate, defined projects, a retainer may not be the right structure. Compare the trade-offs in fixed-fee and time-and-materials pricing before turning every ongoing relationship into a monthly agreement.

Calculate a sustainable price floor

Your price should cover the cost of delivering the commitment and leave room for the agency’s target margin. Start with the people and resources likely to work on the account, not just the person who attends client meetings.

Estimate the real delivery cost

List the expected monthly effort by role: account management, strategy, design, development, writing, analytics, or other specialist work. Use a realistic average based on the service, and include recurring tasks such as planning, internal reviews, project administration, and reporting. A retainer that appears to require 20 hours of production may need several more hours of coordination and quality control.

For each role, use a fully loaded hourly cost rather than salary divided by working hours alone. Include employer payroll costs and benefits where applicable, along with any direct delivery costs that belong to the account. The IRS explains that U.S. employers generally have obligations for the employer share of Social Security and Medicare taxes; see IRS Publication 15. The exact costs depend on location and employment arrangements.

For a simple illustration, assume a retainer takes 30 hours a month across the team, with an average fully loaded delivery cost of $60 per hour. Direct labor cost is $1,800. If you use a 55% gross-margin target for this service, the price floor based on that labor cost is $1,800 ÷ (1 − 0.55), or $4,000 per month. This is a planning example, not a universal margin target. Add other direct costs if they are not already included, and check how your agency defines gross margin.

Separate margin from markup

A common pricing error is to add a 55% markup and assume that produces a 55% margin. It does not. Margin is the share of revenue left after the defined direct costs; markup is an addition to cost. Use one method consistently, and make sure the target makes sense for your agency’s overhead, service mix, and utilization.

This price floor is a guardrail, not necessarily your final quote. The value and risk of the work, the client’s service needs, and your available capacity can all affect the final fee. But if the proposed price falls below the floor, be explicit about what scope, access, or capacity must change.

Price for normal variation, not the busiest month

Look at recent work or a detailed forecast to understand the pattern. Group activities into recurring baseline work, predictable peaks, and genuinely unpredictable requests. If you have limited history, treat your estimate as a hypothesis and set an early review date rather than pretending the workload is certain.

Suppose an account usually needs 24 to 36 hours a month, with a typical month near 30. You might price and reserve capacity around that baseline, then define how a month above 30 hours is handled. The fee should not quietly assume the maximum every month while the agency delivers the minimum; nor should it leave the team exposed whenever demand rises.

Consider an agreed monthly capacity band, a stated set of deliverables, or a baseline plus separately priced work above the baseline. The right choice depends on how predictable the work is and whether the client values guaranteed availability. A narrow band is easier to resource but gives the client less flexibility. A broader band may be attractive to the client, but it requires enough slack in your team or a clear overflow process.

Set rules for busy and quiet months

Variability becomes a commercial problem when both sides assume different rules. Put the practical details in the proposal or agreement, then reinforce them in kickoff and monthly planning.

Define what counts as included

Describe the service, the typical monthly capacity or output, the people or expertise available, and any expected meeting or reporting cadence. Also name likely exclusions: new campaign builds, major site changes, out-of-hours support, rush work, travel, or third-party costs. “Included” should not depend on who happens to be managing the account.

Decide what happens to unused capacity

If the client uses less than the agreed capacity, the agency may still have reserved team time and turned away other work. You can explain that the monthly fee buys availability and ongoing service, not a bank of hours. If some rollover is commercially useful, cap it, set an expiry date, and state that it is subject to scheduling. Unlimited rollover creates a liability: quiet months can accumulate into a future workload spike.

Set an overflow process

When work exceeds the agreement, pause and agree on the next step before the team proceeds. Options include deferring lower-priority work, using pre-approved overage rates, or issuing a scoped change order. State who can approve extra work and how quickly approval is needed. If the agency routinely absorbs overflow without documenting it, the retainer price and scope will drift apart.

A useful client conversation is specific: “We have 30 hours planned for the month. The new landing page is likely to add 12. Would you prefer to move two existing tasks to next month, approve the additional work at the agreed rate, or reduce the page scope?” That gives the client a choice without presenting unpaid work as inevitable.

Use a planning rhythm to control scope drift

Agree on priorities before work starts each month. A short planning meeting or written review can confirm the available capacity, top deliverables, dependencies, and decisions the client owes the team. Record requests that arrive during the month and whether they replace planned work or add to it.

Track actual effort by account for an initial period, even if you do not invoice by the hour. The purpose is to compare the commitment with delivery cost and identify patterns: repeated revisions, too many stakeholders, unplanned meetings, or a recurring seasonal peak. Time data is diagnostic, not a reason to turn every client interaction into a stopwatch exercise.

For a new or changing service, review after two or three billing cycles. If the work consistently exceeds the plan, first investigate why. The solution may be a higher fee, narrower scope, better client inputs, a different approval process, or a separate project fee. If the work is consistently lighter, consider whether the commitment is still valuable to the client and whether you can safely release some capacity.

Make the agreement clear before work begins

A practical retainer proposal should answer these questions:

  • What recurring work or capacity is included, and what is not?
  • How will priorities be set, and who on the client side can approve changes?
  • What happens when work is delayed by missing access, content, or feedback?
  • Can unused capacity roll over? If so, how much and for how long?
  • How are extra requests priced, approved, and scheduled?
  • What is the initial term, renewal process, and notice period for ending or changing the arrangement?
  • When will the fee and workload be reviewed?

Do not use a long minimum term to conceal a weak scope. A defined review point can make a new retainer more workable: it gives both sides a chance to adjust the price or service after real delivery data is available. For smaller, bounded pieces of work that sit outside the monthly agreement, a minimum project fee can prevent small requests from consuming disproportionate coordination time.

Common pricing mistakes to avoid

  • Pricing from the client’s budget alone: Budget helps shape the offer, but it does not show whether the work is viable. Adjust scope to fit rather than promising the original service for less.
  • Using one month as the forecast: A launch month may be unusually heavy; a quiet month may hide work that arrives quarterly. Look at the pattern and known calendar events.
  • Ignoring non-production effort: Meetings, project management, revisions, and reporting are real delivery costs.
  • Leaving “as needed” undefined: Flexible access can be valuable, but it needs response expectations, capacity limits, and a way to prioritize requests.
  • Failing to review the economics: A retainer that was profitable at launch may change as client needs, team costs, or service expectations change.

A simple decision rule

If the client needs predictable ongoing support, can collaborate on priorities, and accepts clear capacity or scope boundaries, a retainer can smooth delivery and revenue. If demand is highly uneven, the client expects unlimited availability, or each request is a distinct project, consider a hybrid: a smaller monthly commitment for planning and access, with separately scoped production work.

The goal is not to eliminate variation. It is to make variation visible and agree who carries its cost. Price the baseline honestly, define what happens outside it, and use delivery data to adjust the arrangement before resentment or margin loss becomes the signal that something is wrong.

FAQ

Should an agency retainer be based on hours or deliverables?

Use the structure that best describes what the client is buying. Hours or capacity can suit changing priorities; deliverables can work when outputs are predictable. Either way, define limits and the process for extra work so that changing requests do not become unlimited scope.

Should unused retainer hours roll over?

Not automatically. The monthly fee may pay for reserved availability, which has value even when the client uses less capacity. If you allow rollover, set a cap and expiry date, and make clear that scheduling depends on available capacity.

How should we price work that exceeds the retainer?

Set the approach in advance: defer lower-priority tasks, approve an agreed overage rate, or scope the request as a separate project. Get approval before starting additional work, and identify who is authorized to approve it.

How often should we review a retainer price?

Review early when the service is new or the workload is changing, then at a regular interval such as renewal or an agreed annual review. Also reopen the discussion when the scope, client response needs, team costs, or volume changes materially.

What if the workload changes a lot each month?

Use a baseline commitment with a clear overflow process, or separate ongoing planning and access from variable production work. If the client expects guaranteed capacity for peaks, price for the availability needed to meet that expectation—not just the average hours used.

Similar Posts