workflow

Recurring deliverable

Any client-facing artifact an agency produces on a fixed cadence — the same shape of work, period after period.

What it is#

A recurring deliverable is any artifact an agency owes a client on a fixed cadence — a monthly performance brief, a weekly status update, a quarterly business review. The defining trait is repetition: the same shape of output, due again, on a schedule that doesn't stop.

Recurring deliverables are distinct from project work, which has an end. A campaign ships and is done. A monthly brief is never done — next month's is already coming.

Why it matters for agencies#

Recurring deliverables are where agency margin is won or lost, because they're the work that compounds. A campaign produced inefficiently costs you once. A monthly brief produced inefficiently costs you every month, for the life of the retainer, across every client on that cadence.

This is the core economic argument for treating recurring deliverables as a system rather than a series of one-off efforts:

  • The cost of doing it by hand multiplies by clients and by periods.
  • The cost of templating it once is paid once and amortized across every cycle.
  • The gap between those two numbers is the agency's recurring reporting tax.

In SendBriefs specifically#

SendBriefs is built specifically around recurring deliverables. A brief template is authored once; from then on, each cycle's brief is a render of that template against fresh data, delivered on a schedule. The recurring part stops being recurring work.

See Recurring deliverable in the product

Browse brief templates

See Recurring deliverable in action.