Agency SOPs: From Client Onboarding to QBRs

Agencies sell expertise, but they deliver process. The client buys a strategy or a creative team; what they experience is a kickoff, a sequence of drafts and approvals, a monthly report and a review every quarter. When those steps depend on which account manager they got, client experience varies, and so does retention.

Agency SOPs are the written procedures an agency follows across the client lifecycle: the handoff from sales, onboarding and kickoff, production and approvals, reporting, quarterly reviews, renewals and offboarding. They make the client experience consistent regardless of who is on the account, and they let the agency grow without every new hire learning by trial and error on a live client.

This guide covers the SOPs an agency needs, what goes in each, the order to write them and where they tend to break.

Map agency SOPs to the business pillars

Organize SOPs by the stage of the client relationship. SOPCompass puts every workspace into Company plus five pillars, and they fit an agency closely:

• Company: handbook, tool stack, brand standards, team onboarding.
• Lead Acquisition: your own marketing, referrals, partnerships, inbound handling.
• Lead Nurture: follow-up, discovery calls, audits and pitches.
• Sales Execution: proposals, scoping, pricing, contracts.
• Fulfillment & Delivery: onboarding, kickoff, production, approvals, reporting.
• Retention: QBRs, renewals, upsells, referrals and offboarding.

The order to write them

1. Sales to onboarding handoff. The most common source of early client friction.
2. Client onboarding and kickoff. Sets expectations for the whole engagement.
3. Approvals. The step where timelines slip and scope creeps.
4. Production. So work moves the same way through every team.
5. Reporting. Monthly, visible to the client, and easy to do inconsistently.
6. QBRs and renewals. Your main retention levers.
7. Offboarding. Rare, but it shapes whether a client comes back or refers you.

The sales to onboarding handoff

This SOP closes the gap between what sales promised and what delivery knows. Define a handoff document that must be complete before an account manager takes over:

• Signed scope, deliverables and timeline, with anything unusual called out.
• The client’s goals in their own words and how they will judge success.
• Stakeholders: decision maker, day-to-day contact, approvers.
• Anything promised verbally in the sales process.
• Budget, billing terms and start date.
• Risks sales noticed: tight deadlines, a previous agency relationship that ended badly, internal politics.

End with a short internal handoff call. Common failure point: the handoff is a forwarded email thread. Require the document, not the thread.

Client onboarding and kickoff

Onboarding covers the admin before the work starts: welcome email, access requests (ad accounts, analytics, website, brand assets, social accounts), setting up the project in your tools, the communication channel and meeting cadence, and the billing setup. Use a checklist, because missing access is the most common reason week one stalls.

Kickoff is the first working meeting. Document the agenda: introductions and roles, goals and success measures, timeline and milestones, how approvals work, how and when you report, and what you need from the client. Send a written summary within a day.

Take Beacon Studio, an invented coaching and agency business in our coaching and agency example. It documents client onboarding as SOPs alongside its client-facing method, a 30-day audit written phase by phase so it is delivered the same way for every client. The client onboarding SOP template is a good starting structure for your own.

Content and campaign production

Production SOPs should describe how work moves from brief to delivery:

• The brief: what it must contain before work starts.
• Stages: draft, internal review, client review, revisions, final.
• Who reviews internally, against what standard (brand guidelines, a QA checklist).
• Revision limits from the scope, and what happens when a client asks for more.
• File naming, storage and handover.
• For campaigns: launch checklist, tracking and a post-launch check.

Write one SOP per repeatable deliverable type (blog post, ad campaign, email campaign, social calendar, landing page) rather than one giant production SOP. For screen-heavy steps in ad platforms or project tools, add screenshots at the points where people usually get lost. Our guide on how to document business processes covers how much detail each step needs.

Client approvals

Approvals deserve their own SOP because they cause most of the delays. Cover:

• How work is presented for approval, and in which tool.
• Who at the client can approve, and what happens when a second stakeholder appears late.
• Turnaround expectations for the client, and what happens to the timeline when feedback is late.
• How feedback is consolidated, so you are not reconciling five conflicting comments.
• What counts as a revision versus a change in scope, and how a change in scope is raised.

Common failure point: approval by silence. Decide whether no response means approved or blocked, and say so at kickoff.

Reporting

Monthly reports should read the same whoever builds them. Document:

• Data sources and how each is pulled.
• The report template and which metrics go in it for each service.
• A plain-language summary: what happened, why and what you are doing next.
• Internal review before it goes out.
• The delivery date and format.

Tie metrics to the goals captured at handoff. A report that does not mention the client’s own success measures invites the question of what they are paying for.

Quarterly business reviews and renewals

A QBR SOP covers preparation (results against goals, work delivered, what did not go to plan), the agenda, the forward plan for next quarter, and follow-up. Include the questions you ask about the client’s business, since that is where upsell and renewal conversations start naturally.

The renewal SOP sets when the conversation starts before contract end, who leads it, what gets reviewed, how pricing changes are proposed and approved, and what happens if the client does not respond.

Client offboarding

When a client leaves, a clean exit protects your reputation. Cover:

• Confirming end date and final deliverables.
• Handing over files, accounts and credentials; removing your own access.
• Final invoice and any outstanding work.
• An exit conversation to learn why, recorded where the team can see it.
• Whether and when to ask for a testimonial or referral from a client who is leaving on good terms.

Contract terms around notice periods, ownership of work and data vary; check your agreements rather than writing assumptions into the SOP.

Where agency SOPs go wrong

• Written for the founder, not the team. SOPs that assume knowledge only the founder has will not work for a new account manager.
• One SOP per client. That multiplies fast. Keep the method generic and client details in the brief.
• Out of date after a tool change. When you switch project or reporting tools, update every SOP that references them.
• Never assigned. New hires told to “read the wiki” rarely do. Assigning specific SOPs with due dates turns onboarding into a list that can be finished.

If a client or freelancer needs one procedure, like how your approval process works, share that single SOP with a read-only link that expires instead of giving them access to everything.

Start from a template

Our marketing agency SOP templates give you a starting structure for onboarding, production and reporting. Start with the handoff and onboarding SOPs, and have your newest account manager test them on the next client that signs.