peterbamuhigire/playbook-client-retainer-management

Playbook: Client Retainer Management

A practical operating guide for managing retainer-based client relationships. Scope creep, communication breakdown, and poor renewal handling are the three leading causes of retainer loss. This playbook prevents all three.

Cross-reference: biz-dev-proposal (scope definition at proposal stage), playbook-agency-operations (team-level processes), playbook-daily-operations-routine (day-to-day execution discipline).

---

<!-- dual-compat:start -->

Use when

• Generates scope management documentation and scripted protocols for consultants and agencies managing ongoing client retainer agreements. Covers scope definition, scope creep prevention, change request handling, monthly check-in structure, performance review triggers, and retainer renewal. Invoke when setting up a new retainer agreement, when a client starts requesting work outside the agreed scope, when a retainer is approaching renewal, or when a client relationship is deteriorating and needs a structured reset.
• Use this skill when it is the closest match to the requested deliverable or workflow.

Do not use when

• Do not use this skill for graphic design, video production, software development, or legal advice beyond the repository's stated scope.
• Do not use it when another skill in this repository is clearly more specific to the requested deliverable.

Workflow

1. Collect the required inputs or source material before drafting, unless this skill explicitly generates the intake itself.
2. Follow the section order and decision rules in this SKILL.md; do not skip mandatory steps or required fields.
3. Review the draft against the quality criteria, then deliver the final output in markdown unless the skill specifies another format.

Anti-Patterns

• Do not invent client facts, performance data, budgets, or approvals that were not provided or clearly inferred from evidence.
• Do not skip required inputs, mandatory sections, or quality checks just to make the output shorter.
• Do not drift into out-of-scope work such as code implementation, design production, or unsupported legal conclusions.

Outputs

• A structured markdown document, plan, playbook, or strategy ready for client-facing or internal use.

References

• Use the inline instructions in this skill now. If a references/ directory is added later, treat its files as the deeper source material and keep this SKILL.md execution-focused.

<!-- dual-compat:end -->

Required Input

Before generating any output, ask for the following:

1. Client name and industry — who is this retainer for?
2. Retainer start date and end date — when does the current agreement run?
3. Current deliverables — what is explicitly in scope (list every deliverable)?
4. Primary pain point — select one: scope creep / non-communication / pricing disputes / renewal negotiation
5. Relationship health — select one: good / strained / crisis

Use these inputs to tailor the output to the specific situation. If the relationship is strained or in crisis, prioritise Sections 5 and the reset conversation script. If the retainer end date is within six weeks, prioritise Section 6.

---

Section 1: Defining Scope Before Work Begins

Scope creep starts before the contract is signed — when the scope is vague. Prevent it at the proposal stage (see biz-dev-proposal).

A complete retainer scope definition includes six named elements:

1. Deliverables List

Name every deliverable with a quantity. Vague language creates disputes.

• Good: "5 Instagram posts per week, 1 Facebook post per day, 1 monthly report, 1 strategy review call per quarter."
• Avoid: "social media management."

2. Platform List

Name each platform explicitly. Any platform not listed is out of scope by default. Do not write "and other platforms as agreed" — this invites scope creep.

3. Revision Rounds

State how many rounds of revisions are included per deliverable. Standard is two rounds. Round three is a change request and is billed separately.

4. Response Time

Define community management hours precisely: "Respond to comments and DMs Monday–Friday, 8am–6pm EAT within 2 hours." Out-of-hours response is not included unless explicitly stated and priced.

5. Approval Process

State how long the client has to approve content before publication. Recommended: 24 hours. State what happens if the client does not reply — standard position is that the consultant publishes after 24 hours, unless the client opts for a mandatory-approval process (which must then be reflected in the timeline).

6. Exclusions

Name what is NOT included. Common exclusions:

• Paid advertising management (bidding, targeting, creative testing)
• Graphic design beyond approved templates
• Video production or video editing
• PR outreach or media relations
• Website updates or web development
• Photography or event coverage

---

Section 2: Scope Creep Recognition

Scope creep is any work requested that is not in the deliverables list. Recognise it early — the longer it goes unaddressed, the harder it is to correct.

Common scope creep requests in the East African context:

| Request Type | Example | Response | |---|---|---| | Platform add-on | "Can you also manage our TikTok?" | Change request: quote additional fee | | Volume increase | "Can we do 2 extra posts this week for the promotion?" | Change request: quote fee or defer to next month | | New service | "Can you design our new flyer?" | Decline politely; graphic design is out of scope | | Urgent out-of-hours | "Can you post this now? It's 9pm." | Remind of working hours; schedule for first thing tomorrow | | Reporting expansion | "Can you add more detail to the monthly report?" | Accommodate once; add to scope at renewal | | Ad-hoc strategy calls | "Can we have a quick call?" | Count against the quarterly call inclusion; additional calls are billable | | Translation request | "Can you do a version in Luganda?" | Change request if only English was agreed in scope |

EA-specific patterns to watch for:

• WhatsApp messages requesting "quick things" that accumulate into significant unbilled work across the month
• Clients adding family members or colleagues to the content approval chain without prior discussion — this extends turnaround times and creates conflicting feedback
• Requests for content in Luganda or Swahili when the agreed scope specified English only
• New campaigns added mid-month without a conversation about capacity or additional cost
• Clients sharing competitor content in a group chat with an implied expectation to replicate it

---

Section 3: Change Request Protocol

When a request falls outside the agreed scope, use this protocol consistently. Consistency is what distinguishes a professional agency from a freelancer who says yes to everything and then resents it.

Step 1: Acknowledge the request positively

Never make the client feel wrong for asking. Acknowledge the idea, then redirect.

Script (WhatsApp or email):

"Thanks for the idea — I think this could work really well. This falls outside our current agreement, but I'd be happy to add it. The additional cost would be [UGX X] for [deliverable]. Would you like me to go ahead, or shall we include this in the renewal next month?"

Step 2: Never say the following

• "That's not in my job description." — sounds defensive and damages the relationship.
• "You're asking too much." — unprofessional and accusatory.
• "I'll do it this once." — sets the precedent that extra work is free, and the client will ask again.

Step 3: Document every approved change request in writing

Confirm via WhatsApp message after verbal agreement. Maintain a running log:

| Date | Request | Status | Agreed Fee | Notes | |---|---|---|---|---| | [Date] | TikTok management (3 posts/week) | Approved | UGX 350,000/month | Starts Month 4 | | [Date] | Extra posts for Eid campaign (4 posts) | Approved | UGX 80,000 one-off | Published 9 April |

Keep this log as a living document. Reference it at the monthly check-in and at renewal.

---

Section 4: Monthly Check-In Structure

A structured monthly check-in prevents relationship drift and gives scope issues a formal channel — so they do not accumulate as WhatsApp grievances.

Monthly check-in agenda (30 minutes maximum):

| Time | Agenda Item | Purpose | |---|---|---| | 0–10 min | Results review | Walk through the monthly report; name 1 win and 1 area for improvement | | 10–20 min | Client priorities | "What's your biggest business focus next month? Any campaigns, events, or launches?" | | 20–25 min | Scope review | "We've been delivering [X]. Is there anything you'd like to adjust for next month?" | | 25–30 min | Action items | Agree on 2–3 specific actions; confirm who owns each |

Format guidance:

• In-person or WhatsApp call preferred in EA — email check-ins are frequently ignored or deprioritised.
• Send a WhatsApp voice note summary immediately after the call to confirm what was agreed. This creates a record without requiring the client to read a formal document.
• If the client cancels the check-in twice in a row, treat this as a non-communication trigger (see Section 5).

---

Section 5: Performance Review Triggers

These situations require an unscheduled review conversation. Do not wait for the next monthly check-in — early action protects both the client relationship and the retainer.

| Trigger | Action | |---|---| | Primary metric (enquiries/leads) drops for 2 consecutive months | Request an emergency strategy review; proactively surface the issue before the client raises it | | Client posts content outside the agreed approval process | Clarify the process in writing immediately; risks include inconsistent brand voice and content conflicts | | Client is unresponsive for 2 or more weeks | Send a formal review request via WhatsApp and email; unresponsiveness is a retainer risk and must be named | | Client requests a price reduction without proposing a scope reduction | Prepare a counter-proposal pairing the reduced price with a corresponding reduction in deliverables | | Client relationship feels adversarial or mistrustful | Request a reset meeting; name the dynamic professionally without blame |

Reset meeting script:

"I want to make sure we're working well together — I think there may be some things worth discussing openly. Can we schedule 30 minutes to do a relationship check-in? I want to make sure this retainer is working for both of us."

Name the dynamic professionally. Avoidance makes adversarial relationships worse.

---

Section 6: Retainer Renewal

Renewals must be initiated six weeks before the retainer end date. Raising renewal at the last minute signals poor planning and weakens the consultant's negotiating position.

Renewal Preparation (4 Weeks Before End Date)

Complete these four steps before the renewal conversation:

1. Compile results for the full period. Pull primary metric trends, campaign highlights, and wins. Frame these as outcomes for the client's business, not as a list of tasks completed.

2. Identify scope additions to propose. What new services would benefit this client in the next period? This is the expansion opportunity.

3. Identify low-value deliverables. What has been in scope but produced little demonstrable result? Propose adjusting or replacing these — this demonstrates strategic thinking, not just execution.

4. Prepare a revised proposal. Updated scope, updated pricing, clear rationale. Use biz-dev-proposal to generate the formal document.

Pricing at Renewal

An annual price increase of 10–20% for active retainers is standard and should be communicated six weeks in advance, not on the day of renewal.

Frame the increase in terms of results and forward value:

"Over the past year we've achieved [result]. For next year, the investment will be [new price], which includes [new addition or quality improvement]. I've put together a proposal — can we schedule 30 minutes to go through it?"

Do not apologise for the increase. A price increase tied to demonstrated results is professional and justified.

Renewal Conversation Script

"I'd love to continue working together. I've put together a review of what we've achieved this year and a proposal for next year. Can we schedule 30 minutes to go through it?"

Schedule the meeting before sending the proposal document. A proposal sent without a conversation is easier to decline.

If the Client Does Not Renew

Handle the offboarding professionally. East African professional communities are small — word travels.

1. Complete all contracted deliverables through the final day of the retainer period. Do not scale back effort because the relationship is ending.

2. Hand over all assets within five working days of the final date: content files, brand assets, login credentials (where held), strategy documents, and reports.

3. Send a formal offboarding message:

   "It's been a pleasure working with you. Attached is everything you'll need for a smooth handover. Please don't hesitate to reach out if you have any questions during the transition."

4. Do not speak negatively about the client in professional circles.

5. Log the experience: what worked, what did not, what to change in the next retainer agreement. Use this to improve the scope definition at the next proposal stage.

---

Quality Criteria

Output from this skill meets the standard when:

• The scope definition checklist covers all six named elements: deliverables, platforms, revision rounds, response time, approval process, and exclusions
• The scope creep table lists at least six common EA request types, each with a specific scripted or recommended response
• The change request protocol includes a word-for-word script that is positive in tone and professionally firm on boundaries
• The monthly check-in is structured as a timed 30-minute agenda with four named segments and a clear purpose for each
• Performance review triggers are defined as specific, observable signals with specific named actions — not general advice
• Renewal preparation is framed as a six-week process, not a last-minute conversation
• The offboarding process is included for non-renewals, with a word-for-word handover message and a five-working-day asset handover deadline