RevOps for Agencies: Retainers, Statements of Work, Delivery Records and Retainer Margin
RevOps for agencies explained: retainers and projects, statements of work and scope change, which system owns each record, and retainer margin by client.
An agency's pipeline review names one retained client as its fastest-growing account, because three change orders added a fifth to that client's fee during the year. The utilisation report agrees, showing the client's team recording more billable hours than any other. At year end the same client returns the lowest margin in the book. Its change orders recovered part of the work delivered outside the statement of work, and the rest was absorbed as hours no invoice carries.
This article sets out revenue operations for a marketing, creative or digital agency as an operating model, independent of any software product. It starts with the revenue arrangements agencies sell and the statement of work that fixes each one, then follows the lifecycle from pitch to renewal and the system that owns each record. Sample data then computes retainer margin after scope change for three clients, before the handoffs, metrics, costs, symptoms, a monthly procedure, common questions and the limits of the evidence.
The finding can be checked against any agency's records. Out-of-scope work on a retainer raises utilisation, because a time entry can be billable without ever being billed, and a change order recovering part of it raises contracted value, which the CRM reports as expansion. Both read as growth while margin falls. Retainer margin after scope change reads the account correctly, and it needs three records no single system holds: the hour allowance in the statement of work, time entries classified in or out of scope in the project tool, and fees with a loaded cost rate from finance.
Revenue operations is defined in the firm's foundations paper as a capability that keeps objectives, records, measures, systems and decisions traceable to one another. A retainer is a recurring fee for an allowance of work over a term, and a project is a defined deliverable priced as a fixed fee or at hourly rates. A statement of work (SOW) fixes one engagement's scope, deliverables, fee basis and assumptions. Retainer margin after scope change is fees billed, change orders included, less delivered hours at a loaded cost rate, over fees billed; the loaded rate prices an hour at what the person working it costs the agency.
Agency Revenue Arrangements: Retainers, Projects and Pass-Through Costs
Omnicom, a listed agency holding company, describes client contracts in its annual report for 2025 as primarily fees for service on a rate per hour or per project basis. Those fees combine an agreed fee or hourly rate for the level of effort, commissions on media bought from third parties, incentive provisions, and reimbursement of third-party costs where the agency acts as principal.
A retainer buys the agency's readiness to work against an allowance for a term. The report recognises revenue from such stand-ready arrangements evenly over time, and describes them as running typically for periods up to one year. A project buys a defined deliverable and ends at acceptance, so the report measures its progress by staff effort or by milestones reached.
On a retainer the fee is fixed for the month and the hours vary, so every hour beyond the allowance comes out of margin unless a change is priced; a fixed-fee project carries that exposure over the whole engagement, and hourly work bills the overrun.
Third-party costs make the word revenue ambiguous. Where an agency arranges media or production at the client's direction without controlling it, Omnicom records revenue net of those costs, equal to the amount retained as fee or commission. Where the agency controls the service and carries its pricing risk, it acts as principal and records the gross amount. A proposal quoting media and fee together therefore states more than the revenue it will produce, by the whole pass-through in the agent case.
One retainer thus carries several values: the fee and allowance in the SOW, change orders, gross billings, net revenue and the cost of hours delivered. HubSpot, for example, defines a deal's Amount as the total value of the deal and computes annual recurring revenue from the term and recurring line items (default deal properties), and neither field holds an hour.
Statements of Work, Allowances and Change Orders
Every later figure is measured against the SOW, so its terms decide what the agency can compute. For a retainer it needs, as data rather than prose, the monthly fee, the allowance in hours by role, the term and notice period, the treatment of unused hours, and the test for what falls outside scope.
Unused hours that roll over are work still owed, so a quiet month defers cost rather than adding margin; hours that lapse become margin when the month closes. A SOW silent on the point leaves finance reading the month as profit while the account lead reads it as a liability.
Scope change has a precise definition in the revenue standard. Paragraph 18 of IFRS 15 defines a contract modification as a change in scope or price, or both, approved by the parties, and notes that it may be called a change order, a variation or an amendment. The standard was issued in May 2014 together with Topic 606 of the Financial Accounting Standards Board's codification.
Under that definition, work delivered outside the SOW without an approved change in price leaves the fee where it was, so the hours carry cost with no revenue against them. Omnicom's report gives the commercial answer: changes in client requirements during a contract, which can be significant, are negotiated in the usual case as new contracts, with additional fees for the incremental work.
Out-of-scope work therefore ends in one of three ways. A change order prices it during the term, a new SOW prices it at renewal, or absorption leaves it unpriced. The first two leave records in the CRM and the ledger, while absorption leaves only time entries, and only if each entry was classified against the SOW when it was recorded.
The Client Lifecycle from Pitch to Renewal
The lifecycle has seven stages across three systems, and two cycles: one monthly inside the term and one at each renewal.
Before signature the record is a pursuit in the CRM. A brief arrives through a referral, an invitation to pitch or an existing relationship, and the proposal prices the work. Pitch hours are spent before any fee exists and appear only if booked to a new-business code. At signature the SOW fixes fee and allowance, and delivery sets up a budget in the project tool with the allowance as its hours.
Each month the team delivers and records time, finance invoices the retainer and any change orders, and the account lead reviews scope, reading hours against the allowance and deciding each out-of-scope request before the next month's delivery.
At the end of the term the relationship is renewed, re-scoped, expanded or ended. Expansion arrives as change orders, a larger allowance or a new project for the same client. Churn arrives as notice under the SOW or a renewal not taken up, and Omnicom's report notes that clients are generally able to reduce or cancel marketing spending at any time on short notice. An agency can also choose churn, declining to renew a retainer whose margin stays below its floor.
Systems of Record for Agency Revenue
The CRM holds the relationship, the pursuit and the commercial terms: the proposal, the signed fee and allowance, change orders and renewal dates. A document tool holds the SOW text and its signature state.
The project tool or PSA is the delivery system of record, and its records decide whether scope can be measured. Harvest's API describes a project that can be fixed-fee, carries a budget in hours that can reset every month, holds the fee the agency plans to invoice, and can notify managers when it goes over budget (Harvest projects API). Productive, a PSA, holds deals and budgets in one endpoint, and a deal generated by a retainer contract carries its value per retainer period (Productive deals API). Where the PSA holds the pipeline too, the open question is which system owns the relationship across engagements.
Time tracking separates two records that share a name. Federal rules require employers to keep, for each employee covered by the minimum wage and overtime provisions, the hours worked each workday and each workweek. That record counts hours for pay. The client time record allocates hours to a client, a SOW line and a task, and no statute requires it to be complete.
Harvest's time entry carries separate fields for whether an entry is billable and whether it has been marked as invoiced, beside a billable rate and a cost rate (Harvest time entries API). The finding sits in the gap between those two fields. ClickUp's time entry also carries a billable flag, and time entry tags, unlimited on its Business Plus and Enterprise plans, can mark an entry as outside scope (ClickUp time entry API).
A resource plan allocates people to clients by week or month, and an allocation above a client's allowance is scope drift planned before any hour is recorded. Finance holds the ledger: invoices, payments, pass-through costs, freelance and production spend attributed to its client, and the cost rates payroll supports.
| Record | System of record and owner | What the client record needs |
|---|---|---|
| RecordPitch, brief, proposal | System of record and ownerCRM; new business | What the client record needsThe whole record, since it starts here |
| RecordSOW: fee, allowance, term, rollover, scope test | System of record and ownerDocument tool with CRM fields; account lead | What the client record needsFee, allowance by role, term, renewal date |
| RecordChange orders | System of record and ownerCRM and document tool; account lead | What the client record needsValue, hours priced, approval date |
| RecordBudget, tasks, assignments | System of record and ownerProject tool or PSA; delivery lead | What the client record needsHours consumed against the allowance |
| RecordTime entries | System of record and ownerProject tool or time tracker; everyone delivering | What the client record needsHours in and out of scope, by month |
| RecordResource plan | System of record and ownerPSA or resource planner; resourcing | What the client record needsAllocated hours against the allowance |
| RecordInvoices, payments, pass-through | System of record and ownerAccounting; finance | What the client record needsFees billed, net revenue, collected |
| RecordCost rates and direct costs | System of record and ownerPayroll, accounting, spend platform; finance | What the client record needsLoaded cost rate, direct cost by client |
| RecordRetainer margin after scope change | System of record and ownerComputed in finance from the rows above | What the client record needsThe figure by client, with its date |
Retainer Margin After Scope Change on Sample Data
The figures below are sample data for an invented digital agency and describe no client. One delivery team with 5,000 available hours served three retained clients for twelve months. Every retainer was sold at $160 per allowance hour, every delivered hour costs $90 at the loaded rate, and unused hours lapse at month end. The first table holds what the CRM and the project tool record.
| Measure | Client A | Client B | Client C |
|---|---|---|---|
| MeasureMonthly fee and allowance | Client A$20,000 for 125 hours | Client B$16,000 for 100 hours | Client C$9,600 for 60 hours |
| MeasureRetainer fees for the year | Client A$240,000 | Client B$192,000 | Client C$115,200 |
| MeasureChange orders approved | Client A$48,000 for 300 hours | Client BNone | Client C$14,400 for 90 hours |
| MeasureGrowth in contracted value | Client A20.0% | Client B0.0% | Client C12.5% |
| MeasureHours delivered within scope | Client A1,500 | Client B1,140 | Client C720 |
| MeasureHours delivered outside scope | Client A800 | Client B0 | Client C90 |
| MeasureBillable hours recorded | Client A2,300 | Client B1,140 | Client C810 |
On this record client A leads twice. Its contracted value grew by $48,000, or 20.0%, the largest expansion in the book, and its team recorded 2,300 of the 4,250 billable hours, or 54.1%, against a team utilisation of 4,250 ÷ 5,000 = 85.0%. The second table adds what finance holds.
| Measure | Client A | Client B | Client C |
|---|---|---|---|
| MeasureFees billed, change orders included | Client A$288,000 | Client B$192,000 | Client C$129,600 |
| MeasureDelivery cost at $90 an hour | Client A$207,000 | Client B$102,600 | Client C$72,900 |
| MeasureGross profit | Client A$81,000 | Client B$89,400 | Client C$56,700 |
| MeasureRetainer margin after scope change | Client A28.1% | Client B46.6% | Client C43.8% |
| MeasureScope capture rate | Client A37.5% | Client BNo hours outside scope | Client C100% |
| MeasureFees per delivered hour | Client A$125.22 | Client B$168.42 | Client C$160.00 |
The ranking reverses. Client A returns $81,000 ÷ $288,000 = 28.1%, against 46.6% for B and 43.8% for C, and earns $8,400 less gross profit than B on $96,000 more in fees. The mechanism is 500 hours delivered outside scope that no change order priced: they cost $45,000 at $90 and would have billed $80,000 at $160. Had all 800 out-of-scope hours been priced, A would have billed $368,000 for the year and returned C's 43.75%, since C priced every hour it delivered outside scope. B exceeds that figure only because 60 of its 1,200 allowance hours lapsed unused.
Utilisation hides the same hours from the other side. Counting only hours that an allowance or a billed change order covers, utilisation is 3,750 ÷ 5,000 = 75.0%, ten points below the reported 85.0%, and all 500 missing hours sit on client A.
The decision these figures inform is client A's renewal. Renewed at $20,000 a month with the same demand and no change orders, the account would return ($240,000 − $207,000) ÷ $240,000 = 13.75%. Its change orders lifted that to 28.1%, and pricing every hour would reach 43.75%, so the choice lies between an allowance priced at A's observed demand and a SOW holding the work to 125 hours a month. The sample sizes that choice and cannot say whether client A would accept either.
Handoffs Between New Business, Account Management, Delivery and Finance
New business hands account management a signed SOW. The handoff fails when a proposal prices a programme rather than deliverable units, so the allowance never exists as a number. A published marketing agency integration between the CRM and ClickUp found 41 percent of 74 engagements with no documented scope in the delivery system, and changed the agency's proposals so that every line item carried hours. The SOW also fails when its rates are typed by hand, and a staffing agency's contract engagement bound every rate on its agreements to one CRM property.
Account management hands delivery the allowance, which becomes the budget in the project tool. The ClickUp study checked at set-up that task estimates summed to the hours sold, rather than letting delivery rebuild the plan from a kickoff conversation.
Delivery hands account management the month's hours, in scope and out. The same study notified the account lead when planned hours crossed the sold quantity and generated nothing the client saw, treating the choice between absorbing, billing and renegotiating as a commercial decision.
Finance hands back fees billed and collected, direct costs by client and the cost of hours. A published agency cost-to-serve engagement found 31 percent of direct cost with no client attribution, and twelve accounts reconstructed by hand ranging from 71 percent to negative 4 percent gross margin, against a 54 percent average used for pricing. A consultancy's project margin integration left the margin calculation in the finance system and stamped each figure on the deal with the time it was produced. This fourth handoff carries the finding, since the CRM and the project tool hold every input except fees billed and cost.
Agency Revenue Metrics and Their Source Records
| Metric | Definition | Records it reads |
|---|---|---|
| MetricPitch win rate | DefinitionPitches won over pitches made, by number and by value | Records it readsCRM |
| MetricAllowance consumption | DefinitionHours delivered within scope over allowance hours, by month | Records it readsCRM, project tool |
| MetricOut-of-scope share | DefinitionHours delivered outside scope over all hours delivered | Records it readsProject tool |
| MetricScope capture rate | DefinitionOut-of-scope hours priced by change order over out-of-scope hours delivered | Records it readsCRM, project tool |
| MetricUtilisation | DefinitionBillable hours over available hours | Records it readsProject tool, resource plan |
| MetricCovered utilisation | DefinitionHours an allowance or a billed change order covers, over available hours | Records it readsCRM, project tool, finance |
| MetricGrowth in contracted value | DefinitionChange orders and allowance increases over the fee at the start of the term | Records it readsCRM |
| MetricClient revenue retention | DefinitionThis year's fees from last year's clients over their fees last year | Records it readsFinance, CRM |
| MetricRetainer margin after scope change | DefinitionFees billed less delivered hours at the loaded rate and direct costs, over fees billed | Records it readsCRM, project tool, finance |
Utilisation carries the conflation the sample exposes. As billable hours over available hours it measures capacity in use, and as covered hours over available hours it measures capacity that earns a fee, so the gap between the two is absorbed scope. Whether open pitches can be staffed by role and month is a third question, answered from the pipeline and worked through in capacity forecasting across a professional services pipeline.
Costs and Returns for an Agency
The firm publishing this page is a HubSpot Solutions Partner and is itself a services practice selling retainers and projects, two interests to weigh below; none of its own operating figures appear here.
The model buys renewal and pricing decisions made on each client's margin rather than a portfolio average, and scope conversations held in the month the work drifts. It costs a classification on every time entry, a SOW written as data, a loaded cost rate finance agrees to publish, and an owner for the monthly return of fees and cost. The classification is the weak point, because the person recording time bears the effort while the benefit falls to the account lead.
The configuration costs depend on the workstreams an implementation carries, set out in how an implementation is scoped and sequenced. The firm's scenario model of returns in professional services projects returns for a hypothetical consultancy from assumed uplifts, which makes it a scenario rather than a measurement, and this page adds no measured outcome to it.
The case is strongest for an agency with many retainers, scope that moves between months, and too many time entries for the account lead to read. It is weakest for a studio whose principal scopes, delivers and invoices every fixed-fee job, and for an agency using value-based pricing, where hours are not the unit of price.
Symptoms in Agency Revenue and Their Sources
The fastest-growing account in the CRM is the least profitable at year end. Its change orders priced part of the work already delivered outside scope, and growth in contracted value counted them as expansion; margin after scope change, reviewed monthly, shows the gap while it is small.
Utilisation is high while margin falls. Hours outside scope are recorded as billable and never billed, raising utilisation and cost together, and covered utilisation reported beside it measures the gap.
The CRM and finance report different revenue for one client. The deal carries gross billings including media and production, while the ledger records net revenue where the agency acts as agent, so net revenue needs its own field.
Retainer renewal reminders stop after a CRM migration. A rule that fires once a year looks dead in a usage window of one quarter, and a published professional services migration abandoned two such rules in error and rebuilt them in its second month; its method now treats annual and quarterly rules as live unless someone argues otherwise.
Monthly Scope Review Procedure
- List every system holding a record of a client, pitch, SOW, change order, time entry, invoice or cost, and complete the records table above with one owner per row.
- Record each SOW's fee, allowance by role, term, notice period, rollover rule and out-of-scope test as fields on the client record.
- Create the delivery budget from the SOW at signature, and carry the SOW identifier into the project tool and finance so records match on it.
- Classify every time entry against a SOW line when it is recorded, as within scope, outside scope or new business.
- Agree a loaded cost rate with finance, for the agency or by role, and publish its definition with the date it was set.
- At month end, return fees billed, change orders billed and direct costs by client from finance, and hours within and outside scope from the project tool, to the client record.
- Compute margin after scope change and scope capture rate by client, monthly and over twelve months, and record the decision on each out-of-scope request: change order, re-scope at renewal, or absorption with a reason.
- Verify on one client for one closed month. Hours within and outside scope sum to the client's time entries, and hours within scope stay inside the allowance unless the rollover clause permits more. The retainer fee plus change orders billed equals the client's invoices in the ledger, pass-through excluded. Margin recomputed by hand from those figures matches the client record, and every out-of-scope hour carries a decision. A failed check names the handoff that broke.
Frequently Asked Questions
Revenue operations for an agency: what does it cover?
It covers the records that carry a client from pitch through SOW, delivery, invoicing and monthly scope review to renewal, expansion or churn: which system owns each, what crosses each handoff and how each metric is defined, so that a renewal is decided on margin after scope change.
Does a marketing agency need RevOps?
It needs the discipline where retainers renew, scope moves between months, and the person who sells an account is not the person who records its time. A studio whose principal sells, delivers and invoices every job holds the chain in one place, where a consistent SOW with time recorded against it may be enough.
Is revenue operations different from agency operations or traffic management?
Yes. Traffic management, as the term is used here, schedules and routes jobs through creative and production teams, and agency operations runs the practice as a whole: people, tools, facilities and process. Revenue operations governs the records connecting what was sold, what was delivered and what was billed. The three meet at the time entry, which traffic management needs to schedule the next job and revenue operations needs to price the next month.
Does revenue operations apply to an agency that sells only projects?
It applies over a different cycle. A project's scope change is priced or absorbed once, and its margin is known at closeout, so the review moves from each month to each milestone and informs the price of the next project of the same type.
Coverage, Dates and Limits of the Evidence
This page covers an agency's commercial record from pitch to renewal, and leaves out CRM configuration, product selection, revenue recognition beyond the definitions quoted, compensation and media buying. Fee arrangements and agent treatment are as Omnicom described them in its annual report for 2025, filed in February 2026, which describes a large holding company rather than an independent agency. IFRS 15 is quoted from an Internet Archive capture of EUR-Lex dated 22 December 2024, because EUR-Lex refuses automated clients. Product behaviour is as documented by Harvest, ClickUp, Productive and HubSpot in September 2026.
No published study located for this page measures whether an operating model of this kind changes margin or client retention at agencies, and the direct research reviewed in the firm's history of revenue operations is recent and small. The sample agency is invented, so its reversal shows that growth, utilisation and margin can rank the same clients in opposite orders, not how frequently they do. Case study figures are those engagements' own measurements, with the limits their studies state. Any single loaded rate moves every margin and leaves the sample's ranking unchanged, while rates that differ by role could change it.
In Summary
An agency sells retainers and projects under statements of work, delivers against them in a project tool or PSA, and bills through finance, with media and production passing through as agent or principal. Revenue operations for agencies assigns each record to one system, states what crosses the four handoffs, and defines each metric by the records it reads.
Retainer margin after scope change is the figure a renewal reads, and it joins the SOW's allowance, time classified within or outside scope, and fees with a loaded cost rate. On the sample data it moves client A from the fastest-growing account with the busiest team to the lowest margin in the book, 28.1% against 46.6% and 43.8%, because 500 hours delivered outside scope were never priced. Those hours were countable only because each time entry carried a scope classification, the first record to build.