Agency utilization and retainer budgets: a playbook

Why agency utilization breaks on retainers

Retainers feel simple: a fixed monthly fee, a bag of hours or outcomes, and a team that “should” stay productive. Utilization breaks when three different numbers get treated as one.

Billable % vs capacity vs budget burn

A designer at 78% utilization can still blow a retainer if most of those hours sit on one underpriced client. A PM at 55% can still protect margin if non-billable time is intentional (sales support, QA, mentoring). Finance needs the utilization formula; ops needs burn and capacity beside it.

• Agency utilization rate: of available hours, how many were billable? High utilization on a loss-making retainer still hurts.
• Capacity: who is free next week, and for which skills? Calendar free ≠ billable free if approvals lag.
• Budget burn: of a retainer’s sold hours or value, how much is used? Happy utilization can hide an oversold retainer.

Scope creep is a timesheet problem first

If the timesheet is late, incomplete, or unlocked, sales cannot renegotiate what nobody can see. Fix the weekly rhythm before you rewrite the SOW.

• “Quick” requests logged to the retainer project with no change note
• Internal polish recorded as billable client hours (or the reverse)
• Unsubmitted weeks that hide burn until invoice week
• Unapproved weeks that leave finance guessing what is real

Define utilization the way finance accepts

Utilization for a person or team over a period:

• Formula: Utilization = Billable hours ÷ Available hours.
• Available hours (finance definition): Working hours − Holidays − Sick / approved leave.

Caveats to write into policy

• “Billable” means hours tagged billable under your rules (task type / project), not “hours a client might accept.”
• Decide whether PTO, training and parental leave reduce the denominator the same way as holidays/sick — document it.
• Period matters. Weekly swings a lot; monthly or rolling 4‑week views are stabler for management.
• Role mix matters. Do not average a junior producer and a managing partner into one “good” rate.
• Agent / automation time (if you track it) should not inflate a person’s utilization. Keep people timesheets and agent-logged time separate when you report capacity.

Worked example (assumptions stated)

Assumptions:

• Person: mid‑level strategist at a 12‑person agency

• Calendar month: 20 working days × 8 h = 160 working hours

• Holidays + sick: 16 h

• Available: 160 − 16 = 144 h

• Billable hours logged: 94 h

Utilization = 94 ÷ 144 ≈ 65%. Same math as the old 104 ÷ 160 = 65% illustration, but with holidays/sick made explicit in the denominator. Always publish inputs with the percentage.

Role-based targets (internal, not industry averages)

This playbook does not publish invented market benchmarks. Set internal targets from your own margins, rates and role mix. Compare people to their own trend and peers in the same role, and always pair utilization with project or retainer margin. Leave room for learning and internal work — utilization alone is not a performance grade.

• Producer / specialist: start from sold capacity after meetings + QA buffer; watch retainer burn vs sold hours.
• Account / PM: lower billable share is often intentional; watch delivery risk and unbilled coordination.
• Lead / director: protect non-billable for sales and quality; watch margin on booked work, not peak %.
• Ops / finance: usually non-billable by design; watch approval SLA and lock completeness.

Retainer budget anatomy

Hours vs outcomes vs hybrid — what utilization + burn must show:

• Hours retainer: e.g. “40 hours / month”. Show hours used vs hours sold; convert to value with rate × hours if needed.
• Outcomes / fixed-scope: deliverables or SLA inside a fee. Time is evidence of cost, not the invoice unit; still track hours so overrun is visible before renewal.
• Hybrid: soft hour band + priority outcomes. Track both outcome status and hour burn.

Early‑warning signals

• Unsubmitted time — burn is invisible; utilization is fiction.
• Unapproved time — finance cannot trust the number.
• Non‑billable creep on a “billable” retainer — internal meetings swallowing the band.
• Single‑person concentration — one specialist carrying most of the retainer hours (capacity cliff).
• Budget amber/red — treat budget thresholds as ops alerts, not vanity charts.
• Scope notes missing — extra requests with no change log in project chat or tasks.

Weekly operating rhythm

Hourtick matches this pattern: people submit; managers approve or send back; submitted weeks lock for the owner; approved weeks lock for everyone; a week with a running timer cannot be submitted; approvals are included on every plan.

1. Track daily.
2. Friday: submit the week.
3. Monday: managers approve or send back.
4. On approval: weeks lock so billing matches reviewed time.

Who owns the number

• Personal utilization trend — owner: the person + their lead; secondary: ops.
• Retainer burn — owner: PM / account lead; secondary: finance.
• Team utilization rollup — owner: ops or managing partner; secondary: finance.
• Approval SLA (e.g. Monday complete) — owner: managers; secondary: ops.

Playbook: spot overrun before the invoice

1. Every active retainer has a project (or clear task types) and a written sold hour/value band.
2. Timers/entries this week point at the right retainer — not a dump bucket.
3. Mid‑week: hours used ÷ sold band; flag if the pace implies >100% by month‑end.
4. Chase unsubmitted days before Friday.
5. Friday: all contributors submit; Monday: managers clear the approval queue.
6. Explain or reclassify non‑billable spikes.
7. Log scope extras as tasks/notes for renewal or change order.
8. Review not‑yet‑invoiced; mark invoiced only after the invoice is real.
9. Review utilization by role monthly — never weaponize it weekly.

In practice (hypothetical / anonymized)

Hypothetical composite for a ~15‑person B2B marketing agency on monthly retainers. “Northline” sells a content retainer at a fixed fee described internally as “about 35 hours / month” of strategy + production. Three people touch the account. By Thursday of week 3 they have logged 31 hours; two days of the lead strategist are still unsubmitted. Utilization looks fine on a partial week; budget burn is already near the monthly band.

Friday–Monday: (1) chase unsubmitted days; strategist submits; true burn shows ~38 hours with one week left. (2) PM moves “extra landing‑page copy” (never in the SOW) to a separate task marked for change‑order discussion. (3) Managers approve Monday; week locks; finance sees the same numbers the PM sees. (4) Renewal uses timesheet evidence, not memory.

Lesson: overrun was visible four days earlier as unsubmitted time plus scope in the wrong bucket, not as a surprise invoice. Utilization alone would have said the strategist was productive; burn + approval would have said the retainer was already spent.

Tools: calculate, then track

Calculate: sanity‑check the formula with your own inputs at /tools/utilization-rate-calculator.

Track (soft CTA): once the definition is shared, you need the same numbers every week — hours by client/project/person, billable share, budget burn, submit/approve/lock, and a clear invoiced state.

Hourtick is built for teams and their AI agents to put time on the right task: Mac menu bar + browser timer, timesheet approvals, reports (including billable share/amount, not‑yet‑invoiced, budget burn, CSV), and mark‑invoiced locks. Free: unlimited people, every feature, 500 MB/month. Pro: $29/month for 5 GB + $10 per extra GB. No per‑seat pricing.