The Agency Retainer Agreement That Turns Repeat Revenue Into Recurring Revenue

The proposal gets the yes. The agency retainer agreement decides whether the revenue after the yes is worth anything to anyone but you.

I've talked to a founder whose agency runs above 85 percent recurring revenue, and none of it came from selling harder. It came from the paper. Twelve-month contracts, automatic renewals, an exit clause the client can actually use, and a price increase written into every agreement and negotiated up front.

Every template on the first page of Google will hand you twelve clauses, most of them behind an email gate. Four of those clauses are the reason his agency is worth what it is. The other eight are the reason nobody ends up in court.

So this post gives you the whole template, no email required, with sample language you can copy today. Then it spends most of its time on the four clauses that make your revenue count, and the two that keep you out of the monthly argument about hours.

One thing before we start. I'm not a lawyer, and none of this is legal advice. It covers the business decisions you should make before a lawyer ever sees the document.

A Retainer Agreement Is an Asset, Not Armor

Most founders treat the agreement as armor. You put it on so a bad client can't hurt you. That's a fair way to think about it, and every vendor page is right that you don't need a law degree to write one.

But protection is the smallest job this document does. A retainer agreement also decides what your recurring revenue is worth, and it decides who at your agency has to be in the room every time a client asks for more.

First, the split, because most founders get it backwards. The proposal's job is to persuade. The agreement's job is to protect the engagement after the yes, and to make the revenue count. If you send a twelve-page contract as the proposal and a handshake as the agreement, you've done both jobs badly.

The proposal’s job is to persuade. The agreement’s job is to protect the engagement after the yes, and to make the revenue count.

I covered the proposal side in the monthly retainer proposal template. A termination clause never belongs in a proposal, and a value case never belongs in an agreement.

Here's what it looks like when the agreement is missing. A founder told me he'd lost three of his retainer clients in a single month, which left him with one retainer and a handful of projects.

His revenue had looked recurring on a spreadsheet for a long time. But nothing in writing said how long a client was committed or how much notice they owed him. It was repeat revenue that happened to repeat, right up until it didn't.

Now, I know most of you aren't selling the agency this year. I bring up the buyer anyway, because a prospective agency acquirer runs the most honest test of whether your revenue is real. They don't take the spreadsheet's word for it. They read the contracts.

That's the first job the agreement does that no template names. Four clauses (term, notice, renewal and IP) decide whether an acquirer counts your retainers as recurring revenue or as repeat work.

The second job is closer to home. Two clauses (capacity and change requests) decide whether the founder has to settle every "can we squeeze this in" conversation personally. Get those two right and the account lead can answer without you.

The other six clauses are boilerplate. A lawyer should read them once, and then you should stop thinking about them.

One more situation, because it comes up every time a project client wants to stay on. The old project contract ends on delivery. The retainer starts on a new effective date with its own agreement, and its scope clause points at the new proposal, not the old statement of work.

Don't stretch a project contract into a retainer by email. The revenue you're building there is the most valuable revenue your agency has, and it deserves its own paper.

The Agency Retainer Agreement Template (Ungated)

An agency retainer agreement has twelve clauses: parties, scope, term, fee and payment, capacity and rollover, change requests, client responsibilities, termination and notice, renewal and price adjustment, intellectual property, confidentiality and liability, and governing law. Four of them, term, notice, renewal and IP, decide whether the revenue counts as recurring.

How to use it: what to copy, what to negotiate, what to leave to the lawyer

Copy all twelve clauses into a document and replace the bracketed fields. Clause 5 has two versions, one for deliverables and one for hours. Delete the one you're not using.

Negotiate clauses 3, 5, 8 and 9 with the client. Those are the business terms, and they're the ones this post is about. Have a lawyer read clauses 10 through 12 once, in your state, and then leave them alone.

Then reuse the same retainer agreement for every client. A founder I talked to had a couple of different iterations of his contract floating around, and had ended up running payments through Stripe links to keep it simple.

That's fine for getting paid. But it means nobody, including a future buyer, can tell what your standard terms are. One version, reused, is the asset.

One version, reused, is the asset.

The sample percentages and day counts below are common defaults, not recommendations. Your lawyer and your market will move them. And again, this is a template, not legal advice.

The template

All twelve clauses as plain text. Paste into a doc, fill the brackets, delete the clause 5 version you're not using.

The twelve clauses

1. Parties and effective date.

This Retainer Agreement ("Agreement") is made on [date] between [Agency legal name], a [state] [entity type] ("Agency"), and [Client legal name], a [state] [entity type] ("Client"). The Agreement takes effect on [effective date].

2. Services and scope.

Agency will provide the services described in the Scope Summary attached as Exhibit A, which reflects the proposal dated [date] and accepted by Client on [date]. Work not listed in Exhibit A is out of scope, including [name two or three things clients commonly assume are included, such as paid media spend, new site builds, or on-site meetings]. Out-of-scope work is handled under Clause 6.

3. Term.

The initial term is [12] months from the effective date. After the initial term, the Agreement continues month to month until ended under Clause 8 or renewed under Clause 9.

For a first engagement with a client you don't know, six months is a reasonable initial term. Anything shorter is a project with a monthly invoice.

4. Retainer fee and payment.

Client will pay Agency a monthly retainer fee of $[amount]. Agency invoices on the first business day of each month, and payment is due within [15] days. Client will keep a valid credit card or ACH authorization on file. Late payments accrue interest at [1.5] percent per month after [10] days past due. Agency may pause work after [30] days past due and resume when the account is current.

The fee itself is set in the proposal, not here. How to price a retainer, and what goes into the number, is on the proposal template. The agreement just records the number the client already agreed to.

5. Capacity and rollover.

Deliverables version:

Each month, Agency will deliver the outputs listed in Exhibit A within the response windows stated there. Deliverables not requested by Client in a given month do not carry forward to later months.

Hours version:

The monthly fee covers up to [40] hours of Agency time. Hours not used in a month expire at month end and do not roll over. Where Client gives written notice before the month starts, up to [10] unused hours may carry into the following month, once. Work beyond the monthly cap is billed at $[rate] per hour and requires written approval under Clause 6.

6. Change requests and overage.

Requests outside Exhibit A are change requests. Agency will provide a written estimate within [3] business days. Work begins only after written approval from [Client approver name or title], and is invoiced with the next monthly retainer fee. [Agency approver name or title] is authorized to approve estimates for Agency.

7. Client responsibilities.

Client will provide access to the accounts, systems, materials and people Agency needs within [5] business days of request, will respond to requests for review or feedback within [5] business days, and will name one decision maker with authority to approve work. Delays caused by Client do not extend deadlines or reduce the monthly fee.

8. Termination and notice.

After the initial term, either party may end this Agreement with [60] days' written notice. Either party may end this Agreement for material breach if the breach is not cured within [10] days of written notice. On termination, Agency will deliver all completed and paid-for work, and Client will pay for work performed through the termination date. Prepaid fees for periods after termination will be refunded.

Thirty days is the floor. Sixty is normal. Ninety is what a prospective agency acquirer likes to see.

9. Renewal and price adjustment.

At the end of the initial term and each renewal term, this Agreement renews for a further [12] months unless either party gives written notice at least [60] days before the term ends. On each renewal, the monthly fee adjusts by [4] percent, or by the change in [named index], whichever is greater. Agency will confirm the adjusted fee in writing at least [60] days before renewal.

10. Intellectual property.

On full payment, Client owns the deliverables created for Client under this Agreement. Agency keeps ownership of its pre-existing materials, tools, methods, templates and code libraries ("Agency Materials") and grants Client a perpetual, non-exclusive license to use Agency Materials as part of the deliverables. Agency may reference the engagement and display non-confidential deliverables in its portfolio and case studies with Client's written approval, which will not be unreasonably withheld.

11. Confidentiality, non-solicitation and limitation of liability.

Each party will keep the other's non-public information confidential during the Agreement and for [2] years after. Neither party will solicit the other's employees or contractors for employment during the Agreement and for [12] months after. Agency's total liability under this Agreement is limited to the fees paid by Client in the [6] months before the claim. Neither party is liable for lost profits or indirect damages.

12. Governing law, disputes and signatures.

This Agreement is governed by the laws of [state]. Disputes will first go to mediation, then binding arbitration in [city], if mediation fails. This Agreement, with its exhibits, is the entire agreement between the parties and replaces prior discussions. Changes must be in writing and signed by both parties. Signatures delivered electronically are valid.

On the signatures. Electronic signatures are binding in the United States under the federal ESIGN Act and state UETA laws, so any e-signature tool works. Keep the countersigned copy next to the signed proposal. When a buyer asks for the contracts, that folder is the answer.

The Four Clauses a Buyer Reads Before Your Client Table

A prospective agency acquirer doesn't trust a retainer line until they've read the contracts behind it. Two agencies can each show $30,000 a month from a client and hold two different assets.

I call it repeat versus recurring. Repeat revenue is a client who keeps paying because they keep choosing to. Recurring revenue is a client who has agreed, in writing, to keep paying unless they take a specific step to stop. Same invoice, different value.

Repeat revenue

$30,000 a month, on a handshake

  • Month to month, no initial term
  • 30 days' notice, or none written down
  • Same price as the year you signed them
  • IP never put in writing
  • Every "one more thing" lands on the founder

What a buyer sees: revenue that can leave inside a quarter.

Recurring revenue

$30,000 a month, on paper

  • 12-month term, renews unless someone acts
  • 60 to 90 days' written notice
  • Fee steps up at every renewal
  • Client owns the work, agency keeps its methods
  • The clause answers the question before it's asked

What a buyer sees: a contract book they can underwrite.

Four clauses in the retainer agreement draw the line.

Term. Month to month is repeat revenue, whatever the spreadsheet says. Twelve months with a renewal clause is recurring. The founder at 85 percent recurring didn't get there by selling better than you. He papered it.

Month to month is repeat revenue, whatever the spreadsheet says.

Notice. Thirty days' notice means the revenue can vanish inside a quarter, which is exactly the timeframe a buyer models. Sixty to ninety days gives your agency, and anyone who buys it, time to replace a client before the gap hits.

This is also the fix for the client who's too big to lose. The client concentration post covers how a buyer reads that table. The short version is that a whale on ninety days' notice is a very different risk from a whale on thirty.

Renewal with a price escalator. An annual increase written into the agreement means your book doesn't age in place. Without it, the client you priced three years ago is still paying the price from three years ago, and a buyer opening your contracts can see it. A stated escalator doesn't make the revenue safe. It makes it more defensible, which is the honest claim.

IP. The client owns the work on payment. The agency keeps its methods and its templates. A buyer wants to know that the things your agency runs on belong to your agency, and that no client can walk off with them or claim them. Software agencies get this wrong in both directions, and I'll come back to that below.

So what's a retainer for an agency, in plain terms? It's an agreement where a client pays a fixed monthly fee for a defined set of services or capacity, on a set term, with renewal and notice rules both sides signed.

The valuation multiples post shows what recurring versus repeat does to the multiple. Here, the point is simpler. The four clauses are the difference between the two.

And here's the test you can run on your own agency this week. A founder told me all of his client signals were lagging ones. Do they pay their invoice on time, and do they renew their contract. He'd never seen those two numbers until he ran a survey.

You can see them today. Pull every retainer, and for each one write down two things: paid on time, and renewed on time.

If you can't answer the second one because the agreement has no term, you've found the clause to fix first.

The Relevance Engineering Program

The contract can make the revenue count. It can't make the client stay.

Clients renew because of the relationship and the judgment behind the work, and at most agencies both still live with the founder. The Program moves what makes your agency worth renewing out of your head and into positioning, offers and plays your team runs without you.

See if it's a fit

The Two Clauses That Stop You Arguing About Hours

A founder described his retainer work to me as hard to plan. One week a client would use the team for a big block of time, and the next week nothing. So every month ended in a conversation about hours, and every one of those conversations ran through him.

The vendor pages call this scope creep. It's the hours model. When a retainer agreement is defined by hours, every month produces a number to argue about, and the founder is the only person with the authority to settle it.

The vendor pages call this scope creep. It’s the hours model.

Compare that with a founder who runs managed services. His description was that you sign a contract, promise to do something, and do it. You're not arguing about hours, and you're not beholden to the client after every fifteen minutes.

That's clause 5, the deliverables version. The month is defined by what the client gets and how fast, not by the time it took.

Now, some agencies genuinely need the hours version. Development and support work often does.

The fix there is to make the hours version answer every question before it's asked. A cap. Expiry at month end. One exception, in writing, once. And an overage rate the client already agreed to when they signed.

When the client asks for more, the account lead reads the clause instead of calling you.

Clause 6 finishes the job. Change requests get a written estimate and a named approver on both sides. The agency's approver is not the founder. If your name is in that blank, the agreement is still routing every decision through you, and you'll feel it the first month a client gets busy.

Curious if this applies to you? Think about who answered the last "can we squeeze in one more thing" question at your agency. If it was you, the agreement isn't doing its job yet. The retainer versus project economics post goes deeper on why the deliverables model holds margin and the hours model leaks it.

One honest caveat. A founder I talked to sells blocks of hours on purpose. His clients buy a sprint, use it up, and choose whether to continue, and he likes that it's a low-commitment way to test his agency.

That's a fine way to start a relationship. Just call it what it is, which is a project with a monthly invoice, and move the client onto a real retainer agreement once they've decided to stay.

Five questions

Does your retainer revenue count as recurring?

Answer for your typical retainer client, not your best one.

1. What's the term?

2. How much notice does a client owe you to leave?

3. When does the fee go up?

4. Who owns what?

5. Who answered the last "can we squeeze in one more thing"?

What Changes for a Marketing, Creative, Advertising, or Development Agency

The twelve clauses of the retainer agreement hold for every kind of agency. What changes is which clause carries the risk.

Marketing and advertising

The risk is in clause 4 and clause 10

Media spend passes through you. Add a line to clause 4 separating the retainer fee from ad spend, and a line to clause 10 saying the ad accounts sit in the client's name and stay with the client at termination.

Reporting cadence belongs in the scope exhibit, not in the agreement.

Creative

The IP clause splits in two

Who owns the asset, and who can use it where. Add revision rounds per deliverable to the scope exhibit, and a usage-rights line to clause 10 that names the channels and the term.

Portfolio rights matter more here than anywhere else, so keep the approval language.

Development and software

Answer the ransom fear in writing

A founder told me plenty of software agencies hold their clients ransom: they keep the code, they keep the infrastructure, and it all sits under the agency's name because of some small gotcha in the contract. He said it was all too common.

Repository ownership in the client's name, hosting accounts in the client's name, source delivered on payment, and no clause anywhere that says otherwise. Reference any maintenance SLA from a separate schedule.

Consultancies and strategy

Define the cadence, not the hours

Your deliverable is judgment. Calls, reviews, written recommendations, and the response window for each.

Keep clause 10 tight on your methods, because your methods are the agency.

The Next Step

Most founders reading this already know the real problem. It isn't the contract. It's that the reputation, the relationships, and the judgment that make your agency worth hiring still live in your head. So the business only grows when you're in the room.

That's the work we do at Haus Advisors. The Relevance Engineering Program is six months of implementation, not a strategy document. We pull what makes your agency relevant out of your head, build it into positioning, offers, and growth plays your team can run, and hand ownership to them. If you want an agency that grows without needing you in every deal, book a call to see if it's a fit.

If you want to see which of the six growth pillars still runs through you, the Bottleneck Score takes about five minutes.

Previous
Previous

The Agency Revenue Per Employee Benchmark (And the 20-Person Wall)

Next
Next

Client Concentration Risk Is a Demand Problem, Not a Diversification Problem