TL;DR: Retainer clients churn because they can't see the work, not because the work is bad. A monthly retainer report makes the work visible. The 6-section structure below takes 25 minutes to write, ships by the 5th of every month, and is the single highest-leverage habit for protecting retainer revenue. Skip it and you lose retainers around month four for "no clear reason."
Month 4 of a $2,400/month retainer. Slack message at 9:17 AM: "Hey, we've been thinking about the retainer. Can we hop on a call this week? Trying to figure out what we're actually getting for our $2,400." You stare at the screen. You know you did good work. You shipped two landing pages, fixed a checkout bug, ran three rounds of A/B tests. You just didn't write any of it down where the client could see it. To them, the month was silence. To you, it was 22 hours of value. Both things are true, and only one of them matters at renewal.
I'm Sammie Oku, founder of Eximius Studio, a web design and dev agency in Tyler, TX. The retainer above is the one that taught me this lesson. After I rebuilt the relationship around a monthly report, the client renewed for a second year and added an SEO scope. The work didn't change. The visibility did.
This post is the monthly retainer report template I send every retainer client, plus the structure, the cadence, and the exact sections that build renewal trust.
For the bigger picture, how to run a web design agency covers the seven systems this fits inside. Retainer reporting is System 5. This is the full playbook for the reporting piece.
Why retainer churn usually happens around month 4
Retainer relationships follow a predictable arc. Month 1 is honeymoon: deposit cleared, kickoff happened, energy is high. Months 2 and 3 are delivery: real work shipped, client is busy with their own job, communication is mostly transactional. Month 4 is the audit. The client looks at their P&L, sees a recurring $X line item, and starts asking whether the value matches the spend.
If they have evidence of value in front of them, the answer is obvious. If they don't, the answer becomes a question they ask on a Slack call.
The average agency retainer is under $5,000 per month (Promethean Research) and 47% of clients churn within the first 90 days (Agency Simplifier). The math is harsh: lose a $4,000/month retainer at month 4 and you've earned $16,000 instead of the $48,000 a full year would have been. Two churned retainers a year, you're down $64,000.
The fix is not more communication. The fix is structured monthly evidence. Same evidence, same format, same date, every month. The client never has to ask.
The 6 sections every retainer report needs
A retainer report is not a status update and it is not a comprehensive document. It's a one-page summary that answers six questions the client has whether they ask them or not.
Section 1: Executive summary (the part the CEO reads). Three sentences max. What was the headline result this month, what's at risk, what's coming next month.
Section 2: Hours / scope consumed vs. contracted. A simple comparison. You contracted for 20 hours, you used 18, here's where they went.
Section 3: What we shipped this month. Specific deliverables, named, with links or screenshots where applicable.
Section 4: What's planned next month. Forward visibility so the client knows what they're paying for next.
Section 5: Strategic recommendations. One or two ideas that came out of the month's work. Not upsells. Genuine recommendations.
Section 6: Outstanding decisions or blockers. What you need from them to keep moving.
That's the whole report. Six sections, one page. Anyone who reads it should be able to answer "is this retainer worth it?" in under 90 seconds.
Section 1: Executive summary
This is the only section the CEO will read. Optimize for that.
The template:
"In [Month], we delivered [headline outcome or shipped work]. [Specific result or metric, if available]. Looking ahead, [one-sentence preview of next month]."
Example:
"In May, we shipped two landing pages for your spring campaign and improved checkout conversion from 2.1% to 2.6% through three A/B tests. Combined, those changes are projected to add ~$8,400 in monthly revenue at current traffic. Looking ahead, June focuses on mobile checkout optimization and a homepage hero refresh."
Three sentences. Headline, evidence, forward look. Done.
A bad executive summary is vague: "We did some great work this month and we're excited for next month." That sentence is a confidence killer. Specifics build trust. Generalities erode it.
Section 2: Hours / scope consumed vs. contracted
Transparency on hours matters even when the client isn't asking. It teaches them what they're paying for and creates the foundation for the "use-it-or-lose-it" conversation if hours go unused.
A simple table works:
| Category | Contracted | Used | Remaining |
|---|---|---|---|
| Design hours | 12 | 11 | 1 |
| Development hours | 8 | 7 | 1 |
| Strategy / review | 2 | 2 | 0 |
| Total | 22 | 20 | 2 |
Add a one-line note if hours were over or under: "Hours used came in slightly under this month due to the holiday week. Per the retainer agreement, unused hours do not roll over."
That last sentence is critical. Reinforce the use-it-or-lose-it policy in writing every single month. By month four, it's been said in the contract, repeated at the kickoff, and stated in every monthly report. No client can claim surprise.
If the retainer is deliverables-based instead of hours-based, replace the hours table with a deliverables table:
| Deliverable | Planned | Delivered |
|---|---|---|
| Landing pages | 2 | 2 |
| Blog post designs | 4 | 4 |
| Monthly performance review | 1 | 1 |
| Strategy call | 1 | 1 |
Section 3: What we shipped this month
This is the longest section by line count but should still fit in half a page. Format as a bulleted list, each bullet 1 to 2 sentences, with links or screenshots where the work is reviewable.
Example structure:
- Spring campaign landing page (shipped May 8): Built a new product launch page with hero video, three feature blocks, and CTA section. Live at yoursite.com/spring. Conversion rate at first 1,000 visitors: 4.2%.
- Checkout optimization (shipped May 14): Reduced checkout form from 11 fields to 7. Conversion improved from 2.1% to 2.6% over a 14-day test window.
- Mobile nav fix (shipped May 19): Resolved a layout issue on iOS Safari that was hiding the menu button on iPhone 12 and earlier.
- Email signup form A/B test (May 22 to May 31): Variant B (single-field) outperformed Variant A (two-field) by 18%. Variant B is now live.
Every bullet has a specific deliverable, a date, and a result or location where the work can be seen. Nothing vague. No "various small improvements." If it can't be specified, it shouldn't be in the report. Approved Change Orders shipped this month also belong here, called out as such so the client sees the extra value they paid for.
Section 4: What's planned next month
Forward visibility is the section most agencies skip. It's also the section that prevents the "what are we paying for" question, because the client always knows what's coming.
Three to five planned items, written in the same specific format as Section 3:
- Mobile checkout flow rebuild (planned ship: June 12): Redesigning the three-step mobile checkout to single-page based on May's session recordings.
- Homepage hero refresh (planned ship: June 19): Replacing the static hero image with a new short-form video and updated headline based on positioning workshop notes.
- Blog post template update (planned ship: June 26): Adding a related-posts module and a reading-progress bar to improve session duration.
- Monthly strategy review call (scheduled June 28): Quarterly review of conversion metrics and Q3 priorities.
If a planned item depends on the client (waiting on copy, approvals, assets), flag it inline: "[Dependent on receiving updated brand photography by June 5]." This sets expectation and protects you if delays happen.
Section 5: Strategic recommendations
One or two recommendations per month. Not upsells. Genuine suggestions that show you're thinking about their business beyond the immediate work.
Example:
"Recommendation: Add product schema markup to category pages. Based on Google Search Console data, your category pages are getting decent impressions but low CTR. Adding structured data could lift CTR by an estimated 8 to 15% with minimal dev effort. I'd estimate 4 to 6 hours, which fits inside next month's retainer. Want me to add it to June's plan?"
This recommendation does four things at once. It demonstrates you're paying attention to data the client may not be looking at. It connects to a measurable outcome. It scopes the effort. And it asks for a decision so the client feels in control.
Two rules for recommendations. First, they should always be inside the retainer scope, not pitched as add-ons. Add-ons feel like sales. Recommendations feel like advice. Second, alternate the type: one month it's a technical fix, next month a design improvement, the month after a strategic shift. Variety signals you're seeing the whole business, not running one playbook.
Section 6: Outstanding decisions or blockers
The last section. What you need from the client to keep moving.
Format as a short list with deadlines:
- Decision needed: Final approval on the June homepage hero direction. Deadline: June 7 to keep planned ship date.
- Asset needed: Updated product photography for the mobile checkout rebuild. Deadline: June 5.
- Access needed: Admin access to Klaviyo to set up the post-purchase email automation.
If there are no outstanding items, write: "Nothing outstanding from your side this month. We're set to proceed." Don't skip the section. Its existence reassures the client that you always tell them what you need.
Cadence: when to send, how to send
Send by the 5th of the following month. Every month. Set a recurring calendar reminder. The consistency is more important than the date itself. A report that arrives on the 5th every month is more valuable than a report that arrives on the 1st sometimes and the 12th other times. This is one of the most important agency SOPs to write down because the discipline lives or dies on whether the cadence is documented.
Format: PDF or shared Notion page. PDF is more polished. Notion is more flexible and lets clients comment inline. Both work. Pick one and stick with it.
Delivery: email with a brief cover note. Don't drop the report cold. Wrap it in a two-sentence email:
"Hi [name], May report attached. Quick summary: checkout conversion is up to 2.6% and we shipped both planned landing pages. Outstanding from your side: I need updated product photography by June 5 to stay on schedule. Let me know if you have any questions."
That email is the most-read piece of communication of your entire month with that client. Make it count.
Time required to write the report: 25 minutes if you've logged work consistently throughout the month. 2+ hours if you're reconstructing from memory. The difference is whether you've built the habit of logging deliverables in real time or only at month-end. The Time Entries database in agency project management in Notion is the spine that makes 25-minute reports possible.
Building this from scratch is slow. The full monthly report template, the hours-logging database it pulls from, and the recommendation tracker are inside Agency Operations OS. Deploys in an afternoon, $79. Link at the end.
What to leave out of the report
Equal in importance to what to include.
Don't include internal complications. "We had some technical issues with the staging server" is not the client's problem. They paid for outcomes, not for your operational hiccups.
Don't include process detail. "We held a sprint planning meeting and assigned tickets in Linear" is meaningless to a non-technical client. They want to know what shipped, not how it shipped.
Don't include hours by team member. It's too granular and invites "why did the developer spend 4 hours on that?" conversations. Aggregate hours by category, not by person.
Don't include disclaimers or apologies. "Sorry we didn't ship X this month" undermines confidence. If something slipped, name the new ship date in Section 4 and move on. No grovel.
Don't pad. A two-page report is worse than a one-page report. If you're padding to look busy, you've already lost.
How to use the report at renewal
Three months before the retainer renewal date, the monthly reports become renewal evidence. Save every one. At renewal, send a short summary that aggregates:
- Total hours delivered across the engagement
- Major deliverables shipped (top 5 to 7 across the entire term)
- Measurable outcomes (conversion lifts, revenue impact, traffic growth)
- Strategic recommendations implemented vs. pending
- Forward roadmap if the retainer renews
That summary is built from the monthly reports you've already written. No extra work, just compilation. The renewal conversation goes from "we should probably renew this" to "here's the documented case for renewal." Renewal rate goes up. Renegotiation pressure goes down.
If you also enforce the retainer agreement clauses that protect rate increases (annual 5% built-in escalator, written renewal notice required), the renewal becomes mechanical. The monthly reports do most of the selling.
What to do when the client cancels anyway
Sometimes a client cancels despite excellent reporting. Usually for reasons outside your control: budget cuts, internal restructure, new CMO who wants their own agency. When this happens, the monthly reports become your reference for the offboarding handoff and your case study material for future pitches.
Two specific moves. First, ask for a testimonial while the relationship is still warm: "We've appreciated working with you. Would you be open to a short testimonial we could use on our site?" Most departing clients will say yes if asked within two weeks of cancellation. Second, archive the reports as a case study. The aggregated outcomes ("we lifted conversion 24% over 8 months") become evidence in your next pitch.
The agency margin leak numbers post covers the financial side of retainer churn and the metrics to watch so you see cancellations coming before they happen.
Frequently asked questions
What should be included in a monthly retainer report?
Six sections: executive summary (3 sentences), hours/scope consumed vs. contracted, what was shipped this month (with links or screenshots), what's planned next month, one or two strategic recommendations, and outstanding decisions or blockers the client owes you. Keep it to one page. Include specifics with dates and measurable outcomes wherever possible. Skip internal process detail, hours by team member, and apologies.
How often should I send retainer reports?
Monthly, by the 5th of the following month, every month. Consistency matters more than the specific date. Some agencies layer in a weekly status email and a quarterly strategic review on top of the monthly report. For retainers under $5,000/month, monthly alone is enough. For retainers over $10,000/month, add quarterly business reviews. Daily or weekly reports are usually overkill and signal a transactional relationship rather than a strategic one.
How long should a retainer report be?
One page. Two pages maximum for retainers over $10,000/month. A 10-page report is not a report, it's a document the client won't read. The discipline of one page forces you to write the executive summary that matters and cut the process detail that doesn't. If your report doesn't fit on one page, the issue is the writing, not the work.
Should retainer reports include hours by team member?
No. Aggregate hours by category (design, development, strategy) instead. Hours by team member invites micro-management questions and isn't useful to most clients. The exception is enterprise engagements with formal billing requirements, where time tracking by person is contractually required. For the typical small agency retainer, category-level hours is the right granularity.
What should I do if a retainer client doesn't read the reports?
Keep sending them anyway. The report is not just for the current contact. It's evidence for renewal conversations, for procurement reviews, for the next CFO who'll evaluate the spend, and for any internal restructure. A report that exists and isn't read is still doing work. Continue the cadence. If you can confirm the current contact isn't engaging, find out who else internally should be receiving it.
The shortcut: Agency Operations OS
Writing the report is straightforward. Building the system that captures the work in real time, so the report takes 25 minutes instead of 2 hours, is the harder part.
Agency Operations OS is the Notion template I use to run Eximius Studio. It includes:
- 7 core databases: Leads, Deals, Projects, Retainers, Change Orders, Financials, AR Aging
- 5 dashboards: Weekly Owner Review, Pipeline, Active Projects, Retainer Health (with hours used, margin, and renewal dates per retainer), Margin by Client
- 15 SOPs including the full monthly reporting cadence, the renewal review process, and the work-logging discipline from this post
- 5 bonus docs: Master Services Agreement, Retainer Agreement (with monthly reporting requirement built in), Project Proposal template, Discovery Call script, and the 47-item Pre-Launch QA Checklist
One template, deploys in an afternoon, $79.
The structure above is the monthly retainer report template that's kept Eximius retainers renewing. Build the habit, ship by the 5th, watch the renewal conversations get easier.
For the broader retainer system, how to price a web design retainer covers the math, how to run a web design agency covers the seven systems this fits inside, and the best Notion templates for web design agencies compares the options that ship with retainer reporting built in.
